Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-15729

Fix offline Connect registration from Admin

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.9.6-SNAPSHOT
    • Fix Version/s: 6.0
    • Component/s: Connect

      Description

      On tab Nuxeo Connect/registration, when trying to use the offline process, an error message "An empty response was received from the server. Check server error logs." is displayed in the UI.

      Server logs show the following error:

      Caused by: java.lang.IndexOutOfBoundsException: Index: 2, Size: 2
	at java.util.ArrayList.rangeCheck(ArrayList.java:635)
	at java.util.ArrayList.get(ArrayList.java:411)
	at org.nuxeo.connect.identity.LogicalInstanceIdentifier.load(LogicalInstanceIdentifier.java:203)
	at org.nuxeo.connect.identity.LogicalInstanceIdentifier.load(LogicalInstanceIdentifier.java:210)
	at org.nuxeo.connect.identity.LogicalInstanceIdentifier.instance(LogicalInstanceIdentifier.java:169)
	at org.nuxeo.connect.identity.LogicalInstanceIdentifier.isRegistered(LogicalInstanceIdentifier.java:239)
	at org.nuxeo.connect.connector.service.ConnectGatewayComponent.isInstanceRegistred(ConnectGatewayComponent.java:76)
	at org.nuxeo.connect.client.jsf.ConnectStatusActionBean.isRegistred(ConnectStatusActionBean.java:133)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
	at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:32)
	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
	at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)

      When such an error happens, it's not possible to get back to the registration tab, error is shown again, and logging in/out does not solve the issue, server needs to be restarted.

      This is because inclance clid is lacking a line for the description (workaround: add an extra line to the nxserver/data/instance.clid file)

        Attachments

          Issue Links

          is required by

          Bug - A problem which impairs or prevents the functions of the product. NXP-16034 Fix connect client failure when CLID isn't validated in admin center

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: