7 Replies Latest reply on Jun 4, 2007 2:55 AM by Mikhail Kolesnikov

    ERROR: [AbstractService] E_busy (10400)

    Mikhail Kolesnikov Newbie

      Some time I received the following error message:

      19:07:27,295 ERROR [AbstractService] E_busy (10400) The request cannot be processed at the current time. The Registry is currently unavailable.


      What can I do to prevetn this error message?

      To receive this message I'm trying to send about 6 messages per minute in 2 threads.
      See my test project here http://www.4shared.com/file/16574137/2784c172
      Need to import to eclipse anr run "RunComponents" than "PerfLoadTest" launchers.

        • 1. Re: ERROR: [AbstractService] E_busy (10400)
          Mark Little Master

          Maybe Kurt can answer this, because the error isn't something that's generated by the ESB code. Perhaps jUDDI/Scout?

          • 2. Re: ERROR: [AbstractService] E_busy (10400)
            Kurt Stam Master

            Yes it's something generated by jUDDI. So far I have not seen it causinfg any problems, but one of these days I will get a chance to take a closer look. It seems to only happen when connected over RMI, we recommend using a local transport (not rmi) in high volume situations.

            --Kurt

            • 3. Re: ERROR: [AbstractService] E_busy (10400)
              Mikhail Kolesnikov Newbie

               

              we recommend using a local transport (not rmi)

              I had change the transport like that
              <property name="org.jboss.soa.esb.scout.proxy.transportClass"
               value="org.apache.ws.scout.transport.LocalTransport"/>

              But I had receive such an error when trying to start ESB components:
              Caused by: org.jboss.soa.esb.services.registry.RegistryException: java.lang.ClassNotFoundException: /InquiryService
               at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.registerEPR(JAXRRegistryImpl.java:250)
               at org.jboss.soa.esb.listeners.RegistryUtil.register(RegistryUtil.java:138)
               at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:212)
               ... 9 more
              Caused by: javax.xml.registry.JAXRException: java.lang.ClassNotFoundException: /InquiryService
               at org.apache.ws.scout.registry.BusinessQueryManagerImpl.findClassificationSchemeByName(BusinessQueryManagerImpl.java:457)
               at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findService(JAXRRegistryImpl.java:460)
               at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.registerEPR(JAXRRegistryImpl.java:186)
               ... 11 more


              What else shall i change? May be all URL need to be changed to "localhost" instead of "localhost:1099" ???

              • 4. Re: ERROR: [AbstractService] E_busy (10400)
                Kurt Stam Master

                Try using this:


                <properties name="registry">
                <property name="org.jboss.soa.esb.registry.queryManagerURI" value="org.apache.juddi.registry.local.InquiryService#inquire"/>
                <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" value="org.apache.juddi.registry.local.PublishService#publish"/>
                <property name="org.jboss.soa.esb.registry.implementationClass" value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
                <property name="org.jboss.soa.esb.registry.factoryClass" value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
                <property name="org.jboss.soa.esb.registry.user" value="jbossesb"/>
                <property name="org.jboss.soa.esb.registry.password" value="password"/>
                <!-- the following parameter is scout specific to set the type of communication between scout and the UDDI (embedded, rmi, soap) -->
                <property name="org.jboss.soa.esb.scout.proxy.transportClass" value="org.apache.ws.scout.transport.LocalTransport"/>
                </properties>


                and make sure you have the juddi.jar on your classpath

                • 5. Re: ERROR: [AbstractService] E_busy (10400)
                  Kurt Stam Master

                  trying again:

                  <properties name="registry">
                   <property name="org.jboss.soa.esb.registry.queryManagerURI" value="org.apache.juddi.registry.local.InquiryService#inquire"/>
                   <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" value="org.apache.juddi.registry.local.PublishService#publish"/>
                   <property name="org.jboss.soa.esb.registry.implementationClass" value="org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl"/>
                   <property name="org.jboss.soa.esb.registry.factoryClass" value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
                   <property name="org.jboss.soa.esb.registry.user" value="jbossesb"/>
                   <property name="org.jboss.soa.esb.registry.password" value="password"/>
                   <!-- the following parameter is scout specific to set the type of communication between scout and the UDDI (embedded, rmi, soap) -->
                   <property name="org.jboss.soa.esb.scout.proxy.transportClass" value="org.apache.ws.scout.transport.LocalTransport"/>
                   </properties>
                  


                  • 6. Re: ERROR: [AbstractService] E_busy (10400)
                    Mikhail Kolesnikov Newbie

                    Sorry, I forget to write additional message in this thread on friday.
                    I had already found that configuration (in helloworld_db_registration), but always bumped in such an error:

                    09:21:37,463 ERROR JDBCDataStore:88 - Exception occured while attempting to aquire a JDBC connection: socket creation error
                    java.sql.SQLException: socket creation error


                    I'm trying to change JDBC connection to DS one - but all in vain :(

                    • 7. Re: ERROR: [AbstractService] E_busy (10400)
                      Mikhail Kolesnikov Newbie

                      Oh! I had fully understoud my fault!

                      Local transport works only in one JVM - so it's impossible to send local messages between different JVM's!

                      Thread may be closed as I see, thank's a lot for Kurt!