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 134162 - FAST:EAP:KBC FAST:PRIORITY:3-IMPORTANT MQ BC cannot connect in Binding Mode
Summary: FAST:EAP:KBC FAST:PRIORITY:3-IMPORTANT MQ BC cannot connect in Binding Mode
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: Binding Components (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Venkat Chellasamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-29 14:17 UTC by mfoster
Modified: 2009-06-09 21:07 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-04-29 14:17:07 UTC 
I raised this a couple of months ago via email, this incident is for tracking purposes.....

You cannot leave the "Channel Name" blank in the MQ BC properties which means that all connections are probably via
client Mode - this may have some bearing on the other incident I raised about using XA with the MQ BC - I seem to
remember if you use Client mode XA is only supported using the IBM Extended Transactional Client which you have to buy.
Comment 1 mfoster 2008-05-09 13:22:25 UTC 
I've investigated this further and it appears you can connect in Binding mode, but only with some bizarre combinations
of properties along the lines of....

HostName - blank
PortName - 1414
ChannelName - entered but invalid

I think that merely leaving the channelName blank should force "Binding Mode" as this channel is specifically required
for client connections.

Can this please be sorted out and documented

Priority changed to 2
Comment 2 mfoster 2008-05-14 14:57:07 UTC 
Priority changed to 3