Sebastiano Vigna created HTTPASYNC-32:
-----------------------------------------
Summary: Weird JMX interaction on Mac OS X
Key: HTTPASYNC-32
URL: https://issues.apache.org/jira/browse/HTTPASYNC-32
Project: HttpComponents HttpAsyncClient
Issue Type: New Feature
Affects Versions: 4.0-beta3
Environment: Mac OS X 10.8.2
Java(TM) SE Runtime Environment (build 1.7.0_10-b18)
Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode)
Reporter: Sebastiano Vigna
We are experiencing a very weird interaction between DefaultHttpAsyncClient and
JMX on Mac OS X. We start our application with
java -Xmx3G -server -Dcom.sun.management.jmxremote.port=9999
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false it.unimi.dsi.law.bubing.Agent
Under Linux (always JDK 7u10), everything works fine and we can access JMX at
port 9999. On Mac OS X, if DefaultHttpAsyncClient is started but inactive any
attempt to open the JMX connection hangs, whereas if it is actively working
(i.e., there is some ongoing connection) we get various kind of socket
exceptions like
Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root
exception is java.rmi.ConnectIOException: error during JRMP connection
establishment; nested exception is:
java.io.EOFException]
(this is from JMXterm). If we create but don't start the client, everything
works fine.
Unfortunately we don't know if this is a problem with the client, JMX or the
implementation of some subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
