https://bz.apache.org/bugzilla/show_bug.cgi?id=65521
--- Comment #5 from Marius Tantareanu <[email protected]> --- Steps to reproduce: 1. Deploy the attached EAR file (simple-ear.ear) in WildFly. The EAR contains a single EJB that will be accessed by the client. 2. Configure httpd as a reverse proxy to WildFly (httpd should handle HTTP protocol upgrade to jboss-remoting): ProxyPass "/" "ws://localhost:1026/" upgrade=jboss-remoting A sample configuration file is attached (httpd.conf) 3. Run the attached standalone Java client that attempts to invoke an EJB in WildFly via httpd. Before running the client, you need to copy the WildFly client library (jboss-client.jar) to the lib folder (this is not included in the archive due to its size). cd echo-client-wf20 java -cp ./bin:./lib/jboss-client.jar:./lib/simple-ejbClient.jar com.microfocus.echoclient.EchoClient "remote+https" "localhost" "4433" Port 4433 is SSL enabled. For clear text communication use protocol as "remote+http" and port as "80". The client requires Java 11 or above (testing was done with Java 11). After the client completes the EJB call, it simply exits without explicitly closing the connection to httpd / WildFly. In practice this can happen due to an unexpected crash but httpd should not get into this state due to a misbehaving client. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
