JBoss Community

jbpm ran fine for 1 day, now is broken.. :)

created by Carlos Crosetti in jBPM - View the full discussion

Once I got the jBPM 5.3 up and running, by the means of calling standalone.bat after "ant start.demo.noeclipse", I reviewed the deployments folder and cleared the dot failed files, cleaned the logq and started back again but now typing "ant start.demo". (see this time I wanted to start Eclipse).

 

Now, the interesting finding was that after Eclipse was launched, I see the ant output more clean now with

 

 

start.h2:

 

start.jboss:

 

check.jboss.version:

 

start.jboss5:

 

check.jboss.version:

 

start.jboss7:

 

start.eclipse:

 

start.demo:

 

BUILD SUCCESSFUL

Total time: 38 seconds

 

and now when I browse the activvity in the "deployments" folder I can see several .ISDEPLOYING files so started to feel more

confident to the start  script with Eclipse as it is scheduling all the war deplyments. Cool...

 

After some like 5 minutes, I checked all deployments failed and the server.log shows lots of entries like the ones below

 

 

18:26:52,140 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jaxb-impl.jar in "/C:/jbpm-installer/content/drools-guvnor.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar"  does not point to a valid jar for a Class-Path reference.

18:26:52,140 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jsr173_1.0_api.jar in "/C:/jbpm-installer/content/drools-guvnor.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar"  does not point to a valid jar for a Class-Path reference.

18:26:52,140 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry activation.jar in "/C:/jbpm-installer/content/drools-guvnor.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar"  does not point to a valid jar for a Class-Path reference.

 

the only thing I changed was the way I exceuted ant from "noeclipse" and without Eclipse.

 

What is missing now?

 

If you are interested, you can find a screenshot of my first attempt where all apps were enabled at the console level.

Reply to this message by going to Community

Start a new discussion in jBPM at Community