Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Agent.log reports java.net.SocketTimeoutException: Accept timed out every second in DEBUG

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 4.6
  • Fix Version/s: 4.6, 4.x Sprint 28
  • Component/s: Agent / PDK
  • Environment:
    Hyperic server daily build 4.6.0-EE-249 on Solaris 10 SPARC with embedded Postgres DB
    Hyperic agent 4.6.0-EE-251 on HP-UX 11.11
  • Case Links:
    none
  • Regression:
    No
  • Story Points:
    2
  • Tags:

Description

Agent.log reports java.net.SocketTimeoutException: Accept timed out every second in DEBUG

With agent.logLevel=DEBG set in agent.properties, the agent.log scrolls the following message every 1 second:

2011-07-25 10:43:29,812 DEBUG [AgentDaemonMain] [SSLConnectionListener] java.net.SocketTimeoutException: Accept timed out
        at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.java:259)
        at org.hyperic.hq.bizapp.agent.server.SSLConnectionListener.getNewConnection(SSLConnectionListener.java:167)

This appears to be new from post 7/23/11 build.

Expected Result:
No erroneous messages in agent.log

Actual Result:
Reported error message posted every 1 second in agent.log

Steps to Reproduce:

  1. Install Hyperic agent on any platform
  2. Set agent.logLevel=DEBUG in agent.properties
  3. Start agent
  4. Tail agent.log
  5. Note reported exception message every 1 second

Activity

Hide
Scott Feldstein added a comment -

log was harmless, it is expected behavior. The big problem was that there are two places where this could happen in the same try/catch block, this particular message was expected and the other is an error that is handled gracefully.

Show
Scott Feldstein added a comment - log was harmless, it is expected behavior. The big problem was that there are two places where this could happen in the same try/catch block, this particular message was expected and the other is an error that is handled gracefully.
Hide
Frederic Calindas added a comment -

Verified with Hyperic Agent Daily Build 4.6.0-EE-252 (7/26/11).

With earlier 4.5.0-EE-251 agent running on HP-UX 11.11, tailing the agent.log showed the repeated error message.

After upgrading the agent to 4.5.0-EE-252, the agent.log no longer repeated the error message every second.

Show
Frederic Calindas added a comment - Verified with Hyperic Agent Daily Build 4.6.0-EE-252 (7/26/11). With earlier 4.5.0-EE-251 agent running on HP-UX 11.11, tailing the agent.log showed the repeated error message. After upgrading the agent to 4.5.0-EE-252, the agent.log no longer repeated the error message every second.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    2 years, 38 weeks, 6 days ago