Jonathan Anstey created SMX4NMR-314:
---------------------------------------
Summary: jbi-cluster doesn't work with latest activemq-pool
Key: SMX4NMR-314
URL: https://issues.apache.org/jira/browse/SMX4NMR-314
Project: ServiceMix NMR
Issue Type: Bug
Affects Versions: 1.6.0
Reporter: Jonathan Anstey
Assignee: Jonathan Anstey
Fix For: 1.6.1
Since https://issues.apache.org/jira/browse/AMQ-3588 we now get the following
logs from jbi-cluster:
12:13:39,655 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener
invoker failed for destination 'org.apac
he.servicemix.jbi.cluster' - trying to recover. Cause:
org.apache.activemq.pool.PooledMessageConsumer cannot be cast to
org.apache.activemq.MessageAvailableConsumer
12:13:39,656 | INFO | rint Extender: 1 | ManagementEndpointRegistry |
130 - org.apache.servicemix.nmr.management - 1.6.0 | Registering endpoint:
org.apache.servicemix.nmr.core.InternalEndp
ointWrapper@b93143e with properties {NAME=servicemix-cxf-bc,
objectClass=[Ljava.lang.String;@279ad6ff, service.id=372,
TYPE=binding-component}
12:13:39,661 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,662 | INFO | rint Extender: 3 | ManagementEndpointRegistry |
130 - org.apache.servicemix.nmr.management - 1.6.0 | Registering endpoint:
org.apache.servicemix.nmr.core.InternalEndp
ointWrapper@b93143f with properties {NAME=servicemix-file,
objectClass=[Ljava.lang.String;@7085b2a3, service.id=375,
TYPE=binding-component}
12:13:39,674 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,680 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,686 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,689 | INFO | rint Extender: 2 | ComponentRegistryImpl |
196 - org.apache.servicemix.jbi.runtime - 1.6.0 | JBI component registered with
properties: {NAME=servicemix-ftp, obje
ctClass=[Ljava.lang.String;@61e32680, service.id=379, TYPE=binding-component}
12:13:39,691 | INFO | rint Extender: 2 | ManagementEndpointRegistry |
130 - org.apache.servicemix.nmr.management - 1.6.0 | Registering endpoint:
org.apache.servicemix.nmr.core.InternalEndp
ointWrapper@b931440 with properties {NAME=servicemix-ftp,
objectClass=[Ljava.lang.String;@6071bfbf, service.id=380,
TYPE=binding-component}
12:13:39,700 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,709 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,720 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,725 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,728 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,732 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,735 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,738 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
12:13:39,740 | INFO | sRequestorPool-1 | ActiveMQJmsRequestorPool |
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS
Connection
...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
