[JBoss JIRA] Created: (JBWS-1704) The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests
4:02 a.m.
The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All
Requests
----------------------------------------------------------------------------------------
Key: JBWS-1704
URL: http://jira.jboss.com/jira/browse/JBWS-1704
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.2.1
Reporter: Darran Lofthouse
Fix For: jbossws-2.1.0
The use of JBoss Remoting causes a datatype parameter to be sent with all outgoing
requests, this parameter is not required by the server and can cause problems as some
loadbalancers reject the message.
The reason for this is because of a workaround required in JBoss Remoting 1.4.5 to
register the marshaller. See the createRemotingClient method: -
http://anonsvn.jboss.org/repos/jbossws/tags/jbossws-1.2.1.GA/jbossws-core...
It is possible to check the Remoting version using the following method: -
public static int getDefaultVersion()
From 'org.jboss.remoting.Version', a possible solution will be
to check the version to decide if we need to register the marshaller in this way.
--
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
4:02 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1704) The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests
[ http://jira.jboss.com/jira/browse/JBWS-1704?page=all ]
Darran Lofthouse updated JBWS-1704:
-----------------------------------
Component/s: jbossws-jaxrpc
The Use Of Remoting Causes An Additional 'datatype' Parameter
To Be Sent On All Requests
----------------------------------------------------------------------------------------
Key: JBWS-1704
URL: http://jira.jboss.com/jira/browse/JBWS-1704
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-jaxrpc
Affects Versions: jbossws-1.2.1
Reporter: Darran Lofthouse
Fix For: jbossws-2.1.0
The use of JBoss Remoting causes a datatype parameter to be sent with all outgoing
requests, this parameter is not required by the server and can cause problems as some
loadbalancers reject the message.
The reason for this is because of a workaround required in JBoss Remoting 1.4.5 to
register the marshaller. See the createRemotingClient method: -
http://anonsvn.jboss.org/repos/jbossws/tags/jbossws-1.2.1.GA/jbossws-core...
It is possible to check the Remoting version using the following method: -
public static int getDefaultVersion()
From 'org.jboss.remoting.Version', a possible solution will be to check the
version to decide if we need to register the marshaller in this way.
--
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
3:55 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-1704) The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests
[ http://jira.jboss.com/jira/browse/JBWS-1704?page=comments#action_12368166 ]
Alessio Soldano commented on JBWS-1704:
---------------------------------------
Typo
* I think this shouldn't be a problem, since ...
The Use Of Remoting Causes An Additional 'datatype' Parameter
To Be Sent On All Requests
----------------------------------------------------------------------------------------
Key: JBWS-1704
URL: http://jira.jboss.com/jira/browse/JBWS-1704
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-jaxrpc
Affects Versions: jbossws-1.2.1
Reporter: Darran Lofthouse
Assigned To: Alessio Soldano
Fix For: jbossws-2.1.0
The use of JBoss Remoting causes a datatype parameter to be sent with all outgoing
requests, this parameter is not required by the server and can cause problems as some
loadbalancers reject the message.
The reason for this is because of a workaround required in JBoss Remoting 1.4.5 to
register the marshaller. See the createRemotingClient method: -
http://anonsvn.jboss.org/repos/jbossws/tags/jbossws-1.2.1.GA/jbossws-core...
It is possible to check the Remoting version using the following method: -
public static int getDefaultVersion()
From 'org.jboss.remoting.Version', a possible solution will be to check the
version to decide if we need to register the marshaller in this way.
--
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
3:55 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-1704) The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests
[ http://jira.jboss.com/jira/browse/JBWS-1704?page=comments#action_12368165 ]
Alessio Soldano commented on JBWS-1704:
---------------------------------------
public static int getDefaultVersion() didn't exist in org.jboss.remoting.Version
version <= 1.4.6 thus the check could fail.
Anyway I think this is should be a problem, since we are not going to use those old
versions any more, don't we? (currently shipped version in thirdparty is 2.2.0).
I'll commit the fix on maeste_palin branch, removing registration of
marshaller/unmarshaller into the MarshallFactory that is no longer required.
The Use Of Remoting Causes An Additional 'datatype' Parameter
To Be Sent On All Requests
----------------------------------------------------------------------------------------
Key: JBWS-1704
URL: http://jira.jboss.com/jira/browse/JBWS-1704
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-jaxrpc
Affects Versions: jbossws-1.2.1
Reporter: Darran Lofthouse
Assigned To: Alessio Soldano
Fix For: jbossws-2.1.0
The use of JBoss Remoting causes a datatype parameter to be sent with all outgoing
requests, this parameter is not required by the server and can cause problems as some
loadbalancers reject the message.
The reason for this is because of a workaround required in JBoss Remoting 1.4.5 to
register the marshaller. See the createRemotingClient method: -
http://anonsvn.jboss.org/repos/jbossws/tags/jbossws-1.2.1.GA/jbossws-core...
It is possible to check the Remoting version using the following method: -
public static int getDefaultVersion()
From 'org.jboss.remoting.Version', a possible solution will be to check the
version to decide if we need to register the marshaller in this way.
--
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
6:24 a.m.
New subject: [JBoss JIRA] Reopened: (JBWS-1704) The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests
[ http://jira.jboss.com/jira/browse/JBWS-1704?page=all ]
Thomas Diesler reopened JBWS-1704:
----------------------------------
This change causes intermittent failures with jboss-4.0.5.GA, which uses
remoting-1.4.3.GA
Caused by: java.io.NotSerializableException: org.jboss.ws.core.soap.SOAPMessageImpl
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at org.jboss.remoting.marshal.http.HTTPMarshaller.write(HTTPMarshaller.java:69)
at
org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:164)
The Use Of Remoting Causes An Additional 'datatype' Parameter
To Be Sent On All Requests
----------------------------------------------------------------------------------------
Key: JBWS-1704
URL: http://jira.jboss.com/jira/browse/JBWS-1704
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-jaxrpc
Affects Versions: jbossws-1.2.1
Reporter: Darran Lofthouse
Assigned To: Alessio Soldano
Fix For: jbossws-2.1.0
The use of JBoss Remoting causes a datatype parameter to be sent with all outgoing
requests, this parameter is not required by the server and can cause problems as some
loadbalancers reject the message.
The reason for this is because of a workaround required in JBoss Remoting 1.4.5 to
register the marshaller. See the createRemotingClient method: -
http://anonsvn.jboss.org/repos/jbossws/tags/jbossws-1.2.1.GA/jbossws-core...
It is possible to check the Remoting version using the following method: -
public static int getDefaultVersion()
From 'org.jboss.remoting.Version', a possible solution will be to check the
version to decide if we need to register the marshaller in this way.
--
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
11:20 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-1704) The Use Of Remoting Causes An Additional 'datatype' Parameter To Be Sent On All Requests
[ http://jira.jboss.com/jira/browse/JBWS-1704?page=all ]
Thomas Diesler updated JBWS-1704:
---------------------------------
Fix Version/s: jbossws-2.0.2
(was: jbossws-2.1.0)
The Use Of Remoting Causes An Additional 'datatype' Parameter
To Be Sent On All Requests
----------------------------------------------------------------------------------------
Key: JBWS-1704
URL: http://jira.jboss.com/jira/browse/JBWS-1704
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-jaxrpc
Affects Versions: jbossws-1.2.1
Reporter: Darran Lofthouse
Assigned To: Thomas Diesler
Fix For: jbossws-2.0.2
The use of JBoss Remoting causes a datatype parameter to be sent with all outgoing
requests, this parameter is not required by the server and can cause problems as some
loadbalancers reject the message.
The reason for this is because of a workaround required in JBoss Remoting 1.4.5 to
register the marshaller. See the createRemotingClient method: -
http://anonsvn.jboss.org/repos/jbossws/tags/jbossws-1.2.1.GA/jbossws-core...
It is possible to check the Remoting version using the following method: -
public static int getDefaultVersion()
From 'org.jboss.remoting.Version', a possible solution will be to check the
version to decide if we need to register the marshaller in this way.
--
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
6067
days inactive
6191
days old
jbossws-issues@lists.jboss.org
5 comments
3 participants
participants (3)
-
Alessio Soldano (JIRA) -
Darran Lofthouse (JIRA)
-
Thomas Diesler (JIRA)