]
Steven Hawkins resolved TEIID-503.
----------------------------------
Resolution: Out of Date
Host resolution has changed significantly and also the specification of an invalid vmname
will result in an error.
startHost( badHostName ) causes MMProcess to loop, trying to ping bad
host name
-------------------------------------------------------------------------------
Key: TEIID-503
URL:
https://jira.jboss.org/jira/browse/TEIID-503
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 6.0.0
Environment: fedora 10, 553GA
Reporter: Paul Nittel
Fix For: 6.1.1
Persistence is a virtue, but not when it comes to computers. ;-)
I created a test for mmadmin which tried to start a host with a bad name. (I figured it
would give me an error and the test could proceed from there.) What happened was the test
didn't end in a reasonable time, but the server's process log was growing. Turns
out it was filling with these:
Mar 13, 2009 09:34:00.650 [SocketWorkerQueue_Worker_357|0] ERROR
<com.metamatrix.platform|0> Unable to ping bindaddress: CCEtest
Mar 13, 2009 09:34:00.650 [SocketWorkerQueue_Worker_357|0] ERROR
<com.metamatrix.platform|0> Unable to ping bindaddress: CCEtest
Mar 13, 2009 09:34:00.650 [SocketWorkerQueue_Worker_357|0] ERROR
<com.metamatrix.platform|0> Unable to ping bindaddress: CCEtest
Offhand, I'd say one would be sufficient.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: