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.
| Summary: |
FAST:EAP:KBC FAST:PRIORITY:2-URGENT MQ BC does not appear to re-attach correctly to MQ manager |
| Product: |
soa
|
Reporter: |
mfoster <mfoster> |
| Component: |
Binding Components | Assignee: |
Venkat Chellasamy <vchellasamy> |
| Status: |
NEW
---
|
|
|
| Severity: |
blocker
|
|
|
| Priority: |
P2
|
|
|
| Version: |
6.x | |
|
| Hardware: |
All | |
|
| OS: |
All | |
|
|
Issue Type:
|
DEFECT
|
Exception Reporter:
|
|
|---|
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.