[
https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu...
]
Paul Richardson commented on TEIIDDES-1971:
-------------------------------------------
Confirmed [~burrsutter]'s test conditions.
A vanilla eap6 server is all that is required to create the error message in the log.
Therefore, it IS a client / Designer / Teiid Tooling issue.
Investigating this morning, I tentatively think I have pinned it down to
JBossServerUtil.isHostConnected(). This tests generically whether a server is available on
the given host and port (host being your eap6 server and port being the admin port).
The method does this:
{code}
try {
socket = new Socket();
// Comment out the line below
socket.connect(endPoint, 0);
return true;
} catch (Exception ex) {
ex.printStackTrace();
return false;
} finally {
try {
if (socket != null && socket.isConnected()) {
socket.close();
socket = null;
}
} catch (Exception ex2) {
ex2.printStackTrace();
}
}
{code}
I think that due to the frequency this can be called, eg. its called 3 times when the
server start button is clicked, its banging the server too quickly in that its saying
server.connect() then server.close() immediately and I wonder whether the server is
'running out of breath' to respond hence the error messages server-side (not
client-side).
[~blafond], [~mdrillin], can you try repeating the following test:
1) Start vanilla eap6 (no teiid)
2) Open Designer
3) Start server in Server View
4) Review error log, confirming existence of error messages.
5) Quit Designer
6) Restart server - *** important as I think the socket connections are cached and timeout
related so error messages don't always appear straight away.
7) Comment out connect line shown above and repeat 1-4 and confirm no error messages.
8) Repeat lots of times to get a firm idea that this is the problem!!
Connection Reset by Peer messages appearing in JBoss log
--------------------------------------------------------
Key: TEIIDDES-1971
URL:
https://issues.jboss.org/browse/TEIIDDES-1971
Project: Teiid Designer
Issue Type: Bug
Reporter: Steven Hawkins
Assignee: Paul Richardson
Priority: Critical
Fix For: 8.4
Attachments: retransmission-packet.png, server.log
Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually
defining a server -and using an incorrect management password- results in a console log
entry:
14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..."
read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by
peer
On server startup without any indication of what it means.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira