Bug 778197 (SOA-702) - Quickstarts with EJB3 generates exceptions during deployment
Summary: Quickstarts with EJB3 generates exceptions during deployment
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-702
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation, Configuration
Version: 4.3 IR2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP01
Assignee: Jervis Liu
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-25 08:24 UTC by Jiri Pechanec
Modified: 2013-11-07 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-06 06:43:02 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778207 0 high CLOSED Document warnings generated during EJB3 deployment 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-702 0 None None None Never

Internal Links: 778207

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
Note You need to log in before you can comment on or make changes to this bug.