Bug 778197 (SOA-702)

Summary:	Quickstarts with EJB3 generates exceptions during deployment
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Jiri Pechanec <jpechane>
Component:	Documentation, Configuration	Assignee:	Jervis Liu <jliu>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 IR2	CC:	lennart.petersson, mproctor
Target Milestone:	---
Target Release:	4.3 CP01
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-702
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-06 06:43:02 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 2008-08-25 08:24:45 UTC

Date of First Response: 2008-12-16 03:58:22
project_key: SOA

Databse other than HSQLDB is used
When the QS (like business_Service) that contains EJB3 is deployed it generates a WARN with exception
2008-08-25 02:39:13,381 WARN  [org.jboss.ejb.txtimer.DatabasePersistencePolicy] Unable to get timer handles for containerId: jboss.j2ee:service=EJB3,jar=business_service-ejb.jar,name=HelloWorldBean
java.sql.SQLException: ORA-00942: table or view does not exist
.
.
.

The problem is that in ejb-deployer.xml the mbean org.jboss.ejb.txtimer.DatabasePersistencePolicy is enabled. Unfortunately this mbean requires manual coding of SQL statement for each database supported.
There are multiple solutions to this problem
1) State the problem in the docs and provide the reference to EAP docs how to fix it
2) Update schema tool so it either supports different databases or creates hsqldb datasource just for the timers
3) Update schema tool to switch from DatabasePersistencePolicy to NoopPolicy

This exception [probably do not have any impact on QS work so the documentation should be enough.

Comment 1 Jiri Pechanec 2008-08-27 05:24:21 UTC

Link: Added: This issue related SOA-712

Comment 2 Jervis Liu 2008-12-16 08:58:22 UTC

Resolved this issue as SOA-712 has been resolved.

Comment 3 Jiri Pechanec 2009-03-06 06:43:02 UTC

Veirfied in CR3