JMS Queue connection

Hi Experts ,
I have a sticky problem while posting the data from JMS to File System ,
in CC monitoring i got success message that adapter is successfully connected to JMS queue but no data is available while checking 'sxmb_moni'
Note :in this requirement we are doing content conversion in JMS Sender adapter
we r not able to get the data into XI even we connected to JMS with all the proper connections of the JMS queue
the mesage we got in the CC:Sucessfully connected to destination 'jms/queue/SendEscFeedweblogic_DXG'
help me how to get the data into XI for Suitable reward
Thanks
Shoukath

hi shoukath,
Can you check in message monitoring, to check out audit logs and we come to what is the error exactly.
or even you can check the logs at
http://<Hostname>:<portnumber>/MessagingSystem/monitor/monitor.jsp
regards
Ramesh P

Similar Messages

How to create a JMS queue linked to external (remote) JMS server?

Hello,
I'm trying to receive messages from a remote JMS queue. I found some information on the Internet on how to create an external JNDI resource (my remote JMS queue connection factory is bound to LDAP context on remote box). I was able to configure JNDI resource that points to remote queue connection factory, but I don't know what to do next.
How can I create a local JMS destination (queue) that will be the image of the remote queue? At least I'm guessing this is what needs to be done in order to deploy MDBs.
I would appreciate it if someone could tell me how to get this working. Maybe the steps I took were not in the right direction - the bottom line is that JMS queue and queue connection factory are deployed on a remote server, and I need to get messages sent to them on the local server. I'm using Sun App Server from J2EE 1.4.
Thank you,
Mark

Please refer to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6377822, particularly the evaluation. Could your situation be the same too (i.e server ip address changing dynamically)? Also, which OS are you using and do you have any firewalls setup that prevents access to port 3700?

Need help to connect tibco jms queues from OSB

Hi,
We have a requirement in our project "to connect tibco JMS Queues from OSB".
The Queres are created by some othes in remote system, they provided us the details to connect the Queue. the detail are:
Queue Name :EXT_WEALTHHUB.TO_EXT.SYNC.REQ
Jndi Factory :SSLQueueConnectionFactory
and hostName , PORT
Credentails are provided.
We entered the same details in Business service in transport page by choosing 'jms' as protocol and EndpointURI as.
"jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.REQ"
And we created a service account to maintain the credentials and browsed the same at service account in the business service.
In JMS Transport Page we selected
Response Queue : One for all Request URI's
Response Pattern : JMS CorrelaltionID
Response UI :jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.RESP
when we are trying to establish a connection with the above queue getting
javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: er.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
     at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
     at weblogic.jms.common.CDS$1.run(CDS.java:436)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: in.checkLoginSuccess(Login.java:131)
     at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:403)
     at weblogic.rjvm.t3.ConnectionFactoryT3.createConnection(ConnectionFactoryT3.java:34)
     at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1777)
     at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1417)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:437)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     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:198)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl$2.run(MessageDrivenBeanInfoImpl.java:748)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.doPrivilagedAction(MessageDrivenBeanInfoImpl.java:2238)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
     at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
     at weblogic.jms.common.CDS$1.run(CDS.java:436)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:532)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:158)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentM
Any pointers on how to resolve the above issue will be a greate help to us.
Thanks in Advance

Wrong forum, please ask this on dedicated weblogic or soa forums

Are Connection Factory and JMS Queue supposed to be in JNDI tree

I have created Connection Factory and JMS Queue. I am expecting to find both in JNDI tree. Where, in the http://localhost:7001/console/consolejndi.portal, could I find them? I mean, in which branch of the JNDI tree?

Hi,
You should find them following exactly the way you define their JNDI Names... Make sure you are looking into the JNDI tree for the right managed server... Pay attention into the targets of your connection factory and queue...
For example, a JNDI name jms.myConnectionFactory (or jms/myConnectionFactory) targeted to soa_server1 will appear under soa_server1 / jms / myConnectionFactory ...
Hope this helps...
Cheers,
Vlad

Connecting to third party JMS Queue using Patchbay

Hi All,
We are trying to connect to a third party JMS queue configured in a remote weblogic server using ATG patcbay. We have configured the provider in dynamoMessagingSystem.xml and created a InitialContextFactory and provided all the queue configurations.
When it tries to initializes it is trying to create a dynamic queue and saying that JMSHelper class is not configured so that it cannot create the queue (The queue exists in the remote server). When we given configurations based on the details available under C:\ATG\ATG10.0.3\WebLogic\JMSProvider, it is saying that we have to provide a TopicConnectionFactory (We dont need to use any Topics). If we provide TopicConnectionFactory then it will say that your connection factory don't have any Topics configured.
I have read that for configuring with your application server's queue, this will try creating dynamic queues, but nowhere it is mentioned that how it will differentiate it is a third party queue or an application server queue.
In our case the application server and the remote server which acts as queue server are Weblogic.
Not sure why this is behaving like this and there is no proper documentation available in ATG that how to configure the third party queues using Patchbay.
Any pointers regarding this would be of great help.
Thanks,
R.

Hello kilgores. Welcome to the Apple Discussions!
Something to ask your IT staff is if they use a proxy server for Internet access. If so, do they require proxy configuration scripts (.pac) to provide access to the Internet through your company's firewall. This information would normally be added to your browser's settings.
For Safari: Preferences... > Advanced > Proxies > Change Settings... > Automatic Proxy Configuration

Connect from Weblogic JMS queue to SAP WAS JMS queue

Hi,
I am trying to setup a WLS 8.1 messaging bridge between a weblogic JMS queue and a SAP WAS JMS queue. I have configured a queue on both Weblogic and SAP WAS and I have set up the messaging bridge and bridge destintations in weblogic. However when weblogic tries to get the SAP initial context factory it fails with the error below.
I have added the SAP Client jars to the weblogic system classpath, and in the weblogic startup script but it still fails. Has anyone connected from an external JMS queue to a SAP WAS JMS queue that could provide me with some guidence?
<10/08/2006 08:23:45 AM WST> <Warning> <Connector> <BEA-190032> << Weblogic Mess
aging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocatio
nException of javax.resource.ResourceException: ConnectionFactory: failed to get
initial context (InitialContextFactory =com.sap.engine.services.jndi.InitialCon
textFactoryImpl, url = ux0800:55304, user name = username) on createManagedConnectio
n.>
Thanks
Warren

Stoyan,
Thanks for that.
My problem ended up being a classpath problem. I referenced the directory of the SAP jars in the weblogic start up script. When I changed this to reference each jar individually it worked.
I have a new issue now which may have something to do with security. The trace suggests it is logging on as the guest user, even though I entered my username and password in the Messaging bridge.
#1.5#000E7FED310600A30000008A0000302D00041AA399E338B4#1155189870559#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=BWIP#J2EE_GUEST#0####165536f0283611db8903000e7fed3106#SAPEngine_Application_Thread[impl:3]_126##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerInvalidDestinationException: No destination with ID=0 found.
        at com.sap.jms.server.service.impl.RegistryServiceImpl.getDestinationContext(RegistryServiceImpl.java:404)
        at com.sap.jms.server.sessioncontainer.InboundBus.getDestinationContext(InboundBus.java:98)
        at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:153)
        at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
        at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
        at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
        at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:635)
        at com.sap.jms.server.JMSServerFrame.request(JMSServerFrame.java:536)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Warren

How toset JMS_TIBCO_COMPRESS to true ,connecting to tibco jms queue frmBPEl

Hi ,
I m tryingto connect to tibco jms queue from BPEL .How can i set JMS_TIBCO_COMPRESS to true before placing message on the queue.
I am able to send and receive the messages from the queue but I m not able to compress it

Did you figure out a solution for this? I have the same need and I'm investigating using JAAS configuration to accomplish.

Siebel unable to connect to AIA JMS Queue

Hi All,
We are working on AIA 2.5 running on SOA Suite 10.1.3.4. We have installed the Order to Activate PIP. We are facing a problem when we try to sumit orders from Siebel. As per our understanding Siebel will put the message on the AIA_SALESORDERJMSQUEUE. However, when the Siebel tries to do so, it returns an error stating :
12:55:59.699 PM Wed Sep 8: Checking if exception is a connection exception
12:55:59.699 PM Wed Sep 8: CREATING_CONNECTION : is a Connection related exception
12:55:59.703 PM Wed Sep 8: Exception during Send:
oracle.jms.AQjmsException: Io exception: The Network Adapter could not establish the connection
We have tried telnetting from the Siebel server to the SOA server using the SOA hostname and the RMIS port and we were able to connect. We are struggling to resolve this issue and any inputs you may have is igly appreciated.
Thanks in advance for your time.
Thanks and Regards,
Saptarshi

Hi,
Ensure the following set up is done fine.
The following Java Archive (JAR) files are required to be installed on the Siebel Server (for example, in the C:\cp directory) to communicate with Oracle SOA Suite:
Siebel JMS JAR files:
Siebel.jar
SiebelJI_lang.jar, where lang is the language code of the default language of the Siebel installation
JAR files required for accessing the JMS provider. For the OC4J JMS Provider supplied with Oracle SOA Suite, the following files are required:
jms.jar
jta.jar
oc4jclient.jar
optic.jar
javaee.jar (obtained from the Java EE development kit)
jmxri.jar
jms.jar
j2ee_1.3.01.jar
jndi.properties file:
java.naming.factory.initial=oracle.j2ee.rmi.RMIInitialContextFactory
java.naming.provider.url=ormis://10.15.35.22:12701/default
java.naming.security.principal=oc4jadmin
java.naming.security.credentials=welcome1
In order to debug this issue try writing a java client to access the JMS queue with above properties. This will help you to find the root cause.
Regards,
Rahul

Trouble connecting to JMS queue

I created a JMS queue, but I can not get my client to connect to the queue
How can I dod this,
Should I use subdeployments ?
Thanks, Gideon

What error is your client getting? If it is a JNDI error, then there's likely a configuration error -- feel free to post your JMS server config (from your config.xml) and your JMS module config.
As for your question about subdeployments: If you're just experimenting with a simple developer setup, then you don't need subdeployments, otherwise I think one should always use subdeployments for destinations instead of default targeting (where each subdeployment consists of a list of one or more JMS servers), as subdeployments ensure that destinations will only activate on exactly the intended JMS servers. To keep things simple, I recommend configuring a single subdeployment per module (subds are sometimes called "advanced targeting" on the console), and configuring multiple modules when you have multiple target sets...
Tom

Testing ODI connectivity with Sonic MQ JMS Queue server

Hi
We are trying to integrate our ODI to sonic MQ.
Since I am a newbie , could you please guide me in creating a data server and connecting it through physical agent?
Below are the steps I did.
1. I have copied the below jar files in ../driver directory and bounce the agent.
mfcontext.jar sonic_Client.jar sonic_ASPI.jar sonic_XA.jar sonic_Selector.jar sonic_Crypto.jar jndi.jar
3. tesed the connectivity to the JNDI URL and port using 'telnet myserver 7530'
3. created a new JMS Queue Server with below setting.
JNDI Authentification: Simple
JNDI User :Administrator
Password :
JNDI Protocol : <undefined>
JNDI Driver: com.sonicsw.jndi.mfcontext.MFContextFactory
JNDI URL: tcp://myserver:7530
JNDI Resource: ODI_QUEUE.Entry
4. apply the changes
When I tried to test it I got the below messages.
java.lang.Exception:
     at com.sunopsis.graphical.l.pm.a(pm.java)
     at com.sunopsis.graphical.l.pm.s(pm.java)
     at com.sunopsis.graphical.l.pm.g(pm.java
     at com.sunopsis.graphical.l.pm.a(pm.jav)
     at com.sunopsis.graphical.l.pm.a(pm.java)
     at com.sunopsis.graphical.l.iz.actionPerformed(iz.java)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)

I think that you should update the Odiparams.bat in order to add the JMS driver files which are not in the path of the agent.
Stop your agent.
in the odiparams update one of the line
"set ODI_CLASSPATH" with the new files
and then restart your agent.

Connecting Tuxedo/Q to Weblogic as a JMS Queue

We are already using both Tuxedo and Weblogic Server. We are looking at integrating
Messaging into our design and to do so looking at Tuxedo/Q.
The question is: Can we use Tuxedo/Q for messaging and connect it as JMS Server so
that we can use Message driven beans in WLS ?

Yan,
The WTC gateway that is provided as part of WLS provides a tBridge feature,
which will map JMS queues in WLS onto /Q queues in Tuxedo. It sounds as if that
should meet your needs.
Take a look at http://e-docs.beasys.com/wls/docs70/wtc_admin/index.html and
http://e-docs.beasys.com/wls/docs70/wtc_admin/tBridge.html#1113215
Regards,
Peter.
Yan McNicoll wrote:
We are already using both Tuxedo and Weblogic Server. We are looking at integrating
Messaging into our design and to do so looking at Tuxedo/Q.
The question is: Can we use Tuxedo/Q for messaging and connect it as JMS Server so
that we can use Message driven beans in WLS ?

Weblogic JMS Client App fails creating queue connection

Using the example provided from installation: ...\bea\wlserver_10.0\samples\server\examples\src\examples\jms\queue\QueueBrowse.java
I can successfully connect and display the queue when this test app runs on the local Weblogic Server. When I run the test app on a remote server (not the Weblogic server), I get the following error:
Exception in thread "main" weblogic.jms.common.JMSException: [JMSClientExceptions:055053]Error creating connection to the server: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
     java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
     java.lang.NullPointerException
     at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:258)
     at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285)
     at weblogic.jms.client.JMSConnectionFactory.createQueueConnection(JMSConnectionFactory.java:165)
     at com.lodestarcorp.custom.QueueBrowse.init(QueueBrowse.java:53)
     at com.lodestarcorp.custom.QueueBrowse.main(QueueBrowse.java:129)
Caused by: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
     java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
     java.lang.NullPointerException
     at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:91)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:332)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
     at weblogic.jms.frontend.FEConnectionFactoryImpl_1001_WLStub.connectionCreateRequest(Unknown Source)
     at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:224)
     ... 4 more
Caused by: java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
     java.lang.NullPointerException
     at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:118)
     at weblogic.rmi.internal.DescriptorManager.getBasicRuntimeDescriptor(DescriptorManager.java:89)
     at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:55)
     at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:41)
     at weblogic.rmi.internal.OIDManager.makeServerReference(OIDManager.java:194)
     at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:175)
     at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceSmartStubInfo(RemoteObjectReplacer.java:116)
     at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:102)
     at weblogic.rmi.utils.io.InteropObjectReplacer.replaceObject(InteropObjectReplacer.java:62)
     at weblogic.utils.io.ChunkedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:40)
     at weblogic.utils.io.ChunkedObjectOutputStream$NestedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:141)
     at java.io.ObjectOutputStream.writeObject0(Unknown Source)
     at java.io.ObjectOutputStream.writeObject(Unknown Source)
     at weblogic.messaging.dispatcher.DispatcherWrapper.writeExternal(DispatcherWrapper.java:152)
     at weblogic.jms.frontend.FEConnectionCreateRequest.writeExternal(FEConnectionCreateRequest.java:98)
     at java.io.ObjectOutputStream.writeExternalData(Unknown Source)
     at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
     at java.io.ObjectOutputStream.writeObject0(Unknown Source)
     at java.io.ObjectOutputStream.writeObject(Unknown Source)
     at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:614)
     at weblogic.rjvm.MsgAbbrevOutputStream.writeObjectWL(MsgAbbrevOutputStream.java:605)
     at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:38)
     at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:87)
     ... 8 more
Caused by: java.lang.NullPointerException
     at weblogic.rmi.internal.BasicRuntimeDescriptor.createSkeletonClass(BasicRuntimeDescriptor.java:272)
     at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:158)
     at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:140)
     at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:110)
     ... 30 more
FYI: I did create the wlfullclient.jar from the installation.
Could the problem be related to a proxy issue? It's not a DNS problem (I've tested with the IP address).
Thanks,
Brian

I had this very same issue, in a project I was importing directly individual jars:
     <classpathentry kind="lib" path="lib/javax.jms_1.1.1.jar"/>
     <classpathentry kind="lib" path="lib/weblogic.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.identity_1.1.2.1.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager_1.9.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager.ja_1.9.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.transaction_2.7.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client.ja_1.8.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client_1.8.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.wls_1.0.0.0_6-1-0-0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.utils.full_1.9.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security_1.0.0.0_6-1-0-0.jar"/>
     <classpathentry kind="lib" path="lib/wlclient.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.utils.classloaders_1.8.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.management.core_2.8.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.descriptor_1.9.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.logging_1.8.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.timers_1.7.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.socket.api_1.2.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.digest_1.0.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.weblogic.lifecycle_1.4.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.store_1.7.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.common.security.api_1.0.0.0_6-1-0-0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.utils.wrapper_1.4.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.messaging.kernel_1.8.0.0.jar"/>
     <classpathentry kind="lib" path="lib/com.bea.core.utils.expressions_1.4.0.0.jar"/>
and everything was working;
in another project I was importing the "Weblogic System Libraries" libraries, and I was getting the NullPointerException...
I have the sensation that there is room for improvement in the way libraries are managed.

Unable to Connect to JMS Queue in Websphere from WLS 10.3,3

Hi Everyone,
I'm trying to connect to JMS Queue in WebSphere 7.1 from WLS 10.3.3, I'm trying to using Foreign server connection to connect to the Websphere JMS Queue. Its normal Queue not MQ Queue. I have configured the Foreign server but i know for the fact that some weblogic jar files are need on the WLS home. Does anyone let me know what is needed so that i can place them on the WLS home and restart the server.
Also i would like to consume and produce messages to the websphere queue.
Thanks for the help..
Regards
Sabir

Hi Everyone
Has anyone tried connecting to the websphere jms queue from WLS 10.3.3
Let me know if that can be done
regards
Sabir

Problem Connecting to JMS queue with C sharp client

Hi there,
I am trying to connect to a JMS queue using a C# client but i have a problem trying to connect. The problem comes in when i run the C# script a dialog box appears requesting a T3TransportFactory.cs which i do not have on the client. and when i close it i get an exception on
IContext context = ContextFactory.CreateContext(paramMap);
Exception - Failed to connect using URL <t3://10.103.130.18:7001>
StackTrace - at WebLogic.Messaging.Physical.T3TransportFactory.CreateT3Transport(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\T3TransportFactory.cs:line 226
at WebLogic.Messaging.Physical.ContextPhysical.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\ContextPhysical.cs:line 83
at WebLogic.Messaging.Context.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Context.cs:line 56
The stacktrace indicates that it is looking for a T3TransportFactory.cs file in that particular path on the client (This is my speculation) but this directory path does not exist on the client machine with the c# code.
I got a WebLogic.Messaging.dll referenced in my c# project and the ip/port numbers are correct (we know this cause we tried a java client that connected successfully)
Can anyone assist me on this issue?

The issue might be the dll file you are referring to. Did you use the dll from the weblogic installation folder (BEA_HOME/modules/com.bea.weblogic.jms.dotnetclient_1.X.X.X).
Refer - http://docs.oracle.com/cd/E15051_01/wls/docs103/jms_dotnet/install.html#wp1075258
Hope this helps.
Thanks,
Patrick

Connection Problem To "JMS Queue XML"

Hi.
I can't connect to the JMS Queue XML.While Creating Data Server using the JMS XML Queue Technology pointing to WLS and the XML document type definition (dtd ) file books.dtd is provided from the local(C:\Documents and Settings\348773\Desktop\XML FILES) directory. The connection details are as below:-
Definition Tab:
Connection:
User: userXXX
Password: passYYY
These are user name and password for the application server
JNDI tab:
JNDI Authorization: None
JNDI User/password (same as above)
JNDI Protocol: Undefined
JNDI Driver: weblogic.jndi.WLInitialContextFactory
JNDI URL: http://172.18.41.47:7001?d=C:\Documents and Settings\348773\Desktop\XML FILES\books.dtd&JMS_DESTINATION=jms/demoQueue
JNDI Resource:eis/ConnFact/Queue
FYI:-I h'v just copy and pasted the value of JNDI Driver(weblogic.jndi.WLInitialContextFactory) from a document because I don't know how to find the JNDI drivers name for WLS.I think it is a default name.If I'm wrong then Please tell me how to find it.when I test the connection it shows an error like this:-
java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.'.
     at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
     at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
     at com.sunopsis.sql.SnpsConnection.testConnection(SnpsConnection.java:1118)
     at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.getLocalConnect(SnpsDialogTestConnet.java:420)
     at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.localConnect(SnpsDialogTestConnet.java:860)
     at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.jButtonTest_ActionPerformed(SnpsDialogTestConnet.java:806)
     at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.connEtoC1(SnpsDialogTestConnet.java:165)
     at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.access$1(SnpsDialogTestConnet.java:161)
     at com.sunopsis.graphical.dialog.SnpsDialogTestConnet$IvjEventHandler.actionPerformed(SnpsDialogTestConnet.java:111)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2319)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
     at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:272)
     at java.awt.Component.processMouseEvent(Component.java:6289)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3268)
     at java.awt.Component.processEvent(Component.java:6054)
     at java.awt.Container.processEvent(Container.java:2042)
     at java.awt.Component.dispatchEventImpl(Component.java:4652)
     at java.awt.Container.dispatchEventImpl(Container.java:2101)
     at java.awt.Component.dispatchEvent(Component.java:4483)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
     at java.awt.Container.dispatchEventImpl(Container.java:2085)
     at java.awt.Window.dispatchEventImpl(Window.java:2479)
     at java.awt.Component.dispatchEvent(Component.java:4483)
     at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:644)
     at java.awt.EventQueue.access$000(EventQueue.java:85)
     at java.awt.EventQueue$1.run(EventQueue.java:604)
     at java.awt.EventQueue$1.run(EventQueue.java:601)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
     at java.awt.EventQueue$2.run(EventQueue.java:618)
     at java.awt.EventQueue$2.run(EventQueue.java:615)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:175)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:170)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:162)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.'.
     at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
     at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
     at oracle.odi.core.datasource.dwgobject.support.OnConnectOnDisconnectDataSourceAdapter.getConnection(OnConnectOnDisconnectDataSourceAdapter.java:74)
     at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter$ConnectionProcessor.run(LoginTimeoutDatasourceAdapter.java:217)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:139)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
     at java.lang.Thread.run(Thread.java:662)
Caused by: java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.'.
     at com.sunopsis.jdbc.driver.JMSXMLDriver.connect(JMSXMLDriver.java:113)
     at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:409)
     at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:385)
     at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:352)
     at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:331)
     ... 7 more
Caused by: java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.
     at com.sunopsis.jdbc.driver.JMSXMLConnection.<init>(JMSXMLConnection.java:295)
     at com.sunopsis.jdbc.driver.JMSXMLDriver.connect(JMSXMLDriver.java:99)
     ... 11 more
So,
please advise
Thanks
Anindya

Hi,
Hope till now you might have solved this problem.
If not lets do this below workout , we had same kind of problem.
in JNDI tab , you have JNDI authentication, this authentication is for JNDI resources, I am sure you might be using weblogic credentials.
Steps :
1. Clear JNDI User : Blank (No value)
2. Clear Password : Blank (No Value)
3. set JNDI Authentication as None, regenerate the scenario and check
For accessing JNDI responses , JMS XML Queue uses Connection parameters from Definition tab.
Hope this helps

JMS Queue connection

Similar Messages

Maybe you are looking for