This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 134141 - FAST:EAP:KBC FAST:PRIORITY:2-URGENT MQ BC QoS ERROR does not work
Summary: FAST:EAP:KBC FAST:PRIORITY:2-URGENT MQ BC QoS ERROR does not work
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: Binding Components (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Venkat Chellasamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-29 10:26 UTC by mfoster
Modified: 2009-06-09 21:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mfoster 2008-04-29 10:26:57 UTC
In the QoS for the MQ BC you can set the "on failure" to "error". I assumed this would redirect to a given DLQ, it looks
like it should but there is nowhere to set the name of this in the properties, hence on deployment I get the following...

selectQueue error request queue name <KBCInputQueue> has no match.
selectQueue error request queue name <null > has no match.
        at com.sun.jbi.mqbc.extservices.MQClientAgent.accessQueue(MQClientAgent.java:468)
        at com.sun.jbi.mqbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:221)
        at com.sun.jbi.mqbc.InboundMessageProcessor.run(InboundMessageProcessor.java:192)
        at java.lang.Thread.run(Thread.java:619)
;_RequestID=d107b9d8-beb5-4ca2-9886-c79623641ce5;|InboundMessageProcessor Failed to execute java.lang.NullPointerException
        at com.sun.jbi.mqbc.extservices.MQClientAgent.accessQueue(MQClientAgent.java:468)
        at com.sun.jbi.mqbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:221)
        at com.sun.jbi.mqbc.InboundMessageProcessor.run(InboundMessageProcessor.java:192)
        at java.lang.Thread.run(Thread.java:619)
Failed to send message: null
Comment 1 mfoster 2008-04-29 12:45:50 UTC
Ignore the first comment - there was an issue with using "localhost" in the host name, changed to my real host name.

Now I set the "max attempts" to 3 and the "waitTime" to 10 seconds and the "on-failure" to "error", I stop the BPEL SE
and nothing seems to happen like this, it tries to send the message and carries on as normal - here is the GF log....

No message at the queue sleep another millseconds 60,000
BPJBI-5004:Stopping BPEL service engine
BPJBI-5005:BPEL service engine stopped
JBIFW1156: Engine sun-bpel-engine has been stopped.
same queue <KBCInputQueue> was opend with old options <49> can be reused with new options <49>
GMO_DEBUG_MGC_GMO_NONE
GMO_DEBUG_MGC_MO_NONE
GMO_DEBUG_NEW_OBJECT
GMO_DEBUG_MGC_GMO_ACCEPTTRUNCATEDMSG_SET
GMO_DEBUG_MGC_GMO_SYNCPOINT_UNSET
GetWOptions <0x44> wait interval <0x0>
New com.sun.jbi.mqbc.extservices.ExtServiceMQMessage...
CLEARMESSAGE
Queue Manager <QM_mf195848_pc> CCSID <ISO8859_1>
MQRC_NO_MSG_AVAILABLE
No message at the queue sleep another millseconds 60,000
same queue <KBCInputQueue> was opend with old options <49> can be reused with new options <49>
GMO_DEBUG_MGC_GMO_NONE
GMO_DEBUG_MGC_MO_NONE
GMO_DEBUG_NEW_OBJECT
GMO_DEBUG_MGC_GMO_ACCEPTTRUNCATEDMSG_SET
GMO_DEBUG_MGC_GMO_SYNCPOINT_UNSET
GetWOptions <0x44> wait interval <0x0>
New com.sun.jbi.mqbc.extservices.ExtServiceMQMessage...
CLEARMESSAGE
Queue Manager <QM_mf195848_pc> CCSID <ISO8859_1>
getWOptions at queue <KBCInputQueue                                   >
Located service endpoint reference for service [{caTestXA}casaService3] and endpoint name [casaPort3].
MESSAGELENGTH [885]
READFULLY1 [885]
InboundMessageProcessor Sending message exchange with ID 234196678750381-50666-134287620207960177; normalized message
content is [javax.xml.transform.dom.DOMSource@14fa48a]
same queue <KBCInputQueue> was opend with old options <49> can be reused with new options <49>
GMO_DEBUG_MGC_GMO_NONE
GMO_DEBUG_MGC_MO_NONE
GMO_DEBUG_NEW_OBJECT
GMO_DEBUG_MGC_GMO_ACCEPTTRUNCATEDMSG_SET
GMO_DEBUG_MGC_GMO_SYNCPOINT_UNSET
GetWOptions <0x44> wait interval <0x0>
New com.sun.jbi.mqbc.extservices.ExtServiceMQMessage...
CLEARMESSAGE
Queue Manager <QM_mf195848_pc> CCSID <ISO8859_1>
MQRC_NO_MSG_AVAILABLE
No message at the queue sleep another millseconds 60,000
same queue <KBCInputQueue> was opend with old options <49> can be reused with new options <49>
GMO_DEBUG_MGC_GMO_NONE
GMO_DEBUG_MGC_MO_NONE
GMO_DEBUG_NEW_OBJECT
GMO_DEBUG_MGC_GMO_ACCEPTTRUNCATEDMSG_SET
GMO_DEBUG_MGC_GMO_SYNCPOINT_UNSET
GetWOptions <0x44> wait interval <0x0>
New com.sun.jbi.mqbc.extservices.ExtServiceMQMessage...
CLEARMESSAGE
Queue Manager <QM_mf195848_pc> CCSID <ISO8859_1>
MQRC_NO_MSG_AVAILABLE
No message at the queue sleep another millseconds 60,000
Comment 2 Sergey Lunegov 2008-12-10 15:23:52 UTC
Related to GF ESB distribution. Not to NB 7.0
Comment 3 Marian Mirilovic 2009-02-20 18:09:41 UTC
update no67 keyword