[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Paul Richardson edited comment on TEIIDDES-1971 at 12/6/13 7:28 AM:
--------------------------------------------------------------------
Noticed that connection reset messages can repeatedly appear when the 'start' server button is clicked in the Server View in eclipse to connect to an external server, ie.
{code}
12:17:58,594 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
12:17:58,595 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 8237ms - Started 524 of 623 services (95 services are passive or on-demand)
12:17:58,716 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40003 VDB MyRESTCustomers.1 is set to ACTIVE
12:18:09,273 ERROR [org.jboss.remoting.remote.connection] (Remoting "goshawk:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
12:18:09,294 ERROR [org.jboss.remoting.remote.connection] (Remoting "goshawk:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
12:18:09,297 ERROR [org.jboss.remoting.remote.connection] (Remoting "goshawk:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
{code}
At 12:17:58 the server is successfully start and I notice the log that everything is quiet. Only when I click the 'start' button in eclipse does the messages at 12:18:09 get appended to the log. Maybe, we are sending to many requests to the server admin port at the same time?
Looking at the packets between the client and server in wireshark, I do see a large number of packets being retransmitted between the client and server. Almost, like they are having to shout and repeat things to each other in order to be heard!
was (Author: phantomjinx):
Noticed that connection reset messages can repeatedly appear when the 'start' server button is clicked in the Server View in eclipse to connect to an external server, ie.
{code}
12:17:58,594 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
12:17:58,595 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 8237ms - Started 524 of 623 services (95 services are passive or on-demand)
12:17:58,716 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40003 VDB MyRESTCustomers.1 is set to ACTIVE
12:18:09,273 ERROR [org.jboss.remoting.remote.connection] (Remoting "goshawk:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
12:18:09,294 ERROR [org.jboss.remoting.remote.connection] (Remoting "goshawk:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
12:18:09,297 ERROR [org.jboss.remoting.remote.connection] (Remoting "goshawk:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
{code}
At 12:17:58 the server is successfully start and I notice the log that everything is quiet. Only when I click the 'start' button in eclipse does the messages at 12:18:09 get appended to the log. Maybe, we are sending to many requests to the server admin port at the same time?
> 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.3
>
> Attachments: 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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1971:
-------------------------------------------
Noticed that connection reset messages can repeatedly appear when the 'start' server button is clicked in the Server View in eclipse to connect to an external server, ie.
{code}
12:17:58,594 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
12:17:58,595 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 8237ms - Started 524 of 623 services (95 services are passive or on-demand)
12:17:58,716 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40003 VDB MyRESTCustomers.1 is set to ACTIVE
12:18:09,273 ERROR [org.jboss.remoting.remote.connection] (Remoting "goshawk:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
12:18:09,294 ERROR [org.jboss.remoting.remote.connection] (Remoting "goshawk:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
12:18:09,297 ERROR [org.jboss.remoting.remote.connection] (Remoting "goshawk:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
{code}
At 12:17:58 the server is successfully start and I notice the log that everything is quiet. Only when I click the 'start' button in eclipse does the messages at 12:18:09 get appended to the log. Maybe, we are sending to many requests to the server admin port at the same time?
> 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.3
>
> Attachments: 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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Paul Richardson updated TEIIDDES-1971:
--------------------------------------
Attachment: server.log
Attached server log showing 3 occurrences of connection reset by peer message
> 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.3
>
> Attachments: 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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Paul Richardson updated TEIIDDES-1971:
--------------------------------------
Summary: Connection Reset by Peer messages appearing in JBoss log (was: No indication that management authentication fails)
> 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.3
>
>
> 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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Paul Richardson updated TEIIDDES-1971:
--------------------------------------
Description:
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.
was:
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.
> 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.3
>
>
> 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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1971) No indication that management authentication fails
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ]
Paul Richardson reopened TEIIDDES-1971:
---------------------------------------
Reopening this issue as I have now encountered these message in the jboss server log. This has nothing to do with an incorrect authentication since my credentials are all correct and I can do all expected activities with the Teiid instance.
Searches on the net show that this may be tied to jdk version being used:
https://issues.jboss.org/browse/AS7-5017
https://issues.jboss.org/browse/AS7-4026
However, I am currently using
{code}
java version "1.7.0_25"
OpenJDK Runtime Environment (fedora-2.3.10.4.fc18-i386)
OpenJDK Server VM (build 23.7-b01, mixed mode)
{code}
The messages do not seem to prevent any functionality from working correctly in Designer so not considering this to be critical. Canvassing for other more expect opinions...
> No indication that management authentication fails
> --------------------------------------------------
>
> 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.3
>
>
> 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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1981) MongoDB issues in Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1981:
----------------------------------------
Teiid's resource adapter connection factory class name = org.teiid.resource.adapter.mongodb.MongoDBManagedConnectionFactory
Eclipse profileID = org.eclipse.birt.data.oda.mongodb
{code:xml}
<extension
id="org.teiid.designer.datatools.profiles.ldap.ConnectionInfoProvider"
name="%mongoDBConnectionInfoProvider"
point="org.teiid.designer.datatools.ConnectionInfoProvider">
<ConnectionInfoProvider
profile="org.eclipse.birt.data.oda.mongodb"
class="org.teiid.designer.datatools.profiles.mongodb.MongoDBConnectionInfoProvider"/>
</extension>
{code}
> MongoDB issues in Designer
> --------------------------
>
> Key: TEIIDDES-1981
> URL: https://issues.jboss.org/browse/TEIIDDES-1981
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.2
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.3
>
> Attachments: MongoCP.xml, plugin.properties, plugin.xml
>
>
> Attempt to model and query MongoDB in Designer
> 1) Mongo CP is not available in default JBDS
> 2) We cannot set the Mongo CP on source model - not supported. We do not have a connectionProvider
--
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
12 years, 4 months
[JBoss JIRA] (TEIIDDES-1981) MongoDB issues in Designer
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-1981:
---------------------------------------
Summary: MongoDB issues in Designer
Key: TEIIDDES-1981
URL: https://issues.jboss.org/browse/TEIIDDES-1981
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.2
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.3
Attempt to model and query MongoDB in Designer
1) Mongo CP is not available in default JBDS
2) We cannot set the Mongo CP on source model - not supported. We do not have a connectionProvider
--
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
12 years, 4 months