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 "Cathal Callaghan (JIRA)" <ji...@apache.org> on 2008/09/10 12:30:46 UTC
[jira] Created: (AXIS2-4025) Using JMSMessageID as correlationID
for JMS messages
Using JMSMessageID as correlationID for JMS messages
----------------------------------------------------
Key: AXIS2-4025
URL: https://issues.apache.org/jira/browse/AXIS2-4025
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel, transports
Environment: OS: Windows XP Pro 2002 Service Pack 2
Reporter: Cathal Callaghan
Fix For: 1.4
The correlationID solution currently in place in Axis2 version 1.4 does not work.
Currently the option is available to specify a correlationID but when the MessageConsumer is created no MessageSelector is specified. This means that the MessageConsumer will take any message off the queue.
Also, currently the only way to use a correlationID is to explicity specify an ID via the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish to use the option of using the JMSMessageID of the message as the correlationID.
I have attached a proposed solution which firstly ensures that the MessageConsumer is created using a MessageSelector. Also i have given the user a choice, if they explicity specify a correlationID then this will be used otherwise the JMSMessageID of the message will be used as the correlationID.
Thanks,
Cathal
--
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-4025) Using JMSMessageID as correlationID
for JMS messages
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654506#action_12654506 ]
Asankha C. Perera commented on AXIS2-4025:
------------------------------------------
Hi Cathal
We have updated the JMS transport quite a bit recently.. could you check if the issue still persists? If so, you are encouraged to offer a patch to further enhance
thanks
asankha
> Using JMSMessageID as correlationID for JMS messages
> ----------------------------------------------------
>
> Key: AXIS2-4025
> URL: https://issues.apache.org/jira/browse/AXIS2-4025
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel, transports
> Environment: OS: Windows XP Pro 2002 Service Pack 2
> Reporter: Cathal Callaghan
> Fix For: 1.4
>
> Attachments: JMSMessageReceiver.java, JMSSender.java
>
>
> The correlationID solution currently in place in Axis2 version 1.4 does not work.
> Currently the option is available to specify a correlationID but when the MessageConsumer is created no MessageSelector is specified. This means that the MessageConsumer will take any message off the queue.
> Also, currently the only way to use a correlationID is to explicity specify an ID via the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish to use the option of using the JMSMessageID of the message as the correlationID.
> I have attached a proposed solution which firstly ensures that the MessageConsumer is created using a MessageSelector. Also i have given the user a choice, if they explicity specify a correlationID then this will be used otherwise the JMSMessageID of the message will be used as the correlationID.
> Thanks,
> Cathal
--
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-4025) Using JMSMessageID as correlationID
for JMS messages
Posted by "Cathal Callaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cathal Callaghan updated AXIS2-4025:
------------------------------------
Attachment: JMSSender.java
Attaching propsed solution as stated in description
> Using JMSMessageID as correlationID for JMS messages
> ----------------------------------------------------
>
> Key: AXIS2-4025
> URL: https://issues.apache.org/jira/browse/AXIS2-4025
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel, transports
> Environment: OS: Windows XP Pro 2002 Service Pack 2
> Reporter: Cathal Callaghan
> Fix For: 1.4
>
> Attachments: JMSMessageReceiver.java, JMSSender.java
>
>
> The correlationID solution currently in place in Axis2 version 1.4 does not work.
> Currently the option is available to specify a correlationID but when the MessageConsumer is created no MessageSelector is specified. This means that the MessageConsumer will take any message off the queue.
> Also, currently the only way to use a correlationID is to explicity specify an ID via the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish to use the option of using the JMSMessageID of the message as the correlationID.
> I have attached a proposed solution which firstly ensures that the MessageConsumer is created using a MessageSelector. Also i have given the user a choice, if they explicity specify a correlationID then this will be used otherwise the JMSMessageID of the message will be used as the correlationID.
> Thanks,
> Cathal
--
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-4025) Using JMSMessageID as correlationID
for JMS messages
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved AXIS2-4025.
--------------------------------------
Resolution: Won't Fix
Assignee: Asankha C. Perera
The JMS transport is not within the Axis2 project anymore. If there is any issue, please use the latest version from WS-Commons
> Using JMSMessageID as correlationID for JMS messages
> ----------------------------------------------------
>
> Key: AXIS2-4025
> URL: https://issues.apache.org/jira/browse/AXIS2-4025
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel, transports
> Environment: OS: Windows XP Pro 2002 Service Pack 2
> Reporter: Cathal Callaghan
> Assignee: Asankha C. Perera
> Fix For: 1.4
>
> Attachments: JMSMessageReceiver.java, JMSSender.java
>
>
> The correlationID solution currently in place in Axis2 version 1.4 does not work.
> Currently the option is available to specify a correlationID but when the MessageConsumer is created no MessageSelector is specified. This means that the MessageConsumer will take any message off the queue.
> Also, currently the only way to use a correlationID is to explicity specify an ID via the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish to use the option of using the JMSMessageID of the message as the correlationID.
> I have attached a proposed solution which firstly ensures that the MessageConsumer is created using a MessageSelector. Also i have given the user a choice, if they explicity specify a correlationID then this will be used otherwise the JMSMessageID of the message will be used as the correlationID.
> Thanks,
> Cathal
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4025) Using JMSMessageID as correlationID
for JMS messages
Posted by "Cathal Callaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cathal Callaghan updated AXIS2-4025:
------------------------------------
Attachment: JMSMessageReceiver.java
Attaching propsed solution as stated in description
> Using JMSMessageID as correlationID for JMS messages
> ----------------------------------------------------
>
> Key: AXIS2-4025
> URL: https://issues.apache.org/jira/browse/AXIS2-4025
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel, transports
> Environment: OS: Windows XP Pro 2002 Service Pack 2
> Reporter: Cathal Callaghan
> Fix For: 1.4
>
> Attachments: JMSMessageReceiver.java, JMSSender.java
>
>
> The correlationID solution currently in place in Axis2 version 1.4 does not work.
> Currently the option is available to specify a correlationID but when the MessageConsumer is created no MessageSelector is specified. This means that the MessageConsumer will take any message off the queue.
> Also, currently the only way to use a correlationID is to explicity specify an ID via the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish to use the option of using the JMSMessageID of the message as the correlationID.
> I have attached a proposed solution which firstly ensures that the MessageConsumer is created using a MessageSelector. Also i have given the user a choice, if they explicity specify a correlationID then this will be used otherwise the JMSMessageID of the message will be used as the correlationID.
> Thanks,
> Cathal
--
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-4025) Using JMSMessageID as correlationID
for JMS messages
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630298#action_12630298 ]
Andreas Veithen commented on AXIS2-4025:
----------------------------------------
Can you provide a patch rather than the modified code?
> Using JMSMessageID as correlationID for JMS messages
> ----------------------------------------------------
>
> Key: AXIS2-4025
> URL: https://issues.apache.org/jira/browse/AXIS2-4025
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel, transports
> Environment: OS: Windows XP Pro 2002 Service Pack 2
> Reporter: Cathal Callaghan
> Fix For: 1.4
>
> Attachments: JMSMessageReceiver.java, JMSSender.java
>
>
> The correlationID solution currently in place in Axis2 version 1.4 does not work.
> Currently the option is available to specify a correlationID but when the MessageConsumer is created no MessageSelector is specified. This means that the MessageConsumer will take any message off the queue.
> Also, currently the only way to use a correlationID is to explicity specify an ID via the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish to use the option of using the JMSMessageID of the message as the correlationID.
> I have attached a proposed solution which firstly ensures that the MessageConsumer is created using a MessageSelector. Also i have given the user a choice, if they explicity specify a correlationID then this will be used otherwise the JMSMessageID of the message will be used as the correlationID.
> Thanks,
> Cathal
--
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-4025) Using JMSMessageID as correlationID
for JMS messages
Posted by "Cathal Callaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631300#action_12631300 ]
Cathal Callaghan commented on AXIS2-4025:
-----------------------------------------
Hi Andreas,
Network restrictions here mean that I cannot provide a patch. I have
submitted code before in this manner and it was accepted.
Thanks,
Cathal
> Using JMSMessageID as correlationID for JMS messages
> ----------------------------------------------------
>
> Key: AXIS2-4025
> URL: https://issues.apache.org/jira/browse/AXIS2-4025
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel, transports
> Environment: OS: Windows XP Pro 2002 Service Pack 2
> Reporter: Cathal Callaghan
> Fix For: 1.4
>
> Attachments: JMSMessageReceiver.java, JMSSender.java
>
>
> The correlationID solution currently in place in Axis2 version 1.4 does not work.
> Currently the option is available to specify a correlationID but when the MessageConsumer is created no MessageSelector is specified. This means that the MessageConsumer will take any message off the queue.
> Also, currently the only way to use a correlationID is to explicity specify an ID via the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish to use the option of using the JMSMessageID of the message as the correlationID.
> I have attached a proposed solution which firstly ensures that the MessageConsumer is created using a MessageSelector. Also i have given the user a choice, if they explicity specify a correlationID then this will be used otherwise the JMSMessageID of the message will be used as the correlationID.
> Thanks,
> Cathal
--
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