[jBPM] New message: "Error starting jBPM 4.3 on JBoss 5.1.0 - NoSuchMethodError"
by James Nicolson
User development,
A new message was posted in the thread "Error starting jBPM 4.3 on JBoss 5.1.0 - NoSuchMethodError":
http://community.jboss.org/message/519646#519646
Author : James Nicolson
Profile : http://community.jboss.org/people/jamesja
Message:
--------------------------------------------------------------
Hi All,Installing jBPM 4.3 on JBoss 5.1.0 using the standard distribution (ant -Djboss.home=... -Ddatabase=mysql install.jbpm.into.jbpm), When I start JBoss I get a NoSuchMethodError exception while starting the JBPMService as shown in the attached stack trace. This is strange, because the calling method and the called method are both in the same jar (jbpm.jar) and the call looks correct in the source. I have not found any reference to this error from anyone else. Does anyone have any idea what may cause it?
=== Environment ==============================
- jBPM Version : 4.3
- Database : mysql 5.1.39
- JDK : 1.6.0_17
- OS: MacOS 10.6.2
- Container : JBoss 5.1.0 GA
- Configuration : Using jbpm.cfg.xml from the distribution
- Libraries : Using libs from the distribution
=== Process ==================================
N/A
=== API ===================================
N/A
=== Stacktrace ==============================
18:47:44,197 ERROR [AbstractKernelController] Error installing to Start: name=org.jbpm:service=ProcessEngine state=Create
java.lang.NoSuchMethodError: org.jbpm.pvm.internal.wire.descriptor.CollectionDescriptor.addValueDescriptors(Ljava/util/List;)V
at org.jbpm.pvm.internal.wire.descriptor.HistorySessionDescriptor.add(HistorySessionDescriptor.java:50)
at org.jbpm.pvm.internal.wire.binding.HistorySessionsBinding.parse(HistorySessionsBinding.java:50)
at org.jbpm.pvm.internal.xml.Parser.parseElement(Parser.java:513)
at org.jbpm.pvm.internal.wire.xml.WireParser.parseElement(WireParser.java:229)
at org.jbpm.pvm.internal.wire.xml.WireParser.parseDocumentElement(WireParser.java:200)
at org.jbpm.pvm.internal.env.JbpmConfigurationParser.parseDocument(JbpmConfigurationParser.java:107)
at org.jbpm.pvm.internal.xml.Parser.execute(Parser.java:396)
at org.jbpm.pvm.internal.xml.Parse.execute(Parse.java:158)
at org.jbpm.pvm.internal.env.JbpmConfigurationParser.parseDocument(JbpmConfigurationParser.java:82)
at org.jbpm.pvm.internal.xml.Parser.execute(Parser.java:396)
at org.jbpm.pvm.internal.xml.Parse.execute(Parse.java:158)
at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.parse(ProcessEngineImpl.java:222)
at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.setResource(ProcessEngineImpl.java:194)
at org.jbpm.api.Configuration.setResource(Configuration.java:109)
at org.jbpm.api.Configuration.getProcessEngine(Configuration.java:161)
at org.jbpm.jboss.internal.JbpmService.start(JbpmService.java:39)
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.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.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.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
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.start(ServiceController.java:460)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
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:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
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:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
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.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:637)
=== Debug logs ==============================
As above
=== Problem description =========================
As above in the introduction
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519646#519646
16 years, 3 months
[Datasource Configuration] New message: "Re: Problem with number of database connections (Oracle)"
by Adrian Brock
User development,
A new message was posted in the thread "Problem with number of database connections (Oracle)":
http://community.jboss.org/message/519635#519635
Author : Adrian Brock
Profile : http://community.jboss.org/people/adrian@jboss.org
Message:
--------------------------------------------------------------
> michal_rorat wrote:
>
> You might think that with this configuration after starting JBoss you will have 5 connections made to DB but I have 38! Even when I set max-pool-size in oracle-ds.xml to 5 it don't change the number of created connections which I get from Oracle Enterprise Manager.
>
> If I put for example 5 in min-pool-size the numer of connection created is 43.
43-5=38
5 is the number of connections that get created when you first use the datasource, if you specify a min-pool-size of 5.
Since that number matches the difference in configuration that suggests to me that there were none in the pool before the change.
>
>
> Sub Pool Statistics:
> Sub Pool Count: 1
> ---------------------------------
>
> Track By Transaction: true
> Available Connections Count: 60
> Max Connections In Use Count:1
> Connections Destroyed Count:2
> Connections In Use Count:0
> Total Block Time:0
> Average Block Time For Sub Pool:0
> Maximum Wait Time For Sub Pool:0
> Total Timed Out:2
>
> -----------------------------------------------------------------------------------------
>
Can you look on the MBean itself at the attributes. There should be a one called "ConnectionsCreatedCount".
Once you find it, substract the "ConnectionsDestroyedCount" (which we know was 2 and they both timed out).
I don't know why the created count is not shown in listStatistics? You might want to report it as a bug?
> And 5 MDBs with one connection reserved for each of them
When you say 5 MDBs, do you mean one EJB deployment with 5 JMS Sessions in the pool
or do mean 5 EJBs with 15 (the default)?
If the latter, then each MDB instance has a DB connection, that could reach 5 x 15 = 75 connections if all the sessions/instances get used.
This is probably what you are seeing?
What numbers do you get if you don't deploy the MDB(s)?
P.S. Holding an unshared resource in an EJB instance is an anti-pattern. It doesn't scale (see the calculation above).
P.S.2. It can also lead to problems if your MDB throws a RuntimeException or Error, since them the instance is thrown away
and a new one created without the destroy lifecycle getting invoked.
So you have no opportunity to close() the resource - it won't get cleaned up until garbage collection spots it (assuming it has a finalize method).
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519635#519635
16 years, 3 months
[jBPM] New message: "get User / Roles ... from other sources"
by Markus Buchner
User development,
A new message was posted in the thread "get User / Roles ... from other sources":
http://community.jboss.org/message/519631#519631
Author : Markus Buchner
Profile : http://community.jboss.org/people/buchnerm
Message:
--------------------------------------------------------------
Hi
What is the best way if I need to get the user and accessrights / roles from other sources than the jbpm4 schema?
e.g. ldap or opensso or other db schema
Do i need to copy all the information in the jbpm schema? (otherwise I cannot use the query lang anymore or?)
* is there a best practise to extend the org.jbpm.api.identity.User? or do I have to change the schema/mapping/bean ... (would be bad for upcomming updates!)
Is there a tutorial / best practise to do something like that? Where somebody explaind that?
Thanks for your help Max
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519631#519631
16 years, 3 months