axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <>
Subject [jira] Commented: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Date Sat, 30 Jun 2007 10:37:04 GMT


Asankha C. Perera commented on AXIS2-2816:

Hi Mark

Checked in the patch with visual verification. Please check this once it reaches the nightly
build to see if it works now.

Sorry for the delays, as i have been traveling this week


> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>                 Key: AXIS2-2816
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.2
>         Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0
>            Reporter: Mark Badorrek
>            Assignee: Asankha C. Perera
>             Fix For: 1.3
>         Attachments:,
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS
> This is insufficient for WebspherMQ CLIENT connections, where the administrator must
nominate a particular userID and password per connectionfactory, resulting in the following
call which is unsupported in the Axis2 JMS code:
> factory.createConnection(userID, password) 
> The attached Axis2 JMS files contain the fix to allow the deployer to specify a nominated
userID and password through the standard Axis2 JNDI lookup mechanism.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message