August 2009 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-1145) HTTPUnMarshaller shouldn't use the value of content-type to determine the type of an object

by Ron Sigal (JIRA)

HTTPUnMarshaller shouldn't use the value of content-type to determine the type of an object ------------------------------------------------------------------------------------------- Key: JBREM-1145 URL: https://jira.jboss.org/jira/browse/JBREM-1145 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3, 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder), 2.2.3.SP1 org.jboss.remoting.marshal.http.HTTPMarshaller and HTTPUnMarshaller treat Strings as a special case, to avoid the expense of serialization. However, HTTPUnMarshaller is using the metadata value of content-type to determine if an object is a string or not, and. as of JBREM-653 "allow user to set content-type for http responses", that doesn't work. The problem is that the ServerInvocationHandler can set the content-type to, say, text/html, but CoyoteInvoker wraps the result in and InvocationResponse, which gets serialized. On the other side, HTTPUnMarshaller sees "text/html" and tries to read the serialized InvocationResponse as a string. One solution would be for Remoting to use its own metadata key, say "remoting-type" for the purposes of marshaling and unmarshaling. -- 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

15 years, 2 months

1
7
0 / 0

HTTPUnMarshaller ignores the charset of the HTTP request

by Gunther.Olesch＠heagmedianet.de

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1120) Add a socket write timeout facility

by Ron Sigal (JIRA)

Add a socket write timeout facility ----------------------------------- Key: JBREM-1120 URL: https://jira.jboss.org/jira/browse/JBREM-1120 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP11, 2.5.1 (Flounder) Reporter: Ron Sigal Fix For: 2.2.2.SP12, 2.5.2 (Flounder) The timeout parameter of Java sockets applies only to reading. But a write to a bad connection will hang until the underlying TCP implementation detects the problem. A timer that monitors blocked write operations would be useful. -- 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

15 years, 3 months

1
8
0 / 0

[JBoss JIRA] Created: (JBREM-1141) HTTPUnMarshaller should test for "non-text" content-type instead of "binary" content-type

by Ron Sigal (JIRA)

HTTPUnMarshaller should test for "non-text" content-type instead of "binary" content-type ----------------------------------------------------------------------------------------- Key: JBREM-1141 URL: https://jira.jboss.org/jira/browse/JBREM-1141 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3, 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder), 2.2.3.SP1 As an efficiency measure, org.jboss.marshal.http.HTTPUnMarshaller.read() incorporates special handling for strings to avoid serialization. However, there is a flaw in the logic. HTTPUnMarshaller.read() calls isBinaryData() and calls super.read() if the return value is true. If the return value is false, then it processes the input as String data. Originally, this distinction worked because the only two types recognized were org.jboss.remoting..transport.web.WebUtil.HTML ("text/html") and WebUtil.BINARY ("application/octet-stream"). However, JBREM-653 "allow user to set content-type for http responses" allows the introduction of other content types. Instead of testing for "application/octet-stream", HTTPUnMarshaller.read() should treat any content type that starts "text" as a String, and it should treat anything else as an object. -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1148) Remove log.info() calls from ServletServerInvoker

by Ron Sigal (JIRA)

Remove log.info() calls from ServletServerInvoker ------------------------------------------------- Key: JBREM-1148 URL: https://jira.jboss.org/jira/browse/JBREM-1148 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.3.SP1 Two calls to log.info() were inadvertently left in org.jboss.remoting.transport.servlet.ServletServerInvoker. -- 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

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1139) Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT.

by Colin Mondesir (JIRA)

Modify PortUtil to allow a configurable range for MIN_UNPRIVILEGED_PORT and MAX_LEGAL_PORT. ------------------------------------------------------------------------------------------- Key: JBREM-1139 URL: https://jira.jboss.org/jira/browse/JBREM-1139 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP8 Reporter: Colin Mondesir PortUtil could be improved to read the port range configuration. This is straightforward and no side effect is expected. However, PortUtil and its callers will need some refactoring as it is just a static utility classes currently. -- 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

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-1142) Clarify use of "clientConnectAddress" in RemotingGuide

by Ron Sigal (JIRA)

Clarify use of "clientConnectAddress" in RemotingGuide ------------------------------------------------------ Key: JBREM-1142 URL: https://jira.jboss.org/jira/browse/JBREM-1142 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: docs Affects Versions: 2.2.3, 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder), 2.2.3.SP1 The Remoting Guide should spell out the fact that the parameter "clientConnectAddress" is useful only in the context of server side configuration. -- 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

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1077) Fix problem in CompressingMarshaller

by Ron Sigal (JIRA)

Fix problem in CompressingMarshaller ------------------------------------ Key: JBREM-1077 URL: https://jira.jboss.org/jira/browse/JBREM-1077 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 3.0.0.GA In org.jboss.remoting.marshal.compress.CompressingMarshaller.write(), gzos.finish(); oos.flush(); should be oos.flush(); bos.flush(); gzos.flush(); gzos.finish(); as it is on the 2.x branch. -- 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

15 years, 3 months

2
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues August 2009