ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » unable to write message to MQ output queue

Post new topic  Reply to topic Goto page 1, 2  Next
 unable to write message to MQ output queue « View previous topic :: View next topic » 
Author Message
Sam Uppu
PostPosted: Fri Jul 01, 2011 10:21 am    Post subject: unable to write message to MQ output queue Reply with quote

Yatiri

Joined: 11 Nov 2008
Posts: 610

Hi guys,

I am unable to wite message to output queue. The message has the below headers. The data is BLOB. Below are headers of the message.
Can you guys let me know what is the issue with the headers.

( ['SOAPRoot' : 0x11844c550]
(0x01000000:Name):Properties = ( ['MQPROPERTYPARSER' : 0x118481b90]
(0x03000000:NameValue):MessageSet = '' (CHARACTER)
(0x03000000:NameValue):MessageType = '' (CHARACTER)
(0x03000000:NameValue):MessageFormat = '' (CHARACTER)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 819 (INTEGER)
(0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
(0x03000000:NameValue):Persistence = TRUE (BOOLEAN)
(0x03000000:NameValue):CreationTime = GMTTIMESTAMP '2011-07-01 18:10:42.330' (GMTTIMESTAMP)
(0x03000000:NameValue):ExpirationTime = -1 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):ReplyIdentifier = X'e08a141b0c3fd0425b09e190cf1df20e2364000000000000' (BLOB)
(0x03000000:NameValue):ReplyProtocol = 'MQ' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceToken = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourcePassword = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedType = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedToken = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedPassword = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedIssuedBy = '' (CHARACTER)
)
(0x01000000:Name):MQMD = ( ['MQHMD' : 0x11844d050]
(0x03000000:NameValue):SourceQueue = 'REQ' (CHARACTER)
(0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 819 (INTEGER)
(0x03000000:NameValue):Format = 'MQSTR ' (CHARACTER)
(0x03000000:NameValue):Version = 2 (INTEGER)
(0x03000000:NameValue):Report = 0 (INTEGER)
(0x03000000:NameValue):MsgType = 1 (INTEGER)
(0x03000000:NameValue):Expiry = -1 (INTEGER)
(0x03000000:NameValue):Feedback = 0 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):Persistence = 1 (INTEGER)
(0x03000000:NameValue):MsgId = X'e08a141b0c3fd0425b09e190cf1df20e2364000000000000' (BLOB)
(0x03000000:NameValue):CorrelId = X'e08a141b0c3fd0425b09e190cf1df20e2364000000000000' (BLOB)
(0x03000000:NameValue):BackoutCount = 0 (INTEGER)
(0x03000000:NameValue):ReplyToQ = 'RSP ' (CHARACTER)
(0x03000000:NameValue):ReplyToQMgr = 'ESBDPWD1 ' (CHARACTER)
(0x03000000:NameValue):UserIdentifier = 'mqm ' (CHARACTER)
(0x03000000:NameValue):AccountingToken = X'0130000000000000000000000000000000000000000000000000000000000006' (BLOB)
(0x03000000:NameValue):ApplIdentityData = ' ' (CHARACTER)
(0x03000000:NameValue):PutApplType = 6 (INTEGER)
(0x03000000:NameValue):PutApplName = 'WebSphere Datapower MQClient' (CHARACTER)
(0x03000000:NameValue):PutDate = DATE '2011-07-01' (DATE)
(0x03000000:NameValue):PutTime = GMTTIME '18:10:42.330' (GMTTIME)
(0x03000000:NameValue):ApplOriginData = ' ' (CHARACTER)
(0x03000000:NameValue):GroupId = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000:NameValue):MsgSeqNumber = 1 (INTEGER)
(0x03000000:NameValue):Offset = 0 (INTEGER)
(0x03000000:NameValue):MsgFlags = 0 (INTEGER)
(0x03000000:NameValue):OriginalLength = -1 (INTEGER)
)

Quote:
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri Jul 01, 2011 10:46 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Please look in the logs and provide the MQRC.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Fri Jul 01, 2011 11:13 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

lancelotlinc wrote:
Please look in the logs and provide the MQRC.




Or at least tell us what's brought you to the conclusion the headers are the problem.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Sam Uppu
PostPosted: Fri Jul 01, 2011 4:54 pm    Post subject: Reply with quote

Yatiri

Joined: 11 Nov 2008
Posts: 610

Since the data is BLOB and I think there mioght me problem with the parser property of the headers.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Jul 01, 2011 5:21 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Sam Uppu wrote:
Since the data is BLOB and I think there mioght me problem with the parser property of the headers.


WMQ is blind to the content of a message. So it wouldn't care about the message but would still throw a reason code if there was a problem.

Which you've not posted.

So any problem would be serializing the message tree to form a message. But WMB would throw an error if that was the case.

Which you've not posted.

So it's really hard to offer any advice.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Sam Uppu
PostPosted: Fri Jul 01, 2011 5:44 pm    Post subject: Reply with quote

Yatiri

Joined: 11 Nov 2008
Posts: 610

I see execution group restarting and the error in the broker logs is "Fatal Java exception........"

The flow is as below ....
WTX map ---> Compute --->Trace--->MQoutput

After the message comes out of trace node , before writing to output node, execution grp restarts.

When I remove MQ output node from the flow, I dont see any error.


I have no clue why I am getting this error and where the problem is . So Iwas suspecting the message headers.
Back to top
View user's profile Send private message
Vitor
PostPosted: Sat Jul 02, 2011 6:38 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Sam Uppu wrote:
I see execution group restarting and the error in the broker logs is "Fatal Java exception........"


Ok, it's got to say more than 3 words.

Sam Uppu wrote:
The flow is as below ....
WTX map ---> Compute --->Trace--->MQoutput


Ooo, look! Information!

Sam Uppu wrote:
After the message comes out of trace node , before writing to output node, execution grp restarts.


Ooo, look! Another clue!

So the flow doesn't throw an error, the execution group abends? That might have been a helpful fact earlier in this thread.

Sam Uppu wrote:
When I remove MQ output node from the flow, I dont see any error.


So it probably is connected to the serialising of the message.

Sam Uppu wrote:
I have no clue why I am getting this error and where the problem is . So Iwas suspecting the message headers.


I would have suspected the fatal Java error causing the eg to crash myself. Which in fairness probably is connected to the parser details in the headers, but is more likely that they're not installed or configured correctly.

Perhaps you could drip out the following information:

- Level of WMB
- Platform
- The rest of the Java exception!
- Has this flow ever worked?
- Do similar flows on the same machine work?
- Do you have similar flows running on other machines?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Jul 02, 2011 10:25 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

For the MQMD set the format to MQFMT_STRING or if using Java use the constant equivalent field value.

Also the source queue in the MQMD does not seem to have the required length either... same for response queue, qmgr name? etc...
Basically for all the CHAR fields check the required length and pad with spaces

I guess that would do it. Use the defined litteral constants whenever possible, as those will be right. It looks to me that your format is of length 6 where it should be of length 8?

Always use the provided getter and setter and do not set the field value yourself even if you "can" do it. Getters and setters will ensure that the correct format is achieved...

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Sam Uppu
PostPosted: Tue Jul 05, 2011 7:53 am    Post subject: Reply with quote

Yatiri

Joined: 11 Nov 2008
Posts: 610

I set the MQMD to MQFMT_STRING, still I see EG crashing.
['SOAPRoot' : 0x11780a150]
(0x01000000:Name):Properties = ( ['MQPROPERTYPARSER' : 0x1183ada70]
(0x03000000:NameValue):MessageSet = '' (CHARACTER)
(0x03000000:NameValue):MessageType = '' (CHARACTER)
(0x03000000:NameValue):MessageFormat = '' (CHARACTER)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 819 (INTEGER)
(0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
(0x03000000:NameValue):Persistence = TRUE (BOOLEAN)
(0x03000000:NameValue):CreationTime = GMTTIMESTAMP '2011-07-05 15:40:32.560' (GMTTIMESTAMP)
(0x03000000:NameValue):ExpirationTime = -1 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):ReplyIdentifier = X'f0132d7f0ca3c047830be9506dc9267d00cc000000000000' (BLOB)
(0x03000000:NameValue):ReplyProtocol = 'MQ' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceToken = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourcePassword = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedType = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedToken = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedPassword = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedIssuedBy = '' (CHARACTER)
)
(0x01000000:Name):MQMD = ( ['MQHMD' : 0x11780a9f0]
(0x03000000:NameValue):SourceQueue = 'HIPAA.ISD1.REQ' (CHARACTER)
(0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 819 (INTEGER)
(0x03000000:NameValue):Format = 'MQSTR ' (CHARACTER)
(0x03000000:NameValue):Version = 2 (INTEGER)
(0x03000000:NameValue):Report = 0 (INTEGER)
(0x03000000:NameValue):MsgType = 1 (INTEGER)
(0x03000000:NameValue):Expiry = -1 (INTEGER)
(0x03000000:NameValue):Feedback = 0 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):Persistence = 1 (INTEGER)
(0x03000000:NameValue):MsgId = X'f0132d7f0ca3c047830be9506dc9267d00cc000000000000' (BLOB)
(0x03000000:NameValue):CorrelId = X'f0132d7f0ca3c047830be9506dc9267d00cc000000000000' (BLOB)
(0x03000000:NameValue):BackoutCount = 0 (INTEGER)
(0x03000000:NameValue):ReplyToQ = 'HIPAA.ISD1.RSP ' (CHARACTER)
(0x03000000:NameValue):ReplyToQMgr = 'ESBISDWD1 ' (CHARACTER)
(0x03000000:NameValue):UserIdentifier = 'mqm ' (CHARACTER)
(0x03000000:NameValue):AccountingToken = X'0130000000000000000000000000000000000000000000000000000000000006' (BLOB)
(0x03000000:NameValue):ApplIdentityData = ' ' (CHARACTER)
(0x03000000:NameValue):PutApplType = 6 (INTEGER)
(0x03000000:NameValue):PutApplName = 'WebSphere Datapower MQClient' (CHARACTER)
(0x03000000:NameValue):PutDate = DATE '2011-07-05' (DATE)
(0x03000000:NameValue):PutTime = GMTTIME '15:40:32.560' (GMTTIME)
(0x03000000:NameValue):ApplOriginData = ' ' (CHARACTER)
(0x03000000:NameValue):GroupId = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000:NameValue):MsgSeqNumber = 1 (INTEGER)
(0x03000000:NameValue):Offset = 0 (INTEGER)
(0x03000000:NameValue):MsgFlags = 0 (INTEGER)
(0x03000000:NameValue):OriginalLength = -1 (INTEGER)
)
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Jul 05, 2011 9:08 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Sam Uppu wrote:
I set the MQMD to MQFMT_STRING, still I see EG crashing.


Which, as I've said earlier, must be generating more error than the 3 words you posted and could contain an important clue. Like the nature of the abend.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Sam Uppu
PostPosted: Fri Jul 08, 2011 7:42 am    Post subject: Reply with quote

Yatiri

Joined: 11 Nov 2008
Posts: 610

Here is the complete error message.

Quote:
Error BIP2121E: The thread bootstrap code caught an unhandled exception on thread '7197'.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The exception was issued on thread '7197'. Further information may be in the exception information associated with this message.
Restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur, then contact your IBM support center.
2011-07-08 10:33:19.856194 7197 FatalException BIP3702E: A Fatal Java exception was thrown whilst calling the Java JNI method ''method_java_lang_StringBuilder_StringBuilder''. The Java exception was ''''. The Java stack trace was ''''.
Correct the error, and if necessary redeploy the flow.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Jul 08, 2011 7:58 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Sam Uppu wrote:
If the problem still continues to occur, then contact your IBM support center.


Words to live by.

Looks like a PMR to me.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Jul 08, 2011 8:04 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

fjb_saper wrote:

Also the source queue in the MQMD does not seem to have the required length either... same for response queue, qmgr name? etc...
Basically for all the CHAR fields check the required length and pad with spaces

So did you verify the length for each of the above mentioned fields?
Did you right pad with the necessary spaces??
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Sam Uppu
PostPosted: Fri Jul 08, 2011 8:06 am    Post subject: Reply with quote

Yatiri

Joined: 11 Nov 2008
Posts: 610

fjb_saper wrote:
fjb_saper wrote:

Also the source queue in the MQMD does not seem to have the required length either... same for response queue, qmgr name? etc...
Basically for all the CHAR fields check the required length and pad with spaces

So did you verify the length for each of the above mentioned fields?
Did you right pad with the necessary spaces??


yes.
Back to top
View user's profile Send private message
paintpot
PostPosted: Fri Jul 08, 2011 8:13 am    Post subject: Reply with quote

Centurion

Joined: 19 Sep 2005
Posts: 112
Location: UK

What happens when you change the flow to remove the Body before writing to the MQOutput? If it works, it ought to show your headers are ok (and vice versa).
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » unable to write message to MQ output queue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.