[jBPM] - Problem with insertion of process instance into a knowledge session
by Miljenko Norsic
Miljenko Norsic [http://community.jboss.org/people/mnorsic] created the discussion
"Problem with insertion of process instance into a knowledge session"
To view the discussion, visit: http://community.jboss.org/message/629611#629611
--------------------------------------------------------------
Hi all,
I have a small test process that uses persistency to store process and knowledge session data into a database.As part of my process workflow I have a Rule Task that pulls WorkflowProcessInstance from a knowledge session, and therefore I have to insert process instance into a ksession, as shown on picture:
http://community.jboss.org/servlet/JiveServlet/showImage/2-629611-17071/s... http://community.jboss.org/servlet/JiveServlet/downloadImage/2-629611-170...
Upon signalEvent(), process continues, calls rule task and runs to completion, and there is nothing wrong with that.
The problem is that my rule does not run:
rule "Test WorkflowProcessInstance existence" ruleflow-group "test"
when
$p : WorkflowProcessInstance()
then
System.out.println("Process instance exists!");
end
It is obvious that I'm missing WorkflowProcessInstance in a knowledge session, and therefore I've added it.
But now I'm getting the following exception upon calling UserTransaction.commit() method:
java.io.NotSerializableException: org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl$1
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
...
It seems to me it is a bug in jBPM5.1, could someone please check it?
If this is a bug, I can create a Jira issue, but since I'm a jBPM greenhorn, I'd rather like to check on forum first because maybe I'm missing something obvious ;)
I'm attaching a sample Eclipse project with both persistent and non-persistent scenario.
Thanks,
Miljenko
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/629611#629611]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months
[Beginner's Corner] - What does this error message refer to in JBOSS 5.01?
by Ryan Williams
Ryan Williams [http://community.jboss.org/people/captainduh] created the discussion
"What does this error message refer to in JBOSS 5.01?"
To view the discussion, visit: http://community.jboss.org/message/629156#629156
--------------------------------------------------------------
Hello I am new to JBoss and I am working in SpringSource Tool Suite (STS) 2.71. The application is built on the Spring framework. I have not modified any settings with the server since installing it. Perhaps I need to modify some settings? When trying to deploy my application to JBOSS 5.01, I am getting an error that I do not understand.
Here is my stack trace:
ERROR [AbstractKernelController] Error installing to Configured: name=jboss.web.deployment:war=/MVCProj1 state=Instantiated mode=Manual requiredState=Configured
java.lang.RuntimeException: Exception setting attribute SecurityManagement on mbean jboss.web.deployment:war=/MVCProj1
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:170)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:114)
at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58)
at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.install(ServiceController.java:274)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:90)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.management.InvalidAttributeValueException: Set attribute has class class org.jboss.security.integration.JNDIBasedSecurityManagement loaded from BaseClassLoader@2f7cfe{vfsfile:/C:/JBoss%205.01/jboss-5.0.1.GA/server/default/conf/jboss-service.xml} that is not assignable to attribute class interface org.jboss.security.ISecurityManagement loaded from BaseClassLoader@8fddea{vfszip:/C:/JBoss%205.01/jboss-5.0.1.GA/server/default/deploy/MVCProj1.war/}
at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.checkAssignable(ModelMBeanAttributeInterceptor.java:229)
at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:88)
at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461)
at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:166)
... 45 more
Any help would be appreciated. Let me know if you need any other information.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/629156#629156]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months
[Performance Tuning] - Large number of threads/connections marked "keep alive"
by Ben Hsu
Ben Hsu [http://community.jboss.org/people/benhsu_at_bluefly] created the discussion
"Large number of threads/connections marked "keep alive""
To view the discussion, visit: http://community.jboss.org/message/587341#587341
--------------------------------------------------------------
Hello
We're seeing an issue where the performance of our application would degrade over time, to the point where its unresponsive. Based on what I see, I think it might be related to how we're configuring keep-alive, and I'm wondering where I can find more information about configuring keep-alive in JBoss.
The symptoms:
- The application's performance would degrade over the day
- eventually we will get a message saying "all 200 threads are busy, please increase the maximum thread count"
- at this point, doing a thread dump (using "kill -3") shows many threads in the following state:
<blockquote>
"TP-Processor200" daemon prio=1 tid=0x0000002b31e372c0 nid=0x651a runnable [0x000000005408e000..0x000000005408ec30]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
- locked <0x0000002b082abec0> (a java.io.BufferedInputStream)
at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:620)
at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:558)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:685)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
</blockquote>
- when I look at the "connection scoreboard" in the JBoss web console, I see 200 connections marked with a "K" for "keep alive", also these connections look like they've been around for a long time (around 7,000,000ms, which will be 2 hours), long after we've killed all the clientsd
Based on what I saw above and some googling, I'm thinking this might be related to how we're configuring keep alive. I haven't been able to go further than this, because I don't know much about JBoss configuration. Does anybody have any information about how keep alive is being configured in JBoss?
We are using JBoss version 4.0.5 GA
Thank you!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/587341#587341]
Start a new discussion in Performance Tuning at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months
@DataSourceConfiguration with JPA
by fernando＠lozano.eti.br
Hi there,
Are @DatsourceConfiguration and persistence.xml supposed to work together?
>From some posts on the Glassfish user list, it looks they should, but I
cannot make this work with JBoss AS 6.1. Is this a flaw with the Java EE 6
spec or a missing item on AS 6.1 as it is not yet Full Profile certified?
At deploy time, AS complains it cannot find the datasource referenced by
persistence.xml, but I can check with JNDIView from JMX Console and from
the Admin console it's there, with the correct name.
Another question, It should be possible to have a Java EE 6 app without any
XML deployment descriptor, but I could not find annotations to replace
persistence.xml. Am I missing something?
[]s, Fernando Lozano
14 years, 6 months
