Bug 1274312 - WAS: Hibernate in dashbuilder fails to initialize because of 2 conflicting jars in WEB-INF/lib
Summary: WAS: Hibernate in dashbuilder fails to initialize because of 2 conflicting ja...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Build and Assembly
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ER5
: 6.2.0
Assignee: Ryan Zhang
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-22 13:17 UTC by Jan Hrcek
Modified: 2020-03-27 20:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:11:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
SystemOut.log showing exceptions. (366.55 KB, text/plain)
2015-10-22 13:17 UTC, Jan Hrcek
no flags Details

Description Jan Hrcek 2015-10-22 13:17:49 UTC
Created attachment 1085504 [details]
SystemOut.log showing exceptions.

Description of problem:
When running dashbuilder on WebSphere, there is a blank page after user logs in and there are tons of occurrences of this NPE in SystemOut.log:
java.lang.NullPointerException
	at org.jboss.dashboard.database.hibernate.HibernateTransaction.begin(HibernateTransaction.java:140)

(see details in SystemOut.log attached)

Digging deeper reveals, that Hibernate fails to initialize, because there are two conflicting implementations of org.jboss.logging.Logger in WAS deployable dashbuilder.war/WEB-INF/lib

This class is present both in 
dashbuilder.war/WEB-INF/lib/jboss-logging-spi-2.2.0.CR1.jar
and 
dashbuilder.war/WEB-INF/lib/jboss-logging-3.1.4.GA-redhat-2.jar

Discussing with engineering reveals, that community WAS assembly does NOT contain the following jar: jboss-logging-spi-2.2.0.CR1.jar

After deleting jboss-logging-spi...jar from the dashbuilder.war/WEB-INF/lib the hibernate initializes fine.

Version-Release number of selected component (if applicable):
BPM Suite 6.2.0 ER4

How reproducible:
Always

Steps to Reproduce:
1. Deploy BPM Suite with some production database (e.g. Oracle12c or any other supported on)
2. Enter credentials in dashbuilder login page and login


Actual results:
Blank page is displayed - NPE appears in SystemOut.log showing that Hibernate was not initialized.


Expected results:
Login is possible in web sphere distribution.

Additional info:

Comment 1 Petr Široký 2015-10-22 13:25:35 UTC
My apologies. The duplicated jars are in the upstream as well. I was originally looking at https://github.com/droolsjbpm/dashboard-builder/tree/master/builder which is OK but is not what actually ends up in the product.

The assembly that is used in product is located here: https://github.com/droolsjbpm/jbpm-dashboard/tree/master/jbpm-dashboard-distributions and after building with "-Dfull -Dproductized" I can see the duplicated jars there. I will fix this asap.

Comment 2 Petr Široký 2015-10-22 14:01:29 UTC
PR sent: https://github.com/droolsjbpm/jbpm-dashboard/pull/8

Comment 3 Ryan Zhang 2015-10-23 10:57:38 UTC
(In reply to Petr Siroky from comment #2)
> PR sent: https://github.com/droolsjbpm/jbpm-dashboard/pull/8

It seems this  have been merged and should we set this to MODIFIED now?

Comment 5 Jan Hrcek 2015-11-03 15:12:20 UTC
Dashbuilder is working fine with websphere again! Verified with BPM Suite 6.2.0 ER5.


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