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 134921 - FAST:EAP:KBC FAST:PRIORITY:2-URGENT MQ BC does not appear to re-attach correctly to MQ manager
Summary: FAST:EAP:KBC FAST:PRIORITY:2-URGENT MQ BC does not appear to re-attach correc...
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-05-13 09:22 UTC by mfoster
Modified: 2009-06-09 21:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mfoster 2008-05-13 09:22:31 UTC 
If I deploy a CA using the MQ BC inbound and the MQ manager is not started, and then subsequently start the MQ manager
and put a message on the input queue I get the following error in GF log, the message is never read....

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=17e41db9-9fe6-4145-90cf-6446ce836722;|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
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)
No message at the queue sleep another millseconds 60,000

If I undeploy/redeploy the CA the message is read as expected.
Comment 1 Sergey Lunegov 2008-12-10 15:24:26 UTC 
Related to GF ESB distribution. Not to NB 7.0
Comment 2 Marian Mirilovic 2009-02-20 18:03:12 UTC 
update no67 keyword