You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Mark Badorrek (JIRA)" <ji...@apache.org> on 2007/06/18 12:29:25 UTC
[jira] Created: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
JMS over WebsphereMQ doesn't support 'CLIENT' connections
---------------------------------------------------------
Key: AXIS2-2816
URL: https://issues.apache.org/jira/browse/AXIS2-2816
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.2
Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0
Reporter: Mark Badorrek
Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved AXIS2-2816.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.3
Mark
I have applied the patch after a review - but not actual test. Please check the next nightly build and let me know if you encounter any issues.
thanks again for the patch, and sorry for any delay to apply it
asankha
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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: Axis2-websphereMQ-fix.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Mark Badorrek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508723 ]
Mark Badorrek commented on AXIS2-2816:
--------------------------------------
Hi stambo,
Not sure about TIBCO but I wouldn't be suprised if there are some issues there. This fix is about being able to supply an arbitary userID and password rather than accepting the OS userID credentials.
We will be attempting to use SSL with Websphere shortly and if Axis2 needs patching I'll raise a JIRA and let you know.
A point to note is that there is a bug in the code released with this jira. Normal functionality is unchanged, but the new JNDI username/password fix just does not work. I have the fix for this and will get it into the axis2 nightly build hopefully in the next day or so. It really depends on how soon the committers fix their current JMS address problem. Once this is fixed I'll test and submit my patch.
Cheers,
Mark B
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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: Axis2-websphereMQ-fix.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509407 ]
Davanum Srinivas commented on AXIS2-2816:
-----------------------------------------
Looks like Asankha has checked in the patch:
http://svn.apache.org/viewvc?view=rev&revision=552107
thanks,
dims
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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: Axis2-websphereMQ-fix.zip, WebsphereMQ-fix-29-06-2007.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "stambo@bigstring.com (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508707 ]
stambo@bigstring.com commented on AXIS2-2816:
---------------------------------------------
Is this problem true for TIBCO as well ?? We have succesfully connected to one of our TIBCO servers via tcp with user and password but have been unsuccefull with ssl. Is it possible to put the additional jndi and jms parameters necessary for ssl in the services.xml or axis2.xml and have axis do the jndi lookup for the destination ??
Thank you
Quoted from:
http://www.nabble.com/-jira--Created%3A-%28AXIS2-2816%29-JMS-over-WebsphereMQ-doesn%27t-support-%27CLIENT%27-connections-tf3939423.html#a11173164
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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: Axis2-websphereMQ-fix.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Reopened: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Mark Badorrek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Badorrek reopened AXIS2-2816:
----------------------------------
Hi Asankha,
This patch is for a bug in the functionality of the previous fix for this JIRA.
As before, current functionality is unchanged but the new JNDI userID / Password scenario should now work.
I've done as much testing as I can, but another issue https://issues.apache.org/jira/browse/AXIS2-2864 is preventing me for final confirmation.
Cheers,
Mark B
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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: Axis2-websphereMQ-fix.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509279 ]
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
asankha
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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: Axis2-websphereMQ-fix.zip, WebsphereMQ-fix-29-06-2007.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Mark Badorrek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Badorrek updated AXIS2-2816:
---------------------------------
Attachment: WebsphereMQ-fix-29-06-2007.zip
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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: Axis2-websphereMQ-fix.zip, WebsphereMQ-fix-29-06-2007.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
RE: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Posted by Mark Badorrek <mb...@avoga.com.au>.
Hi Asankha, David,
If you can get the fix into the nightly build I'll give it a run and confirm that everything is OK.
Additionally, I'll see if I can get local IBM sales to donate a WebsphereMQ copy.
If that work's out I'll outline what sort of work is required to perform a test.
You can relax, you will only need WebsphereMQ, not WebsphereEverythingAnd TheKitchenSink.
Mark B
________________________________
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Tue 19/06/2007 6:30 PM
To: axis-dev@ws.apache.org
Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Hi David, Mark
I think for right now this would work fine - if Mark can validate that
the fixes does work as expected, and not break anything else. However in
the longer run, and to ensure that we could support MQ as well as
ActiveMQ and any other JMS implementation the best we can, it would make
sense for me and any others to get that copy installed. Hopefully, I
will not need Websphere, DB2 etc..etc.. to just get MQ running ;-)
thanks
asankha
David Illsley wrote:
> Mark, Asankha,
> I believe that developerworks does provide a free 90 day trial version
> of WebSphere MQ [1]. Does that satisfy your needs?
> Cheers,
> David
>
> [1]
> http://www.ibm.com/developerworks/downloads/ws/wmq/?S_TACT=105AGX10&S_CMP=LP
>
>
>
> On 18/06/07, Mark Badorrek <mb...@avoga.com.au> wrote:
>> Hi asankha,
>>
>> As far as I know, IBM does not offer a free version of WebsphereMQ.
>> It's their flagship messaging product and they always collect on it.
>>
>> Having said that, it is obviously in Axis2's interest to support
>> WebsphereMQ as it is one of two dominant messaging products in the
>> world today. More importantly, it is in IBM's interest to have Axis2
>> supporting WebsphereMQ.
>>
>> I'm an IBM business partner so I obviously can't just send over a
>> copy, but I do note that there are quite a few Axis2 committers that
>> work for IBM - can they source a copy? If we can get a copy sent to
>> you I can certainly write up a quick one-page run-sheet outling how
>> to setup QueueManagers, Queues, Authorities etc to conduct a test.
>>
>> Alternatively, in the meantime, if the changes are made, I can
>> confirm whether they succeeded or not. Is this sufficient or do you
>> wish to have this become a part of the standard regression test suite?
>>
>> Unfortunately I'm having no end of trouble getting maven to behave
>> properly with our proxy so I can't build locally at the moment. :-(
>>
>> Mark B
>>
>>
>> ________________________________
>>
>> From: Asankha C. Perera [mailto:asankha@wso2.com]
>> Sent: Mon 6/18/2007 10:01 PM
>> To: axis-dev@ws.apache.org
>> Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ
>> doesn't support 'CLIENT' connections
>>
>>
>> Mark
>>
>> Does WebSphere have a community edition (i.e. that does not require
>> the purchase of a license) that could be used to test this fix?
>>
>> asankha
>>
>> Mark Badorrek (JIRA) wrote:
>>
>> [
>> https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Mark Badorrek updated AXIS2-2816:
>> ---------------------------------
>>
>> Attachment: Axis2-websphereMQ-fix.zip
>>
>> Can't test as I can't build Axis2 under maven at the moment.
>> If this is included in the nightly build I can run it through
>> a websphereMQ test.
>>
>> Current functionality remains unchanged; there is no logical
>> or API modification.
>> The new functionality is only activated if the new parameters
>> are present in the JNDI tree.
>>
>>
>>
>>
>>
>> JMS over WebsphereMQ doesn't support 'CLIENT'
>> connections
>>
>> ---------------------------------------------------------
>>
>> Key: AXIS2-2816
>> URL:
>> https://issues.apache.org/jira/browse/AXIS2-2816
>> Project: Axis 2.0 (Axis2)
>> Issue Type: Bug
>> Components: kernel
>> Affects Versions: 1.2
>> Environment: Tomcat 6, WindowsXP, WebsphereMQ
>> 6.0
>> Reporter: Mark Badorrek
>> Attachments: Axis2-websphereMQ-fix.zip
>>
>>
>> Currently Axis2 can only connect withthe
>> factory.createConnection() method from the JMS API.
>> 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.
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For
>> additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi David, Mark
I think for right now this would work fine - if Mark can validate that
the fixes does work as expected, and not break anything else. However in
the longer run, and to ensure that we could support MQ as well as
ActiveMQ and any other JMS implementation the best we can, it would make
sense for me and any others to get that copy installed. Hopefully, I
will not need Websphere, DB2 etc..etc.. to just get MQ running ;-)
thanks
asankha
David Illsley wrote:
> Mark, Asankha,
> I believe that developerworks does provide a free 90 day trial version
> of WebSphere MQ [1]. Does that satisfy your needs?
> Cheers,
> David
>
> [1]
> http://www.ibm.com/developerworks/downloads/ws/wmq/?S_TACT=105AGX10&S_CMP=LP
>
>
>
> On 18/06/07, Mark Badorrek <mb...@avoga.com.au> wrote:
>> Hi asankha,
>>
>> As far as I know, IBM does not offer a free version of WebsphereMQ.
>> It's their flagship messaging product and they always collect on it.
>>
>> Having said that, it is obviously in Axis2's interest to support
>> WebsphereMQ as it is one of two dominant messaging products in the
>> world today. More importantly, it is in IBM's interest to have Axis2
>> supporting WebsphereMQ.
>>
>> I'm an IBM business partner so I obviously can't just send over a
>> copy, but I do note that there are quite a few Axis2 committers that
>> work for IBM - can they source a copy? If we can get a copy sent to
>> you I can certainly write up a quick one-page run-sheet outling how
>> to setup QueueManagers, Queues, Authorities etc to conduct a test.
>>
>> Alternatively, in the meantime, if the changes are made, I can
>> confirm whether they succeeded or not. Is this sufficient or do you
>> wish to have this become a part of the standard regression test suite?
>>
>> Unfortunately I'm having no end of trouble getting maven to behave
>> properly with our proxy so I can't build locally at the moment. :-(
>>
>> Mark B
>>
>>
>> ________________________________
>>
>> From: Asankha C. Perera [mailto:asankha@wso2.com]
>> Sent: Mon 6/18/2007 10:01 PM
>> To: axis-dev@ws.apache.org
>> Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ
>> doesn't support 'CLIENT' connections
>>
>>
>> Mark
>>
>> Does WebSphere have a community edition (i.e. that does not require
>> the purchase of a license) that could be used to test this fix?
>>
>> asankha
>>
>> Mark Badorrek (JIRA) wrote:
>>
>> [
>> https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Mark Badorrek updated AXIS2-2816:
>> ---------------------------------
>>
>> Attachment: Axis2-websphereMQ-fix.zip
>>
>> Can't test as I can't build Axis2 under maven at the moment.
>> If this is included in the nightly build I can run it through
>> a websphereMQ test.
>>
>> Current functionality remains unchanged; there is no logical
>> or API modification.
>> The new functionality is only activated if the new parameters
>> are present in the JNDI tree.
>>
>>
>>
>>
>>
>> JMS over WebsphereMQ doesn't support 'CLIENT'
>> connections
>>
>> ---------------------------------------------------------
>>
>> Key: AXIS2-2816
>> URL:
>> https://issues.apache.org/jira/browse/AXIS2-2816
>> Project: Axis 2.0 (Axis2)
>> Issue Type: Bug
>> Components: kernel
>> Affects Versions: 1.2
>> Environment: Tomcat 6, WindowsXP, WebsphereMQ
>> 6.0
>> Reporter: Mark Badorrek
>> Attachments: Axis2-websphereMQ-fix.zip
>>
>>
>> Currently Axis2 can only connect withthe
>> factory.createConnection() method from the JMS API.
>> 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.
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For
>> additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Posted by David Illsley <da...@gmail.com>.
Mark, Asankha,
I believe that developerworks does provide a free 90 day trial version
of WebSphere MQ [1]. Does that satisfy your needs?
Cheers,
David
[1] http://www.ibm.com/developerworks/downloads/ws/wmq/?S_TACT=105AGX10&S_CMP=LP
On 18/06/07, Mark Badorrek <mb...@avoga.com.au> wrote:
> Hi asankha,
>
> As far as I know, IBM does not offer a free version of WebsphereMQ. It's their flagship messaging product and they always collect on it.
>
> Having said that, it is obviously in Axis2's interest to support WebsphereMQ as it is one of two dominant messaging products in the world today. More importantly, it is in IBM's interest to have Axis2 supporting WebsphereMQ.
>
> I'm an IBM business partner so I obviously can't just send over a copy, but I do note that there are quite a few Axis2 committers that work for IBM - can they source a copy? If we can get a copy sent to you I can certainly write up a quick one-page run-sheet outling how to setup QueueManagers, Queues, Authorities etc to conduct a test.
>
> Alternatively, in the meantime, if the changes are made, I can confirm whether they succeeded or not. Is this sufficient or do you wish to have this become a part of the standard regression test suite?
>
> Unfortunately I'm having no end of trouble getting maven to behave properly with our proxy so I can't build locally at the moment. :-(
>
> Mark B
>
>
> ________________________________
>
> From: Asankha C. Perera [mailto:asankha@wso2.com]
> Sent: Mon 6/18/2007 10:01 PM
> To: axis-dev@ws.apache.org
> Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
>
>
> Mark
>
> Does WebSphere have a community edition (i.e. that does not require the purchase of a license) that could be used to test this fix?
>
> asankha
>
> Mark Badorrek (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Mark Badorrek updated AXIS2-2816:
> ---------------------------------
>
> Attachment: Axis2-websphereMQ-fix.zip
>
> Can't test as I can't build Axis2 under maven at the moment.
> If this is included in the nightly build I can run it through a websphereMQ test.
>
> Current functionality remains unchanged; there is no logical or API modification.
> The new functionality is only activated if the new parameters are present in the JNDI tree.
>
>
>
>
>
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0
> Reporter: Mark Badorrek
> Attachments: Axis2-websphereMQ-fix.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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.
>
>
>
>
> --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
RE: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Posted by Mark Badorrek <mb...@avoga.com.au>.
Hi asankha,
As far as I know, IBM does not offer a free version of WebsphereMQ. It's their flagship messaging product and they always collect on it.
Having said that, it is obviously in Axis2's interest to support WebsphereMQ as it is one of two dominant messaging products in the world today. More importantly, it is in IBM's interest to have Axis2 supporting WebsphereMQ.
I'm an IBM business partner so I obviously can't just send over a copy, but I do note that there are quite a few Axis2 committers that work for IBM - can they source a copy? If we can get a copy sent to you I can certainly write up a quick one-page run-sheet outling how to setup QueueManagers, Queues, Authorities etc to conduct a test.
Alternatively, in the meantime, if the changes are made, I can confirm whether they succeeded or not. Is this sufficient or do you wish to have this become a part of the standard regression test suite?
Unfortunately I'm having no end of trouble getting maven to behave properly with our proxy so I can't build locally at the moment. :-(
Mark B
________________________________
From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Mon 6/18/2007 10:01 PM
To: axis-dev@ws.apache.org
Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Mark
Does WebSphere have a community edition (i.e. that does not require the purchase of a license) that could be used to test this fix?
asankha
Mark Badorrek (JIRA) wrote:
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Badorrek updated AXIS2-2816:
---------------------------------
Attachment: Axis2-websphereMQ-fix.zip
Can't test as I can't build Axis2 under maven at the moment.
If this is included in the nightly build I can run it through a websphereMQ test.
Current functionality remains unchanged; there is no logical or API modification.
The new functionality is only activated if the new parameters are present in the JNDI tree.
JMS over WebsphereMQ doesn't support 'CLIENT' connections
---------------------------------------------------------
Key: AXIS2-2816
URL: https://issues.apache.org/jira/browse/AXIS2-2816
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.2
Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0
Reporter: Mark Badorrek
Attachments: Axis2-websphereMQ-fix.zip
Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
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.
--------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Mark Badorrek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Badorrek updated AXIS2-2816:
---------------------------------
Attachment: Axis2-websphereMQ-fix.zip
Can't test as I can't build Axis2 under maven at the moment.
If this is included in the nightly build I can run it through a websphereMQ test.
Current functionality remains unchanged; there is no logical or API modification.
The new functionality is only activated if the new parameters are present in the JNDI tree.
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0
> Reporter: Mark Badorrek
> Attachments: Axis2-websphereMQ-fix.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Mark Badorrek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509727 ]
Mark Badorrek commented on AXIS2-2816:
--------------------------------------
Asankha
I've tried out the fix in the nightly build and everything seems fine. We'll do some more testing over the next few days but at the moment it look good.
Many thanks,
Mark B
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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: Axis2-websphereMQ-fix.zip, WebsphereMQ-fix-29-06-2007.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2816:
------------------------------------
Assignee: Asankha C. Perera
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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
> Attachments: Axis2-websphereMQ-fix.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2816) JMS over WebsphereMQ doesn't support
'CLIENT' connections
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved AXIS2-2816.
-------------------------------------
Resolution: Fixed
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> ---------------------------------------------------------
>
> Key: AXIS2-2816
> URL: https://issues.apache.org/jira/browse/AXIS2-2816
> 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: Axis2-websphereMQ-fix.zip, WebsphereMQ-fix-29-06-2007.zip
>
>
> Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org