[esb-issues] [JBoss JIRA] Commented: (JBESB-1449) SOAPClient cannot handle more than 1 thread in ESB listener

[Kevin Conner (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-1449?page=comments#action_12394716 ] 
            
Kevin Conner commented on JBESB-1449:
-------------------------------------

I was unable to reproduce any problems, given the instructions above, but I believe I may have identified the causes.  The problems only came to light once my configuration was altered to send 10000 messages into the service.

There were three causes identified
- HttpClient was configured to use an unsafe connection factory
- SoapClient was using a DocumentBuilder in an unsafe manner
- SoapUIClientService was using a DocumentBuilder in an unsafe manner.

Once these were fixed I re-ran my test three times.  No further concurrency errors were seen to occur.

> SOAPClient cannot handle more than 1 thread in ESB listener
> -----------------------------------------------------------
>
>                 Key: JBESB-1449
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1449
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: 4.2.1
>         Environment: SOA-P 4.2.0beta1
>            Reporter: Martin Vecera
>         Assigned To: Kevin Conner
>            Priority: Blocker
>             Fix For: 4.2.1 CP1
>
>         Attachments: server.log.gz
>
>
> When I tried to increase number of threads in ESB listener in webservice_consumer1 quickstart the server was not able to process more than 2 messages without problems.
> Steps to reproduce:
> 1. Change webservice_consumer1 to sent ~10 messages.
> 2. Change ESB listener thread count in jboss-esb.xml to at least 2.
> 2. Deploy it.
> 3. Run it and see the server log.
> The server show different errors. Usually: Connection reset, Connection closed, Bad chunk size, Unable to parse status code. See attached file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira