You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Rajeev Verma (JIRA)" <ji...@apache.org> on 2010/09/21 01:27:33 UTC
[jira] Created: (AXIS2-4825) Transaction rollback to backout
requeue with IBM MQ is not working
Transaction rollback to backout requeue with IBM MQ is not working
------------------------------------------------------------------
Key: AXIS2-4825
URL: https://issues.apache.org/jira/browse/AXIS2-4825
Project: Axis2
Issue Type: Bug
Components: transports
Affects Versions: 1.5.1
Environment: Operating System - Windows XP Professional
Tomcat v6.0.28
IBM Websphere MQ v7.0.1.2
Axis2 v1.5.1
JMS Transport version 1.0.0
Reporter: Rajeev Verma
There is an issue with uncommitted messages in the backout queue. This is what we are doing:
We have enabled JMS transportreceiver and JMS transportsender on axis2 (v1.5.1) to connect to IBM Websphere MQ v7.0.1.2. My application is deployed on Tomcat v6.0.28 and services.xml in my service aar file has following parameters set:
<parameter name="transport.jms.ConnectionFactory" locked="false"> LGRIDConnectionFactory</parameter>
<parameter name="transport.jms.Destination" locked="false">TEST</parameter>
<parameter name="transport.jms.SessionAcknowledgement" locked="false">SESSION_TRANSACTED</parameter>
<parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
<parameter name="transport.jms.CacheLevel" locked="false">consumer</parameter>
<parameter name="transport.Transactionality" locked="false">local</parameter>
Service has an operation which gets triggered when a message arrives to TEST queue. We have set SessionTransacted to true so that in case of any exception message gets rolled back to queue and obviously consumed by the application to reprocess. We have also setup Backout Threshold (BOTHRESH) as 2 and Backout requeue queue (BOQNAME) as TEST_DLQ on this TEST Queue. We want application to re-try two times if it still fails move the message to Backout requeue queue.
Now this complete configuration works as we expected but the messages which are moved to Backout requeue queue are not committed and we are not able to browse those messages. When we stop the tomcat messages are moved back to TEST queue and we can browse there. If we start the Tomcat again without removing those message, application does not pick them and they are directly moved to Backout requeue queue and still has uncommitted state. We were expecting the bad messages to get committed in backout queue, so that they can be browsed and handled manually.
Please let us know if any fix is available for this.
Many thanks!!!
Thanks and Regards,
Rajeev Verma
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (TRANSPORTS-17) Transaction rollback to backout
requeue with IBM MQ is not working
Posted by "Rajeev Verma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921031#action_12921031 ]
Rajeev Verma commented on TRANSPORTS-17:
----------------------------------------
This issue was happening as my local set up was connecting to IBM MQ7.x with IBM MQ6.x libraries. Issue is resolved once I upgraded the libraries. Closing the issue.
> Transaction rollback to backout requeue with IBM MQ is not working
> ------------------------------------------------------------------
>
> Key: TRANSPORTS-17
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-17
> Project: Axis2 Transports
> Issue Type: Bug
> Components: JMS
> Affects Versions: 1.0.0
> Environment: Operating System - Windows XP Professional
> Tomcat v6.0.28
> IBM Websphere MQ v7.0.1.2
> Axis2 v1.5.1
> JMS Transport version 1.0.0
> Reporter: Rajeev Verma
>
> There is an issue with uncommitted messages in the backout queue. This is what we are doing:
> We have enabled JMS transportreceiver and JMS transportsender on axis2 (v1.5.1) to connect to IBM Websphere MQ v7.0.1.2. My application is deployed on Tomcat v6.0.28 and services.xml in my service aar file has following parameters set:
> <parameter name="transport.jms.ConnectionFactory" locked="false"> LGRIDConnectionFactory</parameter>
> <parameter name="transport.jms.Destination" locked="false">TEST</parameter>
> <parameter name="transport.jms.SessionAcknowledgement" locked="false">SESSION_TRANSACTED</parameter>
> <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
> <parameter name="transport.jms.CacheLevel" locked="false">consumer</parameter>
> <parameter name="transport.Transactionality" locked="false">local</parameter>
> Service has an operation which gets triggered when a message arrives to TEST queue. We have set SessionTransacted to true so that in case of any exception message gets rolled back to queue and obviously consumed by the application to reprocess. We have also setup Backout Threshold (BOTHRESH) as 2 and Backout requeue queue (BOQNAME) as TEST_DLQ on this TEST Queue. We want application to re-try two times if it still fails move the message to Backout requeue queue.
> Now this complete configuration works as we expected but the messages which are moved to Backout requeue queue are not committed and we are not able to browse those messages. When we stop the tomcat messages are moved back to TEST queue and we can browse there. If we start the Tomcat again without removing those message, application does not pick them and they are directly moved to Backout requeue queue and still has uncommitted state. We were expecting the bad messages to get committed in backout queue, so that they can be browsed and handled manually.
> Please let us know if any fix is available for this.
> Many thanks!!!
> Thanks and Regards,
> Rajeev Verma
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Moved: (TRANSPORTS-17) Transaction rollback to backout
requeue with IBM MQ is not working
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen moved AXIS2-4825 to TRANSPORTS-17:
--------------------------------------------------
Project: Axis2 Transports (was: Axis2)
Key: TRANSPORTS-17 (was: AXIS2-4825)
Affects Version/s: 1.0.0
(was: 1.5.1)
Component/s: JMS
(was: transports)
> Transaction rollback to backout requeue with IBM MQ is not working
> ------------------------------------------------------------------
>
> Key: TRANSPORTS-17
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-17
> Project: Axis2 Transports
> Issue Type: Bug
> Components: JMS
> Affects Versions: 1.0.0
> Environment: Operating System - Windows XP Professional
> Tomcat v6.0.28
> IBM Websphere MQ v7.0.1.2
> Axis2 v1.5.1
> JMS Transport version 1.0.0
> Reporter: Rajeev Verma
>
> There is an issue with uncommitted messages in the backout queue. This is what we are doing:
> We have enabled JMS transportreceiver and JMS transportsender on axis2 (v1.5.1) to connect to IBM Websphere MQ v7.0.1.2. My application is deployed on Tomcat v6.0.28 and services.xml in my service aar file has following parameters set:
> <parameter name="transport.jms.ConnectionFactory" locked="false"> LGRIDConnectionFactory</parameter>
> <parameter name="transport.jms.Destination" locked="false">TEST</parameter>
> <parameter name="transport.jms.SessionAcknowledgement" locked="false">SESSION_TRANSACTED</parameter>
> <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
> <parameter name="transport.jms.CacheLevel" locked="false">consumer</parameter>
> <parameter name="transport.Transactionality" locked="false">local</parameter>
> Service has an operation which gets triggered when a message arrives to TEST queue. We have set SessionTransacted to true so that in case of any exception message gets rolled back to queue and obviously consumed by the application to reprocess. We have also setup Backout Threshold (BOTHRESH) as 2 and Backout requeue queue (BOQNAME) as TEST_DLQ on this TEST Queue. We want application to re-try two times if it still fails move the message to Backout requeue queue.
> Now this complete configuration works as we expected but the messages which are moved to Backout requeue queue are not committed and we are not able to browse those messages. When we stop the tomcat messages are moved back to TEST queue and we can browse there. If we start the Tomcat again without removing those message, application does not pick them and they are directly moved to Backout requeue queue and still has uncommitted state. We were expecting the bad messages to get committed in backout queue, so that they can be browsed and handled manually.
> Please let us know if any fix is available for this.
> Many thanks!!!
> Thanks and Regards,
> Rajeev Verma
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Moved: (TRANSPORTS-17) Transaction rollback to backout
requeue with IBM MQ is not working
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen moved AXIS2-4825 to TRANSPORTS-17:
--------------------------------------------------
Project: Axis2 Transports (was: Axis2)
Key: TRANSPORTS-17 (was: AXIS2-4825)
Affects Version/s: 1.0.0
(was: 1.5.1)
Component/s: JMS
(was: transports)
> Transaction rollback to backout requeue with IBM MQ is not working
> ------------------------------------------------------------------
>
> Key: TRANSPORTS-17
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-17
> Project: Axis2 Transports
> Issue Type: Bug
> Components: JMS
> Affects Versions: 1.0.0
> Environment: Operating System - Windows XP Professional
> Tomcat v6.0.28
> IBM Websphere MQ v7.0.1.2
> Axis2 v1.5.1
> JMS Transport version 1.0.0
> Reporter: Rajeev Verma
>
> There is an issue with uncommitted messages in the backout queue. This is what we are doing:
> We have enabled JMS transportreceiver and JMS transportsender on axis2 (v1.5.1) to connect to IBM Websphere MQ v7.0.1.2. My application is deployed on Tomcat v6.0.28 and services.xml in my service aar file has following parameters set:
> <parameter name="transport.jms.ConnectionFactory" locked="false"> LGRIDConnectionFactory</parameter>
> <parameter name="transport.jms.Destination" locked="false">TEST</parameter>
> <parameter name="transport.jms.SessionAcknowledgement" locked="false">SESSION_TRANSACTED</parameter>
> <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
> <parameter name="transport.jms.CacheLevel" locked="false">consumer</parameter>
> <parameter name="transport.Transactionality" locked="false">local</parameter>
> Service has an operation which gets triggered when a message arrives to TEST queue. We have set SessionTransacted to true so that in case of any exception message gets rolled back to queue and obviously consumed by the application to reprocess. We have also setup Backout Threshold (BOTHRESH) as 2 and Backout requeue queue (BOQNAME) as TEST_DLQ on this TEST Queue. We want application to re-try two times if it still fails move the message to Backout requeue queue.
> Now this complete configuration works as we expected but the messages which are moved to Backout requeue queue are not committed and we are not able to browse those messages. When we stop the tomcat messages are moved back to TEST queue and we can browse there. If we start the Tomcat again without removing those message, application does not pick them and they are directly moved to Backout requeue queue and still has uncommitted state. We were expecting the bad messages to get committed in backout queue, so that they can be browsed and handled manually.
> Please let us know if any fix is available for this.
> Many thanks!!!
> Thanks and Regards,
> Rajeev Verma
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Closed: (TRANSPORTS-17) Transaction rollback to backout
requeue with IBM MQ is not working
Posted by "Rajeev Verma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajeev Verma closed TRANSPORTS-17.
----------------------------------
Resolution: Not A Problem
This is an issue due to mismatch in the IBM library files on my local system. No bug in axis2. Closing this issue.
> Transaction rollback to backout requeue with IBM MQ is not working
> ------------------------------------------------------------------
>
> Key: TRANSPORTS-17
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-17
> Project: Axis2 Transports
> Issue Type: Bug
> Components: JMS
> Affects Versions: 1.0.0
> Environment: Operating System - Windows XP Professional
> Tomcat v6.0.28
> IBM Websphere MQ v7.0.1.2
> Axis2 v1.5.1
> JMS Transport version 1.0.0
> Reporter: Rajeev Verma
>
> There is an issue with uncommitted messages in the backout queue. This is what we are doing:
> We have enabled JMS transportreceiver and JMS transportsender on axis2 (v1.5.1) to connect to IBM Websphere MQ v7.0.1.2. My application is deployed on Tomcat v6.0.28 and services.xml in my service aar file has following parameters set:
> <parameter name="transport.jms.ConnectionFactory" locked="false"> LGRIDConnectionFactory</parameter>
> <parameter name="transport.jms.Destination" locked="false">TEST</parameter>
> <parameter name="transport.jms.SessionAcknowledgement" locked="false">SESSION_TRANSACTED</parameter>
> <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
> <parameter name="transport.jms.CacheLevel" locked="false">consumer</parameter>
> <parameter name="transport.Transactionality" locked="false">local</parameter>
> Service has an operation which gets triggered when a message arrives to TEST queue. We have set SessionTransacted to true so that in case of any exception message gets rolled back to queue and obviously consumed by the application to reprocess. We have also setup Backout Threshold (BOTHRESH) as 2 and Backout requeue queue (BOQNAME) as TEST_DLQ on this TEST Queue. We want application to re-try two times if it still fails move the message to Backout requeue queue.
> Now this complete configuration works as we expected but the messages which are moved to Backout requeue queue are not committed and we are not able to browse those messages. When we stop the tomcat messages are moved back to TEST queue and we can browse there. If we start the Tomcat again without removing those message, application does not pick them and they are directly moved to Backout requeue queue and still has uncommitted state. We were expecting the bad messages to get committed in backout queue, so that they can be browsed and handled manually.
> Please let us know if any fix is available for this.
> Many thanks!!!
> Thanks and Regards,
> Rajeev Verma
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Moved: (TRANSPORTS-17) Transaction rollback to backout
requeue with IBM MQ is not working
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen moved AXIS2-4825 to TRANSPORTS-17:
--------------------------------------------------
Project: Axis2 Transports (was: Axis2)
Key: TRANSPORTS-17 (was: AXIS2-4825)
Affects Version/s: 1.0.0
(was: 1.5.1)
Component/s: JMS
(was: transports)
> Transaction rollback to backout requeue with IBM MQ is not working
> ------------------------------------------------------------------
>
> Key: TRANSPORTS-17
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-17
> Project: Axis2 Transports
> Issue Type: Bug
> Components: JMS
> Affects Versions: 1.0.0
> Environment: Operating System - Windows XP Professional
> Tomcat v6.0.28
> IBM Websphere MQ v7.0.1.2
> Axis2 v1.5.1
> JMS Transport version 1.0.0
> Reporter: Rajeev Verma
>
> There is an issue with uncommitted messages in the backout queue. This is what we are doing:
> We have enabled JMS transportreceiver and JMS transportsender on axis2 (v1.5.1) to connect to IBM Websphere MQ v7.0.1.2. My application is deployed on Tomcat v6.0.28 and services.xml in my service aar file has following parameters set:
> <parameter name="transport.jms.ConnectionFactory" locked="false"> LGRIDConnectionFactory</parameter>
> <parameter name="transport.jms.Destination" locked="false">TEST</parameter>
> <parameter name="transport.jms.SessionAcknowledgement" locked="false">SESSION_TRANSACTED</parameter>
> <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
> <parameter name="transport.jms.CacheLevel" locked="false">consumer</parameter>
> <parameter name="transport.Transactionality" locked="false">local</parameter>
> Service has an operation which gets triggered when a message arrives to TEST queue. We have set SessionTransacted to true so that in case of any exception message gets rolled back to queue and obviously consumed by the application to reprocess. We have also setup Backout Threshold (BOTHRESH) as 2 and Backout requeue queue (BOQNAME) as TEST_DLQ on this TEST Queue. We want application to re-try two times if it still fails move the message to Backout requeue queue.
> Now this complete configuration works as we expected but the messages which are moved to Backout requeue queue are not committed and we are not able to browse those messages. When we stop the tomcat messages are moved back to TEST queue and we can browse there. If we start the Tomcat again without removing those message, application does not pick them and they are directly moved to Backout requeue queue and still has uncommitted state. We were expecting the bad messages to get committed in backout queue, so that they can be browsed and handled manually.
> Please let us know if any fix is available for this.
> Many thanks!!!
> Thanks and Regards,
> Rajeev Verma
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Moved: (TRANSPORTS-17) Transaction rollback to backout
requeue with IBM MQ is not working
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen moved AXIS2-4825 to TRANSPORTS-17:
--------------------------------------------------
Project: Axis2 Transports (was: Axis2)
Key: TRANSPORTS-17 (was: AXIS2-4825)
Affects Version/s: 1.0.0
(was: 1.5.1)
Component/s: JMS
(was: transports)
> Transaction rollback to backout requeue with IBM MQ is not working
> ------------------------------------------------------------------
>
> Key: TRANSPORTS-17
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-17
> Project: Axis2 Transports
> Issue Type: Bug
> Components: JMS
> Affects Versions: 1.0.0
> Environment: Operating System - Windows XP Professional
> Tomcat v6.0.28
> IBM Websphere MQ v7.0.1.2
> Axis2 v1.5.1
> JMS Transport version 1.0.0
> Reporter: Rajeev Verma
>
> There is an issue with uncommitted messages in the backout queue. This is what we are doing:
> We have enabled JMS transportreceiver and JMS transportsender on axis2 (v1.5.1) to connect to IBM Websphere MQ v7.0.1.2. My application is deployed on Tomcat v6.0.28 and services.xml in my service aar file has following parameters set:
> <parameter name="transport.jms.ConnectionFactory" locked="false"> LGRIDConnectionFactory</parameter>
> <parameter name="transport.jms.Destination" locked="false">TEST</parameter>
> <parameter name="transport.jms.SessionAcknowledgement" locked="false">SESSION_TRANSACTED</parameter>
> <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
> <parameter name="transport.jms.CacheLevel" locked="false">consumer</parameter>
> <parameter name="transport.Transactionality" locked="false">local</parameter>
> Service has an operation which gets triggered when a message arrives to TEST queue. We have set SessionTransacted to true so that in case of any exception message gets rolled back to queue and obviously consumed by the application to reprocess. We have also setup Backout Threshold (BOTHRESH) as 2 and Backout requeue queue (BOQNAME) as TEST_DLQ on this TEST Queue. We want application to re-try two times if it still fails move the message to Backout requeue queue.
> Now this complete configuration works as we expected but the messages which are moved to Backout requeue queue are not committed and we are not able to browse those messages. When we stop the tomcat messages are moved back to TEST queue and we can browse there. If we start the Tomcat again without removing those message, application does not pick them and they are directly moved to Backout requeue queue and still has uncommitted state. We were expecting the bad messages to get committed in backout queue, so that they can be browsed and handled manually.
> Please let us know if any fix is available for this.
> Many thanks!!!
> Thanks and Regards,
> Rajeev Verma
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Moved: (TRANSPORTS-17) Transaction rollback to backout
requeue with IBM MQ is not working
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen moved AXIS2-4825 to TRANSPORTS-17:
--------------------------------------------------
Project: Axis2 Transports (was: Axis2)
Key: TRANSPORTS-17 (was: AXIS2-4825)
Affects Version/s: 1.0.0
(was: 1.5.1)
Component/s: JMS
(was: transports)
> Transaction rollback to backout requeue with IBM MQ is not working
> ------------------------------------------------------------------
>
> Key: TRANSPORTS-17
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-17
> Project: Axis2 Transports
> Issue Type: Bug
> Components: JMS
> Affects Versions: 1.0.0
> Environment: Operating System - Windows XP Professional
> Tomcat v6.0.28
> IBM Websphere MQ v7.0.1.2
> Axis2 v1.5.1
> JMS Transport version 1.0.0
> Reporter: Rajeev Verma
>
> There is an issue with uncommitted messages in the backout queue. This is what we are doing:
> We have enabled JMS transportreceiver and JMS transportsender on axis2 (v1.5.1) to connect to IBM Websphere MQ v7.0.1.2. My application is deployed on Tomcat v6.0.28 and services.xml in my service aar file has following parameters set:
> <parameter name="transport.jms.ConnectionFactory" locked="false"> LGRIDConnectionFactory</parameter>
> <parameter name="transport.jms.Destination" locked="false">TEST</parameter>
> <parameter name="transport.jms.SessionAcknowledgement" locked="false">SESSION_TRANSACTED</parameter>
> <parameter name="transport.jms.SessionTransacted" locked="false">true</parameter>
> <parameter name="transport.jms.CacheLevel" locked="false">consumer</parameter>
> <parameter name="transport.Transactionality" locked="false">local</parameter>
> Service has an operation which gets triggered when a message arrives to TEST queue. We have set SessionTransacted to true so that in case of any exception message gets rolled back to queue and obviously consumed by the application to reprocess. We have also setup Backout Threshold (BOTHRESH) as 2 and Backout requeue queue (BOQNAME) as TEST_DLQ on this TEST Queue. We want application to re-try two times if it still fails move the message to Backout requeue queue.
> Now this complete configuration works as we expected but the messages which are moved to Backout requeue queue are not committed and we are not able to browse those messages. When we stop the tomcat messages are moved back to TEST queue and we can browse there. If we start the Tomcat again without removing those message, application does not pick them and they are directly moved to Backout requeue queue and still has uncommitted state. We were expecting the bad messages to get committed in backout queue, so that they can be browsed and handled manually.
> Please let us know if any fix is available for this.
> Many thanks!!!
> Thanks and Regards,
> Rajeev Verma
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org