axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit (JIRA)" <>
Subject [jira] [Updated] (AXIS2-5670) Axis2 1.6.2
Date Wed, 17 Sep 2014 18:23:35 GMT


Rohit updated AXIS2-5670:

Document is a draft version, i expect user to apply his knowledge where ever document is observed
to be helpless and keep updating new version of the document against the jira. That would
help it to be better :)

> Axis2 1.6.2
> -----------
>                 Key: AXIS2-5670
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>         Environment: IBM MQ, Axis2 1.6.2
>            Reporter: Rohit
>            Priority: Critical
>             Fix For: Transports 1.0.0
>         Attachments:
> 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

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

View raw message