[jboss-user] [JBoss Messaging] - Re: ClientCallback Multiplex

aslak do-not-reply at jboss.com
Thu Nov 1 16:31:50 EDT 2007


The actually issue is not the combination of two providers on the same server, but rather using the jboss.messaging.callback.bind.port variable at all in the application server. I see the same behavior on a single local provider. 

When deploying a MDB it first creates a connection to the DLQ, then failes to create a connection to the actual destination. 


  | 12:41:47,891 ERROR [JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec at 10f8ed(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter at 4dd5a1 destination=/queue/jmsxa.in isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=jmsxatest pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
  | org.jboss.jms.exception.MessagingJMSException: Failed to invoke
  |         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:269)
  |         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:187)
  |         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
  |         at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
  |         at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
  |         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
  |         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
  |         at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
  |         at org.jboss.jms.client.JBossConnectionFactory.createXAQueueConnection(JBossConnectionFactory.java:142)
  |         at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupQueueConnection(JmsActivation.java:448)
  |         at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:422)
  |         at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:303)
  |         at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:249)
  |         at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:589)
  |         at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
  |         at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
  |         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
  |         at java.lang.Thread.run(Thread.java:619)
  | Caused by: org.jboss.remoting.InvalidConfigurationException: The invoker for locator (InvokerLocator [bisocket://10.111.111.197:4459/callback?callbackServerHost=10.111.111.197&callbackServerPort=4459&callbackServerProtocol=bisocket&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper]) is already in use by another Connector.  Either change the locator or add new handlers to existing Connector.
  |         at org.jboss.remoting.InvokerRegistry.createServerInvoker(InvokerRegistry.java:519)
  |         at org.jboss.remoting.transport.Connector.init(Connector.java:396)
  |         at org.jboss.remoting.transport.Connector.create(Connector.java:782)
  |         at org.jboss.remoting.transport.Connector.start(Connector.java:301)
  |         at org.jboss.remoting.Client.addListener(Client.java:918)
  |         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
  |         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:316)
  |         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
  |         ... 16 more
  | 
  | 


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101078#4101078

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101078



More information about the jboss-user mailing list