[JBoss AOP] - Getting error while deploying aspectized war file on Jboss 5.0 - ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/C:/jboss....jboss-aop.xml state=Not Installed mode=Manual requiredState=Parse
by Dharani Mishra
Dharani Mishra [https://community.jboss.org/people/dmishra1] created the discussion
"Getting error while deploying aspectized war file on Jboss 5.0 - ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/C:/jboss....jboss-aop.xml state=Not Installed mode=Manual requiredState=Parse"
To view the discussion, visit: https://community.jboss.org/message/722771#722771
--------------------------------------------------------------
Hi,
I am new to AOP. I have a web application that has been aspectized using jboss-aop-2.0.0.GA..
I am using compile time weaving method. I have created a web archive(war) that contains the aspectized classes.
I am able to run the application in standalone mode. How ever, when I deploy the war file on the application server, I get error which I am giving below:
I have done the followings :
1. cloned default server and named it mypocserver
2. added the war file into server/mypocserver/deploy folder
2. copied jboss-aop.xml to server/mypocserver/deploy folder
3. copied server\mypocserver\deployers\jboss-aop-jboss5.deployer\pluggable-instrumentor.jar to jboss-5.0.0.GA\bin\pluggable-instrumentor.jar
4. added following lines to run.bat
set JAVA_OPTS=%JAVA_OPTS% -Djboss.aop.path=%JBOSS_HOME%\server\myPOCserver\deploy\jboss-aop.xml (to set jboss.aop.path)
set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -javaagent:pluggable-instrumentor.jar (I know it is needed for load time weaving. I tried it without setting this property first, but it did not work)
But while starting the server, I am getting the following error:
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/jboss/jboss-5.0.0.GA/server/mypocserver/deploy/jboss-aop.xml
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230)
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.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:545)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=aop
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:239)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:330)
... 22 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=aop
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:313)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 30 more
2012-03-09 16:36:45,832 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Parse: name=vfsfile:/C:/jboss/jboss-5.0.0.GA/server/mypocserver/deploy/jboss-aop.xml state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/jboss/jboss-5.0.0.GA/server/mypocserver/deploy/jboss-aop.xml
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230)
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.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:545)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=aop
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:239)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:330)
... 22 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=aop
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:313)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 30 more
Will appreciate if somebody can let me know what I am doing wrong here.
Thanks in advance
D Mishra
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/722771#722771]
Start a new discussion in JBoss AOP at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[jBPM] - StaleObjectStateException on jBPM 5.1 running on JBoss 6.1
by Linh Pham
Linh Pham [https://community.jboss.org/people/lpham1] created the discussion
"StaleObjectStateException on jBPM 5.1 running on JBoss 6.1"
To view the discussion, visit: https://community.jboss.org/message/724897#724897
--------------------------------------------------------------
Hi All,
I got an intermittent StaleObjectStateException while completing a Human Task in jBPM. My current set up is as follows:
- Message Driven Bean processes a message, and invokes jBPM to complete a human task:
@TransactionAttribute(value = TransactionAttributeType.REQUIRES_NEW)
public void onMessage(Message message)
{
try
{
// pulling out the sessionId, workItemId, and resultsMap from the message
final StatefulKnowledgeSession ksession = ((JbpmLauncher) new InitialContext().lookup("java:module/JbpmLauncher")).getSession(sessionId);
ksession.getWorkItemManager().completeWorkItem(inbound.getWorkItemId(), inbound.getResultsMap());
}
catch(NamingException e)
{
LOGGER.error("Encounterred exception", e);
throw new WorkflowException("Unable to find the JBPM Launcher. ", e); //WorkflowException is RuntimeException with @ApplicationException annotation.
}
catch(Exception e)
{
LOGGER.error("Encounterred exception", e);
throw new WorkflowException(e); //WorkflowException is RuntimeException with @ApplicationException annotation.
}
}
Intermittently, I got StaleObjectStateException and the stack trace is here: http://pastebin.com/HxUfSPh5 http://pastebin.com/HxUfSPh5
I am using jBPM 5.1, JBoss 6.1, the jbpm-ds.xml is XA datasource with transaction isolation of TRANSACTION_READ_COMMITTED. JMS implementation is ActiveMQ with XA Datasource.
My environment is very low traffic, with just one user doing testing at the moment.
Is there a way to reliably reproduce the problem? And more importantly how can I get around this StaleObjectStateException?
Thanks for your help.
Linh
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/724897#724897]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[jBPM] - Re: Designer loading problem in drools-guvnor
by renez
renez [https://community.jboss.org/people/renez] created the discussion
"Re: Designer loading problem in drools-guvnor"
To view the discussion, visit: https://community.jboss.org/message/721414#721414
--------------------------------------------------------------
Hello,
I'm having this problem today, too. I'm using jbpm 5.2 installed by installer on Ubuntu Linux 10.04 with openjdk-6. In Guvnor I can create a BPmn 2.0 process. But when I try to open the File just get a screen "Please wait while loading". In server.log I can find.
18:21:25,182 INFO [stdout] (http--0.0.0.0-8080-5) INFO 04-03 18:21:25,181 (NilAuthenticator.java:authenticate:35)
All users are guests.
18:22:47,125 INFO [stdout] (http--0.0.0.0-8080-6) (null: -1, -1): Premature end of file.
18:22:47,799 INFO [org.jbpm.designer.server.EditorHandler] (http--0.0.0.0-8080-6) The diagram editor is running in development mode. Javascript will be served uncompressed
18:22:47,801 INFO [org.jbpm.designer.server.EditorHandler] (http--0.0.0.0-8080-6) Performing diagram information pre-processing steps.
18:22:48,208 INFO [stdout] (http--0.0.0.0-8080-7) INFO 04-03 18:22:48,206 (NilAuthenticator.java:authenticate:35)
All users are guests.
18:22:48,494 INFO [stdout] (http--0.0.0.0-8080-7) INFO 04-03 18:22:48,493 (NilAuthenticator.java:authenticate:35)
All users are guests.
18:22:48,560 INFO [stdout] (http--0.0.0.0-8080-7) INFO 04-03 18:22:48,559 (NilAuthenticator.java:authenticate:35)
All users are guests.
18:22:48,698 INFO [stdout] (http--0.0.0.0-8080-7) INFO 04-03 18:22:48,697 (NilAuthenticator.java:authenticate:35)
All users are guests.
18:22:48,739 INFO [stdout] (http--0.0.0.0-8080-7) INFO 04-03 18:22:48,738 (NilAuthenticator.java:authenticate:35)
All users are guests.
18:22:48,772 INFO [org.jbpm.designer.web.preprocessing.impl.JbpmPreprocessingUnit] (http--0.0.0.0-8080-6) Successfully deleted file :/opt/jboss/jbpm-5.2/jboss-as-7.0.2.Final/standalone/tmp/vfs/temp5fa1d605b1619162/designer.war-74ced14e8e0c620f/stencilsets/bpmn2.0jbpm/bpmn2.0jbpm.json
18:22:48,773 INFO [org.jbpm.designer.web.preprocessing.impl.JbpmPreprocessingUnit] (http--0.0.0.0-8080-6) Created file:/opt/jboss/jbpm-5.2/jboss-as-7.0.2.Final/standalone/tmp/vfs/temp5fa1d605b1619162/designer.war-74ced14e8e0c620f/stencilsets/bpmn2.0jbpm/bpmn2.0jbpm.json
18:22:48,818 INFO [org.jbpm.designer.web.preprocessing.impl.JbpmPreprocessingUnit] (http--0.0.0.0-8080-6) Created file:/opt/jboss/jbpm-5.2/jboss-as-7.0.2.Final/standalone/tmp/vfs/temp5fa1d605b1619162/designer.war-74ced14e8e0c620f/stencilsets/bpmn2.0jbpm/view/activity/workitems/Log.svg
18:22:48,829 INFO [org.jbpm.designer.web.preprocessing.impl.JbpmPreprocessingUnit] (http--0.0.0.0-8080-6) Created file:/opt/jboss/jbpm-5.2/jboss-as-7.0.2.Final/standalone/tmp/vfs/temp5fa1d605b1619162/designer.war-74ced14e8e0c620f/stencilsets/bpmn2.0jbpm/view/activity/workitems/Email.svg
18:23:10,604 INFO [stdout] (http--0.0.0.0-8080-7) INFO 04-03 18:23:10,603 (NilAuthenticator.java:authenticate:35)
All users are guests.
18:23:10,660 INFO [stdout] (http--0.0.0.0-8080-7) (null: -1, -1): Premature end of file.
Like mika suggested I changed the umlauts and the special charkters. The strang thing is, that everyting works fine on my local developer system with win xp.
Does somebody have a suggestion? Hints a greatly appriciated!
René
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/721414#721414]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years