[JBoss JIRA] Created: (JBPM-1970) Unsupported deployment URL Exception when deploying JBPM unrelated ears
by Mathias Arens (JIRA)
Unsupported deployment URL Exception when deploying JBPM unrelated ears
-----------------------------------------------------------------------
Key: JBPM-1970
URL: https://jira.jboss.org/jira/browse/JBPM-1970
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Integration
Affects Versions: jBPM 3.3.1 GA
Environment: jboss 4.2.3.GA, jdk6, win xp
Reporter: Mathias Arens
I installed jbpm 3.3.1.GA on my JBoss 4.2.3. When I deploy a ear which is not related to JBPM I get the following 'Unsupported deployment URL' exception:
[code]
10:24:25,352 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
10:24:25,493 INFO [EARDeployer] Init J2EE application: file:/C:/applications/jboss-4.2.3.GA/server/default/deploy/access-ear-0.2.5.ear
10:24:26,430 INFO [ProcessDeploymentHelper] Deploy ProcessDefinition: file:/C:/applications/jboss-4.2.3.GA/server/default/tmp/deploy/tmp7730504250088006025access-ear-0.2.5.ear-contents/access-ejb-0.2.5.jar
10:24:26,430 ERROR [MainDeployer] Could not create deployment: file:/C:/applications/jboss-4.2.3.GA/server/default/tmp/deploy/tmp7730504250088006025access-ear-0.2.5.ear-contents/access-ejb-0.2.5.jar
java.lang.IllegalArgumentException: Unsupported deployment URL: file:/C:/applications/jboss-4.2.3.GA/server/default/tmp/deploy/tmp7730504250088006025access-ear-0.2.5.ear-contents/access-ejb-0.2.5.jar
at org.jbpm.integration.spec.service.DeploymentServiceImpl.createDeployment(DeploymentServiceImpl.java:72)
at org.jbpm.integration.jboss42.ProcessDeploymentHelper.create(ProcessDeploymentHelper.java:58)
at org.jbpm.integration.jboss42.PARDeployerInterceptorEJB3.create(PARDeployerInterceptorEJB3.java:49)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy35.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy10.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
10:24:26,555 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@5a249913 { url=file:/C:/applications/jboss-4.2.3.GA/server/default/deploy/access-ear-0.2.5.ear }
deployer: org.jboss.deployment.EARDeployer@1af0af7
status: Deployment FAILED reason: Could not create deployment: file:/C:/applications/jboss-4.2.3.GA/server/default/tmp/deploy/tmp7730504250088006025access-ear-0.2.5.ear-contents/access-ejb-0.2.5.jar; - nested throwable: (java.lang.IllegalArgumentException: Unsupported deployment URL: file:/C:/applications/j
.ear-contents/access-ejb-0.2.5.jar)
state: FAILED
watch: file:/C:/applications/jboss-4.2.3.GA/server/default/deploy/access-ear-0.2.5.ear
altDD: null
lastDeployed: 1231925065899
lastModified: 1231925065493
mbeans:
10:24:26,821 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
10:24:26,852 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
10:24:26,868 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 58s:701ms
[/code]
--
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
15 years, 11 months
[JBoss JIRA] Created: (JBPM-1867) The sql install script for mysql is not correct.
by John Wooten, Ph.D. (JIRA)
The sql install script for mysql is not correct.
------------------------------------------------
Key: JBPM-1867
URL: https://jira.jboss.org/jira/browse/JBPM-1867
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Installer
Affects Versions: jBPM 3.3.0 GA
Environment: MAC OS X 10.5.5, JBoss 4.2.2 GA, JBPM 3.3.0GA
Reporter: John Wooten, Ph.D.
When asked to select a persistence mechanism for the jbpm installation, and one chooses mysql, it isn't clear what needs to be changed. After discovering that, ( though searching the forums ), you learn to create a database in mysql, then select that database and run the installer script located in the installation. However, it fails as there are no ';' (semi-colons) at the end of each statement. For my version of mysql, making those changes at least does not through an exception while trying to log in. It still does not allow login, but I think I've found that there are no default users(admin,user,manager, cookie-monster, etc.) in the install script.
--
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
15 years, 11 months
[JBoss JIRA] Created: (JBPM-1169) NPE in org.jbpm.graph.node.Decision.execute() when using transitions with null conditions migrated from JBPM 3.0
by Julien Kronegg (JIRA)
NPE in org.jbpm.graph.node.Decision.execute() when using transitions with null conditions migrated from JBPM 3.0
----------------------------------------------------------------------------------------------------------------
Key: JBPM-1169
URL: http://jira.jboss.com/jira/browse/JBPM-1169
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: win2000, JBPM 3.2.2, Jboss 4.2.2, Eclipse Europa 3.3
Reporter: Julien Kronegg
Assigned To: Tom Baeyens
A NullPointerException is raised by org.jbpm.graph.node.Decision.execute(ExecutionContext) if the table JBPM_DECISIONCONDITIONS row has null EXPRESSION_ field.
The following conditions must meet:
1) initially, the user has a JBPM database in version 3.0 and a decision with conditional transitions
2) one of the conditional condition is cleared, which leads to setting the field EXPRESSION_ to null in the database
3) the JBPM database migrated from 3.0 schema to version 3.2
Note: the JBPM 3.2 database is (almost?) the same as the version 3.1, so the bug should also occur in version 3.1 (not tested).
The exception is:
Exception in thread "main" org.jbpm.graph.def.DelegationException
at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:387)
at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:378)
at org.jbpm.graph.node.Decision.execute(Decision.java:148)
at org.jbpm.graph.def.Node.enter(Node.java:319)
at org.jbpm.graph.def.Transition.take(Transition.java:151)
at org.jbpm.graph.def.Node.leave(Node.java:394)
at org.jbpm.graph.node.StartState.leave(StartState.java:70)
at org.jbpm.graph.exe.Token.signal(Token.java:195)
at org.jbpm.graph.exe.Token.signal(Token.java:140)
at org.jbpm.graph.exe.ProcessInstance.signal(ProcessInstance.java:271)
at com.sample.TestDecisionNPE.main(TestDecisionNPE.java:53)
Caused by: java.lang.NullPointerException
at org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator.translateExpressionToDollars(JbpmExpressionEvaluator.java:52)
at org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator.evaluate(JbpmExpressionEvaluator.java:38)
at org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator.evaluate(JbpmExpressionEvaluator.java:30)
at org.jbpm.graph.node.Decision.execute(Decision.java:110)
... 8 more
This bug can be tested using the following test case:
package com.sample;
import java.lang.reflect.Field;
import java.util.ArrayList;
import java.util.List;
import org.jbpm.graph.def.ProcessDefinition;
import org.jbpm.graph.def.Transition;
import org.jbpm.graph.exe.ProcessInstance;
import org.jbpm.graph.node.Decision;
import org.jbpm.graph.node.DecisionCondition;
public class TestDecisionNPE {
public static final void main(String[] args) throws SecurityException, NoSuchFieldException, IllegalArgumentException, IllegalAccessException{
ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(
"<process-definition>" +
" <start-state>" +
" <transition to='d' />" +
" </start-state>" +
" <decision name='d'>" +
" <transition name='one' to='a'>" +
" <condition>#{a == 1}</condition>" +
" </transition>" +
" <transition name='two' to='b'>" +
" <condition>#{a == 2}</condition>" +
" </transition>" +
" <transition name='three' to='c'>" +
" <condition>#{a == 3}</condition>" +
" </transition>" +
" </decision>" +
" <state name='a' />" +
" <state name='b' />" +
" <state name='c' />" +
"</process-definition>");
// start-state.
ProcessInstance processInstance = new ProcessInstance(processDefinition);
// Update a transition decision condition as if it was on the old format
// by setting the condition to null (i.e. no condition).
// Build a decisionConditions list (emulates an old database from
// JBPM 3.0, obsolete JBPM_DECISIONCONDITION table).
List decision_conditions = new ArrayList();
decision_conditions.add(new DecisionCondition("one", null));
Decision decision = (Decision) processDefinition.getNode("d");
Field field = decision.getClass().getDeclaredField("decisionConditions");
field.setAccessible(true);
field.set(decision, decision_conditions);
// fire the transition (as we have an old decision condition set, org.jbpm.graph.node.Decision#execute will raise a NullPointerException).
processInstance.signal();
}
}
The bug can be corrected using the following code in the execute() method (added lines ends with "JK") :
// backwards compatible mode based on separate DecisionCondition's
Iterator iter = decisionConditions.iterator();
while (iter.hasNext() && (transition==null)) {
DecisionCondition decisionCondition = (DecisionCondition) iter.next();
if (decisionCondition.expression!=null) {//JK
Object result = JbpmExpressionEvaluator.evaluate(decisionCondition.getExpression(), executionContext);
if (Boolean.TRUE.equals(result)) {
if (transition!=null) {
transition.removeConditionEnforcement();
}
String transitionName = decisionCondition.getTransitionName();
transition = getLeavingTransition(transitionName);
}
} else {//JK
String transitionName = decisionCondition.getTransitionName();//JK
transition = getLeavingTransition(transitionName);//JK
}//JK
Note that the JBPM 3.0.4 version had this check against null values.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months
[JBoss JIRA] Created: (JBPM-1813) Fix create schema generation
by Thomas Diesler (JIRA)
Fix create schema generation
-----------------------------
Key: JBPM-1813
URL: https://jira.jboss.org/jira/browse/JBPM-1813
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Reporter: Thomas Diesler
Fix For: jBPM 3.3.1 GA
<!--jbpmschema output="${scriptsdir}/jbpm.jpdl.informix.sql" jbpmCfg="jbpm/informix.jbpm.cfg.xml" actions="create" text="true"/-->
<!--jbpmschema output="${scriptsdir}/jbpm.jpdl.pointbase.sql" jbpmCfg="jbpm/pointbase.jbpm.cfg.xml" actions="create" text="true"/-->
<!--jbpmschema output="${scriptsdir}/jbpm.jpdl.progress.sql" jbpmCfg="jbpm/progress.jbpm.cfg.xml" actions="create" text="true"/-->
--
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
15 years, 11 months