January 2017 - jboss-remoting-issues

[JBoss JIRA] (JBREM-1337) server uses IP instead of localhost when client is in same box

by Tony Fan (JIRA)

[ https://issues.jboss.org/browse/JBREM-1337?page=com.atlassian.jira.plugin... ] Tony Fan updated JBREM-1337: ---------------------------- Environment: Linux Fedora 9 jboss AS 5 remoting package v2.5.4.SP5 was: Linux Fedora 9 jboss AS 5 > server uses IP instead of localhost when client is in same box > -------------------------------------------------------------- > > Key: JBREM-1337 > URL: https://issues.jboss.org/browse/JBREM-1337 > Project: JBoss Remoting > Issue Type: Bug > Components: callbacks > Affects Versions: 2.5.4.SP5 > Environment: Linux Fedora 9 > jboss AS 5 > remoting package v2.5.4.SP5 > Reporter: Tony Fan > Labels: reported-by-qe > > We have a standalone Swing UI app runs on same box as jboss running, UI make EJB call through Jboss remoting framework, since UI is using localhost to make a call, when the box has network issue we often see this Socket timed out and InvokerLocator was using real IP instead of localhost in UI log: > Caused by: org.jboss.remoting.InvocationFailureException: Socket timed out. Waited 75000 milliseconds for response while calling on InvokerLocator [sslsocket://192.168.3.86:4446/?clientMaxPoolSize=75&dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketFactoryClassName=com.ilrd.gem.plaf.util.rmi.ClientSSLSocketFactory&timeout=75000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]; nested exception is: java.net.SocketTimeoutException: Read timed out > ----------------------------------------------------------------------------------------------------------------- > The JBoss Reoting guide article mentios that: > The InvokerLocator will accept host name as is and will not automatically convert to IP address (since 2.0.0 release) > http://docs.jboss.org/jbossremoting/docs/guide/2.5/html_single/ > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1337) server uses IP instead of localhost when client is in same box

by Tony Fan (JIRA)

[ https://issues.jboss.org/browse/JBREM-1337?page=com.atlassian.jira.plugin... ] Tony Fan updated JBREM-1337: ---------------------------- Issue Type: Bug (was: Task) > server uses IP instead of localhost when client is in same box > -------------------------------------------------------------- > > Key: JBREM-1337 > URL: https://issues.jboss.org/browse/JBREM-1337 > Project: JBoss Remoting > Issue Type: Bug > Components: callbacks > Affects Versions: 2.5.4.SP5 > Environment: Linux Fedora 9 > jboss AS 5 > Reporter: Tony Fan > Labels: reported-by-qe > > We have a standalone Swing UI app runs on same box as jboss running, UI make EJB call through Jboss remoting framework, since UI is using localhost to make a call, when the box has network issue we often see this Socket timed out and InvokerLocator was using real IP instead of localhost in UI log: > Caused by: org.jboss.remoting.InvocationFailureException: Socket timed out. Waited 75000 milliseconds for response while calling on InvokerLocator [sslsocket://192.168.3.86:4446/?clientMaxPoolSize=75&dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketFactoryClassName=com.ilrd.gem.plaf.util.rmi.ClientSSLSocketFactory&timeout=75000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]; nested exception is: java.net.SocketTimeoutException: Read timed out > ----------------------------------------------------------------------------------------------------------------- > The JBoss Reoting guide article mentios that: > The InvokerLocator will accept host name as is and will not automatically convert to IP address (since 2.0.0 release) > http://docs.jboss.org/jbossremoting/docs/guide/2.5/html_single/ > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1337) server uses IP instead of localhost when client is in same box

by Tony Fan (JIRA)

Tony Fan created JBREM-1337: ------------------------------- Summary: server uses IP instead of localhost when client is in same box Key: JBREM-1337 URL: https://issues.jboss.org/browse/JBREM-1337 Project: JBoss Remoting Issue Type: Task Components: callbacks Affects Versions: 2.5.4.SP5 Environment: Linux Fedora 9 jboss AS 5 Reporter: Tony Fan We have a standalone Swing UI app runs on same box as jboss running, UI make EJB call through Jboss remoting framework, since UI is using localhost to make a call, when the box has network issue we often see this Socket timed out and InvokerLocator was using real IP instead of localhost in UI log: Caused by: org.jboss.remoting.InvocationFailureException: Socket timed out. Waited 75000 milliseconds for response while calling on InvokerLocator [sslsocket://192.168.3.86:4446/?clientMaxPoolSize=75&dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketFactoryClassName=com.ilrd.gem.plaf.util.rmi.ClientSSLSocketFactory&timeout=75000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]; nested exception is: java.net.SocketTimeoutException: Read timed out ----------------------------------------------------------------------------------------------------------------- The JBoss Reoting guide article mentios that: The InvokerLocator will accept host name as is and will not automatically convert to IP address (since 2.0.0 release) http://docs.jboss.org/jbossremoting/docs/guide/2.5/html_single/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1336) [GSS](7.0.x) Authentication via remoting fail for larger requests i.e. long password

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created JBREM-1336: --------------------------------------- Summary: [GSS](7.0.x) Authentication via remoting fail for larger requests i.e. long password Key: JBREM-1336 URL: https://issues.jboss.org/browse/JBREM-1336 Project: JBoss Remoting Issue Type: Bug Components: general, security Reporter: Wolf-Dieter Fink Assignee: David Lloyd If the client use authentication and the passwords is really long, the SASL request or kerberos ticket is huge the attempt will fail. In the same environment authentication for other users work correct. The shown message within the server log is TRACE [org.jboss.remoting.remote.connection handleEvent] (Remoting "gravity" read-1) Connection error detail: java.io.IOException: Received an invalid message length of 11857 at org.xnio.channels.FramedMessageChannel.receive(FramedMessageChannel.java:106) [xnio-api-3.0.15.GA.jar:3.0.15.GA] at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:229) [jboss-remoting-3.3.6.Final.jar:3.3.6.Final] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1335) Authentication via remoting fail for larger requests i.e. long password

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/JBREM-1335?page=com.atlassian.jira.plugin... ] Wolf-Dieter Fink reassigned JBREM-1335: --------------------------------------- Assignee: David Lloyd > Authentication via remoting fail for larger requests i.e. long password > ----------------------------------------------------------------------- > > Key: JBREM-1335 > URL: https://issues.jboss.org/browse/JBREM-1335 > Project: JBoss Remoting > Issue Type: Bug > Components: general, security > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > > If the client use authentication and the passwords is really long, the SASL request or kerberos ticket is huge the attempt will fail. > In the same environment authentication for other users work correct. > The shown message within the server log is > TRACE [org.jboss.remoting.remote.connection handleEvent] (Remoting "gravity" read-1) Connection error detail: java.io.IOException: Received an invalid message length of 11857 > at org.xnio.channels.FramedMessageChannel.receive(FramedMessageChannel.java:106) [xnio-api-3.0.15.GA.jar:3.0.15.GA] > at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:229) [jboss-remoting-3.3.6.Final.jar:3.3.6.Final] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1335) Authentication via remoting fail for larger requests i.e. long password

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created JBREM-1335: --------------------------------------- Summary: Authentication via remoting fail for larger requests i.e. long password Key: JBREM-1335 URL: https://issues.jboss.org/browse/JBREM-1335 Project: JBoss Remoting Issue Type: Bug Components: general, security Reporter: Wolf-Dieter Fink If the client use authentication and the passwords is really long, the SASL request or kerberos ticket is huge the attempt will fail. In the same environment authentication for other users work correct. The shown message within the server log is TRACE [org.jboss.remoting.remote.connection handleEvent] (Remoting "gravity" read-1) Connection error detail: java.io.IOException: Received an invalid message length of 11857 at org.xnio.channels.FramedMessageChannel.receive(FramedMessageChannel.java:106) [xnio-api-3.0.15.GA.jar:3.0.15.GA] at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:229) [jboss-remoting-3.3.6.Final.jar:3.3.6.Final] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues January 2017