| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| using JMS in WSAD |
« View previous topic :: View next topic » |
| Author |
Message
|
| hagai2003 |
 Posted: Sun Jun 08, 2003 2:44 am Post subject: using JMS in WSAD |
 |
|
Novice
Joined: 08 Jun 2003
Posts: 15
|
I'm using WSAD version 5.0.
Must i install the embedded messaging feature of the wsad in order to use JMS ? as i read in the wsad installation pdf, i can use mq-series 5.3 servers as jms providers without installing it, but i can't configure it (the wsad) beacuse there seems to be some menus missing.
Any ideas why ? should i install the embedded messaging no matter what ? (the problem is i don't have it)
thanks,
Hagai. |
|
| Back to top |
|
 |
| jackie |
| Posted: Tue Jun 10, 2003 12:29 pm Post subject: |
|
|
Novice
Joined: 01 Jun 2003
Posts: 20
Location: NYC
|
It depends on what you want to do. If you are doing only client connection, you don't need MQ Series installed on your machine.
1. Once you created Server project, go to admin console, go to Websphere MQ JMS and bind MQ objects with your JNDI name such as "jms/SendQCF" and "jms/SendQueue". Even you can add lot more configruation through the admin console.
2. After that, go through EJB reference bind and pretty much good to go.
3. Add all com...mq.jar, com..mqjms.jar,... to your classpath
4. make sure your JNDI context factory--I think you need namingserver.jar and implfactory.jar also.
5. Bind MQ JMS objects with your app.
I think these are pretty much I did go through. But expect lot more problems ahead.
good luck, |
|
| Back to top |
|
|
| shilpooa |
| Posted: Tue Jun 24, 2003 6:57 pm Post subject: |
|
|
Newbie
Joined: 24 Jun 2003
Posts: 1
|
I am still getting the foolwoing errror
[6/24/03 22:52:20:329 EDT] 67b22ecb SystemOut O key, TIMEZONE, not found
[6/24/03 22:52:22:271 EDT] 67b22ecb FreePool E J2CA0046E: Method createManagedConnctionWithMCWrapper caught an exception during creation of the ManagedConnection for resource JMS$EAST_FACTORY, throwing ResourceAllocationException. Original exception: javax.resource.spi.ResourceAdapterInternalException: createQueueConnection failed
at com.ibm.ejs.jms.JMSCMUtils.mapToResourceException(JMSCMUtils.java:123)
at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:174)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:156)
at com.ibm.ejs.jms.JMSManagedQueueConnection.<init>(JMSManagedQueueConnection.java:64)
at com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory.createManagedConnection(WSJMSManagedQueueConnectionFactory.java:84)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:387)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1106)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:897)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1065)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:560)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:374)
at com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConnection(JMSQueueConnectionFactoryHandle.java:80)
Next Linked Exception:
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'MQTEST.BANKOFAMERICA.COM:CSTAX1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:960)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:159)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:215)
at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:163)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:156)
at com.ibm.ejs.jms.JMSManagedQueueConnection.<init>(JMSManagedQueueConnection.java:64)
at com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory.createManagedConnection(WSJMSManagedQueueConnectionFactory.java:84)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:387)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1106)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:897)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1065)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:560)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:374)
at com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConnection(JMSQueueConnectionFactoryHandle.java:80)
| jackie wrote: |
It depends on what you want to do. If you are doing only client connection, you don't need MQ Series installed on your machine.
1. Once you created Server project, go to admin console, go to Websphere MQ JMS and bind MQ objects with your JNDI name such as "jms/SendQCF" and "jms/SendQueue". Even you can add lot more configruation through the admin console.
2. After that, go through EJB reference bind and pretty much good to go.
3. Add all com...mq.jar, com..mqjms.jar,... to your classpath
4. make sure your JNDI context factory--I think you need namingserver.jar and implfactory.jar also.
5. Bind MQ JMS objects with your app.
I think these are pretty much I did go through. But expect lot more problems ahead.
good luck, |
|
|
| Back to top |
|
|
| tlinus2 |
| Posted: Wed Aug 20, 2003 1:23 pm Post subject: wsas wsad 5.0 / mq configuration? |
|
|
Novice
Joined: 20 Aug 2003
Posts: 12
Location: Wash DC
|
Jackie
Were you able to connect WSAS to a MQ sitting on a different box?
I'm getting a jndi NameNotFound error when I try to connect WSAS with the MQ JMS Provider qcf jndi setting.
Thanks in advance
Linus |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Aug 21, 2003 8:14 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I'm not sure what is wrong here. However, it looks like you are using an external qmgr ('MQTEST.BANKOFAMERICA.COM:CSTAX1' ) rather than the embedded JMS. I'd double-check that you actually have this qmgr up and running. The other thing to check would be the parameters that you have specified on your QCF to confirm they are what you want.
I've used both full MQ and embedded JMS when running with WSAD. I've also used both when running with WSAS. I've found that for quick and dirty things, the embedded JMS works perfectly fine. It gives me less to administer and know about. When I want to try and get fancy, I've found the full MQ to be the way to go.
One other consideration to make is what you'll be doing with the MQ. If you will be leaving the J2EE environment (eg, getting to a legacy system), you'll need full MQ to do this. The embedded JMS has a restricted license. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
