[
https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu...
]
Paul Richardson commented on TEIIDDES-1971:
-------------------------------------------
Possible solution at
https://github.com/Teiid-Designer/teiid-designer/pull/276
Essentially rather than closing the socket immediately, it uses the connection to get some
data. Testing has shown that the hostname is returned (in my case 'localhost') so
I have logged this then close the connection. More comprehensive testing to determine
whether this is a viable solution.
{code}
socket = new Socket();
socket.connect(endPoint, 1024);
InputStream socketReader = socket.getInputStream();
final char[] buffer = new char[100];
in = new InputStreamReader(socketReader);
int rsz = in.read(buffer, 0, buffer.length);
if (rsz == -1)
return false;
StringBuffer output = new StringBuffer();
for (int i = 0; i < buffer.length; ++i) {
if (Character.isLetterOrDigit(buffer[i])) {
output.append(buffer[i]);
}
}
String message = DqpPlugin.Util.getString("jbossServerHeartBeat",
host, port, output); //$NON-NLS-1$
IStatus status = new Status(IStatus.OK, DqpPlugin.PLUGIN_ID, message);
DqpPlugin.getInstance().getLog().log(status);
{code}
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