Hi everyone out there, I’m writing this post just to share the slides from the Drools & jBPM workshops that we (Michael Anstis and I) did this week in central London. Hopefully we can host more of these workshops in other cities. If you are interested in running one of these workshops get in contact and we can help you to set it up.
Slides
Video
Special thanks to @mbitencourt for broadcasting the event!
Related Posts
Look at the following posts if you are interested to read about the content of the workshops.
- Human Resources Example
- Customer Relationships Example (work in progress)
- KIE Workbenchs Configurations
All the examples that I’ve demonstrated in the workshops are hosted in this repository:
Feedback
One of the main purposes behind doing these workshops was to collect feedback from the developers before the Final Community release. We manage to identify three major bugs which were identified and will be fixed for the final release, so I would like to thank you everyone out there who has tested the application and gave feedback about it.
If you want to try it out, read my related posts or get in contact with me so I can guide you to try the KIE Workbench.
Salaboy (Open Source Knowledge) 
Can’t deploy KIE-WB to Jboss 7.1, getting an error:
JBAS014777: Services which failed to start: service jboss.deployment.unit.”kie-wb-6.1.0-SNAPSHOT-jboss-as7.war”.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.”kie-wb-6.1.0-SNAPSHOT-jboss-as7.war”.POST_MODULE: Failed to process phase POST_MODULE of deployment “kie-wb-6.1.0-SNAPSHOT-jboss-as7.war”
Cloned, then mvn clean install and deployed to JBoss 7.1 (-Djboss.server.default.config=standalone-full.xml)
Watched your video, but hard to follow from watching it here. Is there some place where to get answers on how to deploy these modules?
LikeLike
Can you please use pastebin.net and paste all the console output. It should be working.
Try renaming the war file to kie-wb.war.
The forums are also good to ask questions.
LikeLike
Looks like starting from NetBeans 4 not working to well, JBoss log:
JAVA_OPTS already set in environment; overriding default settings with values: -Xms128m -Xmx512m -XX:MaxPermSize=256m -Djboss.server.default.config=standalone-full.xml
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Applications/jboss-as-7.1.1.Final
JAVA: /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms128m -Xmx512m -XX:MaxPermSize=256m -Djboss.server.default.config=standalone-full.xml
=========================================================================
14:13:10,064 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
14:13:10,453 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
14:13:10,544 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final “Brontes” starting
14:13:12,811 INFO [org.xnio] XNIO Version 3.0.3.GA
14:13:12,830 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
14:13:12,844 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
14:13:12,867 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
14:13:12,949 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
14:13:12,956 INFO [org.jboss.as.configadmin] (ServerService Thread Pool — 32) JBAS016200: Activating ConfigAdmin Subsystem
14:13:13,002 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 37) JBAS010280: Activating Infinispan subsystem.
14:13:13,010 INFO [org.jboss.as.jacorb] (ServerService Thread Pool — 38) JBAS016300: Activating JacORB Subsystem
14:13:13,087 INFO [org.jboss.as.security] (ServerService Thread Pool — 54) JBAS013101: Activating Security Subsystem
14:13:13,147 INFO [org.jboss.as.security] (MSC service thread 1-8) JBAS013100: Current PicketBox version=4.0.7.Final
14:13:13,150 INFO [org.jboss.as.osgi] (ServerService Thread Pool — 49) JBAS011940: Activating OSGi Subsystem
14:13:13,158 INFO [org.jboss.as.naming] (ServerService Thread Pool — 48) JBAS011800: Activating Naming Subsystem
14:13:13,214 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 58) JBAS015537: Activating WebServices Extension
14:13:13,326 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 33) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:13:13,338 INFO [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
14:13:13,342 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
14:13:13,379 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:13:13,418 INFO [org.jboss.jaxr] (MSC service thread 1-5) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
14:13:13,494 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services – Stack CXF Server 4.0.2.GA
14:13:14,018 WARN [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011600: AIO wasn’t located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
14:13:14,074 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-7) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
14:13:14,207 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/Applications/jboss-as-7.1.1.Final/standalone/data/messagingjournal,bindingsDirectory=/Applications/jboss-as-7.1.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/Applications/jboss-as-7.1.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/Applications/jboss-as-7.1.1.Final/standalone/data/messagingpaging)
14:13:14,216 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) Waiting to obtain live lock
14:13:14,253 INFO [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016330: CORBA ORB Service started
14:13:14,394 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-4) Using NIO Journal
14:13:14,452 INFO [org.jboss.as.jacorb] (MSC service thread 1-5) JBAS016328: CORBA Naming Service started
14:13:14,523 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory /Applications/jboss-as-7.1.1.Final/standalone/deployments
14:13:14,536 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost/127.0.0.1:4447
14:13:14,536 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /127.0.0.1:9999
14:13:14,623 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-4) Waiting to obtain live lock
14:13:14,624 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-4) Live Server Obtained live lock
14:13:15,003 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:13:15,207 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:5455 for CORE protocol
14:13:15,210 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:5445 for CORE protocol
14:13:15,215 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) Server is now live
14:13:15,215 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [4d8c95de-4a1e-11e3-a5f2-542696d4d8ed]) started
14:13:15,220 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.topic.testTopic
14:13:15,257 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test
14:13:15,263 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test
14:13:15,297 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
14:13:15,299 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
14:13:15,304 INFO [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
14:13:15,307 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) trying to deploy queue jms.queue.testQueue
14:13:15,319 INFO [org.jboss.as.messaging] (MSC service thread 1-6) JBAS011601: Bound messaging object to jndi name java:/queue/test
14:13:15,321 INFO [org.jboss.as.messaging] (MSC service thread 1-6) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test
14:13:15,359 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA
14:13:15,390 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-2) HornetQ resource adaptor started
14:13:15,391 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra
14:13:15,402 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
14:13:15,447 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
14:13:15,448 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final “Brontes” started in 5893ms – Started 168 of 247 services (78 services are passive or on-demand)
14:14:01,126 INFO [org.jboss.as.repository] (HttpManagementService-threads – 2) JBAS014900: Content added at location /Applications/jboss-as-7.1.1.Final/standalone/data/content/60/18194c97ef0399f9e2e6d2293216207cd72dcb/content
14:14:10,866 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of “kie-wb.war”
14:14:16,180 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry avalon-framework-4.2.0.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,181 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry batik-all-1.7.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,182 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry commons-io-1.3.1.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,182 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry commons-logging-1.0.4.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,183 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry serializer-2.7.0.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,183 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry servlet-2.2.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,184 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xalan-2.7.0.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,184 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xercesImpl-2.7.1.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,185 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xml-apis-1.3.04.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,185 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xml-apis-ext-1.3.04.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,186 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xmlgraphics-commons-1.3.1.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,186 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry fop-hyph.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,187 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jai_codec.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jai_core.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jai_imageio.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jimi-1.0.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,189 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xmlunit1.0.jar in “/content/kie-wb.war/WEB-INF/lib/fop-0.95.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,191 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jaxb-api.jar in “/content/kie-wb.war/WEB-INF/lib/jaxb-impl-2.2.5.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,191 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry activation.jar in “/content/kie-wb.war/WEB-INF/lib/jaxb-impl-2.2.5.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,192 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jsr173_1.0_api.jar in “/content/kie-wb.war/WEB-INF/lib/jaxb-impl-2.2.5.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,192 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jaxb1-impl.jar in “/content/kie-wb.war/WEB-INF/lib/jaxb-impl-2.2.5.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,193 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jaxb-api.jar in “/content/kie-wb.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,193 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jaxb-impl.jar in “/content/kie-wb.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,193 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jsr173_1.0_api.jar in “/content/kie-wb.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,194 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry activation.jar in “/content/kie-wb.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,196 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xml-apis-1.0.b2.jar in “/content/kie-wb.war/WEB-INF/lib/jbpmmigration-0.11.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,197 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry log4j-1.2.16.jar in “/content/kie-wb.war/WEB-INF/lib/jbpmmigration-0.11.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,205 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xml-apis.jar in “/content/kie-wb.war/WEB-INF/lib/serializer-2.7.1.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xercesImpl.jar in “/content/kie-wb.war/WEB-INF/lib/xalan-2.7.1.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry xml-apis.jar in “/content/kie-wb.war/WEB-INF/lib/xalan-2.7.1.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,208 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry serializer.jar in “/content/kie-wb.war/WEB-INF/lib/xalan-2.7.1.jar” does not point to a valid jar for a Class-Path reference.
14:14:16,452 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name ‘org.springframework.context.ApplicationContext,org.springframework.beans.BeansException,org.springframework.beans.factory.xml.NamespaceHandlerResolver’ for service type ‘org.apache.cxf.bus.factory’
14:14:16,457 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name ‘org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer’ for service type ‘org.xmlpull.v1.XmlPullParserFactory’
14:14:16,459 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Encountered invalid class name ‘org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer’ for service type ‘org.xmlpull.v1.XmlPullParserFactory’
14:14:16,726 INFO [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011401: Read persistence.xml for org.jbpm.domain
14:14:16,962 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment “deployment.kie-wb.war” is using a private module (“org.jboss.netty:main”) which may be changed or removed in future versions without notice.
14:14:16,962 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment “deployment.kie-wb.war” is using a private module (“org.jboss.netty:main”) which may be changed or removed in future versions without notice.
14:14:17,137 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment kie-wb.war
14:14:17,228 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named RetryTrackerSingleton in deployment unit deployment “kie-wb.war” are as follows:
java:global/kie-wb/RetryTrackerSingleton!org.kie.services.remote.jms.RetryTrackerSingleton
java:app/kie-wb/RetryTrackerSingleton!org.kie.services.remote.jms.RetryTrackerSingleton
java:module/RetryTrackerSingleton!org.kie.services.remote.jms.RetryTrackerSingleton
java:global/kie-wb/RetryTrackerSingleton
java:app/kie-wb/RetryTrackerSingleton
java:module/RetryTrackerSingleton
14:14:17,233 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit.”kie-wb.war”.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.”kie-wb.war”.POST_MODULE: Failed to process phase POST_MODULE of deployment “kie-wb.war”
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011232: Only one JAX-RS Application Class allowed. org.glassfish.jersey.server.ResourceConfig$RuntimeConfig org.glassfish.jersey.server.ResourceConfig$WrappingResourceConfig org.glassfish.jersey.server.ResourceConfig
at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.scan(JaxrsScanningProcessor.java:209)
at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.deploy(JaxrsScanningProcessor.java:105)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
… 5 more
14:14:17,246 INFO [org.jboss.as.server] (HttpManagementService-threads – 2) JBAS015870: Deploy of deployment “kie-wb.war” was rolled back with failure message {“JBAS014671: Failed services” => {“jboss.deployment.unit.\”kie-wb.war\”.POST_MODULE” => “org.jboss.msc.service.StartException in service jboss.deployment.unit.\”kie-wb.war\”.POST_MODULE: Failed to process phase POST_MODULE of deployment \”kie-wb.war\””}}
14:14:17,247 INFO [org.jboss.as.controller] (HttpManagementService-threads – 2) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.naming.context.java.module.kie-wb.kie-wb (missing) dependents: [service jboss.naming.context.java.module.kie-wb.kie-wb.ValidatorFactory, service jboss.naming.context.java.module.kie-wb.kie-wb.Validator]
JBAS014777: Services which failed to start: service jboss.deployment.unit.”kie-wb.war”.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.”kie-wb.war”.POST_MODULE: Failed to process phase POST_MODULE of deployment “kie-wb.war”
14:14:18,027 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment kie-wb.war in 777ms
14:14:18,028 INFO [org.jboss.as.controller] (MSC service thread 1-5) JBAS014774: Service status report
JBAS014776: Newly corrected services:
service jboss.naming.context.java.module.kie-wb.kie-wb (new available)
14:15:00,247 INFO [org.jboss.as.repository] (HttpManagementService-threads – 2) JBAS014901: Content removed from location /Applications/jboss-as-7.1.1.Final/standalone/data/content/60/18194c97ef0399f9e2e6d2293216207cd72dcb/content
14:23:55,402 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:/queue/test
14:23:55,404 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/queue/test
14:23:55,432 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
14:23:55,443 INFO [jacorb.orb] prepare ORB for shutdown…
14:23:55,443 INFO [jacorb.orb] ORB going down…
14:23:55,444 INFO [jacorb.poa] POA Naming destroyed
14:23:55,445 INFO [jacorb.poa] POA RootPOA destroyed
14:23:55,444 INFO [jacorb.poa] POA IRPOA destroyed
14:23:55,454 INFO [jacorb.orb] ORB shutdown complete
14:23:55,456 INFO [jacorb.orb] ORB run, exit
14:23:55,458 INFO [jacorb.orb.iiop] Listener exited
14:23:55,467 INFO [org.hornetq.ra.HornetQResourceAdapter] HornetQ resource adapter stopped
14:23:55,471 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
14:23:55,472 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
14:23:55,511 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [4d8c95de-4a1e-11e3-a5f2-542696d4d8ed] stopped
14:23:55,514 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.1.Final “Brontes” stopped in 99ms
Going to use your download outside of NetBeans, I’ve been using GlassFish for so long need to use JBoss AS more now…
LikeLike
Please use pastebin.net … and please try the instructions provided in my previous post -> https://salaboy.com/2013/10/22/kie-wb-jbpm-console-ng-configurations/
You can also try removing all the configurations from JAVA_OPTS
LikeLike