activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kenhans <kenh...@hotmail.co.uk>
Subject Problems upgrading from 5.5.1 to 5.6.0
Date Fri, 17 Aug 2012 11:56:17 GMT
hello,
I can not get my local environment to run when I upgraded from 5.5.1 to
5.6.0. Seems like the system tries to automatically connect to a broker
(which I've added with a phony protocol-name to prevent it from actually
connect). In 5.5.1 it did not seem to try to connect automatically, but in
5.6.0 it does. Is there a change in the configuration for 5.6.0? I could not
find any info regarding this in the release notes, though.

Or is it that the logging just has changed? So that 5.6.0 logs this where
5.5.1 did not?

any hints would be highly appreciated!

regards,
Kenneth


from my message-server.xml:

<jee:jndi-lookup id="jndiConnectionFactory"
jndi-name="QueueConnectionFactory"
                     expected-type="javax.jms.QueueConnectionFactory"
lookup-on-startup="false" resource-ref="false" >
        <jee:environment>
           
java.naming.factory.initial=com.sybase.jms.client.InitialContextFactory
            java.naming.provider.url=xxxiiop://dm:2000
            java.naming.security.principal=xyz
            java.naming.security.credentials=zyx
        </jee:environment>
    </jee:jndi-lookup>


causes the following stacktrace:

12/08/17 10:50:10 INFO jms.DefaultJmsMessageListenerContainer: JMS message
listener invoker needs to establish shared Connection
12/08/17 10:50:10 WARN jms.DefaultJmsMessageListenerContainer: Could not
refresh JMS Connection for destination 'EASJMS_REP_Q' - retrying in 5000 ms.
Cause: JndiObjectTargetSource failed to obtain new target object; nested
exception is javax.naming.NamingException: 
Caused by: java.lang.IllegalArgumentException: protocol = xxxiiop
| at com.sybase.djc.rmi.iiop.Protocol.getNumber(Protocol.java:54)
| at com.sybase.djc.rmi.iiop.client.UrlInfo.init(UrlInfo.java:193)
| at com.sybase.djc.rmi.iiop.client.UrlInfo.getInstance(UrlInfo.java:23)
| at
com.sybase.djc.rmi.iiop.client.ClientNamingContext.init(ClientNamingContext.java:582)
| at
com.sybase.djc.rmi.iiop.client.ClientNamingContext.getInstance(ClientNamingContext.java:77)
| at com.sybase.jms.client.NamingContext.init(NamingContext.java:277)
| at
com.sybase.jms.client.NamingContext_DJC.init(NamingContext_DJC.java:881)
| at com.sybase.jms.client.NamingContext.getInstance(NamingContext.java:28)
| at
com.sybase.jms.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:31)
| at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
| at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
| at javax.naming.InitialContext.init(InitialContext.java:223)
| at javax.naming.InitialContext.<init>(InitialContext.java:197)
| at
org.springframework.jndi.JndiTemplate.createInitialContext(JndiTemplate.java:136)
| at org.springframework.jndi.JndiTemplate.getContext(JndiTemplate.java:103)
| at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:85)
| at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152)
| at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178)
| at
org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95)
| at
org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105)
| at
org.springframework.jndi.JndiObjectTargetSource.getTarget(JndiObjectTargetSource.java:132)
| at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:182)
| at $Proxy33.createConnection(Unknown Source)
| at
org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.java:184)
| at
org.springframework.jms.listener.AbstractJmsListeningContainer.createSharedConnection(AbstractJmsListeningContainer.java:404)
| at
org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:389)
| at
org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:869)
| at
org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:851)
| at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:982)
| at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
| at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
| at java.lang.Thread.run(Thread.java:662)




--
View this message in context: http://activemq.2283324.n4.nabble.com/Problems-upgrading-from-5-5-1-to-5-6-0-tp4655238.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message