Bug 1018209 - NPE while creating a deployment unit for an uploaded kjar
Summary: NPE while creating a deployment unit for an uploaded kjar
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER5
: 6.0.0
Assignee: Toni Rikkola
QA Contact: Ivo Bek
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-11 13:03 UTC by Ivo Bek
Modified: 2014-08-06 20:17 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2014-08-06 20:17:51 UTC


Attachments (Terms of Use)
Evaluation project in kjar (7.02 KB, application/x-java-archive)
2013-10-11 13:03 UTC, Ivo Bek
no flags Details
server log containing the NPE (15.16 KB, text/x-log)
2013-10-11 13:04 UTC, Ivo Bek
no flags Details

Description Ivo Bek 2013-10-11 13:03:26 UTC
Created attachment 811092 [details]
Evaluation project in kjar

Description of problem:

The NPE is thrown when I create deployment unit for an uploaded kjar in business central,

The business central only says "Deployment of unit org.jbpm:Evaluation:1.0 failed: null" but the server log is much more interesting; I will attach it.

How reproducible:

configuration: install bpms-6.0.ER3 with eap 6.1.0.

Steps to Reproduce:
1. upload the attached kjar
2. notice following output in server log:

14:42:29,854 INFO  [stdout] (http-localhost/127.0.0.1:8080-2) GROUP_ID:
14:42:29,854 INFO  [stdout] (http-localhost/127.0.0.1:8080-2) ARTIFACT_ID:
14:42:29,854 INFO  [stdout] (http-localhost/127.0.0.1:8080-2) VERSION_ID:

3. create the deployment unit because it's probably not created during the upload of kjar:

groupId = org.jbpm
artifactId = Evaluation
version = 1.0

4. see exceptions in server log

Comment 1 Ivo Bek 2013-10-11 13:04:31 UTC
Created attachment 811093 [details]
server log containing the NPE

Comment 2 Ivo Bek 2013-12-05 13:42:28 UTC
Verified in BPMS 6.0.0.ER5


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