Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 929206

Summary:	ERROR message when deploying rtgov war
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Ryan Zhang <rzhang>
Component:	Configuration	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED DUPLICATE	QA Contact:	Jiri Sedlacek <jsedlace>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	atangrin, cyu, kconner, ncross, oskutka, soa-p-jira
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-24 14:20:45 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:
Embargoed:

Description Ryan Zhang 2013-03-29 13:46:40 UTC

Description of problem:
This issue has talked to Gadget-server developer Jeff Yu. 
This should not impact the gadget-server function.

But it should be ideal to not show the ERROR to the customer.

21:40:06,015 INFO  [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (pool-10-thread-1) HHH000397: Using ASTQueryTranslatorFactory
21:40:06,129 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
21:40:06,174 INFO  [org.hibernate.tool.hbm2ddl.SchemaExport] (pool-10-thread-1) HHH000227: Running hbm2ddl schema export
21:40:06,181 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (pool-10-thread-1) HHH000389: Unsuccessful: alter table RTGOV_ACTIVITIES drop constraint FK693AE720E3DE5559
21:40:06,182 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (pool-10-thread-1) Table "RTGOV_ACTIVITIES" not found; SQL statement:
alter table RTGOV_ACTIVITIES drop constraint FK693AE720E3DE5559 [42102-168]
21:40:06,182 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (pool-10-thread-1) HHH000389: Unsuccessful: alter table RTGOV_ACTIVITY_CONTEXT drop constraint FK7FFC19525A6A791D
21:40:06,182 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (pool-10-thread-1) Table "RTGOV_ACTIVITY_CONTEXT" not found; SQL statement:
alter table RTGOV_ACTIVITY_CONTEXT drop constraint FK7FFC19525A6A791D [42102-168]
21:40:06,182 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (pool-10-thread-1) HHH000389: Unsuccessful: alter table RTGOV_ACTIVITY_PROPERTIES drop constraint FK728366909BA1A17D
21:40:06,183 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (pool-10-thread-1) Table "RTGOV_ACTIVITY_PROPERTIES" not found; SQL statement:
alter table RTGOV_ACTIVITY_PROPERTIES drop constraint FK728366909BA1A17D [42102-168]
21:40:06,185 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'


Version-Release number of selected component (if applicable):


How reproducible:
Deply rtgov M4 into EAP 6.1. Start with standalone-full.xml configuration.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jeff Yu 2013-04-02 13:35:16 UTC

Hi Ryan,

This is caused by the Hibernate schema population code. Because it will firstly remove all the tables before populating the schema. In which case, it will throw above ERROR since there was no existing table.

Regards
Jeff

Comment 2 Ryan Zhang 2013-04-03 02:50:08 UTC

Thanks for clarification, Jeff.

When I restart the platform(is it suppose created already for the second time startup?), it still reports the same error.

And if it doesn't impact the function, could we make it not show the ERROR log to customer?

(In reply to comment #1)
> Hi Ryan,
> 
> This is caused by the Hibernate schema population code. Because it will
> firstly remove all the tables before populating the schema. In which case,
> it will throw above ERROR since there was no existing table.
> 
> Regards
> Jeff

Comment 3 Nick Cross 2013-04-24 14:20:45 UTC


*** This bug has been marked as a duplicate of bug 947692 ***

Comment 4 Jeff Yu 2013-05-09 07:58:46 UTC

This is because we use the in-memory database, so the database gets destroyed every time at the time of server shutdown.

Regards
Jeff

(In reply to comment #2)
> When I restart the platform(is it suppose created already for the second
> time startup?), it still reports the same error.

Comment 5 kconner 2013-05-14 12:22:31 UTC

In SOA 5 we did not allow hibernate to create the tables, irrespective of whether the database was in memory or not, and we should look to provide the same solution within SOA 6.  This also tied in to the SOA 5 schema tool so that the customer could choose which database was to be configured.