[jira] [Resolved] (AXIS2-5670) Axis2 1.6.2

["Rohit (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohit resolved AXIS2-5670.
--------------------------
       Resolution: Fixed
    Fix Version/s: Transports 1.0.0

Did a code fix in my env. if sounds acceptable then please have the same incorporated. If any thing incorrect do let me know, i shall rectify my code.

> Axis2 1.6.2
> -----------
>
>                 Key: AXIS2-5670
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5670
>             Project: Axis2
>          Issue Type: Bug
>         Environment: IBM MQ, Axis2 1.6.2
>            Reporter: Rohit
>            Priority: Critical
>             Fix For: Transports 1.0.0
>
>
> Hi,
> I have enabled IBM MQ Communication from Axis2 1.6.2, I have added 1 new webservice along with default web service Version of Axis2. While startup i can see couple of JMSWorkers gets registered i.e JMSWorker1 for Version and JMSWorker2 for my new webservice. When i am pushing message from SOAUP UI via Hermes on to IBM Request Q. for new web service. Threadpool randomly allocating the request to axis worker. i.e. If request is picked up by JMSWorker1 which is meant for Version services. I get error. If request gets picked up bu JMSWorker2 i.e. My newly added webservice worker then execution happens properly. I think its a bug. Please correct me if i am wrong.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org