0 Replies Latest reply on Jun 24, 2009 8:46 AM by Marcus A.

    Timeout when using SOAP configuration

    Marcus A. Newbie

      Hi,

      I'm using jbossesb-server-4.5.GA. when I try to configure it to use the SOAP configuration, the server doesn't start any more. Using the Loglevel DEBUG I can see that the internal AvailabilityExecutor needs so much time that the overall timeout allowed for starting is reached. When I try the local configuration everything works fine. Here's the result of the console in debug modus.

      14:43:38,228 DEBUG [ServiceController] starting service jboss.esb:service=MessageStoreDatabaseInitializer
      14:43:38,228 DEBUG [DatabaseInitializer] Starting jboss.esb:service=MessageStoreDatabaseInitializer
      14:43:38,337 INFO [DatabaseInitializer] java:/JBossESBDS datasource is already initialized
      14:43:38,337 DEBUG [DatabaseInitializer] Started jboss.esb:service=MessageStoreDatabaseInitializer
      14:43:38,337 DEBUG [ServiceController] Starting dependent components for: jboss.esb:service=MessageStoreDatabaseInitializer dependent components: [ObjectName: jboss.esb:deployment=jbossesb.esb
      State: CREATED
      I Depend On:
      jboss.esb:service=MessageStoreDatabaseInitializer
      jboss.esb.destination:service=Queue,name=OperationsCollectorQueue
      jboss.esb.destination:service=Queue,name=DataCollectorQueue
      jboss.esb.destination:service=Queue,name=DeadMessageQueue
      jboss.jca:service=DataSourceBinding,name=JBossESBDS
      jboss.esb.destination:service=Queue,name=OperationsResultCollectorQueue
      ]
      14:43:38,337 DEBUG [ServiceController] starting service jboss.esb:deployment=jbossesb.esb
      14:43:38,337 DEBUG [JBoss4ESBDeployment] Starting jboss.esb:deployment=jbossesb.esb
      14:43:38,648 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000
      14:43:38,679 DEBUG [ListenerUtil] No value specified for message-selector attribute - All messages in queue <queue/OperationsResultCollectorQueue> will be picked up by listener
      14:43:38,679 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000
      14:43:38,679 DEBUG [ListenerUtil] No value specified for message-selector attribute - All messages in queue <queue/OperationsCollectorQueue> will be picked up by listener
      14:43:38,679 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000
      14:43:38,679 DEBUG [ListenerUtil] No value specified for message-selector attribute - All messages in queue <queue/DataCollectorQueue> will be picked up by listener
      14:43:38,679 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000
      14:43:38,679 DEBUG [ListenerUtil] No value specified for message-selector attribute - All messages in queue <queue/DeadMessageQueue> will be picked up by listener
      14:43:38,679 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000
      14:43:38,710 DEBUG [ActionProcessingPipeline] Using mep: OneWay, oneWay: true, defaultProcessing: false
      14:43:38,725 DEBUG [LifecycleResource] Creating resource using factory: org.jboss.soa.esb.listeners.message.ServiceMessageCounterLifecycleResource$LifecycleServiceMessageCounterFactory@1a4f2fd with identity ID-0
      14:43:38,725 DEBUG [ActionProcessingPipeline] Registering action class org.jboss.soa.esb.actions.MessageRedeliverer
      14:43:38,741 DEBUG [ActionProcessingPipeline] Using normal action pipeline processor for org.jboss.soa.esb.actions.MessageRedeliverer
      14:43:38,756 DEBUG [ActionProcessingPipeline] SecurityContextPropagator in use for service 'RedeliverService' is 'org.jboss.internal.soa.esb.services.security.JBossASContextPropagator'
      14:43:38,772 DEBUG [ConnectionManagerFactory] Going to load org.jboss.internal.soa.esb.persistence.manager.J2eeConnectionManager
      14:43:38,772 INFO [J2eeConnectionManager] initializing...
      14:43:38,788 DEBUG [MessageRedeliverer] MessagePersister started with classification=null and message-store-class=org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl@b2311b
      14:43:38,803 DEBUG [ActionProcessingPipeline] Using mep: OneWay, oneWay: true, defaultProcessing: false
      14:43:38,803 DEBUG [ActionProcessingPipeline] Registering action class org.jboss.soa.esb.monitoring.client.InvokerAction
      14:43:38,803 DEBUG [ActionProcessingPipeline] Using overridden action lifecycle processor for org.jboss.soa.esb.monitoring.client.InvokerAction
      14:43:38,803 DEBUG [ActionProcessingPipeline] SecurityContextPropagator in use for service 'InvokerService' is 'org.jboss.internal.soa.esb.services.security.JBossASContextPropagator'
      14:43:38,803 DEBUG [RegistryUtil] Registering < InvokerService, JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/OperationsResultCollectorQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/> > ] >
      14:43:38,896 DEBUG [RepositoryClassLoader] Added url: file:/D:/Server/jbossesb-server-4.5.GA/server/esb/tmp/aopdynclasses/ucl8284506718732261677/?dynamic=true, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@19bd735{ url=file:/D:/Server/jbossesb-server-4.5.GA/server/esb/deploy/jbossesb.sar/ ,addedOrder=9}
      14:43:40,326 DEBUG [AvailabilityExecutor] Running Availability Scan...
      14:43:40,374 DEBUG [AvailabilityExecutor] Built availability report for [44] resources with a size of [803] bytes in [48]ms
      14:44:40,165 DEBUG [AvailabilityExecutor] Running Availability Scan...
      14:44:40,166 DEBUG [AvailabilityExecutor] Built availability report for [1] resources with a size of [112] bytes in [1]ms
      14:45:39,973 DEBUG [AvailabilityExecutor] Running Availability Scan...
      14:45:39,973 DEBUG [AvailabilityExecutor] Built availability report for [1] resources with a size of [112] bytes in [0]ms

      Can anyone tell me what I do wrong?

      Thanks a lot,


      Marcus