-
1. Re: About jbpm5 and mysql!when I open "http://localhost:8080/drools-guvnor/", "HTTP Status 404 - /drools-guvnor/" occurred,what should I do?
tsurdilovic Aug 28, 2012 5:36 PM (in response to 92loveinlife)Don't know. Anything in your server log? Did the guvnor war successfuly deploy ?
-
2. Re: About jbpm5 and mysql!when I open "http://localhost:8080/drools-guvnor/", "HTTP Status 404 - /drools-guvnor/" occurred,what should I do?
92loveinlife Aug 28, 2012 10:54 PM (in response to tsurdilovic)Thank you, I found the guvnor war failed to deploy! the problem is my modification in Configuration file??
or I need to reinstall??what about your opinion?
-
3. Re: About jbpm5 and mysql!when I open "http://localhost:8080/drools-guvnor/", "HTTP Status 404 - /drools-guvnor/" occurred,what should I do?
tsurdilovic Aug 29, 2012 7:50 AM (in response to 92loveinlife)Cannot guess without some details on the issue.
-
4. Re: About jbpm5 and mysql!when I open "http://localhost:8080/drools-guvnor/", "HTTP Status 404 - /drools-guvnor/" occurred,what should I do?
92loveinlife Aug 30, 2012 4:51 AM (in response to tsurdilovic)This is my server.log in \jboss-as-7.0.2.Final\standalone\log, can you acquire some info from it??
When I install jbpm5 to work on mysql database, I modify hibernate.cfg.xml, persistence.xml, testDS1-ds.xml, and persistence.xml in jbpm-installer\task-service\resources\META-INF
also standalone.xml in jbpm-installer, move mysql-connector-java-5.1.18-bin.jar into jbpm-installer\db\driver.
jbpm version:5.2
mysql version:5.1.51
-
server.log.zip 24.2 KB
-
-
5. Re: About jbpm5 and mysql!when I open "http://localhost:8080/drools-guvnor/", "HTTP Status 404 - /drools-guvnor/" occurred,what should I do?
kiran_mvv Sep 14, 2012 10:47 AM (in response to 92loveinlife)Eric,
Which jbpm version you are using? is it jbpm5.2 or 5.3?
We have set up jbpm 5.3 and faced similar problem with this issue. It could be because of two reasons. 1) the port number 8080 is used by some other process. (may be some other process. you might want to change the port number to fix this). 2) the drools-guvnor war file is not deployed. for this to be redeployed you might want to create a drools-guvnor.dodeploy file in \jboss-as-7.0.2.Final\standalone\deploy location. when we have such file, when the server starts it will be redeployed again.