[esb-issues] [JBoss JIRA] Updated: (JBESB-1450) SOAPProcessor cannot handle large message backlog

[Martin Vecera (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBESB-1450?page=all ]

Martin Vecera updated JBESB-1450:
---------------------------------

    Attachment: server.log.gz

Note the timing - there's 5s pause after deploying the webservice and before committing the message generating transaction. After committing it, the error appears almost immediately.

> SOAPProcessor cannot handle large message backlog
> -------------------------------------------------
>
>                 Key: JBESB-1450
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1450
>             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.0 beta 1, Oracle 10g
>            Reporter: Martin Vecera
>            Priority: Blocker
>         Attachments: server.log.gz
>
>
> When I generate a big backlog of messages (~10,000) the performance test based on webservice_producer is not able to handle it. It fails on database deadlock due to "Maximum number of cursors exceeded". Maximum number of cursors was set to 600. The issue doesn't appear when MySQL is used.
> See attached log.
> Steps to reproduce:
> 0. Configure JBossESB to use Oracle DB.
> 1. Generate a large backlog of 5kB SOAP messages in a transaction (don't commit it).
> 2. Take webservice_producer, comment out all println, print/debug actions, and non-JMS tests.
> 3. Deploy changed webservice_produce and wait for WSDL to be loaded.
> 4. Commit the transaction from 1.
> If the messages are passed to the server slowly, the problem doesn't appear.

-- 
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