[jBPM] - Unable to save process from process-designer after moving it from Eclipse (NPE)
by mcfeber
mcfeber [https://community.jboss.org/people/mcfeber] created the discussion
"Unable to save process from process-designer after moving it from Eclipse (NPE)"
To view the discussion, visit: https://community.jboss.org/message/750296#750296
--------------------------------------------------------------
I am using guvnor 5.4.0 Final and process-designer.2.2.1.Final in tomcat 7.
I import (Add... via webdav) a simple bpmn2 process (start,script,stop) from Eclipse, open it in the designer, make a small change (move the icons) and select save.
The designer reports:
400 Sorry, a technical error occurred. Please contact a system administrator.
The catalina.out has the following (partial) stack trace:
ERROR 25-07 11:54:33,597 (LoggingHelper.java:error:74) Service method 'public abstract java.lang.String org.drools.guvnor.client.rpc.AssetService.checkinVersion(org.drools.guvnor.client.rpc.Asset) throws com.google.gwt.user.client.rpc.SerializationException' threw an unexpected exception: java. ang.NullPointerException
java.lang.NullPointerException
at org.drools.repository.AssetItem.updateContent(AssetItem.java:390)
at org.drools.guvnor.server.contenthandler.drools.BPMN2ProcessHandler.storeAssetContent(BPMN2ProcessHandler.java:155)
at org.drools.guvnor.server.RepositoryAssetOperations.checkinVersion(RepositoryAssetOperations.java:180)
at org.drools.guvnor.server.RepositoryAssetOperations$Proxy$_$$_WeldClientProxy.checkinVersion(RepositoryAssetOperations$Proxy$_$$_WeldClien Proxy.java)
at org.drools.guvnor.server.RepositoryAssetService.checkinVersion(RepositoryAssetService.java:155)
at org.drools.guvnor.server.RepositoryAssetService$Proxy$_$$_WeldClientProxy.checkinVersion(RepositoryAssetService$Proxy$_$$_WeldClientProxy java)
at org.drools.guvnor.server.RepositoryServiceServlet.checkinVersion(RepositoryServiceServlet.java:596)
After that, any attempt to save the process results in the following message:
Error: Unable to save this asset, as it has been recently updated by [admin]
I've tried this with validation (after creating the PNG) where the designer reports it as valid and without validation, and the result is the same. Is there a way around this? I need to be able to round-trip processes between Eclipse and guvnor.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/750296#750296]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss Remoting] - Thread leakage in long run in JMS remote messaging
by Bhaskar Ethirajulu
Bhaskar Ethirajulu [https://community.jboss.org/people/bhaskar1212] created the discussion
"Thread leakage in long run in JMS remote messaging"
To view the discussion, visit: https://community.jboss.org/message/753942#753942
--------------------------------------------------------------
Hi
Our application has around 10 Java modules. We are using JBOSS App server and JMS messaging for synchronous and asynchronous intercommunication between these modules.
The thread threshold we maintained for our application is 600. But when we do longrun on the application for 2 to 3 days without doing any stress test the thread count has been slowly increasing to more than 1000. The order of thread leakage is unpredictable.
When we run Jstack on the bin location of jdk path we are able to see around 450 threads which are alive and occured during JMS messaging. Please find below the origination of the thread messge.
Please find below the thread origination messages.
Thread 29704: (state = IN_NATIVE)
- java.net.SocketInputStream.socketRead0(java.io.FileDescriptor, byte[], int, int, int) @bci=0 (Interpreted frame)
- java.net.SocketInputStream.read(byte[], int, int) @bci=84, line=129 (Interpreted frame)
- java.net.SocketInputStream.read() @bci=23, line=182 (Interpreted frame)
- java.io.FilterInputStream.read() @bci=4, line=66 (Compiled frame)
- org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlConnectionThread.run() @bci=18, line=741 (Interpreted frame)
Can any one please respond quickly on this. This has to be fixed before moving it to production.
Thanks,
Bhaskar.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/753942#753942]
Start a new discussion in JBoss Remoting at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
[JBoss Remoting] - JBOSS (JMX)
by Anton Yanchev
Anton Yanchev [https://community.jboss.org/people/micros] created the discussion
"JBOSS (JMX)"
To view the discussion, visit: https://community.jboss.org/message/754113#754113
--------------------------------------------------------------
Hi folks,
I'm a beginer in Jboss.
Windows server 2003
Java 1.6.0_33
Jboss 6.1.0 Final.
I want to make remote connection to jmx. I have followed this document http://thwack.solarwinds.com/docs/DOC-166968 http://thwack.solarwinds.com/docs/DOC-166968 when i excuting run.bat file received these errors
Aug 16, 2012 10:37:01 PM org.jboss.resource.connectionmanager.ConnectionFactoryB
indingService bindConnectionFactory
INFO: Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=J
msXA' to JNDI name 'java:JmsXA'
Aug 16, 2012 10:37:01 PM org.jboss.xnio.Xnio <clinit>
INFO: XNIO Version 2.1.0.CR2
Aug 16, 2012 10:37:01 PM org.jboss.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 2.1.0.CR2
Aug 16, 2012 10:37:02 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.1.0.Beta2
Aug 16, 2012 10:37:02 PM org.jboss.web.tomcat.service.deployers.TomcatDeployment
performDeployInternal
INFO: deploy, ctxPath=/
Aug 16, 2012 10:37:02 PM org.hornetq.core.logging.impl.JULLogDelegate info
INFO: trying to deploy queue jms.queue.ExpiryQueue
Aug 16, 2012 10:37:02 PM org.hornetq.core.logging.impl.JULLogDelegate info
INFO: trying to deploy queue jms.queue.DLQ
Aug 16, 2012 10:37:02 PM org.jboss.dependency.plugins.AbstractController increme
ntState
ERROR: Error installing to Instantiated: name=JBossLogService state=Described mo
de=On Demand requiredState=Installed
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(R
eflectionUtils.java:154)
at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.ne
wInstance(ReflectConstructorInfoImpl.java:102)
at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicC
onstructorJoinPoint.java:81)
at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.disp
atch(AOPConstructorJoinpoint.java:109)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$Joi
npointDispatchWrapper.execute(KernelControllerContextAction.java:257)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(Executio
nWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis
patchExecutionWrapper(KernelControllerContextAction.java:125)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis
patchJoinPoint(KernelControllerContextAction.java:72)
at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionIn
ternal(InstantiateAction.java:67)
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.sim
pleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.ins
tall(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install
(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra
ctControllerContext.java:379)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:2044)
at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra
ctController.java:1083)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementSta
teDirectly(AbstractController.java:1322)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:1246)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:1139)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:894)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:641)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(B
eanMetaDataDeployer.java:182)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(B
eanMetaDataDeployer.java:58)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.i
nternalDeploy(AbstractSimpleRealDeployer.java:63)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(
AbstractRealDeployer.java:55)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(Deployer
Wrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(Deployer
sImpl.java:1832)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFi
rst(DeployersImpl.java:1550)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFi
rst(DeployersImpl.java:1571)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(Deployers
Impl.java:1491)
at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra
ctControllerContext.java:379)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:2044)
at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra
ctController.java:1083)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementSta
teDirectly(AbstractController.java:1322)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:1246)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:1139)
at org.jboss.dependency.plugins.AbstractController.change(AbstractContro
ller.java:939)
at org.jboss.dependency.plugins.AbstractController.change(AbstractContro
ller.java:654)
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersI
mpl.java:1983)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(Deployers
Impl.java:1076)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeploye
rImpl.java:679)
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.p
rocess(MainDeployerPlugin.java:106)
at org.jboss.profileservice.dependency.ProfileControllerContext$Delegate
Deployer.process(ProfileControllerContext.java:143)
at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(Profil
eDeployAction.java:151)
at org.jboss.profileservice.dependency.ProfileDeployAction.installAction
Internal(ProfileDeployAction.java:94)
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.sim
pleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.ins
tall(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install
(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra
ctControllerContext.java:379)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:2044)
at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra
ctController.java:1083)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementSta
teDirectly(AbstractController.java:1322)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:1246)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:1139)
at org.jboss.dependency.plugins.AbstractController.change(AbstractContro
ller.java:939)
at org.jboss.dependency.plugins.AbstractController.change(AbstractContro
ller.java:654)
at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicPro
fileActivation.start(ProfileActivationWrapper.java:190)
at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(Pr
ofileActivationWrapper.java:87)
at org.jboss.profileservice.dependency.ProfileActivationService.activate
Profile(ProfileActivationService.java:215)
at org.jboss.profileservice.dependency.ProfileActivationService.activate
(ProfileActivationService.java:159)
at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.ac
tivate(AbstractProfileServiceBootstrap.java:112)
at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolve
rFacade.deploy(BasicResolverFactory.java:87)
at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.st
art(AbstractProfileServiceBootstrap.java:91)
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceB
ootstrap.start(BasicProfileServiceBootstrap.java:132)
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceB
ootstrap.start(BasicProfileServiceBootstrap.java:56)
at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(A
bstractServer.java:827)
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.r
un(AbstractServer.java:417)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IllegalStateException: The LogManager was not properly inst
alled (you must set the "java.util.logging.manager" system property to "org.jbos
s.logmanager.LogManager")
at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
at org.jboss.logmanager.LogService.<clinit>(LogService.java:32)
... 75 more
Aug 16, 2012 10:37:02 PM org.jboss.system.server.profileservice.bootstrap.BasicP
rofileServiceBootstrap start
ERROR: Failed to load profile:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incompl
ete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "Logging:CONTEXT:system" is missing the following dependencies:
Dependency "JBossLogService" (should be in state "Create", but is actually i
n state "**ERROR**")
Deployment "Logging:HANDLER:system:CONSOLE" is missing the following dependenc
ies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:HANDLER_INSTALLER:system::2" is missing the following depe
ndencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Dependency "Logging:LOGGER:system:<root>" (should be in state "Installed", b
ut is actually in state "Described")
Dependency "Logging:HANDLER:system:CONSOLE" (should be in state "Installed",
but is actually in state "Instantiated")
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:<root>" is missing the following dependencie
s:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:com.arjuna.ats" is missing the following dep
endencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:com.sun" is missing the following dependenci
es:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:facelets.compiler" is missing the following
dependencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:jacorb" is missing the following dependencie
s:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:javax.enterprise.resource.webcontainer.jsf"
is missing the following dependencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:javax.xml.bind" is missing the following dep
endencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:org.apache" is missing the following depende
ncies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:org.jboss.management" is missing the followi
ng dependencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:org.jboss.serial" is missing the following d
ependencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:org.jgroups" is missing the following depend
encies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:org.mc4j" is missing the following dependenc
ies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:org.quartz" is missing the following depende
ncies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:org.rhq.plugins.jbossas5.ApplicationServerCo
mponent" is missing the following dependencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:org.springframework" is missing the followin
g dependencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
Deployment "Logging:LOGGER:system:sun" is missing the following dependencies:
Dependency "Logging:CONTEXT:system" (should be in state "Installed", but is
actually in state "Configured")
DEPLOYMENTS IN ERROR:
Deployment "JBossLog4jRepostiorySelector" is in error due to the following rea
son(s): java.lang.IllegalStateException: The LogManager was not properly install
ed (you must set the "java.util.logging.manager" system property to "org.jboss.l
ogmanager.LogManager")
Deployment "JBossLogService" is in error due to the following reason(s): java.
lang.IllegalStateException: The LogManager was not properly installed (you must
set the "java.util.logging.manager" system property to "org.jboss.logmanager.Log
Manager"), **ERROR**
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(Dep
loyersImpl.java:1228)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainD
eployerImpl.java:905)
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.c
heckComplete(MainDeployerPlugin.java:87)
at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.che
ckAllComplete(ProfileDeployerPluginRegistry.java:107)
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceB
ootstrap.start(BasicProfileServiceBootstrap.java:135)
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceB
ootstrap.start(BasicProfileServiceBootstrap.java:56)
at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(A
bstractServer.java:827)
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.r
un(AbstractServer.java:417)
at java.lang.Thread.run(Thread.java:662)
Aug 16, 2012 10:37:02 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
Aug 16, 2012 10:37:02 PM org.apache.coyote.ajp.AjpProtocol start
INFO: Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
Aug 16, 2012 10:37:02 PM org.jboss.bootstrap.impl.base.server.AbstractServer$Sta
rtServerTask run
INFO: JBossAS [6.1.0.Final "Neo"] Started in 33s:970ms
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/754113#754113]
Start a new discussion in JBoss Remoting at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 6 months
