| Summary: | SOAPProcessor cannot handle large message backlog | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Martin Vecera <mvecera> |
| Component: | JBossESB | Assignee: | Tim Fox <tim.fox> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 Beta 1 | CC: | jwulf |
| Target Milestone: | --- | ||
| Target Release: | 4.2 CP02 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-288 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-12 10:20:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 777849, 778034 | ||
|
Description
Martin Vecera
2008-01-07 17:02:23 UTC
Link: Added: This issue depends JBESB-1450 Link: Added: This issue related SOA-84 Link: Added: This issue depends JBMESSAGING-1227 JBMESSAGING-1227 is now the active task Assigning to Tim to handle the JBM issue. Link: Added: This issue is a dependency of SOA-377 Link: Added: This issue depends JBMESSAGING-1218 Yes, that is correct. If we cannot fix the problem then we will document it in the Release Notes (task already created for Josh). Link: Added: This issue duplicates SOA-351 There are two options for progressing this further - Have the oracle datasource enable statement caching. This should reduce the impact of this issue and may allow the server to function in lower volume situations - Wait for the fix or a workaround and then validate. Martin. I have just tried running this test using a separate DS configuration for JMS. This separate configuration has two specific additions to the one generated by the current tool - specifies prepared-statement-cache-size - specified share-prepared-statements The important configuration is the second as this forces the connection to return the *same* prepared statement, whether it has been closed or not. Can you try rerunning your tests for this issue (and SOA-351) using the above changes? Tim. Can you tell me if it is safe to enable share-prepared-statements for JBM? Will this cause any issues? I can't see any problems doing that. Thanks Tim, I believe this is a supportable workaround for these issues. Martin, I believe this will solve the issue for both failure cases but we still need you to verify them. Link: Added: This issue is related to SOA-348 Link: Added: This issue is related to JBESB-1479 Link: Removed: This issue is related to SOA-348 Moving to CP1 as there is a workaround. Link: Removed: This issue is related to JBESB-1479 Downgrading because of workaround. Link: Added: This issue is a dependency of SOA-559 Waiting for CP02 to check whether it is fixed successfully. Verified. |