[JBoss jBPM] - Purge existing process instances
by kbutler
Hi -
I am currently integrating a project that includes jBPM, and do not have time to gain solid familiarity with its inner-workings. Also I trust the community more than the vendor. So I ask you here...
I am cleaning up what was a test database, to ready it for production. One thing I want to clean up is all the pending jBPM process/task instances, while retaining all the process/task definitions. Here is a list of the tables I think should be purged:
| delete from JBPM_MODULEINSTANCE
| delete from JBPM_PROCESSINSTANCE
| delete from JBPM_TASKINSTANCE
| delete from JBPM_VARIABLEINSTANCE
| delete from JBPM_TOKEN
| delete from JBPM_TOKENVARIABLEMAP
| delete from JBPM_TIMER
| delete from JBPM_LOG
|
And here is a list of the tables that were empty, so I am ignoring:
| /*
| -- Tables which are currently unused (empty)
| JBPM_COMMENT
| JBPM_DESCISIONCONDITIONS
| JBPM_EXCEPTIONHANDLER
| JBPM_POOLEDACTOR
| JBPM_RUNTIMEACTION
| JBPM_SWIMLANE
| JBPM_SWIMLANEINSTANCE
| JBPM_TASKACTORPOOL
| */
|
Can someone please tell me if this looks correct?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959909#3959909
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959909
19 years, 9 months
[Tomcat, HTTPD, Servlets & JSP] - JBoss 3.2.5: Logging out does not release session resources
by lduperval
Hi,
We have an application that is distributed across 4 EARs, which we will call A, B, C, and D.
I have configure tomcat as follows:
to enable single signon.
The session logout is implemented in ear B. That is, all of the web pages in all of my applications contain a "Logout" button. When you click it, it calls a logout action which invalidates the session. That action is defined in ear B.
We are doing performance testing where we are simulating the following:
- log on (calls a Login action defined in B)
- execute an operation that resides in A
- log out (which calls a logout action definded in B)
- repeat over and over again
What we are seeing is that sessions are created but the resources are not freed when logging out. I have the impression that it is due to the fact that I am using multiple ears, but I am not quite sure yet.
Eventually, there are so many threads running that the JVM runs out of ressources.
Has anyone had experience with an approach like this one? What have you done to resolve the issue? Or do you have suggestions?
I found this page:
http://www.fwd.at/tomcat/sharing-session-data-howto.html
According to the tomcat documentation:
http://tomcat.apache.org/tomcat-5.5-doc/config/host.html#Single%20Sign%20On
Logging out of one invalidates all sessions, and I can confirm that this works. However, it looks like the ressources for sessions may not be released.
Has anyone else seen this? ANy ideas?
Thanks,
L
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959907#3959907
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959907
19 years, 9 months
[JBoss jBPM] - Re: Ability to choose from determined values
by falazar
You need to deal with a "Web Application" which really has nothing to do with jBPM, it is something totally seperate. You will need some sort of java web app, the starter kit is currently using JSP technology (http://java.sun.com/products/jsp/) so you can take what is created there and expand upon it, that is probably the easiest way, but if you havnt done any JSP pages, then you are in for a little work learning the system.
Basically it is similar to php or perl pages, but it can call all the API's attached to the jBPM system, so you can interact there.
Our info:
JBMP JSP and Java Beans
JSP Pages
/home/broccol/jbpm/jbpm-starters-kit-3.1.1/jbpm/src/resources/jbpm.war
We changed the login.jsp to have a username login box, and added a password box.
Here is the actual login java
/home/broccol/jbpm/jbpm-starters-kit-3.1.1/jbpm/src/java.webapp/org/jbpm/webapp/bean/UserBean.java
/home/broccol/jbpm/jbpm-starters-kit-3.1.1/jbpm/build/classes.webapp/org/jbpm/webapp/bean/UserBean.class
After editing the files, you must recompile with ant:
ant -f build.deploy.xml clean build.webapp build.service.archive
and then copy over two files (from the jbpm/build directory)
cp build/jbpm.[sw]ar ../jbpm-server/server/jbpm/deploy/
To shutdown and start server
bin/shutdown.sh shutdown
bin/run.sh -c jbpm > & jbpm.log &
So as you see there, in the jbpm.war file are a few of the jsp pages that create the webapp, you can go in there and mess aroudn with them a bit, save, rebuild and check your changes.
The
/home/broccol/jbpm/jbpm-starters-kit-3.1.1 is just the location that we installed the starters kit in.
Be aware though, that the 3.2 version of jBPM will be using "faces" a different, hopefully better system than JSP, so if you intend to use the next version, you might should wait for that.
James Ratcliff
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959904#3959904
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959904
19 years, 9 months