Have you tried to
1. Trace the process on the app server while you are trying to connect?
2. Performed a tcpdump on the app server while you are trying to connect?
3. Have you looked ta Glassfish’s server logs?
4. Have you turned on monitoring in the JVM to pull monitor information,
error reports (asadmin)? (off by default)
asadmin generate-jvm-report --type=[type]
https://docs.oracle.com/cd/E19879-01/820-4335/ablvu/index.html
5. Have you tried the jvm tools to look at the jvm (jstat, jmap, jconsole)?
Matthew Parker
Chief Technologist
Dimensional DBA
425-891-7934 (cell)
D&B 047931344
CAGE 7J5S7
<mailto:Dimensional.dba@xxxxxxxxxxx> Dimensional.dba@xxxxxxxxxxx
<http://www.linkedin.com/pub/matthew-parker/6/51b/944/> View Matthew Parker's
profile on LinkedIn
<http://www.dimensionaldba.com/> www.dimensionaldba.com
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Mark J. Bobak
Sent: Friday, September 30, 2016 1:55 AM
To: ORACLE-L
Subject: Intermittent timeouts on Glassgish server
Hi all,
Our standard stack is Oracle Database 12.1.0.2->APEX 5.0->ORDS 3.0.6->
GlassFish 4.1.1.
This generally works well, and is implemented on several sites (possibly with
minor version variations on various components.)
However, on one particular server, Glassgish periodically slow down, and
eventually hang to the point that, when trying to reach the app login screen in
a Web browser, we'll get connection reset errors.
I *thought* this was the JDBC & /dev/random entropy pool problem. But
yesterday, I modified GlassFish JVM configuration to use /dev/urandom, and
users continue to report intermittent slowness and connection reset errors.
I'm about at my wits end here.
Help!
If anyone has any ideas/thoughts/suggestions, I'd love to hear them!
AdvThanksance,
-Mark
