Tibco Remote Jms Provider - Auto-acknowledge

Hi,
We have setup Weblogic 8.1.6 with Tibco EMS 4.2 as remote JMS provider.
It works, and we have configured an MDB as below:
-ejb-jar-
<message-driven>
<display-name>Order receiver MDB</display-name>
<ejb-name>OrderMDB</ejb-name>
<ejb-class>com.company.OrderMDB</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
And the question: We are receiving this in our weblogic log ( two minute intervalls ) and is is NOT application logging. What is it?
2008-08-26 08:39:32 [5816236 TIBCO EMS TCPLink Reader (2856200)] [TIBCO EMS]: received msg from daemon conn=2856200 seqi
d=14151393 msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442
2008-08-26 08:39:32 [-488738086 ExecuteThread: '3' for queue: 'weblogic.kernel.System'] [TIBCO EMS]: send qsndr=1274771
msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442 dlvmode=1 pri=5 ttl=240000 sess=3736118
2008-08-26 08:39:32 [5816236 TIBCO EMS TCPLink Reader (2856200)] [TIBCO EMS]: post msg to session sess=3736020 cons=2737
945 seqid=14151393 msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442
2008-08-26 08:39:32 [9425697 TIBCO EMS Session Dispatcher (3736020)] [TIBCO EMS]: before onMessage sess=3736020 cons=273
7945 seqid=14151393 msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442
/ Peter

Similar Messages

Connecting to a Remote JMS provider from MDB in jboss-4.0

Hi,
I am using Tibco as a remote JMS Provider. When the Tibco server is running on the same machine as JBoss-4.0, the Message Driven Bean deployed in Jboss is able to get the messages from the queue on Tibco server.
I have added the following configuration to jms-ds.xml file

<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
<attribute name="ProviderName">TIBCOJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JNDIProviderAdapter
</attribute>



<attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>

<attribute name="TopicFactoryRef">XATopicConnectionFactory</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=tibjmsnaming://TibcoHost:7222
</attribute>
</mbean>
Also following invoker proxy binding is added to standardjboss.xml & it is used in MDB's jboss.xml
<invoker-proxy-binding>
<name>my-mdb-invoker</name>
<invoker-mbean>does-not-matter</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MinimumSize>1</MinimumSize>
<KeepAliveMillis>30000</KeepAliveMillis>
<MaximumSize>15</MaximumSize>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
But When I try to use Tibco server on some other machine it throws following exception. It actually tryies to connect to Tibco server on same machine.
javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:748)
at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:857)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:611)
at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1769)
at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:35)
at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:90)
at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:151)
at com.tibco.tibjms.TibjmsXAQueueConnectionFactory.createQueueConnection(TibjmsXAQueueConnectionFactory.java:140
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy45.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:170)
at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:262)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy43.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy19.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)

Hi,
I am using Tibco as a remote JMS Provider. When the Tibco server is running on the same machine as JBoss-4.0, the Message Driven Bean deployed in Jboss is able to get the messages from the queue on Tibco server.
I have added the following configuration to jms-ds.xml file

<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
<attribute name="ProviderName">TIBCOJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JNDIProviderAdapter
</attribute>



<attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>

<attribute name="TopicFactoryRef">XATopicConnectionFactory</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=tibjmsnaming://TibcoHost:7222
</attribute>
</mbean>
Also following invoker proxy binding is added to standardjboss.xml & it is used in MDB's jboss.xml
<invoker-proxy-binding>
<name>my-mdb-invoker</name>
<invoker-mbean>does-not-matter</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MinimumSize>1</MinimumSize>
<KeepAliveMillis>30000</KeepAliveMillis>
<MaximumSize>15</MaximumSize>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
But When I try to use Tibco server on some other machine it throws following exception. It actually tryies to connect to Tibco server on same machine.
javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:748)
at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:857)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:611)
at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1769)
at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:35)
at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:90)
at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:151)
at com.tibco.tibjms.TibjmsXAQueueConnectionFactory.createQueueConnection(TibjmsXAQueueConnectionFactory.java:140
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy45.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:170)
at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:262)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy43.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy19.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)

Foreign JMS Server Persistance\Retry in case Remote JMS Provider goes down

Hi All
I would need more clarity on this. How does the Foreign JMS Server behave in case the remote JMS provider goes down. Does it take the message from the Publishing Proxy Service and retries\persists the JMS Message till the remote provide is up?
Please let us know. This would effect our design as retrial is very important here. Thanks

If you want to provide guaranteed delivery with automatic retries when using remote JMS implementations, there are multiple ways to implement it:
1. While reading from a foreign JMS destination
Create a Foreign JMS server using transactional drivers (use XA in case of JMS). The messages remain on remote server JMS queue and OSB proxy polls the message directly on remote server. So if Remote Server is down OSB will not be able to read the message. Once remote server is up OSB will pick up the message (as long as foreign JMS server provides persistence and maintains the messages in the queue during a server restart). In case of error in OSB foreign queue can do retry if it provides a retry mechanism.
2. While writing the message to a foreign JMS destination
a. Use a foreign JMS server using transactional connection. Put the retry mechanism in OSB Business service which writes to the foreign JMS/MQ queue. In case of failure Business Service can retry based on configuration. If you want to provide guaranteed delivery then create a local JMS queue to store the messages. So when remote destination is down for a long time undelivered messages will be rolled back to the local queue. You can put retry mechanism on the local queue.
b. Use a messaging bridge which will write the messages to the remote destination. You can configure retry delivery rules in messaging bridge so once busienss service writes the message to the bridge, a SAF agent will ensure the delivery to remote destination whenever it is up.

Accessing remote jms provider to send message

My application has web tier and app tier. I configured jms provider in web tier and created a message driven bean which listens to this provider. I want to ship all me exception stack trace to web tier logs. In app tier when any exception occurs I want to send message to topic (jms provider) in web tier so that mdb in web tier consumes this message and logs it to the log files. For this I should access jms provider in app tier. How can I achieve this?

Hi,
You can prevent administrators from changing the permissions for a connection by applying the
Do not allow local administrators to customize permissions Group Policy setting.
This Group Policy setting is located in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security
Apart there is one command with which you can set the permission for that check the related
article. Additionally checkthis
thread for more detail.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to use remote JMS in websphere5?

I want to use JMS in another server to send message so that I config required jndi in server. When I lookup local JMS jndi(connection factory, queue) it works correctly. But when I lookup remote connectionfactory, it throws 'javax.naming.CommunicationException'. BTW, local configuration is same as JMS server. And I use WSAD 5.1.1 to develop it.
The first question is if I need use JMS server on another server, I should lookup remote queue and JMS connection factory on that server, right?
The second question : If yes, how to obtain remote JMS connection factory? I use WSAD 5.1.1 trail, I don't know is it possible to obtain remote jndi.
The third question : do I need change any configuration for supporting remote JMS client instead of local(same compute, different jvm) environment?
The following is my client code to obtain remote queue:
public class Test {
     public static void main(String[] args) {
          Properties env = new Properties();
          env.put(Context.INITIAL_CONTEXT_FACTORY,
                "com.ibm.websphere.naming.WsnInitialContextFactory");
          env.put(Context.PROVIDER_URL, "corbaloc:iiop:10.240.4.203:2809");
          try {
               Context initialContext = new InitialContext(env);
               Object obj = initialContext.lookup("jms/IPharmQueue1");
          } catch (NamingException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
}It works ok when ip is localhost. But it can obtain remote queue or connectionfactory. I tried to lookup other EJB, it also failed.

Actually, I have application in one server and four same server as cluster. But only one server provides JMS service. So my application need to use remote JMS server instead of local server. But in my development environment I can not simulate cluster environment as customer environment. So I try to let my application access remote JMS server in different computer. When two server start up I found my application will get local JMS connection factory and queue instead of remote factory. Even I put IP of another computer in PROVIDER_URL.
I did a application client to test it. The code is above. But it can not lookup remote jndi.
I use WAS5 as server and WSAD 5.1.1 as development IDE.
Is any idea about it?

MDBs failed to connect to remote JMS server

Hi,
          We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
          In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
          <weblogic-enterprise-bean>
               <ejb-name>MyBean</ejb-name>
               <message-driven-descriptor>
                    <destination-jndi-name>MyTopic</destination-jndi-name>
          <provider-url>t3://myhost:19009,myhost:19011</provider-url>
          <connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
          di-name>
               </message-driven-descriptor>
          </weblogic-enterprise-bean>
          When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
          (t3://myhost:19009) but got the same result.
          When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
          I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
          Any help would be greatly appreciated.
          Thanks,
          Thao

I'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?).                    I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
          >>> Could you elaborate on the known problem?
          9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
          >>> What else I can try?
          Beyond contacting customer support, I'm not sure.
          Tom

Problem in configuring third party JMS provider

Hi,
I am having a problem in configuring Sun MQ 4.4 JMS provider with weblogic 10.3.I tried the following method:-
1. Created a new outbound connection pool.
2.In the properties for the connection pool :-
ConnetionFactory Location :- myTestCF (this is the remote connection factory JNDI)
Factory properties :- java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory;java.naming.provider.url=file:/C:/my_object_store;java.naming.security.principal=admin;java.naming.security.credentials=admin
3.Provided the username and password also.
But when I am testing it from a SOA composite through a JMS adapter, it is giving me an exception indicating it could not locate the connection factory.I am clueless why this is happening.I've also tried with putting the sun mq jar files inside the <%wl_home%>/user_projects/domains/<%my_domain%>/lib folder.But it did not work.Please help.
Thanks,
Rahul

In third party process SO / PR / PO should be in integrity. Your manual modification violates this I think (you are making one PO item from two SO item...).
http://help.sap.com/erp2005_ehp_04/helpdata/EN/dd/560287545a11d1a7020000e829fd11/frameset.htm
Processing Third-Party Orders in Purchasing
When you save a sales order that contains one or more third-party items, the system automatically creates a purchase requisition in Purchasing. Each third-party item in a sales order automatically generates a corresponding purchase requisition item. During creation of the requisition, the system automatically determines a vendor for each requisition item. If a sales order item has more than one schedule line, the system creates a purchase requisition item for each schedule line.
Purchase orders are created from purchase requisitions in the usual way. For more information about creating purchase orders, see the Purchasing documentation. During creation of the purchase order, the system automatically copies the delivery address of your customer from the corresponding sales order. In a sales order, you can enter purchase order texts for each third-party item. When you create the corresponding purchase order, the texts are automatically copied into the purchase order. The number of the purchase order appears in the document flow information of the sales order.
All changes made in the purchase order are automatically made in the sales order as well. For example, if the vendor confirms quantities and delivery dates different from those you request and enters them in the purchase order, the revised data is automatically copied into the sales order.
Regards,
Csaba

Sender JMS Adapter error: The JMS provider gave the error message as Not permitted, and the error code is null

I am trying to connect tibcoems with PI using a Sender jms adapter.After successfully installing the drivers , the sender adapter goes into error.
"The JMS Provider gave the error message as Not permitted, and the error code is null"
The Transport protocol is 'Access JMS Provider with JNDI' and i have been given the required parameters from the tibco guys.
Your input are highly appreciated.
Shyam

Hi AQmit,
Thanks for the reply.
Please find the screenshots of what i am trying to do.
Also, Can u direct me how to check the right logs?

Guranteed messaging and auto acknowledgement

I have a webservice sending messages to a Topic on the WL server instance. The webservice recieves XML messages from an external system. The mesage after being recieved is send to the different consumers. How willl I implement auto message reciept acknowledgement to be send by the MoM to the webservices.
Secondly the messages are consumed by various consumers. I want to implement Guaranteed messaging. Should I just redirect all the faulty messages in a queue. Any example and documentation on how to do is highly appreciated as per best practice.
Regards
Thomas

Hi Daryl,
I would like to acknowledge the alarms after every
notification automatically.
Base on the user guide, all i need to do is to choose
the alarm tab and configure it to "clear" in the
event of any alarms.First of all, are you sure you want to do this? The end effect would be your SunMC Console would show no coloured alarms... because you ack'd them all. I guess that may be OK if you've already made sure to send out some sort of notification.
However, when i tried to change the action to "clear"
instead of email or script, I can't seem to save my
configuration changes."Clear" in that context isn't an action, it's just a way to remove any email or script actions you've configured. i.e if you were using a script action but decided you didn't want to any more, you'd click clear to remove it.
You can set up universal auto-acknowledge like that in EventAction (http://www.halcyoninc.com/products/EventAction/index.php)
You would setup a script action:
http://www.halcyoninc.com/products/EventAction/help/HALEventAction-add-action-info-script.gif
...that for all alarms instantly calls a script to ack them:
http://www.halcyoninc.com/products/EventAction/help/HALEventAction-remote-acknowledging-h.html
In this case you're just using the remote ack feature locally on the SunMC Server. If you're already forwarding the SunMC alarms someplace else (like another product : Tivoli / Netcool / OpenView / Patrol / [insert_open_source_app_here] etc) then you may as well just use the remote ack feature as intended. So for example if you ack an alarm in Netcool, that ack goes backwards into SunMC and clears it there as well.
I'm getting ahead of myself: I'm not sure what you want to do yet :)
Regards,
[email protected]
http://www.HalcyonInc.com

Auto-Acknowledgement of Alarms

Hi,
I have installed SunMC 3.5.1b in my server.
I would like to acknowledge the alarms after every notification automatically.
Base on the user guide, all i need to do is to choose the alarm tab and configure it to "clear" in the event of any alarms.
However, when i tried to change the action to "clear" instead of email or script, I can't seem to save my configuration changes.
Therefore, I tried to change the action to "email" and saved it. It works ok for "email" but not for "clear".
What is going on?
How can i achieve my auto-acknowledgement?
Any help would be appreciated.
Thanks in advance
regards
Daryl

Hi Daryl,
I would like to acknowledge the alarms after every
notification automatically.
Base on the user guide, all i need to do is to choose
the alarm tab and configure it to "clear" in the
event of any alarms.First of all, are you sure you want to do this? The end effect would be your SunMC Console would show no coloured alarms... because you ack'd them all. I guess that may be OK if you've already made sure to send out some sort of notification.
However, when i tried to change the action to "clear"
instead of email or script, I can't seem to save my
configuration changes."Clear" in that context isn't an action, it's just a way to remove any email or script actions you've configured. i.e if you were using a script action but decided you didn't want to any more, you'd click clear to remove it.
You can set up universal auto-acknowledge like that in EventAction (http://www.halcyoninc.com/products/EventAction/index.php)
You would setup a script action:
http://www.halcyoninc.com/products/EventAction/help/HALEventAction-add-action-info-script.gif
...that for all alarms instantly calls a script to ack them:
http://www.halcyoninc.com/products/EventAction/help/HALEventAction-remote-acknowledging-h.html
In this case you're just using the remote ack feature locally on the SunMC Server. If you're already forwarding the SunMC alarms someplace else (like another product : Tivoli / Netcool / OpenView / Patrol / [insert_open_source_app_here] etc) then you may as well just use the remote ack feature as intended. So for example if you ack an alarm in Netcool, that ack goes backwards into SunMC and clears it there as well.
I'm getting ahead of myself: I'm not sure what you want to do yet :)
Regards,
[email protected]
http://www.HalcyonInc.com

JMS Provider Responsibilities For Concurrent Message Delivery

Hi,
(This question pertains to the JMS api, outside a j2ee container)
Is it JMS-provider dependent on how concurrent message delivery is implemented? In other words, the code below sets up multiple consumers (on a topic), each with their own unique session and MessageListener and then a separate producer (with its own session) sends a message to the topic and I observer that only (4) onMessage() calls can execute concurrently. When one onMessage() method exits, that same thread gets assigned to execute another onMessage().
The only thing I could find on the matter in the spec was section in 4.4.15 Concurrent Message Delivery and it's pretty vague.
It's really important because of the acknowledgment mode. If it turns out that I need to delegate the real work that would be done in the onMessage() to another thread that I must manage (create, pool, etc), then once the onMessage() method completes (i.e., after it does the delegation to another thread), the message is deemed successfully consumed and will not be re-delivered again (and that's a problem if the custom thread fails for any reason). Of course, this assumes I'm using AUTO_ACKNOWLEDGE as the acknowledgment mode (which seems to make sense since using CLIENT_ACKNOWLEDGE mode will automatically acknowledge the receipt of all messages that have been consumed by the corresponding session and that's not good).
My JMS Provider is WL 9.1 and the trival sample code I'm using as my test follows below. I also show the ouput from running the example.
thanks for any help or suggestions,
mike
--- begin TopicExample.java ---
import java.io.*;
import java.util.*;
import javax.naming.*;
import javax.jms.*;
import javax.rmi.PortableRemoteObject;
class TopicExample {
public final static String JMS_PROVIDER_URL = "t3://localhost:8001";
public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";
public final static String JMS_FACTORY="CConFac";
public final static String TOPIC="CTopic";
public final static int NUM_CONSUMERS = 10;
public static void main(String[] args) throws Exception {
InitialContext ctx = getInitialContext(JMS_PROVIDER_URL);
ConnectionFactory jmsFactory;
Connection jmsConnection;
Session jmsReaderSession[] = new Session[10];
Session jmsWriterSession;
TextMessage jmsMessage;
Destination jmsDestination;
MessageProducer jmsProducer;
MessageConsumer jmsConsumer[] = new MessageConsumer[10];
MessageListener ml;
try
// Create connection
jmsFactory = (ConnectionFactory)
PortableRemoteObject.narrow(ctx.lookup(JMS_FACTORY), ConnectionFactory.class);
jmsConnection = jmsFactory.createConnection();
// Obtain topic
jmsDestination = (Destination) PortableRemoteObject.narrow(ctx.lookup(TOPIC), Destination.class);
// Reader session and consumer
for (int i=0; i<NUM_CONSUMERS; i++)
jmsReaderSession[i] = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
jmsConsumer[i] = jmsReaderSession.createConsumer(jmsDestination);
jmsConsumer[i].setMessageListener(
new MessageListener()
public void onMessage(Message msg) {
try {
String msgText;
if (msg instanceof TextMessage) {
msgText = ((TextMessage)msg).getText();
} else {
msgText = msg.toString();
System.out.println("JMS Message Received: "+ msgText );
System.out.println("press <return> to exit onMessage");
char c = getChar();
System.out.println("Exiting onMessage");
} catch (JMSException jmse) {
System.err.println("An exception occurred: "+jmse.getMessage());
// Writer session and producer
jmsWriterSession = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
jmsProducer = jmsWriterSession.createProducer(jmsDestination);
jmsMessage = jmsWriterSession.createTextMessage();
jmsMessage.setText("Hello World from Java!");
jmsConnection.start();
jmsProducer.send(jmsMessage);
char c = '\u0000';
while (!((c == 'q') || (c == 'Q'))) {
System.out.println("type q then <return> to exit main");
c = getChar();
for (int i=0; i<NUM_CONSUMERS; i++)
jmsReaderSession[i].close();
jmsWriterSession.close();
jmsConnection.close();
System.out.println("INFO: Completed normally");
} finally {
protected static InitialContext getInitialContext(String url)
throws NamingException
Hashtable<String,String> env = new Hashtable<String,String>();
env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
env.put(Context.PROVIDER_URL, url);
return new InitialContext(env);
static public char getChar()
char ch = '\u0000';
try {
ch = (char) System.in.read();
System.out.flush();
} catch (IOException i) {
return ch;
--- end code --
Running the example:
prompt>java TopicExample
JMS Message Received: Hello World from Java!
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
press <return> to exit onMessage
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
type q then <return> to exit main
[you see, only 4 onMessage() calls execute concurrently. Now I press <return>]
Exiting onMessage
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
[now once the thread executing the onMessage() completes, the JMS providor assigns it to execute another onMessage() until all 10 onMessage() exections complete).

I am too facing the same issue. but in my case I start getting this problem when the message size is about 1 MB itself.
Any help is appraciated.
Regards,
ved

XI JMS adapter after JMS provider reboot

Hi All,
I have problem with XI JMS adapter. Adapter is in a JMS client role and JMS provider is Tibco. After reboot of JMS service in JMS provider, XI JMS adapter loose username and pw in connection and try logon to queue as an anonymous user.
After deactivation + activation of XI JMS adapter, connection seems to work correctly with uname & pw.
In JMS adapter we have folloving settings and we are connected straight into queue:
Transport Protocol = SonicMQ JMS Provider
General JMS Settings:
Transactional JMS Session is in use
Delivery Mode of Message Producer = Persist JMS messages..
+ Queue user & pw
Error Handling Settings:
Wait After Message Error(msecs) = 60000
Wait Before Reconnect(msecs) = 60000
Does anyone ran into this earlier?
Thanks in advance.
-Kimmo

Hi Saravana,
It seems that no connection is available to queue. In JMS adapter are you using correct path for finding these provider specifig classes in front of class name. Example: javax.jms.QueueConnectionFactory
It is also possible that username of JMS provider which you configure to JMS adapter does not have correct rights for reading/writing or accessing to queue.
We are not using any additional settings for JMS adapter. For server name we have also added protocol which is tcp://<servername> and using transactional JMS session.
We had this same error when trying connect to queue via JNDI. Then we changed JMS adapter to connect straight to queue and it started to work.

How to integrate Websphere MQ as an external JMS Provider?

Hello to all!
I'm trying to integrate Websphere MQ in SAP Web AS 6.40 as an external JMS provider and I'm having some problems. As the use of SAP XI is impossible for me, I started using the built-in JMS Connector.
I've already read (and tried to follow) the documentation in http://help.sap.com/saphelp_nw04/helpdata/en/cd/4d4941abbb4c0de10000000a1550b0/frameset.htm, but unfortunately, it didn't help me that much.
It told me that the JMS Connector is the right place to start, and I already managed to deploy and define the Websphere MQ JMS implementation as a library. And from various examples I'm quite sure that Websphere MQ is an JNDI based JMS provider. But now the problems start.
According to the SAP library mentioned above, I have to enter the JNDI name to the ConnectionFactory in the "New ConnectionFactory" dialogue in the "Provider" tab. As an example there is the (existing) JNDI name "jmsfactory/default/TopicConnection". For doing the same with my Websphere MQ, I expect to need something alike.
Hoping that I'm getting the SAP library right at this point, I'm expecting to need a JNDI entry, like, let's say, "jmsfactory/WebsphereMQ/QueueConnection" connected to the class "com.ibm.mq.jms.MQConnectionFactory" (MQConnectionFactory is the class in the MQ JMS implementation that implements the JMS interface "Connection Factory"). How can I put those Websphere MQ classes, that are implementing the JMS interfaces like Connection Factory, QueueConnectionFactory and so on
in my JNDI tree? The point is, obviously, no JNDI entry was made during deploying Websphere MQ as a library.
Or am I totally wrong an misunderstood the SAP library completely? Any help on this topic would be highly appreciated.
Best greetings!
Bärbel

Integrating WebSphereMQ with SAP Web Application Server
Prerequisites
The native libraries of WebSphereMQ must be added to the environment variables of the host or hosts where the SAP Web AS is running. Typically, if MQ is installed on the same host, the required entries are added to the environment at installation. However, we recommend that you check the MQ documentation for details about the directory where the libraries are located, and make sure it is added to the environment on all hosts with SAP Web AS.
For example, for Windows OS the following libraries are required:
-     amqmtmgr.dll
-     amqvwaa2.dll
-     amqxcs2.dll
-     amqxcsn.dll
-     amqzc.dll
-     amqzsai.dll
-     amqzst.dll
-     amqztm.dll
-     mqjbdf02.dll
-     mqjbnd05.dll
-     mqm.dll
-     mqmvxd.dll
-     mqmxa.dll
-     MQXAi02.dll
Procedure
1)     If the version of the SAP Web AS is SP 7 or lower, you must apply a patch for the JMS Connector Service. The required SDA is attached to this e-mail (jmsconnector.sda). To apply it:
a.     Run the SDM Remote GUI tool. It is located in <SAP_install_dir>\SAPSID\<Instance_ID>\SDM\program.
b.     In the Deployment tab, add the jmsconnector.sda to the deployment list. Choose   Show Deployment Configuration. Select Update deployed SDAs/SCAs that have any version (this ensures that you will have the SDA deployed even if for some reason its timestamp is older than the one of the SP7 SDA that you already have deployed.)
c.     Deploy the SDA following the standard deployment procedure. If prompted to choose if you want to delegate the control to the SDM server, choose Yes. The SDM shuts down the cluster, deploys the SDA, and then restarts the cluster.
2)     Create the IBM MQ library. You can do it using either Visual Administrator or SAP NetWeaver Developer Studio.
a.     Visual Administrator:
i.     Go to Services -> JMS Connector.
ii.     Select JMS Libraries, and choose New.
iii.     Enter a name for the library, such as MQJMSLIB.
iv.     Browse to select the following JAR files:
- com.ibm.mq.jar
- com.ibm.mqbind.jar
- com.ibm.mqjms.jar
- fscontext.jar
- ldap.jar
- postcard.jar
- provider.xml
- providerutil.jar
v.     Deploy the library.
vi.     Go to Services -> Configuration Adapter. In the configuration tree on the right-hand side of the screen browse to cluster_data -> server -> cfg -> ext -> MQJMSLIB-provider.xml. Switch to edit mode using . Open the XML for editing using . Add the following entry (after the reference entry for jms):
<reference type="library" strength="weak">j2eeca</reference>
Choose OK and restart the cluster to apply the changes.
b.     SAP NetWeaver Developer Studio:
i.     Create a J2EE Library project.
ii.     Select the project and choose File -> Import -> File System. Browse to the MQ folder, which contains the JAR files listed above, and select to import them.
iii.     Extend the tree of your library project and open server/provider.xml. Go to the Jars tab.
iv.     Select Jars, and choose Add. Choose to add the JAR files that you have imported in the previous step.
v.     Go to the References tab. Select References, and choose Add. Choose Select library/interface/service. In the list select jms and j2eeca.
vi.     Save and close provider.xml. From the context menu of the library project choose Build Library Archive.
vii.     Select the SDA in the project tree, open its context menu, and choose Deploy to J2EE Engine.
3)     Create a JMS Connector Factory in Visual Administrator.
You can either enter the required values directly in the Visual Administrator (Services -> JMS Connector), or you can edit the following sample deployment descriptors and import them in Visual Administrator using .
a.     Using JNDI:
This is example of factories.xml using JNDI based JMS provider.
<?xml version="1.0" encoding="UTF-8" ?>
<jms-factories>
    <application-name>
      IBM_Test_App
    </application-name>
    <connection-factory>
      <library-name>
        MQJMSLIB
      </library-name>
      <factory-name>
        IBM_Queue_Factory
      </factory-name>
      <context-factory-type>
<!This factory should already exist on WebSphereMQ.-->
        <link-factory-name>
          QCF_1
        </link-factory-name>
        <initial-context-factory>
          com.sun.jndi.fscontext.RefFSContextFactory
        </initial-context-factory>
        <provider-url>
          file:/C:/JNDI-Directory
        </provider-url>
        <security-principal>
        </security-principal>
        <security-credentials>
        </security-credentials>
      </context-factory-type>
    </connection-factory>
</jms-factories>
b.     Using object factory JMS provider
<?xml version="1.0" encoding="UTF-8" ?>
<jms-factories>
    <application-name>
      IBM_Test_App
    </application-name>
    <connection-factory>
      <library-name>
        MQJMSLIB
      </library-name>
      <factory-name>
        IBM_Queue_Factory
      </factory-name>
      <object-factory-type>
        <object-factory-name>
          com.ibm.mq.jms.MQXAQueueConnectionFactoryFactory
        </object-factory-name>
        <class-name>
          com.ibm.mq.jms.MQXAQueueConnectionFactory
        </class-name>
        <properties>
          <property>
            <property-name>
              HOST
            </property-name>

            <property-value>
              localhost
            </property-value>
          </property>
          <property>
            <property-name>
              QMGR
            </property-name>

            <property-value>
              MQ_default
            </property-value>
          </property>
          <property>
            <property-name>
              PORT
            </property-name>

            <property-value>
              1414
            </property-value>
          </property>
          <property>
            <property-name>
              TRAN
            </property-name>

            <property-value>
              1
            </property-value>
          </property>
        </properties>
      </object-factory-type>
    </connection-factory>
</jms-factories>
4)     Use the connection factory in an application:
Code:
Context ctx = new InitialContext();
Object ref = ctx.lookup("java:comp/env/IBM_Queue_Factory");
QueueConnectionFactory f = (QueueConnectionFactory)ref;
QueueConnection connection = f.createQueueConnection();
Resource references:
                 <resource-ref>
          <res-ref-name>
            IBM_Queue_Factory
          </res-ref-name>
          <res-type>
            javax.jms.QueueConnectionFactory
          </res-type>
          <res-auth>
            Container
          </res-auth>
        </resource-ref>
If you are using 6.40 SP7 or below let me know to send you a patch.
Regards Nikola

Using external JMS provider

I am trying to use Tibco EMS as an external jms provider.
I created new factory (named TibcoFN) in JMSConnector service using visual administrator
Then I deployed and started it without any visible problem.
Then I created reference in a web.xml file of web application.
When I am calling lookup of initial context I always get naming exception.
What steps am I missing?
Piya

I am trying to use ActiveMQ as my external JMS provider and having a hard time doing so. I've deployed the activemq jar file in the JMS Connector service > library, and defined jms-factories.xml like:
<?xml version="1.0" encoding="UTF-8" ?>
<jms-factories>
<connection-factory>
    <factory-name>jms/ConnectionFactory</factory-name>
    <library-name>activemq</library-name>
    <context-factory-type>
      <link-factory-name>jmsfactory/default/QueueConnectionFactory</link-factory-name>
      <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>
      <provider-url>sapvm-vc:61616</provider-url>
      <security-principal></security-principal>
      <security-credentials></security-credentials>
    </context-factory-type>
</connection-factory>
</jms-factories>
But I am getting the following error:
Application error occurred during request processing.
Details:   org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'exampleManagerContainer' defined in class path resource [integrationContext.xml]: Invocation of init method failed; nested exception is java.lang.NoSuchMethodError: javax.jms.ConnectionFactory.createConnection()Ljavax/jms/Connection;
Exception id: [005056AB07A0005B0000004100000614000449BF8461CFBE]
Any ideas, please???
thanks,

JMS provider

Hello everyone,
          I need to send an alert message from the client to a server(which is
          remote). Can I use JMS for this?. If so can anyone please suggest me
          an open source JMS provider.
          Thank you,
          poornima


          poorni wrote:
          > Hello everyone,
          > I need to send an alert message from the client to a server(which is
          > remote). Can I use JMS for this?.
          Yes.
          If so can anyone please suggest me
          > an open source JMS provider.
          WebLogic has JMS built-in.
          > Thank you,
          > poornima

Tibco Remote Jms Provider - Auto-acknowledge

Similar Messages

Maybe you are looking for