| Author |
Message
|
| bamboozled_by_MQ |
 Posted: Thu Oct 07, 2004 9:15 am Post subject: JMS point to point issue |
 |
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
hello all,
I followed the direction for this demo to the 'T' that vennella posted it looks perfect but... I am getting this error. when I am performing the last step, running it..
| Code: |
IBM WebSphere Application Server, Release 5.0
J2EE Application Client Tool
Copyright IBM Corp., 1997-2002
WSCL0012I: Processing command line arguments.
WSCL0001I: Command line, property file, and system property arguments resolved to:
File to launch = C:/Documents and Settings/user1/My Documents/IBM/wsad/workspace100/JMSTutorialsEAR
CC Property File = null
Client Jar File = <default>
Alternate DD = null
BootstrapHost = XPWRKSTN
BootstrapPort = <default>
Trace enabled = false
Tracefile = null
Init only = false
Classpath Parameter = null
Security Manager = disable
Security Manager Class = Not used. -CCsecurityManager=disable
Security Manager Policy = Not used. -CCsecurityManager=disable
Exit VM = false
Soap Connector Port = null
Application Parameters =
WSCL0013I: Initializing the J2EE Application Client Environment.
WSCL0600I: Binding HandleDelegate object.
WSCL0031I: The object was bound successfully.
WSCL0900I: Initializing and starting components.
WSCL0910I: Initializing component: com.ibm.ws.activity.ActivityServiceComponentImpl
WSCL0911I: Component initialized successfully.
WSCL0901I: Component initialization completed successfully.
WSCL0035I: Initialization of the J2EE Application Client Environment has completed.
WSCL0014I: Invoking the Application Client class PointToPoint
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2012
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:246)
at com.ibm.mq.MQJDManagedConnectionFactoryJ11._createManagedConnection(MQJDManagedConnectionFactoryJ11.java:128)
at com.ibm.mq.MQJDManagedConnectionFactoryJ11.createManagedConnection(MQJDManagedConnectionFactoryJ11.java:146)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:171)
at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:737)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:671)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:452)
at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1698)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1168)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:170)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:80)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:145)
at PointToPoint.<init>(PointToPoint.java:33)
at PointToPoint.main(PointToPoint.java:92)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:616)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:420)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'WAS_localhost_server1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:556)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1775)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1168)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:170)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:80)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:145)
at PointToPoint.<init>(PointToPoint.java:33)
at PointToPoint.main(PointToPoint.java:92)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:616)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:420)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
|
when looking at 2012 in the messages redbook, it says environment not set????
what am I doing wrong?
I am on winxp and I installed WMQ5.3 server and WSAD 5 (i dont think i used embedded messging install)
thanks |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Oct 07, 2004 10:20 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
failed to create MQQueueManager for 'WAS_localhost_server1'
|
I got the same error first time
http://www.mqseries.net/phpBB2/viewtopic.php?t=10842&highlight=admin+console
That article is pretty good for writing the application.
The only part that you need to change is, defining the JNDI resources.
You need to open the admin console and define them yourself instead of how it is specified in the article.
If you have a problem let me know and I 'll try to post the steps for you |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Thu Oct 07, 2004 3:11 pm Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
ok, thank you venny.
after reading your post I went into WSAD
into Server Configuration,
selected the 'Configuration' tab
I checked the chekbox saying 'Enable Administration Console'
I started the server and logged into http://localhost:9090/admin/
and VOILA!
**NOTE I am using WSAD 5(no embedded msg) instead I installed WMQ5.3 server to use the real deal
now that I am in there, should I now go to > resources > websphere MQ JMS providers> and scroll to the bottom and set QCF and destQ like the article said???
thanks alot |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Oct 07, 2004 3:35 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
now that I am in there, should I now go to > resources > websphere MQ JMS providers> and scroll to the bottom and set QCF and destQ like the article said???
|
Yup
That's what you neeed to do. |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Thu Oct 07, 2004 4:24 pm Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
what do i put in for BASE QUEUE NAME..
OR should i just install the embedded messaging and then use :
resources > websphere JMS provider instead of
resources > websphere 'MQ' JMS provider?
thanks again |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Fri Oct 08, 2004 5:41 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
okay I deleted everything in the wsad config and went instead to the the admin console and added the objects, now here is what I am getting:
| Code: |
IBM WebSphere Application Server, Release 5.0
J2EE Application Client Tool
Copyright IBM Corp., 1997-2002
WSCL0012I: Processing command line arguments.
WSCL0001I: Command line, property file, and system property arguments resolved to:
File to launch = C:/Documents and Settings/user1/My Documents/IBM/wsad/workspace100/JMSTutorialsEAR
CC Property File = null
Client Jar File = <default>
Alternate DD = null
BootstrapHost = XPWRKSTN
BootstrapPort = <default>
Trace enabled = false
Tracefile = null
Init only = false
Classpath Parameter = null
Security Manager = disable
Security Manager Class = Not used. -CCsecurityManager=disable
Security Manager Policy = Not used. -CCsecurityManager=disable
Exit VM = false
Soap Connector Port = null
Application Parameters =
WSCL0013I: Initializing the J2EE Application Client Environment.
WSCL0600I: Binding HandleDelegate object.
WSCL0031I: The object was bound successfully.
WSCL0900I: Initializing and starting components.
WSCL0910I: Initializing component: com.ibm.ws.activity.ActivityServiceComponentImpl
WSCL0911I: Component initialized successfully.
WSCL0901I: Component initialization completed successfully.
WSCL0035I: Initialization of the J2EE Application Client Environment has completed.
WSCL0014I: Invoking the Application Client class PointToPoint
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:239)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:276)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:296)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:171)
at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:737)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:671)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:452)
at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1698)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1168)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:170)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:80)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:145)
at PointToPoint.<init>(PointToPoint.java:33)
at PointToPoint.main(PointToPoint.java:92)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:616)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:420)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:WAS_localhost_server1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:556)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1775)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1168)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:170)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:80)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:145)
at PointToPoint.<init>(PointToPoint.java:33)
at PointToPoint.main(PointToPoint.java:92)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:616)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:420)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
|
am i getting these errors becuase I did not install embedded message with WSAD or what?
thanks |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Oct 08, 2004 7:34 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
Your exception above shows two things of interest:
- A 2059 return code: Queue manager unavailable
- WAS_localhost_server1: The qmgr name for an embedded JMS queue manager with WSAD
You should be able to issue the dspmq command to confirm that you actually have a WAS_localhost_server1 qmgr. Your last comment above leads me to believe that you didn't select embedded JMS so you probably don't have this qmgr and that is why you are getting the errors. |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Fri Oct 08, 2004 8:44 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
no i did not install embedded messaging..
when I did dspmq it show the one I created in full WMQ5.3 and it is running,
so you are syaing I need to instlal the embedded messaging and try again?
or is there any way I use the webshere one.... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Oct 08, 2004 8:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| bamboozled_by_MQ wrote: |
| when I did dspmq it show the one I created in full WMQ5.3 and it is running, |
Is it named EXACTLY (case matters!) 'WAS_localhost_server1'?
If not, that is the problem. You need to use the correct name of the queue manager.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Oct 08, 2004 9:00 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| or is there any way I use the webshere one.... |
For your QCF that you defined through admin console, there is a QMANAGER name property. There give the QUEUE MANAGER that you created using full MQ |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Fri Oct 08, 2004 10:05 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
LOL
right after I installed embedded messaging, I read your post Venny.
I went and added the QMname to use my full WMQ and VOILA!!!!!
it worked
thanks so much,
I learn so much from this site, I love it. |
|
| Back to top |
|
|
|
|
