| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMSAdmin start fail |
« View previous topic :: View next topic » |
| Author |
Message
|
| antelope |
 Posted: Mon Sep 26, 2005 11:39 pm Post subject: JMSAdmin start fail |
 |
|
Novice
Joined: 26 Sep 2005
Posts: 15
|
I have installed Webshpere MQ 6.0, and want to use JMSAdmin.
I modified JMSAdmin.config file as following:
INITIAL_CONTEXT_FACTORY=com.ibm.mq.jms.context.WMQInitialContextFactory
PROVIDER_URL=localhost:1414/SYSTEM.DEF.SVRCONN
and also put com.ibm.mq.pcf.jar and mqcontext.jar to classpath.
but when I run JMSAadmin.bat, it cause error:
[Root exception is com.ibm.mq.M
QException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager]
how to solve it? please help me. thx. |
|
| Back to top |
|
 |
| hopsala |
| Posted: Tue Sep 27, 2005 1:17 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Which OS are you using, and why use JMSAdmin.?
Did you look in the MQ error logs after installation? Any FDC's?
Search this site for MQJE020, you'll find some interesting things... |
|
| Back to top |
|
|
| antelope |
| Posted: Thu Sep 29, 2005 1:01 am Post subject: |
|
|
Novice
Joined: 26 Sep 2005
Posts: 15
|
| hopsala wrote: |
Which OS are you using, and why use JMSAdmin.?
Did you look in the MQ error logs after installation? Any FDC's?
Search this site for MQJE020, you'll find some interesting things... |
OS is windows XP.
Now I use factory "INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory", jmsadmin can run.
Before I think jmsadmin is a tool about create queue, topic...etc. But now I know it's only a mapping tool, right?
I only have WMQ, how can I test PUB/SUB, by the way, how to create topic in WMQ? |
|
| Back to top |
|
|
| JohnRodey |
| Posted: Thu Sep 29, 2005 2:16 am Post subject: |
|
|
Centurion
Joined: 13 Apr 2005
Posts: 103
|
You are correct, JMSAdmin is used to create JNDI mapping for your queues to be accessed via JMS.
To find out more about creating JMS applications using publish/subscribe (topics) check out the "WebSphere MQ Using Java" manual. There are also many examples around that show how to make use of pub/sub.
Note: You will still most likely need to make use of JMSAdmin to create the JNDI mapping to your topics.
I also noticed you use two different initial context factories :
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory AND INITIAL_CONTEXT_FACTORY=com.ibm.mq.jms.context.WMQInitialContextFactory
I would recommend if you are just starting to look at JMS w/ MQ to start with the "RefFSContextFactory" as this will write all your jndi definitions to a file, rather then "WMQInitialContextFactory" which will store these definitions in your qmgr (It might just add another layer of complexity). Although in time, if you have a distributed system, you may want to move to the qmgr repository or LDAP.
Hope this is of some help |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 29, 2005 3:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You do NOT need to use JMSAdmin to create "topics".
In fact, you do not need to use JMSAdmin at all.
You can follow the instructions in the Using Java manual in the section on JMS to dynamically create a Topic Connection Factory and a Topic, without doing anything other than writing Java.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JohnRodey |
| Posted: Thu Sep 29, 2005 5:28 am Post subject: |
|
|
Centurion
Joined: 13 Apr 2005
Posts: 103
|
Agreed.
You are talking about creating these JNDI object during runtime, correct?
I've never taken this road but will it lock you in to using MQ, with calls like "factory.setQueueManager(QMGRNAME);"? If so, doesn't that kind of defeat some of the purpose of using JMS, in case you change vendors it is abstracted from the application level?
I may be totally off since I've never created them during runtime though, that's why I said "You will still most likely need to make use of JMSAdmin" |
|
| Back to top |
|
|
| antelope |
| Posted: Fri Oct 07, 2005 6:38 pm Post subject: |
|
|
Novice
Joined: 26 Sep 2005
Posts: 15
|
Sorry, from Oct 1 to Oct 7, I have a long holiday.
Thanks for hopsala, john and jeff.
I read detail about Chapter 11. Writing WebSphere MQ JMS publish/subscribe
applications in using java manual.
My broken is WebSphere MQ Publish/Subscribe, and my WMQ version is 6.0. But when I check by "The publish/subscribe installation verification test", it failed. The following is message:
5724-H72, 5655-L82, 5724-L26 (c) Copyright IBM Corp. 2002,2005. All Rights Reser
ved.
Websphere MQ classes for Java(tm) Message Service 6.0
Publish/Subscribe Installation Verification Test
Creating a TopicConnectionFactory
Creating a Connection
Creating a Session
Creating a Topic
Creating a TopicPublisher
Creating a TopicSubscriber
Caught exception: com.ibm.mq.jms.NoBrokerResponseException: MQJMS5053: *** No br
oker response. Please ensure that the broker is running. If you are using the We
bSphere MQ broker check that your brokerVersion is set to V1 ***
linked exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 203
3
PSIVT finished
how to set brokerVersion?
And to John, I try to use INITIAL_CONTEXT_FACTORY=com.ibm.mq.jms.context.WMQInitialContextFactory(PROVIDER_URL=localhost:1414/JAVA.CHANNEL) to initiliaze context, but cause error:
MQJE020: CCSID not supported by queue manager. |
|
| 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
|
|
|
|
