[Microcontainer] - Parsing Error run DZone_1_0 demos
by Gary Marsh
Hi I just downloaded the latest DZone_1_0 demos branch and got the following error when attempting to run JMXMain :
org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/C:/JBoss/DZone_1_0/branches/DZone_1_0/bootstrap/src/main/resources/META-INF/bootstrap-beans.xml@
| 94,101
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:184)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:139)
| at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:147)
| at org.jboss.demos.bootstrap.Main.configure(Main.java:80)
| at org.jboss.demos.bootstrap.Main.main(Main.java:45)
| at org.jboss.demos.bootstrap.jmx.JMXMain.main(JMXMain.java:33)
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {urn:jboss:classloading:1.0}classloading not found as a child of {urn:jboss:bean-deployer:2.0}property
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:370)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
| at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
| at org.apache.xerces.xinclude.XIncludeHandler.emptyElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(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:180)
| ... 5 more
| Deployed URL: file:/C:/JBoss/DZone_1_0/branches/DZone_1_0/jmx/src/main/resources/META-INF/system-jmx-beans.xml
| org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/C:/JBoss/DZone_1_0/branches/DZone_1_0/jmx/src/main/resources/META-INF/aop-beans.xml@71,72
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:184)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:139)
| at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:147)
| at org.jboss.demos.bootstrap.Main.deploy(Main.java:116)
| at org.jboss.demos.bootstrap.jmx.JMXMain.main(JMXMain.java:37)
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {urn:jboss:aop-beans:1.0}lifecycle-configure not found as a child of {urn:jboss:bean-deployer:2.0}deployment
|
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:370)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
| at org.apache.xerces.parsers.AbstractSAXParser.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.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:180)
|
| Do I need to update an .xsd file somewhere?
|
| Regards,
| GMarsh
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199895#4199895
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199895
17 years, 3 months
[Installation, Configuration & DEPLOYMENT] - JBoss native windows service won't start/stop cleanly
by peter.lyons
I am trying to use the JBoss Native Windows Service to start/stop JBoss, but start won't work cleanly (details below), and because of that stop won't work.
System Info: jboss-web-2.1.1-GA, jboss-native-2.0.6-windows-x86-ssl
I have tried on Windows Server 2003 EE SP2 and Windows Server 2008 with identical results.
Here is what I have discovered:
1. The "service.bat" script from JBoss Native has a bug since it references the non-existant "run.bat" file instead of "startup.bat". I filed bug https://jira.jboss.org/jira/browse/JBNATIVE-71 for this, but it is trivial to workaround just by doing "copy startup.bat run.bat", so this is not causing me any problems.
2. Once that is fixed, "service.bat start", "service.bat stop", and "service.bat install" and "service.bat uninstall" all seem to work correctly. However, starting the service from the Services Control Panel or via the "net start JBAS50SVC" command both misbehave in the same way. The actual jboss java process does indeed start and run correctly, but for some reason windows thinks the service started then stopped. Because of that, you cannot stop the service because windows incorrectly thinks it is not running. So the fact that "net start JBAS50SVC" does not work cleanly is the problem I am trying to solve. (In the nestat output below, the process listening on port 80 is jboss since I have it configured to listen on that port. Thus this shows it is indeed running)
C:\Program Files\CDE\jboss-web-2.1.1.GA\bin>net start JBAS50SVC
| The JBoss Application Server 5.0 service is starting.
| The JBoss Application Server 5.0 service could not be started.
|
| The service did not report an error.
|
| More help is available by typing NET HELPMSG 3534.
|
| C:\Program Files\CDE\jboss-web-2.1.1.GA\bin>netstat -an | find "80"
| TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
| TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING
| TCP 127.0.0.1:8005 0.0.0.0:0 LISTENING
|
| C:\Program Files\CDE\jboss-web-2.1.1.GA\bin>net stop JBAS50SVC
| The JBoss Application Server 5.0 service is not started.
|
| More help is available by typing NET HELPMSG 3521.
Unfortunately, run.log does not seem to provide any clues:
C:\Program Files\CDE\jboss-web-2.1.1.GA\bin>type run.log
| Starting JBoss Application Server 5.0 [2009-01-06 09:58:34]
| Using CATALINA_BASE: C:\Program Files\CDE\jboss-web-2.1.1.GA
| Using CATALINA_HOME: C:\Program Files\CDE\jboss-web-2.1.1.GA
| Using CATALINA_TMPDIR: C:\Program Files\CDE\jboss-web-2.1.1.GA\temp
| Using JRE_HOME: C:\Program Files\CDE\jboss-web-2.1.1.GA\..\cde_winpe_shar
| e
Anyone have any insights into this problem? Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199891#4199891
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199891
17 years, 3 months
[JBoss jBPM] - Problem persisting tasks
by tangomannn
Hi, first of all I want to say that I checked the forum, but I didn't find anything to solve my doubt.
Intro:
I'm creating the process definition in a programmatic way. I create the ProcessDefinition, then the process Instances, and then I create the tasks dinamically. To create the tasks I have an event "node enter" and createTask = false in the NodeTask.
This is the ActionHandler I use to create the tasks: (I just put the important code)
| public void execute(ExecutionContext executionContext) throws Exception {
| JbpmContext jbpmContext = JbpmConfiguration.getInstance().createJbpmContext();
|
| TaskMgmtInstance tmi = executionContext.getTaskMgmtInstance();
| TaskNode nodeApproval = (TaskNode)executionContext.getNode();
| //get the only task definited in the processDefinition
| Task task = (Task)nodeApproval.getTasks().iterator().next();
| //taskNumber and user are variables
| //I instantiate for example 3 task
| for (int i=0; i<tasksNumber; i++){
| TaskInstance newTaskInstance= tmi.createTaskInstance(task, executionContext.getToken());
| newTaskInstance.setActorId(user);
| //THIS IS THE LINE that is not working
| jbpmContext.getSession().save(newTaskInstance);
|
| }
|
I have to put that line because if I don't put, the task instance does not save the actor. But the problem is that even if I instance three tasks it only saves one.
If I do this, with an xml (not programmatically) work well.
I had to use
jbpmContext.getSession().save(newTaskInstance);
and not jbpmContext.save( ..); because if I use this one on the close it gives me "object references an unsaved transient instance" exception
any idea, clue?
Thanks
Fernando
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199878#4199878
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199878
17 years, 3 months