| Author |
Message
|
| jarun111 |
 Posted: Tue Oct 04, 2005 12:08 pm Post subject: MQJE046: Unsupported codeset |
 |
|
Acolyte
Joined: 19 Apr 2004
Posts: 70
|
Hi,
We are getting the following error intermittently:
2005.10.03 07:30:00 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
MQ client version is 5.3.0.5 and client is running from Solaris box. Queue manager is in Solaris and is in 5.3.0.6. We don't set any special properties for Queue/QCF in regard to encoding/CCSID.
Any help would be greatly appreciated. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Tue Oct 04, 2005 12:30 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| Completion Code 2, Reason 2195 |
Unexpected Error. Time to start searching for the FDCs.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jarun111 |
| Posted: Tue Oct 04, 2005 12:33 pm Post subject: |
|
|
Acolyte
Joined: 19 Apr 2004
Posts: 70
|
| No FDC'S generated in the server. Also we see this issue occuring intermittently |
|
| Back to top |
|
|
| moogoo |
| Posted: Tue Apr 18, 2006 10:37 am Post subject: |
|
|
Acolyte
Joined: 20 Sep 2002
Posts: 54
Location: US
|
Hi jarun111,
Were you able to resolve this error? We are getting the same thing that also happens on an intermittent basis.
Thanks,
MG |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 18, 2006 10:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Update to CSD 12.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| moogoo |
| Posted: Tue Apr 18, 2006 10:58 am Post subject: |
|
|
Acolyte
Joined: 20 Sep 2002
Posts: 54
Location: US
|
Hi Jeff,
I'm thumbing through the CSD 12 documentation for MQ v5.3 but am not seeing it mentioned that this issue is fixed. Do you have the item # that refers to this?
Thanks,
MG |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 18, 2006 11:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
No, I'm not saying that there is a specific fix for this in CSD12.
I'm just saying that, given the vast number of fixes since CSD05, it's fairly likely that there is a fix - in one way or another - for this issue.
Particularly, there are a lot of JMS fixes even since CSD 9.
Plus, it's best practice to upgrade to the lastest CSD within three months of it's release - at least in my opinion.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| moogoo |
| Posted: Tue Apr 18, 2006 1:30 pm Post subject: |
|
|
Acolyte
Joined: 20 Sep 2002
Posts: 54
Location: US
|
|
| Back to top |
|
|
| moogoo |
| Posted: Wed Apr 26, 2006 2:01 pm Post subject: |
|
|
Acolyte
Joined: 20 Sep 2002
Posts: 54
Location: US
|
Just to followup for all those in the future who may encounter this problem. After the update to CSD12, the problem still ended up occurring. We then opened up a problem ticket to IBM who responded with the following:
This error is a result of the application using either an MQTopicPublisher or an MQQueueSender object on two or more separate threads.
One thread is trying to use the object to instantiate a new MQJMSMessage at the same time as another thread is using the same message producer (either the Topic Publiser or the Queue Sender) to write a message. The first thread resets the codepage of the message to 0, which causes the second thread to throw the error:
MQJE046: Unsupported codeset : 0
Sharing message producers across threads is not supported. If this problem occurs, the application should be reviewed to ensure that each thread creates it's own MQTopicPublisher or MQQueueSender
Hope this is helpful!
MG |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 26, 2006 3:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| moogoo wrote: |
Just to followup for all those in the future who may encounter this problem. After the update to CSD12, the problem still ended up occurring. We then opened up a problem ticket to IBM who responded with the following:
This error is a result of the application using either an MQTopicPublisher or an MQQueueSender object on two or more separate threads.
One thread is trying to use the object to instantiate a new MQJMSMessage at the same time as another thread is using the same message producer (either the Topic Publiser or the Queue Sender) to write a message. The first thread resets the codepage of the message to 0, which causes the second thread to throw the error:
MQJE046: Unsupported codeset : 0
Sharing message producers across threads is not supported. If this problem occurs, the application should be reviewed to ensure that each thread creates it's own MQTopicPublisher or MQQueueSender
Hope this is helpful!
MG |
You mean you did not have each thread using at least its own session if not its own connection?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| pabloparets |
| Posted: Sat May 05, 2007 6:06 pm Post subject: codeset |
|
|
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:47 am Post subject: Re: codeset |
|
|
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? |
1) It's rude to double post
2) It's unusual to add stuff to the bottom of old posts
3) How do you know this is the same problem as yours, given this it's a different problem to the one you posted on before?
4) See my comments on your other post. My recommendation is you start a new thread in the JMS section, give full details of your application, platform and errors, and what you've tried so far. This will enable us to give you the best assistance we can.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
