Details
-
Question
-
Resolution: Obsolete
-
Major
-
None
-
7.2.0.GA
-
None
Description
We have several JBoss 6.4 servers. One is migrated to JBoss 7.2 and for migration of standalone-full was used jboss-server-migration tool, without any troubles. When new JBoss 7.2 is running, then we can see a lot of warnings:
13:36:57,175 WARN [org.apache.activemq.artemis.jms.bridge] (Thread-229) AMQ342010: Failed to connect JMS Bridge N/A: javax.jms.JMSException: Failed to create session factory at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:673) [hornetq-jms-client-2.4.7.Final-redhat-1.jar:2.4.7.Final-redhat-1] at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:112) [hornetq-jms-client-2.4.7.Final-redhat-1.jar:2.4.7.Final-redhat-1] at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:107) [hornetq-jms-client-2.4.7.Final-redhat-1.jar:2.4.7.Final-redhat-1] at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.createConnection(JMSBridgeImpl.java:981) [artemis-jms-server-2.6.3.redhat-00014.jar:2.6.3.redhat-00014] at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1159) [artemis-jms-server-2.6.3.redhat-00014.jar:2.6.3.redhat-00014] at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1258) [artemis-jms-server-2.6.3.redhat-00014.jar:2.6.3.redhat-00014] at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.access$2600(JMSBridgeImpl.java:74) [artemis-jms-server-2.6.3.redhat-00014.jar:2.6.3.redhat-00014] at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:1759) [artemis-jms-server-2.6.3.redhat-00014.jar:2.6.3.redhat-00014] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_222-4-redhat] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_222-4-redhat] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_222-4-redhat] Caused by: HornetQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=HQ119013: Timed out waiting to receive cluster topology. Group:null] at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:946) [hornetq-core-client-2.4.7.Final-redhat-1.jar:2.4.7.Final-redhat-1] at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:669) [hornetq-jms-client-2.4.7.Final-redhat-1.jar:2.4.7.Final-redhat-1] ... 10 more
in new standalon-full config we have connectors
<remote-connector name="netty" socket-binding="messaging"/> <remote-connector name="netty-throughput" socket-binding="messaging-throughput"> <param name="batch-delay" value="50"/> </remote-connector> <in-vm-connector name="in-vm" server-id="0"/>
acceptors
<remote-acceptor name="netty" socket-binding="messaging"/> <remote-acceptor name="netty-throughput" socket-binding="messaging-throughput"> <param name="batch-delay" value="50"/> <param name="direct-deliver" value="false"/> </remote-acceptor> <in-vm-acceptor name="in-vm" server-id="0"/>
connection factories:
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/> <connection-factory name="RemoteConnectionFactory" entries="RemoteConnectionFactory java:jboss/exported/jms/RemoteConnectionFactory" connectors="netty"/> <pooled-connection-factory name="hornetq-ra" entries="java:/JmsXA" connectors="in-vm" transaction="xa"> <outbound-config allow-local-transactions="true"/> </pooled-connection-factory>
and several bridges like:
<jms-bridge name="AbcQueueToXyz" module="com.tibco" quality-of-service="DUPLICATES_OK" failure-retry-interval="40000" max-retries="-1" max-batch-size="10" max-batch-time="100"> <source connection-factory="ConnectionFactory" destination="mojo.publishing.AbcQueue"/> <target connection-factory="TopicConnectionFactory" destination="test.system.abc.bridge.community" user="abc" password="abctest"> <target-context> <property name="java.naming.factory.initial" value="com.tibco.tibjms.naming.TibjmsInitialContextFactory"/> <property name="java.naming.provider.url" value="tcp://testmsg01.aabbcc.net:7777,tcp://testmsg02.aabbcc.net:7777"/> <property name="java.naming.factory.url.pkgs" value="org.jboss.naming:org.jnp.interfaces:com.tibco.tibjms.naming"/> <property name="java.naming.security.principal" value="abc"/> <property name="java.naming.security.credentials" value="abctest"/> </target-context> </target> </jms-bridge>
Then we have question:
What do we have to change to have functional bridges and avoid these log warnings?