Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

JMX connection failures

Description

The problem is indicative of the RMI naming service refusing requests due to too many connects. I will
attach logs.

Environment

Operating System: All Platform: All

Acceptance / Success Criteria

None

Attachments

5

Lucidchart Diagrams

Activity

Show:

Seth Leger August 4, 2011 at 10:45 AM

No further feedback about the issue, resolving.

Benjamin Reed October 3, 2008 at 1:57 PM

is this still an issue?

David Hustace October 19, 2005 at 2:48 PM

Mike, looks to us like everything is getting closed properly in the code you submitted. I'm having the user
eliminate all but one of the 17 JMX services using the JBossMonitor class to see if the problem disipates.
When there is only one service being monitored on the 3 app servers.

David Hustace October 19, 2005 at 11:53 AM

Created an attachment (id=249)
netstat and lsof output, logs, and configs.

David Hustace October 19, 2005 at 11:53 AM

Created an attachment (id=248)
netstat and lsof output, logs, and configs.

Incomplete

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created October 19, 2005 at 11:47 AM
Updated August 4, 2011 at 10:45 AM
Resolved August 4, 2011 at 10:45 AM