Author |
Message
|
mvs |
Posted: Tue Nov 13, 2007 11:54 pm Post subject: MB -properties of the message nulls |
|
|
Voyager
Joined: 06 Jul 2007 Posts: 85
|
Hi,
Today we facing a strange problem. We are getting nulls in the propeties of the message in Trace node.
our flow like below
InputNode -> Trace Node -> Compute node-Output Node
The input node properties, Message Domain is blank.
In the Trace Node properties shows like below.
-------------------------
$ more xmlpass.log
(
(0x01000000):Properties = (
(0x03000000):MessageSet = NULL
(0x03000000):MessageType = NULL
(0x03000000):MessageFormat = NULL
(0x03000000):Encoding = NULL
(0x03000000):CodedCharSetId = NULL
(0x03000000):Transactional = NULL
(0x03000000):Persistence = NULL
(0x03000000):CreationTime = NULL
(0x03000000):ExpirationTime = NULL
(0x03000000):Priority = NULL
(0x03000000):ReplyIdentifier = NULL
(0x03000000):ReplyProtocol = 'MQ'
(0x03000000):Topic = NULL
(0x03000000):ContentType = NULL
)
-----------------------------
The message failing and shows the exception is no data in the message.
Any idea regarding this?
Thanks and Regards
MVS |
|
Back to top |
|
 |
Vitor |
Posted: Wed Nov 14, 2007 1:41 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Is your input node an MQInput node? Or what?
What domain is the input in?
What data do you believe it is receiving? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mvs |
Posted: Fri Nov 16, 2007 1:59 am Post subject: MB -properties of the message nulls |
|
|
Voyager
Joined: 06 Jul 2007 Posts: 85
|
Yes, its MQInput Node. I am not using any domain. just blank. by default it considers BLOB |
|
Back to top |
|
 |
Vitor |
Posted: Fri Nov 16, 2007 2:12 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
So you're receiving a message, treating it as a BLOB & not parsining it, then wondering why the message has NULL properties....
Has this just started happening? What are you trying to do with the message? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mvs |
Posted: Fri Nov 16, 2007 3:57 am Post subject: MB -properties of the message nulls |
|
|
Voyager
Joined: 06 Jul 2007 Posts: 85
|
Hi,
Its happening suddenly.
We have moved the flows from Dev environment to Preprod. This problem occured. The same the flow working fine in dev. We checked the data before submitting into the queue, both evnvironments data is same.
Thanks and Regards
MVS |
|
Back to top |
|
 |
Vitor |
Posted: Fri Nov 16, 2007 4:01 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Odd.
What were you getting in the Properties previously?
Have you made all the usual checks about software at the same level, that sort of thing? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Nov 16, 2007 4:05 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Stop the flow and check the data on the input queue. Make sure you don't have any message with no body...
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|