November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBREM-1316) MicroSocketClientInvoker can could lead to a remote ejb being sent data twice to the same server

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1316?page=com.atlassian.jira.plugin... ] Ron Sigal resolved JBREM-1316. ------------------------------ Resolution: Done > MicroSocketClientInvoker can could lead to a remote ejb being sent data twice to the same server > ------------------------------------------------------------------------------------------------ > > Key: JBREM-1316 > URL: https://issues.jboss.org/browse/JBREM-1316 > Project: JBoss Remoting > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 2.5.4.SP4 > Reporter: Shaun Appleton > Assignee: Ron Sigal > Fix For: 2.5.4.SP5 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1316) MicroSocketClientInvoker can could lead to a remote ejb being sent data twice to the same server

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1316?page=com.atlassian.jira.plugin... ] Ron Sigal closed JBREM-1316. ---------------------------- > MicroSocketClientInvoker can could lead to a remote ejb being sent data twice to the same server > ------------------------------------------------------------------------------------------------ > > Key: JBREM-1316 > URL: https://issues.jboss.org/browse/JBREM-1316 > Project: JBoss Remoting > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 2.5.4.SP4 > Reporter: Shaun Appleton > Assignee: Ron Sigal > Fix For: 2.5.4.SP5 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1316) MicroSocketClientInvoker can could lead to a remote ejb being sent data twice to the same server

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1316?page=com.atlassian.jira.plugin... ] Ron Sigal updated JBREM-1316: ----------------------------- Issue Type: Enhancement (was: Bug) > MicroSocketClientInvoker can could lead to a remote ejb being sent data twice to the same server > ------------------------------------------------------------------------------------------------ > > Key: JBREM-1316 > URL: https://issues.jboss.org/browse/JBREM-1316 > Project: JBoss Remoting > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 2.5.4.SP4 > Reporter: Shaun Appleton > Assignee: Ron Sigal > Fix For: 2.5.4.SP5 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1322) Cannot set up serverBindAddress for secondarySocket in bisocket transport

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1322?page=com.atlassian.jira.plugin... ] Ron Sigal updated JBREM-1322: ----------------------------- Fix Version/s: (was: 2.5.4.SP5) > Cannot set up serverBindAddress for secondarySocket in bisocket transport > ------------------------------------------------------------------------- > > Key: JBREM-1322 > URL: https://issues.jboss.org/browse/JBREM-1322 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: transport > Affects Versions: 2.5.4.SP4 > Reporter: Igor Kostromin > Assignee: Ron Sigal > > Using IS_CALLBACK_SERVER = true. > In BisocketClientInvoker.java:355 > InvokerLocator getSecondaryLocator() throws Throwable { > ... > 355: Object o = invoke(r); > ... > } > It retrieves host from server, but if you want to use original client invoker host, you cannot do this (it is necessary if server is behind translating firewall). If you want to do this, you have to patch this code manually to > Object o = invoke(r); > // DZ: patch to use original server address for creating secondary connection > // instead of address retrieved from server (because server will return jboss bind address > // that can be local address, inaccessible from client) > InvokerLocator patchedLocator = new InvokerLocator( (( InvokerLocator ) o).getOriginalURI().replace( > (( InvokerLocator ) o).getHost(), this.getLocator().getHost() ) > ); > log.debug("secondary locator: " + o); > log.debug("patched secondary locator: " + patchedLocator); > return patchedLocator; > and rebuild jboss-remoting project. > For ports there are settings SECONDARY_BIND_PORT, SECONDARY_CONNECT_PORT allowing to set up them as you want. For address there is no one to do this. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1316) MicroSocketClientInvoker can could lead to a remote ejb being sent data twice to the same server

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1316?page=com.atlassian.jira.plugin... ] Ron Sigal reopened JBREM-1316: ------------------------------ > MicroSocketClientInvoker can could lead to a remote ejb being sent data twice to the same server > ------------------------------------------------------------------------------------------------ > > Key: JBREM-1316 > URL: https://issues.jboss.org/browse/JBREM-1316 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.5.4.SP4 > Reporter: Shaun Appleton > Assignee: Ron Sigal > Fix For: 2.5.4.SP5 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1325) Release 2.5.4.SP5

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1325?page=com.atlassian.jira.plugin... ] Ron Sigal updated JBREM-1325: ----------------------------- Fix Version/s: 2.5.4.SP5 > Release 2.5.4.SP5 > ----------------- > > Key: JBREM-1325 > URL: https://issues.jboss.org/browse/JBREM-1325 > Project: JBoss Remoting > Issue Type: Release > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assignee: Ron Sigal > Fix For: 2.5.4.SP5 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBREM-1318) Zero is a valid value so SoLinger

by Ron Sigal (JIRA)

[ https://issues.jboss.org/browse/JBREM-1318?page=com.atlassian.jira.plugin... ] Ron Sigal updated JBREM-1318: ----------------------------- Fix Version/s: 2.5.4.SP5 Affects Version/s: 2.5.4.SP4 (was: 2.5.4.SP3) > Zero is a valid value so SoLinger > --------------------------------- > > Key: JBREM-1318 > URL: https://issues.jboss.org/browse/JBREM-1318 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.5.4.SP4 > Reporter: Doug Grove > Priority: Minor > Fix For: 2.5.4.SP5 > > > MicroSocketClientInvoker checks to see that SoLinger is greater than zero: > if (soLingerSet && > soLingerDuration > 0) s.setSoLinger(soLinger, soLingerDuration); > Zero is a valid value for SoLinger. > The code should be changed to greater than or equal to zero. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1970) Make mod_cluster status interval configurable

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1970?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-1970: --------------------------------- Summary: Make mod_cluster status interval configurable (was: Make mod_cluster status configurable) > Make mod_cluster status interval configurable > --------------------------------------------- > > Key: WFLY-1970 > URL: https://issues.jboss.org/browse/WFLY-1970 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Alpha4 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > There is a TODO in UndertowEventHandlerAdapter.start(StartContext) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-331) PropagationContext getting lost

by Mark Proctor (JIRA)

Mark Proctor created DROOLS-331: ----------------------------------- Summary: PropagationContext getting lost Key: DROOLS-331 URL: https://issues.jboss.org/browse/DROOLS-331 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor Rules are not obeying no-loop, where the root node, after the lian, are eval, not and exists. This is because the parent chain skips nodes. We need to not skip nodes in the reference chain, and instead skip during iteration. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-372) Use ServiceLoader to locate mod_cluster custom load metrics

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-372?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated WFLY-372: -------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) > Use ServiceLoader to locate mod_cluster custom load metrics > ----------------------------------------------------------- > > Key: WFLY-372 > URL: https://issues.jboss.org/browse/WFLY-372 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR1 > > > Solves the problem of having to identify load metrics by class names. -- 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, 6 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 November 2013