Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1146427

Summary:

Issues in readme for app-client quickstart

Product:

[JBoss] JBoss Enterprise Application Platform 6

Reporter:

Nikoleta Hlavickova <nziakova>

Component:

Quickstarts

Assignee:

jboss-set

Status:

CLOSED CURRENTRELEASE

QA Contact:

Nikoleta Hlavickova <nziakova>

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

6.4.0

CC:

bsutter, jkudrnac, wfink

Target Milestone:

DR9

Target Release:

EAP 6.4.0

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2019-08-19 12:45:13 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
EAP 6.4 DR5 build of the app-client README.html file	none

Description Nikoleta Hlavickova 2014-09-25 08:56:35 UTC

There are some unclear instructions and typos.

(1) Product Versions: EAP 6.1, EAP 6.2, EAP 6/3
-- a typo, it should be 'EAP 6.3' instead of 'EAP 6/3'

(2) Make sure you have started and configured the JBoss Server successful as described above.
-- a typo? It probably should be 'successfully'. But in other quickstarts' readme there is a sentence 'Make sure you have started the JBoss EAP server as described above.' so I think we could use this one to keep it consistent.

(3) 6. Create a jboss-ejb-client.properties file with the following content
-- not clear on which machine and in which directory. The next step (7.) assumes that it is located in the same directory where the command is run from, but it is not clear in actual step (6.).

(4) 7. Type this command to run the application
-- the same as above, not clear which server the EAP_HOME refers to.

(5) Undeploy the Archives
-- instructions in this section work for undeploying from local EAP, not the remote one. There are no isntructions for undeploying the application from the remote EAP server.

Comment 1 sgilda 2014-09-25 12:06:33 UTC

1. Was fixed when I added the EAP 6.4 product version.
2. Yes, that's a typo, but made it consistent:

    Make sure you have configured and started the JBoss Server as described above.

3, 4, 5: You are correct. This is confusing. I am not able to test this section as I don't have 2 machines on a network. I will try to clarify these steps with Wulf's help.

Comment 2 sgilda 2014-09-25 15:15:20 UTC

Modified the instructions in this commit:
https://github.com/jboss-developer/jboss-eap-quickstarts/commit/3bd0281ff3d763f60a458467fef91d51fd4aff34

Fix can be previewed here:
https://github.com/jboss-developer/jboss-eap-quickstarts/blob/6.4.x/app-client/README.md

Comment 3 sgilda 2014-09-30 14:42:28 UTC

This is available in the DR3 build.

Comment 4 Nikoleta Hlavickova 2014-10-02 12:56:12 UTC

This way it is much better, thanks!

However, there are still some unclear instructions. 

Section Access the Remote Client Application from a different machine talks about Machine 1 and Machine 2. For Machine 2 the first step says:
Install JBoss EAP and the app-client quickstart on this machine.
I assume that "installing app-client quickstart" means deploying following the Build and Deploy the Quickstart section because this is the only instruction to deploy the quickstart in the readme. This means that the quickstart is deployed on a local machine. But the Undeploy the Archives section says how to undeploy from both local and remote machine. Where should be the application deployed - Machine 1 or Machine 2? Which one is local and which one is remote?

Please test the instructions. I have tried and got a warning and an error but, unfortunately, I have not got enough time to investigate it. 

My output after the step 5. Type this command to run the application:

11:33:11,011 WARN  [org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector] (Thread-44) Could not register a EJB receiver for connection to 10.16.88.177:4447: java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
	at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:92) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:77) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:146) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:115) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:47) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.EJBClientContext.getCurrent(EJBClientContext.java:272) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.as.quickstarts.appclient.acc.client.Main.main(Main.java:60) [simpleClient.jar:]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_26]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_26]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_26]
	at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_26]
	at org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:122)
	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
Caused by: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388)
	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.11.GA-redhat-2.jar:3.0.11.GA-redhat-2]
	at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) [xnio-api-3.0.11.GA-redhat-2.jar:3.0.11.GA-redhat-2]
	at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) [xnio-api-3.0.11.GA-redhat-2.jar:3.0.11.GA-redhat-2]
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.11.GA-redhat-2.jar:3.0.11.GA-redhat-2]
	at org.xnio.nio.NioHandle.run(NioHandle.java:90)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
	at ...asynchronous invocation...(Unknown Source)
	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:386)
	at org.jboss.ejb.client.remoting.EndpointPool$PooledEndpoint.connect(EndpointPool.java:182) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:152) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:133) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:75) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	... 12 more

11:33:12,550 ERROR [org.jboss.as.appclient.logging] (Thread-44) JBAS013201: InvocationTargetException running app client main: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_26]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_26]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_26]
	at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_26]
	at org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:122)
	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
Caused by: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:jboss-app-client, moduleName:ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@40f186b8
	at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:736) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.as.quickstarts.appclient.acc.client.interceptor.ClientInterceptor.handleInvocation(ClientInterceptor.java:38) [simpleClient.jar:]
	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:254) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:199) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:182) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:145) [jboss-ejb-client-1.0.26.Final-redhat-1.jar:1.0.26.Final-redhat-1]
	at $Proxy11.getGreeting(Unknown Source)
	at org.jboss.as.quickstarts.appclient.acc.client.Main.main(Main.java:61) [simpleClient.jar:]
	... 6 more

Comment 11 sgilda 2014-10-16 14:26:01 UTC

These changes are in the DR5 build.

Comment 14 sgilda 2014-10-16 15:05:18 UTC

Created attachment 947660 [details]
EAP 6.4 DR5 build of the app-client README.html file

Wolf, I have attached the latest README file for this quickstart to make it easier for you to review.

Comment 18 Nikoleta Hlavickova 2014-10-29 13:55:09 UTC

The additional space is also in the Access the Remote Client Application from the same machine section:
ClientContext is here = {Client=myhost}

Comment 19 sgilda 2014-11-06 19:31:17 UTC

Fixed in this commit: https://github.com/jboss-developer/jboss-eap-quickstarts/commit/b8b98bcc76c7b07ea76bec9b31581924421e0b60

Comment 20 Nikoleta Hlavickova 2014-11-12 07:46:50 UTC

Verified with EAP 6.4.0.DR9.