MQSeries.net :: View topic - Message Broker 7 and Business Monitor end transaction event

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Broker 7 and Business Monitor end transaction event

Message Broker 7 and Business Monitor end transaction event

« View previous topic :: View next topic »

Author

Message

marcin.kasinski

Posted: Fri Dec 21, 2012 1:35 pm Post subject: Message Broker 7 and Business Monitor end transaction event

Sentinel

Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw

WebSphere Message Broker 7.0.0.5

I have problem with Business monitoring my message Flow.

On MQ Input node I set monitoring (Transaction start and transaction endevent source)

Everything works fine.

I can see 2 events sent from broker .

Code:

<wmb:event xmlns:wmb="http://www.ibm.com/xmlns/prod/websphere/messagebroker/6.1.0/monitoring/event">
<wmb:eventPointData>
<wmb:eventData wmb:productVersion="7005" wmb:eventSchemaVersion="6.1.0.3" wmb:eventSourceAddress="MQ Input2.transaction.Start">
<wmb:eventIdentity wmb:eventName="MQ Input2.TransactionStart"/>
<wmb:eventSequence wmb:creationTime="2012-12-21T21:18:04.244Z" wmb:counter="1"/>
<wmb:eventCorrelation wmb:localTransactionId="fbad06c3-fd35-4ffa-b016-b86297751bfd-1" wmb:parentTransactionId="" wmb:globalTransactionId=""/>
</wmb:eventData>
...
</wmb:event>

<wmb:event xmlns:wmb="http://www.ibm.com/xmlns/prod/websphere/messagebroker/6.1.0/monitoring/event">
<wmb:eventPointData>
<wmb:eventData wmb:productVersion="7005" wmb:eventSchemaVersion="6.1.0.3" wmb:eventSourceAddress="MQ Input2.transaction.End">
<wmb:eventIdentity wmb:eventName="MQ Input2.TransactionEnd"/>
<wmb:eventSequence wmb:creationTime="2012-12-21T21:18:04.244Z" wmb:counter="2"/>
<wmb:eventCorrelation wmb:localTransactionId="fbad06c3-fd35-4ffa-b016-b86297751bfd-1" wmb:parentTransactionId="" wmb:globalTransactionId=""/>
</wmb:eventData>
...
</wmb:event>

Now I would like to set only end transation on this MQ Input.

Having only Transaction end I have strange event

Code:

As you can there is empty localTransactionId.

Because of this Business Monitor can not corellate this event.

Problem is that localTransactionId is empty always, even if I set $Root/MQMD/MsgId as source of localTransactionId

Any hint What I do wrong ?
_________________
Marcin

kimbert

Posted: Sat Dec 22, 2012 2:04 am Post subject:

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Could be a product defect. I would open a PMR.

sajtron

Posted: Wed Feb 06, 2013 6:15 am Post subject:

Novice

Joined: 31 May 2011
Posts: 24

Any progress with the issue. I am facing same problem.

kimbert

Posted: Wed Feb 06, 2013 6:21 am Post subject:

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

If you really need a fix then you will need to request a fix from IBM.
But there is a fairly easy workaround - just define a transactionStart event on the MQInput node and ignore it.

marcin.kasinski

Posted: Wed Feb 06, 2013 6:37 am Post subject:

Sentinel

Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw

kimbert wrote:

If you really need a fix then you will need to request a fix from IBM.
But there is a fairly easy workaround - just define a transactionStart event on the MQInput node and ignore it.

Exactly as kimbert said dummy EtransactionStart solves the problem.
_________________
Marcin

sajtron

Posted: Wed Feb 06, 2013 8:57 am Post subject:

Novice

Joined: 31 May 2011
Posts: 24

Finaly I used events from terminals inside flow.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Broker 7 and Business Monitor end transaction event

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