Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-7643

Remote method invocation fails in ejb-asynchronous quickstart

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.DR14
    • 7.1.0.DR8, 7.1.0.DR9, 7.1.0.DR10, 7.1.0.DR11, 7.1.0.DR12, 7.1.0.DR13
    • Quickstarts
    • None

    Description

      When following the instructions for ejb-asynchronous quickstart application, step Acess the application currently produces Exception which prevents further execution of the application. As the quickstart applications are supposed to expose features to users, this is a functional blocker. However, it is not caused by error in quickstart itself, but rather by wrong implementation of feature it presents. Quickstarts are expected to run when following the instructions in the quickstart readme file.

      [mjurc@tigris client]$ mvn exec:exec
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss EAP Quickstart: ejb-asynchronous - client 7.1.0.Alpha1
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:exec (default-cli) @ jboss-ejb-asynchronous-client ---
Dec 06, 2016 11:29:41 AM org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient <init>
INFO: Lookup Bean >ejb:/jboss-ejb-asynchronous-ejb/AsynchronousAccessBean!org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess
Dec 06, 2016 11:29:42 AM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 3.0.0.Beta2
Dec 06, 2016 11:29:42 AM org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient <init>
INFO: Lookup Bean >ejb:/jboss-ejb-asynchronous-ejb/ParallelAccessBean!org.jboss.as.quickstarts.ejb.asynchronous.ParallelAccess
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoadException
	at org.jboss.remoting3.EndpointBuilder.build(EndpointBuilder.java:117)
	at org.jboss.remoting3.RemotingXmlParser.parseEndpoint(RemotingXmlParser.java:53)
	at org.jboss.remoting3.ConfigurationEndpointSupplier.lambda$static$0(ConfigurationEndpointSupplier.java:44)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.jboss.remoting3.ConfigurationEndpointSupplier.<clinit>(ConfigurationEndpointSupplier.java:42)
	at org.wildfly.common.context.ContextManager.setGlobalDefaultSupplierIfNotSet(ContextManager.java:108)
	at org.jboss.remoting3.Endpoint.lambda$static$0(Endpoint.java:58)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.jboss.remoting3.Endpoint.<clinit>(Endpoint.java:56)
	at org.jboss.ejb.client.remoting.EndpointPool.getEndpoint(EndpointPool.java:89)
	at org.jboss.ejb.client.remoting.RemotingEndpointManager.getEndpoint(RemotingEndpointManager.java:49)
	at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:136)
	at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:118)
	at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:47)
	at org.jboss.ejb.client.EJBClientContext.getCurrent(EJBClientContext.java:279)
	at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:289)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:178)
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
	at com.sun.proxy.$Proxy0.fireAndForget(Unknown Source)
	at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.fireAndForget(AsynchronousClient.java:76)
	at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.main(AsynchronousClient.java:158)
Caused by: java.lang.ClassNotFoundException: org.jboss.modules.ModuleLoadException
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 21 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.206 s
[INFO] Finished at: 2016-12-06T11:29:42+01:00
[INFO] Final Memory: 12M/238M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (default-cli) on project jboss-ejb-asynchronous-client: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

      Upon manually wiring the missing dependency, the following error is still produced:

      [mjurc@tigris client]$ mvn exec:exec
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss EAP Quickstart: ejb-asynchronous - client 7.1.0.Alpha1
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:exec (default-cli) @ jboss-ejb-asynchronous-client ---
Dec 06, 2016 11:40:12 AM org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient <init>
INFO: Lookup Bean >ejb:/jboss-ejb-asynchronous-ejb/AsynchronousAccessBean!org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess
Dec 06, 2016 11:40:12 AM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 3.0.0.Beta2
Dec 06, 2016 11:40:12 AM org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient <init>
INFO: Lookup Bean >ejb:/jboss-ejb-asynchronous-ejb/ParallelAccessBean!org.jboss.as.quickstarts.ejb.asynchronous.ParallelAccess
Dec 06, 2016 11:40:12 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.0.Beta7
Dec 06, 2016 11:40:12 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.4.1.Final-redhat-1
Dec 06, 2016 11:40:12 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.4.1.Final-redhat-1
Dec 06, 2016 11:40:12 AM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.1.0.Beta13
Dec 06, 2016 11:40:12 AM org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector setupEJBReceivers
WARN: Could not register a EJB receiver for connection to localhost:8080
javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server are supported
	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:391)
	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:225)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
	at ...asynchronous invocation...(Unknown Source)
	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:438)
	at org.jboss.ejb.client.remoting.EndpointPool$PooledEndpoint.connect(EndpointPool.java:173)
	at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:194)
	at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:150)
	at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:81)
	at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
	at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:161)
	at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:118)
	at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:47)
	at org.jboss.ejb.client.EJBClientContext.getCurrent(EJBClientContext.java:279)
	at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:289)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:178)
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
	at com.sun.proxy.$Proxy0.fireAndForget(Unknown Source)
	at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.fireAndForget(AsynchronousClient.java:76)
	at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.main(AsynchronousClient.java:158)

Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-asynchronous-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@7cbd213e
	at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:774)
	at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
	at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
	at com.sun.proxy.$Proxy0.fireAndForget(Unknown Source)
	at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.fireAndForget(AsynchronousClient.java:76)
	at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.main(AsynchronousClient.java:158)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.321 s
[INFO] Finished at: 2016-12-06T11:40:12+01:00
[INFO] Final Memory: 10M/298M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (default-cli) on project jboss-ejb-asynchronous-client: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9351 wildfly-discovery client shouldn't fail if JBoss Modules is not present

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8983 Legacy EJB client configuration ignores user credentials and can't be used to invoke even unsecured beans

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7282 Remoting dependency on jboss-modules must be optional

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          relates to

          Task - Represents a small unit of work that is not end-user facing. JBDS-4046 Test Quick Starts (EAP 7.1) with devstudio

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              tomazcerar Tomaž Cerar (Inactive)
              mjurc@redhat.com Michal Jurc
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: