WildFly Alpha 4: "Operation failed with status WAITING" in JavaEE application client

[wolfgangknauf]

Hi JBoss gurus,

I have a small JavaEE application client, which worked fine with previous versions (7.2, and as far as I remember also with WildFly 8 Alpha 2). But with Alpha 4, after 30 seconds, I see an error.

C:\Temp>C:\Temp\wildfly-8.0.0.Alpha4\bin\appclient.bat c:\Temp\Stateless.ear#StatelessClient.jar

21:16:28,209 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Beta3

21:16:28,443 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.0.Beta2

21:16:28,552 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015899: WildFly 8.0.0.Alpha4 "WildFly" starting

21:16:30,081 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 13) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

21:16:30,096 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 16) JBAS016300: Activating JacORB Subsystem

21:16:30,143 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.17.Final)

21:16:30,159 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2

21:16:30,159 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 19) JBAS011800: Activating Naming Subsystem

21:16:30,206 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 22) JBAS015537: Activating WebServices Extension

21:16:30,206 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 20) JBAS013171: Activating Security Subsystem

21:16:30,315 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

21:16:30,346 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.17.SP1

21:16:30,533 WARN  [jacorb.codeset] (MSC service thread 1-4) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

21:16:30,549 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016330: CORBA ORB Service started

21:16:30,752 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

21:16:30,752 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS_disabled]

21:16:30,767 INFO  [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016328: CORBA Naming Service started

21:16:30,767 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([

    ("subsystem" => "naming"),

    ("service" => "remote-naming")

]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.remote is missing [jboss.remoting.endpoint.subsystem]"]}

21:16:30,830 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

JBAS014775:    New missing/unsatisfied dependencies:

      service jboss.remoting.endpoint.subsystem (missing) dependents: [service jboss.naming.remote]

21:16:30,830 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Alpha4 "WildFly" started (with errors) in 3448ms - Started 108 of 111 services (1 services failed or missing dependencies, 9 services are lazy, passive or on-demand)

21:16:30,861 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Stateless.ear" (runtime-name: "Stateless.ear")

21:16:31,001 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "null" (runtime-name: "StatelessClient.jar")

21:16:31,001 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "StatelessWeb.war")

21:16:31,001 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "null" (runtime-name: "StatelessEJB.jar")

21:16:31,298 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named GeometricModelBean in deployment unit subdeployment "StatelessEJB.jar" of deployment "Stateless.ear" are as follows:

    java:global/Stateless/StatelessEJB/GeometricModelBean!de.fhw.komponentenarchitekturen.knauf.stateless.GeometricModelRemote

    java:app/StatelessEJB/GeometricModelBean!de.fhw.komponentenarchitekturen.knauf.stateless.GeometricModelRemote

    java:module/GeometricModelBean!de.fhw.komponentenarchitekturen.knauf.stateless.GeometricModelRemote

    java:jboss/exported/Stateless/StatelessEJB/GeometricModelBean!de.fhw.komponentenarchitekturen.knauf.stateless.GeometricModelRemote

21:16:31,532 INFO  [org.jboss.as.server] (Thread-32) JBAS018559: Deployed "Stateless.ear" (runtime-name : "Stateless.ear")

21:16:31,547 INFO  [org.jboss.ejb.client] (Thread-37) JBoss EJB Client version 2.0.0.Beta3

21:16:31,563 INFO  [stdout] (Thread-37) MAIN has started

21:16:31,563 INFO  [org.xnio] (Thread-37) XNIO Version 3.1.0.CR3

21:16:31,578 INFO  [org.xnio.nio] (Thread-37) XNIO NIO Implementation Version 3.1.0.CR3

21:16:31,594 INFO  [org.jboss.remoting] (Thread-37) JBoss Remoting version 4.0.0.Beta1

21:17:01,702 ERROR [stderr] (Thread-37) java.lang.RuntimeException: Operation failed with status WAITING

21:17:01,702 ERROR [stderr] (Thread-37)     at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:93)

21:17:01,733 ERROR [stderr] (Thread-37)     at org.jboss.as.appclient.service.LazyConnectionContextSelector.createConnection(LazyConnectionContextSelector.java:77)

21:17:01,733 ERROR [stderr] (Thread-37)     at org.jboss.as.appclient.service.LazyConnectionContextSelector.getCurrent(LazyConnectionContextSelector.java:96)

21:17:01,733 ERROR [stderr] (Thread-37)     at org.jboss.as.appclient.service.LazyConnectionContextSelector.getCurrent(LazyConnectionContextSelector.java:52)

21:17:01,733 ERROR [stderr] (Thread-37)     at org.jboss.ejb.client.EJBClientContext.getCurrent(EJBClientContext.java:271)

21:17:01,733 ERROR [stderr] (Thread-37)     at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:281)

21:17:01,733 ERROR [stderr] (Thread-37)     at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:176)

21:17:01,733 ERROR [stderr] (Thread-37)     at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)

21:17:01,733 ERROR [stderr] (Thread-37)     at com.sun.proxy.$Proxy13.computeCuboidVolume(Unknown Source)

21:17:01,733 ERROR [stderr] (Thread-37)     at de.fhw.komponentenarchitekturen.knauf.stateless.GeometricModelApplicationClient.main(GeometricModelApplicationClient.java:30)

21:17:01,733 ERROR [stderr] (Thread-37)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

21:17:01,749 ERROR [stderr] (Thread-37)     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

21:17:01,749 ERROR [stderr] (Thread-37)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

21:17:01,749 ERROR [stderr] (Thread-37)     at java.lang.reflect.Method.invoke(Unknown Source)

21:17:01,749 ERROR [stderr] (Thread-37)     at org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:120)

21:17:01,749 ERROR [stderr] (Thread-37)     at java.lang.Thread.run(Unknown Source)

21:17:01,780 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]

21:17:01,796 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS_disabled]

21:17:01,811 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = h2

21:17:01,842 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment null (runtime-name: StatelessClient.jar) in 79ms

21:17:01,842 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment null (runtime-name: StatelessEJB.jar) in 81ms

21:17:01,858 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment null (runtime-name: StatelessWeb.war) in 83ms

21:17:01,858 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment Stateless.ear (runtime-name: Stateless.ear) in 96ms

21:17:01,874 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015950: WildFly 8.0.0.Alpha4 "WildFly" stopped in 60ms

The application client jar has no configuration and uses the defaults. It should connect to a local WildFly server (also with defaults). Has there been any change introduced so that I need some configuration?

The sample is here: http://www.cs.hs-rm.de/~knauf/JavaEE6/stateless/Stateless.ear

I will give it a try in the next few days with the most recent snapshot.

Best regards

Wolfgang

[ctomc]

Hi,

WildFly has different remoting protocol out of the box.

Now it by default uses http upgrade to upgrade to remoting protocol.

Did you use configuration from 7.2 in wildfly? or is this error with default configuration that comes with wildfly?

[wolfgangknauf]

Hi Tomaz,

it is all plain default configuration, no change by me, and no config files in my application client EAR.

The same error also happens with todays Beta1 snapshot.

Best regards

Wolfgang

[jaikiran]

This was fixed recently. Can you try the latest nightly build WildFly nightly builds available

[jaikiran]

Actually, hold on. There appear to be 2 issues in your stacktrace. One issue has been fixed. Let me take a look at the code for the other.

[jaikiran]

It's a bug. As a workaround, use:

./appclient.bat -H=http-remoting://localhost:8080 c:\Temp\Stateless.ear#StatelessClient.jar

(notice the use of -H)

[jaikiran]

jaikiran wrote:

It's a bug.

This should fix the bug https://github.com/wildfly/wildfly/pull/5141 once it's merged to upstream

[wolfgangknauf]

Hi Jaikiran,

thanks for the great support!

It seems your commit caused a build failure and was rejected. So this is not integrated in the latest nightly build?

Onemore question: with the "-H" parameter, my sample runs fine. But the application client does not really terminate afterwards.

I see this output after my own main method ends:

11:00:34,085 INFO  [org.jboss.ejb.client.remoting] (Remoting "endpoint" task-10) EJBCLIENT000016: Channel Channel ID a7584c5c (outbound) of Remoting connection7c7f57ac to localhost/127.0.0.1:8080 can no longer process messages

11:00:34,115 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-16) JBAS010418: Stopped Driver service with driver-name = h2

11:00:34,125 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment null (runtime-name: StatelessEJB.jar) in 30ms

11:00:34,125 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment null (runtime-name: StatelessClient.jar) in 31ms

11:00:34,125 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment null (runtime-name: StatelessWeb.war) in 33ms

11:00:34,125 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment Stateless.ear (runtime-name: Stateless.ear) in 17ms

11:00:34,135 INFO  [org.jboss.as] (MSC service thread 1-9) JBAS015950: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" stopped in 17ms

But it does not return to console.

Best regards

Wolfgang

[jaikiran]

Wolfgang Knauf wrote:

Hi Jaikiran,

thanks for the great support!

It seems your commit caused a build failure and was rejected. So this is not integrated in the latest nightly build?

The build did fail but it isn't related to that commit. It will be merged when it gets picked up by the PR reviewers.

Wolfgang Knauf wrote:

But it does not return to console.

Can you get a thread dump after you see the last message on that console?

[wolfgangknauf]

Attached is a thread dump of the client after its "exit".

[wolfgangknauf]

The problem does not seem to happen with Alpha 4, so it was either introduced on the way to Beta1, or it works with Alpha 4 because of a difference between my machines at home  (tested with Alpha 4) and at work (Beta 1)...

[wolfgangknauf]

One more: the WildFly 8 doc for a standalone application client ( https://docs.jboss.org/author/display/WFLY8/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project ) still has the the old ports and protocol.

[wolfgangknauf]

The hangup after the end of the application client seems to be fixed in most recent Beta2 snapshot.

[brian.stansberry]

Wolfgang Knauf wrote:

The hangup after the end of the application client seems to be fixed in most recent Beta2 snapshot.

Probably by this:

Make the ServerDeplyoemntRepository-temp-threads daemon https://communit... · c18323f · wildfly/wildfly · GitHub