Bug 1113109 - Starting bean org.jboss.dashboard.database.hibernate.HibernateInitializer throws an error during (cluster) boot up process when JDV is not coneected to Internet
Summary: Starting bean org.jboss.dashboard.database.hibernate.HibernateInitializer thr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Dashboard Builder
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: One-off release
Assignee: jolee
QA Contact:
URL:
Whiteboard:
Depends On: 1113114 1259982
Blocks: 1118345
TreeView+ depends on / blocked
 
Reported: 2014-06-25 12:52 UTC by Rick Wagner
Modified: 2018-12-04 17:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: TEIIDDSHB-5
: 1113114 (view as bug list)
Environment:
Last Closed: 2015-02-06 16:30:53 UTC
Type: Support Patch
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDDSHB-5 0 Major Closed Starting bean org.jboss.dashboard.database.hibernate.HibernateInitializer throws an error during boot up process when JD... 2015-09-08 14:20:07 UTC

Comment 1 Rick Wagner 2014-06-25 12:53:43 UTC
This BZ opened to track Cluster fix.  (Parent BZ fixed Standalone).

Thanks,

Rick

Comment 4 jolee 2014-09-18 13:59:15 UTC
This DV fix is dependent upon https://bugzilla.redhat.com/show_bug.cgi?id=1113114

Comment 12 Filip Elias 2014-11-27 16:41:50 UTC
Hi John,

I read the customer portal tickets and I think that users are confused by the exception itself rather than some functionality reduction. Users will still see quite similar exception when applying this patch.

But If you think that it is not a problem, feel free to set the Roll up patch DV_6.0_4_2014 to ON_QA and we will resume testing.

By the way, the original error/exception has been fixed already in Roll up patch DV_6.0_2_2014 so this patch doesn't have any effect on this bug.

Comment 13 jolee 2014-11-27 19:07:19 UTC
Filip,
  Thanks!  I will set the roll up back to QA and I will write a proactive KCS solution detailing the exception and the explanation to help limit the confusion found for those searching for information on it.

JLee

Comment 15 JBoss JIRA Server 2015-04-01 21:53:40 UTC
Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-5 to Closed

Comment 16 JBoss JIRA Server 2015-09-04 12:40:40 UTC
Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-5 to Reopened

Comment 17 JBoss JIRA Server 2015-09-04 20:48:13 UTC
Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-5 to Closed


Note You need to log in before you can comment on or make changes to this bug.