8:30 a.m.
continue=async on <start> causes NullPointerException
-----------------------------------------------------
Key: JBPM-2771
URL: https://jira.jboss.org/jira/browse/JBPM-2771
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Any
Reporter: Martin Porter
Adding continue="async" on a <start> of a process will cause a
NullPointerException when you attempt to start the process. We need this to prevent the
caller waiting when the process instance is created but it does not work. Currently we use
a workaround to call a <java> activity which prints a message to the log and does
the async continuation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:42 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2771) continue=async on <start> causes NullPointerException
[
https://jira.jboss.org/jira/browse/JBPM-2771?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2771:
-------------------------------------------
Reading through the section async executions in the documentation I was just wondering how
to start a process without blocking the client. It came to my mind that this should be
possible via the API without the need to specifiy this in the process defnition
explicitly. So additional to fixing this does it make sense to provide a
startProcessInstance() -method enabling users to start process definitions in a
non-blocking way (= not in the client thread)?
continue=async on <start> causes NullPointerException
-----------------------------------------------------
Key: JBPM-2771
URL: https://jira.jboss.org/jira/browse/JBPM-2771
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Any
Reporter: Martin Porter
Adding continue="async" on a <start> of a process will cause a
NullPointerException when you attempt to start the process. We need this to prevent the
caller waiting when the process instance is created but it does not work. Currently we use
a workaround to call a <java> activity which prints a message to the log and does
the async continuation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:06 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2771) continue=async on <start> causes NullPointerException
[
https://jira.jboss.org/jira/browse/JBPM-2771?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2771:
----------------------------------------
Thanks for the testcase...
After a lot (really, a lot, 4 hours) of writing a testcase, puzzeling, debugging, step by
step, I came to the conclusion that this can be solved by adding a
name='whateverValueYouChoose' attribute to the start node.
The reason for this is that jobExecutor does not get an activity when there no name is
specified and hence the NPE, so probably the timer creator needs this.
I think the description should be changed that IF there is a continue = 'async', a
name should be required and the parsing fails if it is not there. In other nodes you
cannot omit a name since transitions have to point to it.
We couldcould also change the name attribute to be REQUIRED (Tom B, if you read this ;-))
continue=async on <start> causes NullPointerException
-----------------------------------------------------
Key: JBPM-2771
URL: https://jira.jboss.org/jira/browse/JBPM-2771
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Any
Reporter: Martin Porter
Adding continue="async" on a <start> of a process will cause a
NullPointerException when you attempt to start the process. We need this to prevent the
caller waiting when the process instance is created but it does not work. Currently we use
a workaround to call a <java> activity which prints a message to the log and does
the async continuation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:06 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2771) continue=async on <start> causes NullPointerException
[
https://jira.jboss.org/jira/browse/JBPM-2771?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2771:
----------------------------------------
I think the description...
should read
I think the parser...
continue=async on <start> causes NullPointerException
-----------------------------------------------------
Key: JBPM-2771
URL: https://jira.jboss.org/jira/browse/JBPM-2771
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Any
Reporter: Martin Porter
Adding continue="async" on a <start> of a process will cause a
NullPointerException when you attempt to start the process. We need this to prevent the
caller waiting when the process instance is created but it does not work. Currently we use
a workaround to call a <java> activity which prints a message to the log and does
the async continuation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:25 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2771) prevent NPE when using continue=async on <start> without a name attribute
[
https://jira.jboss.org/jira/browse/JBPM-2771?page=com.atlassian.jira.plug...
]
Ronald van Kuijk updated JBPM-2771:
-----------------------------------
Summary: prevent NPE when using continue=async on <start> without a name
attribute (was: continue=async on <start> causes NullPointerException)
Issue Type: Feature Request (was: Bug)
Priority: Minor (was: Major)
prevent NPE when using continue=async on <start> without a name
attribute
-------------------------------------------------------------------------
Key: JBPM-2771
URL: https://jira.jboss.org/jira/browse/JBPM-2771
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Any
Reporter: Martin Porter
Priority: Minor
Adding continue="async" on a <start> of a process will cause a
NullPointerException when you attempt to start the process. We need this to prevent the
caller waiting when the process instance is created but it does not work. Currently we use
a workaround to call a <java> activity which prints a message to the log and does
the async continuation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:47 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2771) prevent NPE when using continue=async on <start> without a name attribute
[
https://jira.jboss.org/jira/browse/JBPM-2771?page=com.atlassian.jira.plug...
]
Ronald van Kuijk updated JBPM-2771:
-----------------------------------
Fix Version/s: jBPM 4.4
Added a check for this in the StartBinding.
prevent NPE when using continue=async on <start> without a name
attribute
-------------------------------------------------------------------------
Key: JBPM-2771
URL: https://jira.jboss.org/jira/browse/JBPM-2771
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Any
Reporter: Martin Porter
Assignee: Ronald van Kuijk
Priority: Minor
Fix For: jBPM 4.4
Adding continue="async" on a <start> of a process will cause a
NullPointerException when you attempt to start the process. We need this to prevent the
caller waiting when the process instance is created but it does not work. Currently we use
a workaround to call a <java> activity which prints a message to the log and does
the async continuation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:47 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2771) prevent NPE when using continue=async on <start> without a name attribute
[
https://jira.jboss.org/jira/browse/JBPM-2771?page=com.atlassian.jira.plug...
]
Ronald van Kuijk resolved JBPM-2771.
------------------------------------
Resolution: Done
prevent NPE when using continue=async on <start> without a name
attribute
-------------------------------------------------------------------------
Key: JBPM-2771
URL: https://jira.jboss.org/jira/browse/JBPM-2771
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Any
Reporter: Martin Porter
Assignee: Ronald van Kuijk
Priority: Minor
Fix For: jBPM 4.4
Adding continue="async" on a <start> of a process will cause a
NullPointerException when you attempt to start the process. We need this to prevent the
caller waiting when the process instance is created but it does not work. Currently we use
a workaround to call a <java> activity which prints a message to the log and does
the async continuation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:47 p.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2771) prevent NPE when using continue=async on <start> without a name attribute
[
https://jira.jboss.org/jira/browse/JBPM-2771?page=com.atlassian.jira.plug...
]
Ronald van Kuijk reassigned JBPM-2771:
--------------------------------------
Assignee: Ronald van Kuijk
prevent NPE when using continue=async on <start> without a name
attribute
-------------------------------------------------------------------------
Key: JBPM-2771
URL: https://jira.jboss.org/jira/browse/JBPM-2771
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Any
Reporter: Martin Porter
Assignee: Ronald van Kuijk
Priority: Minor
Fix For: jBPM 4.4
Adding continue="async" on a <start> of a process will cause a
NullPointerException when you attempt to start the process. We need this to prevent the
caller waiting when the process instance is created but it does not work. Currently we use
a workaround to call a <java> activity which prints a message to the log and does
the async continuation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5415
days inactive
5446
days old
7 comments
3 participants
participants (3)
-
Martin Porter (JIRA) -
Ronald van Kuijk (JIRA)
-
Sebastian Schneider (JIRA)