Bug 1021409 - s-ramp-demos-switchyard-multiapp throws NPE in server log
Summary: s-ramp-demos-switchyard-multiapp throws NPE in server log
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: DT Governance
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER7
: 6.0.0
Assignee: Nobody
QA Contact: Stefan Bunciak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-21 09:09 UTC by Stefan Bunciak
Modified: 2023-05-15 19:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Stefan Bunciak 2013-10-21 09:09:46 UTC
Description of problem:

After successful deployment of s-ramp-demos-switchyard-multiapp to S-RAMP:

* 2 dtgov tasks were created - I'm not sure whether it's all right.
* NPE was thrown, see log: http://pastebin.test.redhat.com/171476

Version-Release number of selected component (if applicable):
* 6.0.0.ER6

How reproducible:


Steps to Reproduce:
1. Install FSW 6.0.0.ER6
2. run mvn -Pdemo clean deploy from quickstarts/overlord/sramp/s-ramp-demos-switchyard-multiapp
3. Check the server log

Actual results:


Expected results:


Additional info:

Comment 1 Kurt T Stam 2013-10-21 13:51:56 UTC
I have not seen this error in development; can it be the workflow.jar disappeared in the middle of processing? It seems to want to start a process or work on a task when the NPE shows.

Comment 2 Kurt T Stam 2013-10-28 13:32:17 UTC
I was able to reproduce it. This is caused when the workflow is invoked for the first time; and the definition has not be loaded. It can be prevented by the server after first deploying the workflow. This is obviously an issue that needs fixing.

Comment 5 Kurt T Stam 2013-11-15 05:13:36 UTC
After the deployment of the workflows no restart should be required anymore, and no errors should occur.

Comment 6 Stefan Bunciak 2014-01-06 14:59:27 UTC
No restart was required for server to load the workflows from s-ramp. Verified in FSW 6.0.0.ER8.


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