| Author |
Message
|
| csmith28 |
 Posted: Mon Feb 28, 2005 2:22 pm Post subject: Resolved Java Client getting 2195 |
 |
|
Grand Master
Joined: 15 Jul 2003
Posts: 1197
Location: Arizona
|
I have some developers that are getting the following error when they attempt to put 20 messages at a time to my MQManager.
The are working from an XP-Pro box try connect as a remote Client to my AIX5.1.0.0/WMQ5.3.0.6 Server.
| Quote: |
2005.02.28 11:30:27 MQJMS1016E an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mqservices.MQI
nternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE046: Unsupported codeset : 0
Sender Thread# 1 Error=javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Det
ail: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE046: Unsupported codeset : 0 |
I told them about this,
| Quote: |
2195 X’0893’ MQRC_UNEXPECTED_ERROR
The call was rejected because an unexpected error occurred.
Corrective action: Check the application’s parameter list to ensure, for example, that the
correct number of parameters was passed, and that data pointers and storage keys are valid. |
When they do this I don't see any activity in my ~qmgrs/QMGR/error/AMQERR01.LOG but they do seem to be causing the following FFST to be created:
| Quote: |
| Date/Time :- Monday February 28 13:33:15 PST 2005 |
| Host Name :- mqserver (AIX 5.1) |
| PIDS :- 5724B4101 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC035021 |
| Application Name :- MQM |
| Component :- xcsCreateThread |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00006800 (mqm) |
| Program Name :- amqrmppa |
| Process :- 00040458 |
| Thread :- 00000001 |
| QueueManager :- OAX06 |
| Major Errorcode :- xecP_E_NO_RESOURCE |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 1 | |
I found this on the IBM Website but I don't think it applies:
| Quote: |
Support & downloads >
A Java client application using a connection pool of size 100 fails to start with FDC Probe Id of XC035021.
Technote (FAQ)
Problem
A Java client application using a connection pool of size 100 fails to start with FDC Probe Id of XC035021.
Cause
A heavily loaded system may run short of available memory.
Solution
As a 32-bit application WebSphere® MQ has a restriction on available memory resources. Reduce the size of the connection pool.
Historical Number
34674 B122 C000
Product Alias/Synonym
WebSphere MQ
WMQ
MQ |
The message data from the FFST is just garbage characters.
If anyone has seen this before or has any ideas about what the problem may be I would appreciate your input.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Last edited by csmith28 on Fri Mar 04, 2005 12:44 pm; edited 1 time in total |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Mar 01, 2005 5:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Unsupported codeset seems like a hint. It may be a red herring, but it's probably worth reviewing the code and environment for CCSID/Encoding settings validity.
Also, there might be errors on the XP box, either in the Event Viewer or in the Client error directory.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| malammik |
| Posted: Tue Mar 01, 2005 8:31 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
|
| Back to top |
|
|
| clindsey |
| Posted: Tue Mar 01, 2005 9:12 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Chris, I believe this is due an AIX problem documented in IY15770. It references a local fix in IY25655. I think you can search the IBM site and read about these. Applying the local fix depends on whether you are using inetd listener or runmqlsr.
For runmqlsr, export AIXTHREAD_SCOPE=S in the shell where the program is launched. For inetd, you have to add this export to /etc/environment.
You can contact WMQ support if you need to get the official details.
Charlie |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Mar 04, 2005 12:45 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1197
Location: Arizona
|
Unsupported codeset
nuff said.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Mar 04, 2005 2:26 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| csmith28 wrote: |
Unsupported codeset
nuff said. |
Developers, ehh? 
Fixed it, did you?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Mar 04, 2005 3:00 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1197
Location: Arizona
|
No actually, fixed it they did,  but then they didn't bother to actually tell me they fixed it. So I was still researching the problem.
Then suddenly I get this email that says they performed a successful Stress Test.
So I asked them how they fixed it and they told me not to worry about it. 
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Mar 04, 2005 3:42 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| csmith28 wrote: |
| they told me not to worry about it. |
Then I guess it's a low priority error the next time it happens... 
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rehab_desoki |
| Posted: Mon Apr 16, 2007 11:28 pm Post subject: This happen with me also |
|
|
Novice
Joined: 25 Oct 2005
Posts: 18
|
I make an application to listen from a file system and if there any message it consume it and send it to the MQ queue but when i left the sender listener running for many hours it give me the same exception u get
MQJMS1016: an internal error has occurred
but when i stop this sender listener and start it again it can send to MQ succesfully , but i dont know why that happen , do u have any idea |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 16, 2007 11:37 pm Post subject: Re: This happen with me also |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rehab_desoki wrote: |
I make an application to listen from a file system and if there any message it consume it and send it to the MQ queue but when i left the sender listener running for many hours it give me the same exception u get
MQJMS1016: an internal error has occurred
but when i stop this sender listener and start it again it can send to MQ succesfully , but i dont know why that happen , do u have any idea |
I have no idea why you've added this to the bottom of a thread last posted on in 2005, which on the face of it has nothing to do with your problem! 
Turning to your problem, the error message you post is so generic as to be meaningless. You at least need the linked exception with an MQ reason code to give some reasonable chance of us working out what's going on.
You might also want to post some details about what platform this is, what version of MQ you're using (patched to what level), some detail about your application rather than "listen from a file system". Does it run standalone, under WAS, how does it connect to MQ, etc, etc?
You might also want to post a few details about what you've already tried to fix this, if only to stop us posting possible fixes that have already failed.
There's a sticky "How to ask questions the smart way" I recommend at moments like this. It contains (IMHO) valuable information not only on how to get the best from the forum, but valuable tips on problem solving.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pabloparets |
| Posted: Sat May 05, 2007 5:28 pm Post subject: MQJE046: Unsupported codeset : 0 |
|
|
Novice
Joined: 05 May 2007
Posts: 11
|
| I have the same problem, when I'm trying to send messages to a queue with a jms java program from a XP Box, the same program runs ok from a windows 2000 box, any idea how to fix this problem? |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun May 06, 2007 9:43 am Post subject: Re: MQJE046: Unsupported codeset : 0 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pabloparets wrote: |
| I have the same problem, when I'm trying to send messages to a queue with a jms java program from a XP Box, the same program runs ok from a windows 2000 box, any idea how to fix this problem? |
And I repeat my comments above - why are you adding this to such an old post?
Also how do you know it's the same problem - a 2195 can be caused by a variety of issues? What does the linked exception say? What platform are you running on? What version of MQ? Patched to what level? Running in what environment (WAS etc)?
Read the sticky I mention above. It will hel us to help you if you post specific queries.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pabloparets |
| Posted: Sun May 06, 2007 9:55 am Post subject: MQJE046: Unsupported codeset : 0 |
|
|
Novice
Joined: 05 May 2007
Posts: 11
|
Hi thanks for response , I have a JMS client application ussing the jars provided by MQ client 6, when I run this client on a Windows2000 plataform there is no problem, but when the client plataform is a Windows XP get the "MQJE046: Unsupported codeset : 0" error. the MQ server is from a third party, i don't known what plataform they are using, and i don't known how to figure that.
this is the error I get :
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueue.putMsg2(MQQueue.java:1688)
at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1792)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1130)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1183)
at com.atsi.jms.AbstractQueueHandler.sendMessage(AbstractQueueHandler.java:951)
at com.atsi.jms.AbstractQueueHandler.sendTextMessage(AbstractQueueHandler.java:933)
at com.atsi.jms.AbstractQueueHandler.writeMessage(AbstractQueueHandler.java:447)
at com.atsi.acex.ChannelHandler.sendFiles(ChannelHandler.java:347)
at com.atsi.acex.ChannelHandler.sendOutgoing(ChannelHandler.java:223)
at com.atsi.acex.ChannelHandler.execute(ChannelHandler.java:175)
at com.atsi.acex.Main.run(Main.java:221)
at java.lang.Thread.run(Thread.java:619)
2007.05.05 20:36:01 MQJMS1016E an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE046: Unsupported codeset : 0 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun May 06, 2007 12:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
you have 2 different errors here:
| Quote: |
| Completion Code 2, Reason 2009 |
Search the forum. This has already been discussed to death...
| Quote: |
Completion Code 2, Reason 2195
MQJE046: Unsupported codeset : 0 |
Check your code. According to some other posts on the forum this is either a CCSID problem that you did not set right or a thread safety coding issue...
Be sure if you add any MQ header that you cannot use 0 as default CCSID on this added header. You need to set the real value. 0 as default CCID only works on the MQMD....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| pabloparets |
| Posted: Sun May 06, 2007 12:39 pm Post subject: MQJE046: Unsupported codeset : 0 |
|
|
Novice
Joined: 05 May 2007
Posts: 11
|
Hi, thakns for the answer ,this is the complete trace I am getting trying to put 3 messeges on the queue, the extrage thing is the same program works fine on a windows2000 box, but not in a XP.
that's is the reason i am discarting a thread safety coding issue....
regarding the CCSID i'm not setting it. I think that it come from the .bindings file , the one say that are using a 819 codeset.
I need to explicit set the CCSID? how I do that?.
I try to set it on the queue doing it :
queue:///queue?targetClient=1?CCSID=918
but it does not work.
it's the complete trace:
init:
deps-jar:
compile-single:
Non-existing path "C:\Program Files\Java\jdk1.6.0_01\jre\lib\sunrsasign.jar" provided.
Non-existing path "C:\Program Files\Java\jdk1.6.0_01\jre\classes" provided.
INFO: File logging initialized; see log file for further messages: acex.log
INFO: using application home directory = 'C:\devel\ATS_ACEXII'
INFO: using configuration directory = 'C:\devel\ATS_ACEXII/conf'
INFO: using log files directory = 'C:\devel\ATS_ACEXII/logs'
May 6, 2007 4:16:40 PM com.atsi.acex.Main <init>
INFO: Starting execution loop...
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueue.putMsg2(MQQueue.java:1688)
at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1792)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1130)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1183)
at com.atsi.jms.AbstractQueueHandler.sendMessage(AbstractQueueHandler.java:951)
at com.atsi.jms.AbstractQueueHandler.sendTextMessage(AbstractQueueHandler.java:933)
at com.atsi.jms.AbstractQueueHandler.writeMessage(AbstractQueueHandler.java:447)
at com.atsi.acex.ChannelHandler.sendFiles(ChannelHandler.java:347)
at com.atsi.acex.ChannelHandler.sendOutgoing(ChannelHandler.java:223)
at com.atsi.acex.ChannelHandler.execute(ChannelHandler.java:175)
at com.atsi.acex.Main.run(Main.java:221)
at java.lang.Thread.run(Thread.java:619)
2007.05.06 16:21:51 MQJMS1016E an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE046: Unsupported codeset : 0
com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE046: Unsupported codeset : 0
at com.ibm.mq.MQMsg2.copyStrIntoBytes(MQMsg2.java:525)
at com.ibm.mq.MQMsg2.setFormat(MQMsg2.java:698)
at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1488)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1130)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1183)
at com.atsi.jms.AbstractQueueHandler.sendMessage(AbstractQueueHandler.java:951)
at com.atsi.jms.AbstractQueueHandler.sendTextMessage(AbstractQueueHandler.java:933)
at com.atsi.jms.AbstractQueueHandler.writeMessage(AbstractQueueHandler.java:447)
at com.atsi.acex.ChannelHandler.sendFiles(ChannelHandler.java:347)
at com.atsi.acex.ChannelHandler.sendOutgoing(ChannelHandler.java:223)
at com.atsi.acex.ChannelHandler.execute(ChannelHandler.java:175)
at com.atsi.acex.Main.run(Main.java:221)
at java.lang.Thread.run(Thread.java:619)
2007.05.06 16:22:41 MQJMS1016E an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE046: Unsupported codeset : 0
com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
MQJE046: Unsupported codeset : 0
at com.ibm.mq.MQMsg2.copyStrIntoBytes(MQMsg2.java:525)
at com.ibm.mq.MQMsg2.setFormat(MQMsg2.java:698)
at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1488)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1130)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1183)
at com.atsi.jms.AbstractQueueHandler.sendMessage(AbstractQueueHandler.java:951)
at com.atsi.jms.AbstractQueueHandler.sendTextMessage(AbstractQueueHandler.java:933)
at com.atsi.jms.AbstractQueueHandler.writeMessage(AbstractQueueHandler.java:447)
at com.atsi.acex.ChannelHandler.sendFiles(ChannelHandler.java:347)
at com.atsi.acex.ChannelHandler.sendOutgoing(ChannelHandler.java:223)
at com.atsi.acex.ChannelHandler.execute(ChannelHandler.java:175)
at com.atsi.acex.Main.run(Main.java:221)
at java.lang.Thread.run(Thread.java:619)
debug-single:
BUILD SUCCESSFUL (total time: 6 minutes 45 seconds) |
|
| Back to top |
|
|
|
|
