| Author |
Message
|
| Unnamed |
 Posted: Tue Aug 23, 2005 1:28 am Post subject: Problems with using JMSAdmin |
 |
|
Newbie
Joined: 01 Aug 2005
Posts: 6
|
Hello.
I have some questions about correct usage of JMSAdmin.
Configurations:
WinXP, JDK 1.5 Update 4, WebSphere MQ 5.3 (Trial)
Goals:
Create and manipulate Administrative object throw console tool. (JMSAdmin)
(in future create stand alone application like in
http://www-128.ibm.com/developerworks/websphere/techjournal/0502_woolf/0502_woolf.html#sec3-4
)
Steps:
1. Installing JDK
2. Installing MQ
3. Create Queue Manager QMGR by using WebSphere MQ Explorer with Listener on 1414 port (only QueueManager without creating queue)
4. Download and extract ME01 and MS0B support packs.
5. Modify ClassPath in JMSAdmin.bat file:
set CLASSPATH=%CLASSPATH%;%MQ_JAVA_INSTALL_PATH%\lib\mqcontext.jar;%MQ_JAVA_INSTALL_PATH%\lib\com.ibm.mq.pcf.jar
6. Modify INITIAL_CONTEXT and PROVIDER_URL in JMSAdmin.config like:
INITIAL_CONTEXT_FACTORY=com.ibm.mq.jms.context.WMQInitialContextFactory
PROVIDER_URL=localhost:1414/SYSTEM.DEF.SVRCONN
7. Create sample script (script name - test.scp):
def qcf(SampleQCF) qmgr(QMGR) tran(client) chan(SYSTEM.DEF.SVRCONN) +
host(localhost) port(1414)
def q(SampleQueue) qmgr(QMGR) qu(SAMPLE.QUEUE)
8. Run JMSAdmin.bat :
JMSADmin.bat -t -v < test.scp
As result i have messages:
5648-C60, 5724-B41, 5655-F10 (c) Copyright IBM Corp. 2002. All Rights Reserved.
Starting Websphere MQ classes for Java(tm) Message Service Administration
Initialising JNDI Context...
INITIAL_CONTEXT_FACTORY: com.ibm.mq.jms.context.WMQInitialContextFactory
PROVIDER_URL: localhost:1414/SYSTEM.DEF.SVRCONN
JNDI initialisation failed, please check your JNDI settings and service
Queue Manager log:
23.08.2005 11:40:55
AMQ9503: Channel negotiation failed.
EXPLANATION:
Channel '' between this machine and the remote machine could not be established
due to a negotiation failure.
ACTION:
Tell the systems administrator, who should attempt to identify the cause of the
channel failure using problem determination techniques. For example, look for
FFST files, and examine the error logs on the local and remote systems where
there may be messages explaining the cause of failure. More information may be
obtained by repeating the operation with tracing enabled.
----- amqrmsaa.c : 572 --------------------------------------------------------
23.08.2005 11:40:55
AMQ9228: The TCP/IP responder program could not be started.
EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason
code was 0.
Part of majms.trc from WebSphere MQ Services -> Trace
...
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mq.MQInternalCommunications@929206
<== parseInitialDataResponse (via exception)() exit
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
==> MQException constructor(cc, rc, source, msgid)() entry
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
common/javabase/com/ibm/mq/MQException.java, java, j530, j530-L020820 02/08/09 13:29:42 @(#) 1.39
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
cc = 2
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
rc = 2195
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
source = null
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
msgId = 61
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
Explanation is 'MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported
by queue manager'
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
<== MQException constructor() exit
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
==> MQInternalException constructor (cc, rc, msgId)() entry
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
@(#) common/javabase/com/ibm/mqservices/MQInternalException.java, java, j530, j530-L020820 02/08/20 12:32:40
11:53:33 [1124783613456] Thread: main, Object: com.ibm.mqservices.MQInternalException:
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager
<== MQInternalException constructor() exit
11:53:33 [1124783613456] Thread: main Class: MQSESSIONClient MQException occurred whilst
connecting
11:53:33 [1124783613456] Thread: main <== MQSESSIONClient::MQCONN() exit
...
What does it all means and what should i do to create administrative objects by JMSAdmin.
By using search i found this topic that simmilar to my problem
http://www.mqseries.net/phpBB2/viewtopic.php?t=22804&highlight=2195
but it didn`t help me.
Maybe i didn`t understande some things?
Any help is welcome.
Thanks in advance. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Aug 23, 2005 3:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Since you're just testing stuff, try using a bindings connection rather than a client connection.
Particularly since you're using a trial version of MQ, client connections may be problematic.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Unnamed |
| Posted: Tue Aug 23, 2005 5:22 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2005
Posts: 6
|
Thanks for answer jefflowrey.
But I am newbie in MQ. Can you explain how should I modify settings in configure files to work in bindings mode? As i know I can change the transport type for a connection factory by using the setTransportType() method in code. But I use only JMSAdmin.
Best regards. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Aug 23, 2005 5:44 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Quote: |
| PROVIDER_URL=localhost:1414/SYSTEM.DEF.SVRCONN |
I don't think you want to be using WMQ as your provider URL. You should be using a file system context if you are just playing around:
| Code: |
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
PROVIDER_URL=file:/c:/support/jms/jmsadmin
SECURITY_AUTHENTICATION=none |
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 23, 2005 5:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
He's using support pack ME01.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Aug 23, 2005 6:27 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
Step 4....I see it now.....I should have guessed that I was missing something when you didn't make a comment about what he was using....  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 23, 2005 6:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, I'm probably missing something, as I've never used that support pack... and in general, JNDI is not in my core skill set.
But maybe it is the PROVIDER_URL that is the problem... should that have a different format? Shouldn't it have a protocol identifier?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Aug 24, 2005 12:20 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I just downloaded and gave ME01 a quick test. It worked for me. I followed your basic steps (except I didn't actually try to create anything). As far as the switch to bindings mode, change your PROVIDER_URL to be:
PROVIDER_URL=your.qmgr.name
This will remove the network from being a possible problem. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 24, 2005 12:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Can you specify the CCSID of the qmgr and the CCSID of your platform
See error message:
| Quote: |
MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE020: CCSID not supported by queue manager |
 |
|
| Back to top |
|
|
| Unnamed |
| Posted: Thu Aug 25, 2005 4:32 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2005
Posts: 6
|
| CCSID of Qmgr - 866 and there is CCSID 866 and other on my platform (OS: WinXP) |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Aug 25, 2005 4:56 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| The 2195 error should also create an *.FDC file. I'd take a look at it to see if it sheds any light on what is wrong. |
|
| Back to top |
|
|
| Unnamed |
| Posted: Thu Aug 25, 2005 4:59 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2005
Posts: 6
|
a little bit more info.
1. Create qmgr with name QMGR
2. Set PROVIDER_URL=QMGR in JMSAdmin.config.
3. Start JMSAdmin (JMSAdmin -t -v)
Result:
Have same msg:
JNDI initialisation failed, please check your JNDI settings and service
But new error descriptions in qmgr error log 
25.08.2005 16:34:11
AMQ6047: Conversion not supported.
EXPLANATION:
WebSphere MQ is unable to convert string data tagged in CCSID 819 to data in
CCSID 866.
ACTION:
Check the WebSphere MQ Application Programming Reference Appendix and the
appropriate National Language Support publications to see if the CCSIDs are
supported by your system.
----- amqvxcca.c : 511 --------------------------------------------------------
25.08.2005 16:34:11
AMQ6174: The library C:\Program Files\IBM\WebSphere MQ\exits\MQADMIN.dll was
not found. The queue manager will continue without this module.
EXPLANATION:
The dynamically loadable file C:\Program Files\IBM\WebSphere
MQ\exits\MQADMIN.dll was not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.
Try to find 819 code page in OS codepages but didn`t find.. 
Also i didn`t understand: Does second error conserned with first?
Strange. Also i try to repeat same sequence of steps like i discribes in first post with WebSphere MQ v6 (Trial) all works fine. |
|
| Back to top |
|
|
| Unnamed |
| Posted: Thu Aug 25, 2005 5:09 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2005
Posts: 6
|
| bower5932 wrote: |
| The 2195 error should also create an *.FDC file. I'd take a look at it to see if it sheds any light on what is wrong. |
No fdc files found |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Aug 25, 2005 12:23 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Unnamed wrote: |
| Try to find 819 code page in OS codepages but didn`t find.. |
819 is the standard CCSID for Unix qmgrs (en_US).
Enjoy |
|
| Back to top |
|
|
| Unnamed |
| Posted: Thu Aug 25, 2005 8:58 pm Post subject: |
|
|
Newbie
Joined: 01 Aug 2005
Posts: 6
|
| But what should I do to resolve this problem, I don`t find 819 CCSID in "Regional options and settings -> Advanced -> code page conversion settings. Maybe I must find in other place? And why did conversion error apear if qmgr CCSID is 866 and in OS code pages 819 not found? |
|
| Back to top |
|
|
|
|
