KIE WB 6.1.0 Final and WildFly 8.[12].0 Final 404 error

[John Emmerling]

Long story short. Further details on request.

I deployed WildFly 8.2.0 then later deployed 8.1.0. The only significant "tweak" was to increase memory allocation via JAVA_OPTS env. variable (now "-Xms1024M -Xmx1024M -XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true"). My other tweak was to specify a port offset so that the different WildFly instances would be on different ports (and different from my jboss-eap-6.1 installation).

I deployed kie-wb-distribution-wars-6.1.0.Final-wildfly.war which I got from Here.

The deployment seems to go smoothly except for one stacktrace which I show below.

However, when I try the URL for the workbench (http://localhost:<port#>/kie-wb) I get a 404 error. Interestingly, in the Admin Console you can see a link for a WSDL which is on the same port. That link works OK. But no workbench.

The stacktrace I saw when deploying (both WildFly versions) begins as:

Am I installing the right thing?

P.S. stacktrace mentioned above:

2015-02-08 13:09:19,938 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 1) JBAS014134: EJB Invocation failed on component SimpleAsyncExecutorService for method public void org.uberfire.commons.async.SimpleAsyncExecutorService.execute(java.lang.Runnable): javax.ejb.ConcurrentAccessTimeoutException: JBAS014373: EJB 3.1 PFD2 4.8.5.5.1 concurrent access timeout on org.jboss.invocation.InterceptorContext$Invocation@6dda7ac - could not obtain lock within 5000MILLISECONDS

at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:100) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]

at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)

at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:55) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]

at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) [wildfly-weld-8.1.0.Final.jar:8.1.0.Final]

<etc.>

[Mauricio Salatino]

How did you start the wildfly instance? with ./standalone -c standalone-full.xml ?

--
You received this message because you are subscribed to the Google Groups "jBPM Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-setup+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-setup/dd1aff84-5c02-44c8-be2d-2a615a520e86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

 - MyJourney @ http://salaboy.com

 - Co-Founder @ http://www.jugargentina.org
 - Co-Founder @ http://www.jbug.com.ar
 
 - Salatino "Salaboy" Mauricio -

[Mauricio Salatino]

can you try by removing the .niogit/ directory before starting wildfly?

[John Emmerling]

standalone.bat -server-config=standalone-full.xml

That's equivalent, right (obviously windows rather than linux).

[Mauricio Salatino]

Yeah, that should do the work. 

--
You received this message because you are subscribed to the Google Groups "jBPM Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-setup+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-setup/8d44d7a6-d533-4765-8d2b-e559e1a60a9a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[John Emmerling]

I just did this i.e. stop WildFly, delete the directory, then restart WildFly. Still 404 error. URL is http://localhost:8180/kie-wb. Line 468 of standalone-full.xml looks like:

    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:100}">

[John Emmerling]

Well, having successfully installed it on jboss-eap-6.1 previously, I have decided to just stick with that and forget about installing to WildFly. The jboss-eap-6.1 installation seems to be working well. It may help that I've created the JAVA_OPTS environment variable to increase the heap size.

I wonder if the only foolproof way to do this is to use Maven to build the WAR on your own system.

[Frank Norman]

If you deploy war kie-wb-distribution-wars-6.1.0.Final-wildfly.war, then you will be able to access it here:  http://localhost:<port>/kie-wb-distribution-wars-6.1.0.Final-wildfly