January 2017 - jboss-jira - Jboss List Archives

[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)

9 years, 3 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)

9 years, 3 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)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2229) Create serverside operations to redeploy deployments affected by an overlay

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2229?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-2229: -------------------------------------- Summary: Create serverside operations to redeploy deployments affected by an overlay (was: Create serverside operations to redploy deployments affected by an overlay) > Create serverside operations to redeploy deployments affected by an overlay > --------------------------------------------------------------------------- > > Key: WFCORE-2229 > URL: https://issues.jboss.org/browse/WFCORE-2229 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 3.0.0.Alpha22 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > A deployment-overlay resource must certainly have a "redeploy-affected" operation where it works out the set of affected deployments and adds steps to redeploy them. The full set of deployments, their runtime names, and their enabled status would all be available to the handler for such an operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2229) Create serverside operations to redploy deployments affected by an overlay

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-2229: ----------------------------------------- Summary: Create serverside operations to redploy deployments affected by an overlay Key: WFCORE-2229 URL: https://issues.jboss.org/browse/WFCORE-2229 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Affects Versions: 3.0.0.Alpha22 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet A deployment-overlay resource must certainly have a "redeploy-affected" operation where it works out the set of affected deployments and adds steps to redeploy them. The full set of deployments, their runtime names, and their enabled status would all be available to the handler for such an operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-5) Initial setup for the build infrastructure

by Luis Barreiro (JIRA)

Luis Barreiro created AG-5: ------------------------------ Summary: Initial setup for the build infrastructure Key: AG-5 URL: https://issues.jboss.org/browse/AG-5 Project: Agroal Issue Type: Task Components: build Affects Versions: 0.0.0 Reporter: Luis Barreiro Assignee: Luis Barreiro Choose a build tool and do it's initial setup -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-4) Choose a license for the project

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-4?page=com.atlassian.jira.plugin.syste... ] Luis Barreiro resolved AG-4. ---------------------------- Fix Version/s: 0.0.1 Resolution: Done > Choose a license for the project > -------------------------------- > > Key: AG-4 > URL: https://issues.jboss.org/browse/AG-4 > Project: Agroal > Issue Type: Task > Components: infrastructure > Affects Versions: 0.0.0 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.0.1 > > > The project must have a License that governs the use and redistribution of the software -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7956) Coverity static analysis: Performace optimalization in map iterating

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7956?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFLY-7956: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Coverity static analysis: Performace optimalization in map iterating > -------------------------------------------------------------------- > > Key: WFLY-7956 > URL: https://issues.jboss.org/browse/WFLY-7956 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Minor > > Coverity static analysis found iterating over map can be enhanced > https://scan7.coverity.com/reports.htm#v23632/p12664/fileInstanceId=84867... > Instead of Map.keySet() + Map.get() combo use just Map.entrySet(). > > {code:java|title=ElytronHttpExchange#getRequestParameters} > for (String name : queryParameters.keySet()) { > List<String> values = new ArrayList<>(queryParameters.get(name)); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7956) Coverity static analysis: Performace optimalization in map iterating

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7956?page=com.atlassian.jira.plugin.... ] Martin Choma reassigned WFLY-7956: ---------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Coverity static analysis: Performace optimalization in map iterating > -------------------------------------------------------------------- > > Key: WFLY-7956 > URL: https://issues.jboss.org/browse/WFLY-7956 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Priority: Minor > > Coverity static analysis found iterating over map can be enhanced > https://scan7.coverity.com/reports.htm#v23632/p12664/fileInstanceId=84867... > Instead of Map.keySet() + Map.get() combo use just Map.entrySet(). > > {code:java|title=ElytronHttpExchange#getRequestParameters} > for (String name : queryParameters.keySet()) { > List<String> values = new ArrayList<>(queryParameters.get(name)); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7956) Coverity static analysis: Performace optimalization in map iterating

by Martin Choma (JIRA)

Martin Choma created WFLY-7956: ---------------------------------- Summary: Coverity static analysis: Performace optimalization in map iterating Key: WFLY-7956 URL: https://issues.jboss.org/browse/WFLY-7956 Project: WildFly Issue Type: Bug Components: Security Reporter: Martin Choma Assignee: Darran Lofthouse Priority: Minor Coverity static analysis found iterating over map can be enhanced https://scan7.coverity.com/reports.htm#v23632/p12664/fileInstanceId=84867... Instead of Map.keySet() + Map.get() combo use just Map.entrySet(). {code:java|title=ElytronHttpExchange#getRequestParameters} for (String name : queryParameters.keySet()) { List<String> values = new ArrayList<>(queryParameters.get(name)); {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2017