December 2009 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-1166) Possible race condition in ConnectionValidator

by Takayoshi Kimura (JIRA)

Possible race condition in ConnectionValidator ---------------------------------------------- Key: JBREM-1166 URL: https://jira.jboss.org/jira/browse/JBREM-1166 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3.SP1, 2.2.3 Reporter: Takayoshi Kimura Fix For: 2.2.3.SP2 The 2.2.3 has a minor regression. The ConnectionValidator#start() has been moved outside of synchronized block in this release, this leads a race condition problem. ConnectionValidator#start(): TimerUtil.schedule(this, pingPeriod); // will call ConnectionValidator.run() timer = new Timer(true); // is used in ConnectionValidator.run() These 2 lines looks odd, because it initializes the timer for new thread after spawn the thread. In 2.2.2-SP11 the timer variable is protected by synchronized blocks, so it's not the case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (JBREM-1162) Release 2.5.2.SP1

by Ron Sigal (JIRA)

Release 2.5.2.SP1 ----------------- Key: JBREM-1162 URL: https://jira.jboss.org/jira/browse/JBREM-1162 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2.SP1 (Flounder) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1173) Assure version compatibility with earlier versions of Remoting

by Ron Sigal (JIRA)

Assure version compatibility with earlier versions of Remoting -------------------------------------------------------------- Key: JBREM-1173 URL: https://jira.jboss.org/jira/browse/JBREM-1173 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
3
0 / 0

[JBoss JIRA] Closed: (JBREM-904) Remoting 1/2 protocol compatibility

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-904?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-904. ----------------------------- Resolution: Won't Fix Not a requirement of AS. > Remoting 1/2 protocol compatibility > ----------------------------------- > > Key: JBREM-904 > URL: https://jira.jboss.org/jira/browse/JBREM-904 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 r2 compatibility > Reporter: David Lloyd > Fix For: 3.1.0.Beta1 > > > A protocol compatibility layer needs to be developed that allows a Remoting 3 server to respond to a Remoting 1/2 request, and also that allows a Remoting 3 client to connect to a Remoting 1/2 server. This will be required before integration with AS5 can be considered. > Another item worth exploration is looking into providing a Remoting 1/2 compatibilty API that allows legacy applications to use the newer transports. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1096) Remoting 2 entity metadata

by David Lloyd (JIRA)

Remoting 2 entity metadata -------------------------- Key: JBREM-1096 URL: https://jira.jboss.org/jira/browse/JBREM-1096 Project: JBoss Remoting Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1153) Malformed Method line in HTTP requests thru HTTP Proxy

by Gerald Turner (JIRA)

Malformed Method line in HTTP requests thru HTTP Proxy ------------------------------------------------------ Key: JBREM-1153 URL: https://jira.jboss.org/jira/browse/JBREM-1153 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.2.SP8 Environment: JBoss 4.2.3.GA patched with JBossWS 3.0.5 Reporter: Gerald Turner Attachments: jbossws-noproxy.cap, jbossws-proxy.cap Invoking a web service with http.proxyHost and http.proxyPort System properties is broken. It produces a request like the following: POST http://btnwks10.corp.inthosts.net:9090/HVODWebService/Import HTTP/1.1 Authorization: Basic b5V0am91bmR5ZbN0ZXI6bH5cdW9yT3Aw SOAPAction: "" Content-Type: text/xml; charset=UTF-8 JBoss-Remoting-Version: 22 User-Agent: JBossRemoting - 2.2.2.SP8 Host: btnwks10.corp.inthosts.net:9090 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Proxy-Connection: keep-alive Transfer-Encoding: chunked With the System properties removed, the request is sent correctly: POST /HVODWebService/Import HTTP/1.1 Authorization: Basic b5V0am91bmR5ZbN0ZXI6bH5cdW9yT3Aw SOAPAction: "" Content-Type: text/xml; charset=UTF-8 JBoss-Remoting-Version: 22 User-Agent: JBossRemoting - 2.2.2.SP8 Host: btnwks10.corp.inthosts.net:9090 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Transfer-Encoding: chunked Bug appears to be exactly as described in JBREM-569, however that bug claims to have been fixed in 2.0.0.GA, maybe a regression occurred? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (JBREM-1160) CLONE -Version compatibility problem with leasing

by Ron Sigal (JIRA)

CLONE -Version compatibility problem with leasing ------------------------------------------------- Key: JBREM-1160 URL: https://jira.jboss.org/jira/browse/JBREM-1160 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder) If "useClientConnectionIdentity" is set to "true, then org.jboss.remoting.ServerInvoker.updateClientLease() tries to get a leasePingerId from the request map and compare it to the leasePingerId in a Lease. But if the InvocationRequest came from an older client that doesn't know about connection identity, the value of leasePingerId is null. The test calls leasePingerId.equals(clientLease.getLeasePingerId() which causes a NullPointerException. The test should be reversed. Also, org.jboss.test.remoting.versioning.lease.LeaseVersionTestCase should be strengthened to catch this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-998) JBoss Serailization 1.0.3 does not work. Make sure a new Serializtion jar gets sent out with this fix with remoting.

by Jay Howell (JIRA)

JBoss Serailization 1.0.3 does not work. Make sure a new Serializtion jar gets sent out with this fix with remoting. --------------------------------------------------------------------------------------------------------------------- Key: JBREM-998 URL: http://jira.jboss.com/jira/browse/JBREM-998 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: serialization Affects Versions: 2.2.2.SP7 Reporter: Jay Howell Priority: Critical Jboss serialization is broken. We need to make sure that we fix http://jira.jboss.org/jira/browse/JBSER-108 and it gets out with future versions of remoting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues December 2009