Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1061149 - Deployment of Dashbuilder to WebSphere app server 8.5 fails with "Singleton is not set" exception
Summary: Deployment of Dashbuilder to WebSphere app server 8.5 fails with "Singleton i...
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: BAM
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ER3
: 6.0.2
Assignee: Ryan Zhang
QA Contact: Radovan Synek
Depends On: 1060747
TreeView+ depends on / blocked
Reported: 2014-02-04 12:56 UTC by Radovan Synek
Modified: 2014-08-06 19:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-08-06 19:50:23 UTC
Type: Bug

Attachments (Terms of Use)

Description Radovan Synek 2014-02-04 12:56:13 UTC
The same issue as bug 1060747 occurred during deployment of Dashbuilder to WebSphere AS. I am aware this can be closed as a duplicate in the future, but just for evidence.

Comment 1 David Gutierrez 2014-02-20 18:28:34 UTC
We have downloaded and installed the Websphere App Server version on a Fedora 19 host. 

We've created a new assembly for WAS8 and fixed some cross-compatibility CDI issues on both the dashboard-builder and the jbpm-dashboard repos. These changes are basically the following:

1.- Weld jars must be removed from the distribution WAR since WAS provides its own CDI implementation based on Apache OpenWebBeans.

2.- Methods annotated with @PostConstruct, @PreDestroy must not declare to throw an exception. Otherwise WAS will reject to deploy the app.

3.- Our apps are SLF4J based and WAS used JUL. So the slf4j-log4j.jar dep. has been added to our assemblies in order to integrate with the WAS logging service.

I've successfully deployed & tested the application and I've also created a brief guide to explain the steps to deploy the jbpm-dashboard distribution on WAS:

- For the standalone Dashbuilder installation:

- For the jBPM integrated Dashboard installation:

Github commits (master):

Github commits (6.0.x):

Github commits - (product branding):

Required to ensure branding is applied to the WAS8 distribution.

Comment 2 Radovan Synek 2014-03-06 14:10:21 UTC

WEB-INF/lib still contains weld-* jars.

I doubt this can work without building the was-8 assembly introduced by commits stated in comment 1, and thus additional (brms/bpms) will be needed.

Comment 3 Radovan Synek 2014-03-18 16:44:21 UTC
qe_test_coverage: failure of deployment - no need for additional test

Comment 4 Radovan Synek 2014-04-28 16:29:05 UTC
The weld libraries are still present in dashbuilder WAS8 build (6.0.2.ER2) and no surprise, it cannot be deployed.
Could you please check if those commits stated in comment 1 made it into product?

Comment 5 Edson Tirelli 2014-04-28 20:23:37 UTC
The commits are in the tag:

Looks like a problem with the product build.

Comment 6 Ryan Zhang 2014-04-29 06:52:26 UTC
Sorry, I am afraid this mistake is on me.
I didn't realize that we do jbpm-dashboard special distribution for was8.

I have already fixed this on product assembly code.
Moving to MODIFIED.

Comment 7 Ryan Zhang 2014-05-06 12:11:57 UTC
Before ER3 is available, here is a fixed binary based on ER2:

If applicable, test on the above package for further test on dashbard.war for WAS8

Comment 8 Radovan Synek 2014-05-07 15:31:45 UTC
(In reply to Ryan Zhang from comment #7)
Thanks for the additional build of dashbuilder Ryan, I was able to identify two more BZs (bug 1095363 and bug 1095391). This issue is fixed, but I will wait for a regular build to verify.

Comment 9 Radovan Synek 2014-06-02 06:42:12 UTC
Verified with BPMS-6.0.2.ER3

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