12:22 a.m.
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: transport
Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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
12:22 a.m.
New subject: [JBoss JIRA] Updated: (JBREM-675) Problems with Servlet invoker
[ http://jira.jboss.com/jira/browse/JBREM-675?page=all ]
Tom Elrod updated JBREM-675:
-----------------------------
Attachment: ServletServerInvoker.java
Source patch for issues.
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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:58 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-675) Problems with Servlet invoker
[ http://jira.jboss.com/jira/browse/JBREM-675?page=all ]
Tom Elrod updated JBREM-675:
-----------------------------
Fix Version/s: 2.2.0.Beta2 (Boon)
(was: 2.2.0.Beta1 (Bluto))
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta2 (Boon)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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
5:54 p.m.
New subject: [JBoss JIRA] Assigned: (JBREM-675) Problems with Servlet invoker
[ http://jira.jboss.com/jira/browse/JBREM-675?page=all ]
Ron Sigal reassigned JBREM-675:
-------------------------------
Assignee: Ron Sigal (was: Tom Elrod)
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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
2:58 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-675) Problems with Servlet invoker
[ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385210 ]
Ron Sigal commented on JBREM-675:
---------------------------------
There seem to be three changes in the attached ServletServerInvoker:
1. The MBean Object Name is no longer hard coded.
2. Leasing information is added to responses.
3. Response code 200 is used instead of 204 to avoid a null response.
ServletServerInvoker has been updated as follows:
1. The ServletServerInvoker.getMBeanObjectName() method is deleted, so that
org.jboss.remoting.ServerInvoker.getMBeanObjectName() is called instead. The latter adds
values for "port", "host", and all parameters that appear in the
InvokerLocator.
2. Leasing is handled by ServerInvoker and doesn't need to be handled by
ServletServerInvoker.
3. The response code issue has been fixed along the lines of the treatment in
org.jboss.remoting.transport.coyote.CoyoteInvoker. That is, if the request did not come
from org.jboss.remoting.transport.http.HTTPClientInvoker or the request method was PUT,
then 204 is used for a null response. Otherwise, 200 is used.
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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
9:16 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-675) Problems with Servlet invoker
[ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385458 ]
Ron Sigal commented on JBREM-675:
---------------------------------
The default exception handling behavior is now to return the exception thrown by the
invocation handler. To turn off that behavior, so that an error message is returned, it
is necessary to add the parameter
org.jboss.remoting.transport.http.HTTPMetadataConstants.DONT_RETURN_EXCEPTION (actual
value "dont-return-exception") with a value of "true" to the metadata
map received by ServerServletInvoker. For example, "dont-return-exception=true"
could be added to the InvokerLocator.
This change is related to JBREM-813 "ServletServerInvoker should return an exception
instead of just an error message".
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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
9:46 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-675) Problems with Servlet invoker
[ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385461 ]
Ron Sigal commented on JBREM-675:
---------------------------------
Testing:
1. New unit test:
org.jboss.test.remoting.transport.servlet.ServletInvokerNoExceptionTestClient.
2. Ran EJB3 example from wiki page Accessing_EJB3s_over_HTTP_HTTPS, after updating example
(see EJBTHREE-1094 "Update wiki page "Accessing_EJB3s_over_HTTP_HTTPS" for
Remoting 2.4.0"). It ran with HTTP and HTTPS with the non-APR connector. With the
APR connector, the example ran with HTTP, but there is a problem with HTTPS. It seems
that the APR connector expects the keystore in openssl format. See also JBREM-825
"Verify that CoyoteInvoker works with Apache Portable Runtime".
3. Created a servlet example in JBossMessaging, parallel to the http example, and it ran
correctly. See JBMESSAGING-1131 "Add configuration for Remoting servlet
transport".
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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
2:50 a.m.
New subject: [JBoss JIRA] Closed: (JBREM-675) Problems with Servlet invoker
[ http://jira.jboss.com/jira/browse/JBREM-675?page=all ]
Ron Sigal closed JBREM-675.
---------------------------
Resolution: Done
The tests pass when run manually.
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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
2:50 a.m.
New subject: [JBoss JIRA] Commented: (JBREM-675) Problems with Servlet invoker
[ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385670 ]
Ron Sigal commented on JBREM-675:
---------------------------------
Ran the JBossMessaging servlet example and the EBJ3 example at the same time.
Problems with Servlet invoker
-----------------------------
Key: JBREM-675
URL: http://jira.jboss.com/jira/browse/JBREM-675
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Attachments: ServletServerInvoker.java
Several problems with servlet invoker:
1) There can't be two servlet invokers (it's necessary, for example, if you want
to use them for JBoss Messagning and for EJBs - they require separate connectors) because
ObjectName is hard-coded in ServletServerInvoker.java
2) Null returns from invokers are sent to client as empty 204 responses and custom
marshallers have no change to process return value. This breaks JBoss Messaging which
expects that EVERY message contains at least two bytes (version tag and format tag).
--
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
6266
days inactive
6553
days old
8 comments
2 participants
participants (2)
-
Ron Sigal (JIRA) -
Tom Elrod (JIRA)