| Summary: | jBPM cannot be certified on SOA-P for HP | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | JBPM - within SOA, JBPM - standalone | Assignee: | Default User <jbpapp-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.3 QE | ||
| Target Milestone: | --- | ||
| Target Release: | One Off Releases | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1513 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
HP.UX
risc, ia64
HP Java 5, 6
PostgreSQL, oracle 9i, Oracle 10g
4.3 CP02 CR4
|
|
| Last Closed: | 2009-10-01 11:54: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: | |
|
Description
Jiri Pechanec
2009-09-23 14:00:08 UTC
Link: Added: This issue depends JBPM-2549 I had a suspicion that the issue could be realated to default Hibernate connection pool. I thus reconfigured tests to use c3p0 pool and the problem has disappeard when tested with PostgreSQL. I suggest to follow these next steps 1) Sanitize solution and re-run the test 2) Re-run the tests with Oracle 3) Modify Hudson jobs to use this pool 4) Len or PM will confirm that c3p0 pool is supported solution. If not it will try to find which of the pools is supported The Hibernate documentation says that the default pool is not for produciton use (like e.g. hsqldb) http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-configuration.html#configuration-hibernatejdbc - Hibernate's own connection pooling algorithm is, however, quite rudimentary. It is intended to help you get started and is not intended for use in a production system, or even for performance testing. You should use a third party pool for best performance and stability. We MUST support at least one of the pools otherwise we are forcing customers to use non-production code in production environment. Final conclusion The behaviour of jBPM test suite on HP-UX is as follows MySQL - works Oracle - works if c3p0 connection pooling is enabled and prepared statement caching is ENABLED PostgreSQL - works if c3p0 connection pooling is enabled and prepared statement caching is DISABLED Final recommendation I recommend as a standard to certify jBPM on HP-UX using c3p0 connection pool (if supported) with disabled prepared statement caching. This solution will be used fro ALL databases and will be documented as limitation in Release Notes. I tried to run the test suite INSIDE the container but it is too restrictive environment that causes a lot of errors due to limited access rights etc. This option is not viable as a way how to certify HP-UX. When the testsuite is configured to use non-local datasources from SOA-P then it does not display on HP any behavior different to other systems. |