Created attachment 807019 [details]
server log from 'server started' msg to SIGSEGV (appended as well)

Description of problem:
When you click Build & Deploy, the selected project starts building. You can than hit the button again. If you do so, you may get:

WARN  [com.arjuna.ats.jta] ... ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.drools.persistence.jta.JtaTransactionSynchronizationAdapter@2811375c with exception: java.lang.IllegalStateException: Illegal method call. This session was previously disposed.

in the server log, the builds still succeed. You may also get:

ERROR [org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl] ... Deployment of unit <groupID>:<artifact>:<version> failed: RuntimeManager with id org.jboss.qa.brms:console:1.0 is already registered: org.jbpm.console.ng.bd.exception.DeploymentException: RuntimeManager with id <groupID>:<artifact>:<version> is already registered

in the server log, one of the builds may fail then. If you're lucky (and probably only if you do this a few times), you can get even this:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000003a37b44c4f, pid=648, tid=140365116819200
...

which aborts your server. Getting to this point sometimes takes longer, sometimes less.


While the last is a Bad Thing, so far it seems you actually have to do this on purpose, many times. I could understand doing this once or twice - by mistake or when the building process takes too long and the user gets impatient.


Version-Release number of selected component (if applicable):
BPMS 6.0 ER3


Steps to Reproduce:
Repeatedly click Build & Deploy on the same project, without waiting for success/failure notification.