11:02 a.m.
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
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
11:12 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ 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
5:22 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=comments#action_12394051 ]
Mark Little commented on JBESB-1450:
------------------------------------
I assume that you're getting the ORA-01000 message. The limit on open cursors is per
session and is controlled by the open_cursors parameter. So that's a workaround, but
really not closing cursors is a memory leak. Cursors in OCI are associated to Statement
Handles and when you free the handle the cursor will be closed.
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
3:26 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ 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
7:15 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=all ]
Kevin Conner updated JBESB-1450:
--------------------------------
Fix Version/s: 4.2.1 CP1
Assignee: Kevin Conner
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
6:36 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=comments#action_12394525 ]
Kevin Conner commented on JBESB-1450:
-------------------------------------
Martin, can you provide the changes necessary to run this using Oracle?
The log shows that the errors are being generated within the JMS code and I would have
expected that datasource to have been pooled by the JCA layer.
Thanks
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
8:25 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=comments#action_12394539 ]
Martin Vecera commented on JBESB-1450:
--------------------------------------
Use this tool https://svn.corp.jboss.com/repos/soa/trunk/qa/dbinstall/
Sample build.properties:
org.jboss.esb.server.home=/opt/jboss-soa-p.4.2.0.beta1
org.jboss.esb.server.config=all
org.jboss.esb.server.database=oracle
source.dir=oracle10g
db.name=soaesb1
db.hostname=jawa01
db.port=1521
db.username=soaesb1
db.password=soaesb1
db.minpoolsize=15
db.maxpoolsize=50
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
10:05 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=comments#action_12396602 ]
Martin Vecera commented on JBESB-1450:
--------------------------------------
Very similar errors occur with SOAPClient.
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
10:17 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=all ]
Work on JBESB-1450 started by Kevin Conner.
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
10:17 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=comments#action_12396606 ]
Kevin Conner commented on JBESB-1450:
-------------------------------------
This issue will have nothing to do with SOAPProcessor nor SOAPClient.
The logs show a stacktrace generated from within JMS and this may (or may not) be
relevant. I am currently investigating this issue.
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
2:18 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=comments#action_12397538 ]
Kevin Conner commented on JBESB-1450:
-------------------------------------
This leak appears to be coming from JBoss Messaging, specifically
JDBCPersistenceManager$1HandleBeforeCommit1PCRunner.doTransaction(JDBCPersistenceManager.java:1587)
This line creates a prepared statement within a loop but only the last statement created
will be released. Other examples of this construct, within this file, use a simple guard
to prevent subsequent allocations. This appears to be the only occurrence which does
not.
I am going to create a local fix for this and double check, just in case there are any
other issues.
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
5:09 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=comments#action_12397559 ]
Kevin Conner commented on JBESB-1450:
-------------------------------------
The following change fixes the leak.
Index: src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java
===================================================================
--- src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java (revision 3648)
+++ src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java (working copy)
@@ -1584,8 +1584,11 @@
ChannelRefPair pair = (ChannelRefPair) i.next();
MessageReference ref = pair.ref;
- psReference = conn
+ if (psReference == null)
+ {
+ psReference = conn
.prepareStatement(getSQLStatement("INSERT_MESSAGE_REF"));
+ }
// Now store the reference
addReference(pair.channelID, ref, psReference, false);
Will create a JBM task and link it into SOA.
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
5:14 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=comments#action_12397560 ]
Kevin Conner commented on JBESB-1450:
-------------------------------------
Created JBMESSAGING-1227
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
5:16 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=all ]
Kevin Conner closed JBESB-1450.
-------------------------------
Resolution: Rejected
This is a JBM issue and not a JBESB one.
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
2:04 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1450) SOAPProcessor cannot handle large message backlog
[ http://jira.jboss.com/jira/browse/JBESB-1450?page=comments#action_12397613 ]
Tim Fox commented on JBESB-1450:
--------------------------------
The JBM issue is a duplicate of JBMESSAGING-1218 which was fixed a while back in
Branch_Stable and is in JBossMessaging 1.4.1 and will be in EAP 4.3 CP01
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
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP1
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
5999
days inactive
6023
days old
14 comments
4 participants
participants (4)
-
Kevin Conner (JIRA) -
Mark Little (JIRA)
-
Martin Vecera (JIRA)
-
Tim Fox (JIRA)