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

Tue Jan 8 04:26:43 EST 2008

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

Martin Vecera commented on JBESB-1450:
--------------------------------------

Correctly, ORA-01000. I agree with you, it seems to me like memory leak definitely. The workaround is great but the default value to open_cursors is 300 - I used 600 and it was not better. In the worst case, it would require as many cursors as the number of processed messages...

> 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