[teiid-issues] [JBoss JIRA] Resolved: (TEIID-602) Connecting to server from client fails with SingleInstanceCommunicationException and MMProcess goes into a loop
Steven Hawkins (JIRA)
jira-events at lists.jboss.org
Fri May 15 12:40:58 EDT 2009
[ https://jira.jboss.org/jira/browse/TEIID-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Hawkins resolved TEIID-602.
----------------------------------
Resolution: Done
added checks to prevent child exceptions from reporting their cause as themselves (which shouldn't be happening, but may be coming from an inappropriate override by a third-party). this doesn't prevent more exotic recursive scenarios, but those typically don't happen.
> Connecting to server from client fails with SingleInstanceCommunicationException and MMProcess goes into a loop
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-602
> URL: https://jira.jboss.org/jira/browse/TEIID-602
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 6.0.0
> Environment: Fedora 10, JBEDSP 13 May
> Reporter: Paul Nittel
> Assignee: Steven Hawkins
> Priority: Blocker
> Attachments: pnittel_localdomain_hc.log, SingleInstanceCommunicationException.txt
>
>
> I tried to connect to the server from SQuirreL and, while it appeared to be on its way to success, finally failed with the exception noted above. As I have noted a few times now, the jvm running MMProcess is in a loop, consuming 99+% of the CPU.
> I did a kill -3 and will attach the host controller log to the Jira.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the teiid-issues
mailing list