Problems while creating a bridge service

[paulme]

Hi all,

I've some problems with creating a bridge service.

I get to the point when I try to look for a queue that isn't there, it get the error 'Name not found' which indicates that it can reach the server, etc.

However when I try to lookup a name that is on the server. I get the following error :

2009-06-15 11:34:42,604 WARN [org.jboss.jms.server.bridge.Bridge] (main) jboss.jms:name=TestBridge,service=Bridge Failed to set up connections
javax.jms.JMSException: Failed to connect to the server at tcp://W2K-TBC04O:7222
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:817)
at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:913)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1002)
at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:2699)
at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:36)
at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:186)
at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:239)
at com.tibco.tibjms.TibjmsConnectionFactory.createConnection(TibjmsConnectionFactory.java:58)
at org.jboss.jms.server.bridge.Bridge.createConnection(Bridge.java:906)
at org.jboss.jms.server.bridge.Bridge.setupJMSObjects(Bridge.java:1015)
at org.jboss.jms.server.bridge.Bridge.start(Bridge.java:320)
at org.jboss.jms.server.bridge.BridgeService.startService(BridgeService.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:269)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
at $Proxy38.start(Unknown Source)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.start(ServiceController.java:460)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:595)
2009-06-15 11:34:42,931 WARN [org.jboss.jms.server.bridge.Bridge] (main) jboss.jms:name=TestBridge,service=Bridge Failed to start bridge

I try to connect to a Tibco EMS server using a jar given to me by the Tibco developers.
Futher I use the standard settings with a extra queue and an extra datasource (jms-ds.xml)

[gaohoward]

make sure W2K-TBC04O:7222 is accessible to your client. Also this looks like a tibco JMS client configuration issue.

[paulme]

It seems to me that the server is reachable, because when I try to query an unexisting queue name. I get an error that the Queue isn't found.

Could it be that my server is running on Localhost that the other server needs a connection back or something ??

[gaohoward]

javax.jms.JMSException: Failed to connect to the server at tcp://W2K-TBC04O:7222
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:817)

This sounds like to me you cannot create a tcp socket on port 7222. This is a different connection other than your JNDI lookup.

It looks like your JNDI works fine.

[paulme]

I've downloaded a JMS Gui client ( Hermes ) and I could connect from my computer to the Tibco Server.

Could the problem originate because the server runs on 127.0.0.1 ???

These are the settings I've entered in my JBoss configuration

xyz-tibco-bridge-service.xml

<?xml version="1.0" encoding="UTF-8"?>

<!--
 Messaging Destinations deployment descriptor.

 $Id: destinations-service.xml 85945 2009-03-16 19:45:12Z [e-mail] $
 -->

<server>
<mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.jms:service=Bridge,name=TestBridge" xmbean-dd="xmdesc/Bridge-xmbean.xml">
 <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
 <depends optional-attribute-name="TargetProviderLoader">jboss.jms:service=JMSProviderLoader,name=MyRemoteJMSProvider</depends>
 <attribute name="SourceDestinationLookup">/queue/local</attribute>
 <attribute name="TargetDestinationLookup">remote/queue/name</attribute>
 <attribute name="TargetUsername">*******</attribute>
 <attribute name="TargetPassword">*******</attribute>
 <attribute name="QualityOfServiceMode">0</attribute>
 <attribute name="MaxBatchSize">5</attribute>
 <attribute name="MaxBatchTime">-1</attribute>
 <attribute name="FailureRetryInterval">5000</attribute>
 <attribute name="MaxRetries">-1</attribute>
 <attribute name="AddMessageIDInHeader">false</attribute>
</mbean>
</server>

jms-ds.xml

<?xml version="1.0" encoding="UTF-8"?>

<connection-factories>

 <!-- ==================================================================== -->
 <!-- JMS Stuff -->
 <!-- ==================================================================== -->

 <!--
 The JMS provider loader. Currently pointing to a non-clustered ConnectionFactory. Need to
 be replaced with a clustered non-load-balanced ConnectionFactory when it becomes available.
 See http://jira.jboss.org/jira/browse/JBMESSAGING-843.
 -->
 <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
 name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider">
 <attribute name="ProviderName">DefaultJMSProvider</attribute>
 <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
 <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
 <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
 <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
 </mbean>
 <!-- Remote JMS Provider -->
 <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
 name="jboss.jms:service=JMSProviderLoader,name=MyRemoteJMSProvider">
 <attribute name="ProviderName">RemoteConnectionFactory</attribute>
 <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
 <attribute name="FactoryRef">QueueConnectionFactory</attribute>
 <attribute name="QueueFactoryRef">QueueConnectionFactory</attribute>
 <attribute name="TopicFactoryRef">TopicConnectionFactory</attribute>
 <attribute name="Properties">
 java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
 java.naming.factory.url.pkgs=com.tibco.tibjms.naming
 java.naming.provider.url=tcp://serverip:7222
 </attribute>
 </mbean>

 <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
 <tx-connection-factory>
 <jndi-name>JmsXA</jndi-name>
 <xa-transaction/>
 <rar-name>jms-ra.rar</rar-name>
 <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
 <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
 <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
 <max-pool-size>20</max-pool-size>
 <security-domain-and-application>JmsXARealm</security-domain-and-application>
 <depends>jboss.messaging:service=ServerPeer</depends>
 </tx-connection-factory>

</connection-factories>

[gaohoward]

Could the problem originate because the server runs on 127.0.0.1 ???

If you suspect this, you can use -b option to override it.