10:05 p.m.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Fix For: 2.0.0 Alpha
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one
ServerSocket is used. In principle, it's the appropriate transport to use when the
server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
10:05 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Ron Sigal updated JBMESSAGING-1131:
-----------------------------------
Description: In addition to the "http" transport, Remoting also has the
http-based "servlet" transport. The servlet transport is the same as the http
transport on the client side (they both use
org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server
side. In particular, CoyoteInvoker, the http transport server invoker, uses the network
layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads. But in the servlet
transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields
invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.
The advantage, which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
(was: In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one
ServerSocket is used. In principle, it's the appropriate transport to use when the
server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Fix For: 2.0.0 Alpha
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
10:12 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Ron Sigal updated JBMESSAGING-1131:
-----------------------------------
Attachment: messaging-servlet-service.xml
ServletExample.java
build.xml
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Fix For: 2.0.0 Alpha
Attachments: build.xml, messaging-servlet-service.xml, ServletExample.java
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
10:14 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Ron Sigal updated JBMESSAGING-1131:
-----------------------------------
Attachment: remoting-servlet-service.xml
web.xml
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Fix For: 2.0.0 Alpha
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
10:18 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=comments#action_1... ]
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------
I've attached the various files relevant to this example.
1. build.xml, messaging-servlet-service.xml and ServletExample.java go in
<root>/docs/examples/servlet
2. remoting-servlet-service.xml goes in <root>/src/etc/remoting
3. web.xml goes in <root>/src/etc/remoting/remoting-servlet-invoker.war/WEB-INF
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Fix For: 2.0.0 Alpha
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
1:10 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Tim Fox updated JBMESSAGING-1131:
---------------------------------
Fix Version/s: 2.0.0 Beta
(was: 2.0.0 Alpha)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Fix For: 2.0.0 Beta
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
1:14 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Tim Fox updated JBMESSAGING-1131:
---------------------------------
Fix Version/s: EAP 4.3 Integration
(was: 2.0.0 Beta)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Fix For: EAP 4.3 Integration
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
1:23 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Tim Fox updated JBMESSAGING-1131:
---------------------------------
Fix Version/s: JBM Stable branch
(was: EAP/SOA-P Integration)
Priority: Minor (was: Major)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Priority: Minor
Fix For: JBM Stable branch
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
1:06 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Ron Sigal updated JBMESSAGING-1131:
-----------------------------------
Attachment: (was: remoting-servlet-service.xml)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Priority: Minor
Fix For: Stable branch
Attachments: build.xml, messaging-servlet-service.xml, ServletExample.java,
web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
1:08 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Ron Sigal updated JBMESSAGING-1131:
-----------------------------------
Attachment: remoting-servlet-service.xml
Replaced remoitng-servlet-service.xml - path parameter had incorrect contex.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Priority: Minor
Fix For: Stable branch
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
1:11 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Ron Sigal updated JBMESSAGING-1131:
-----------------------------------
Attachment: (was: ServletExample.java)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Priority: Minor
Fix For: Stable branch
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
1:13 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]
Ron Sigal updated JBMESSAGING-1131:
-----------------------------------
Attachment: ServletExample.java
Replaced ServletExample.java - removed an unnecessary import.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Priority: Minor
Fix For: Stable branch
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=comments#action_1... ]
David Smiley commented on JBMESSAGING-1131:
-------------------------------------------
I'm trying to employ this but I've not been successful. I put the
servlet-invoker.war from JBoss remoting 2.2.0 into my JBoss AS 4.2.1 w/ JBoss Messaging
1.4.0.SP3 installed already (w/ the jboss remoting 2.2.2.SP4-brew per the instructions).
I dropped the *-service.xml attachments here into my deploy directory. I went to the
existing http config example in my JBoss messaging distro, modified the JNDI
ConnectionFactory path to be /ServletConnectionFactory (I also modified its build.xml to
not deploy or undeploy files; I prefer to do that manually). I modified
remoting-servlet-service.xml to have the path: servlet-invoker/ServerInvokerServlet. I
at first tried the web.xml attached here but it didn't work because that long
invokerName value wasn't in JMX... so I truncated it to the part that was:
jboss.remoting:service=invoker,transport=servlet
So I try the example and I can tell its talking to the invoker, but it fails and I have no
clue what to do. Here's the exception :
java.io.IOException: org.jboss.jms.wireformat.ConnectionFactoryGetClientAOPStackResponse
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80)
at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
at
org.jboss.remoting.transport.servlet.ServletServerInvoker.processRequest(ServletServerInvoker.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
at $Proxy55.processRequest(Unknown Source)
at
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.processRequest(ServerInvokerServlet.java:127)
at
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.doPost(ServerInvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:613)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Priority: Minor
Fix For: Stable branch
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
8:18 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1131:
--------------------------------------
Hi David-
We haven't actually tried it yet either, so no idea if it works or not.
If you can get it to work great :) Please report your findings back.
This is not currently very high up the priority list right now, but hopefully we will get
round to it eventually.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assigned To: Tim Fox
Priority: Minor
Fix For: Stable branch
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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:42 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Pelle B commented on JBMESSAGING-1131:
--------------------------------------
The web.xml file has a reference to a MBean as follows:
<param-value>jboss.remoting:service=invoker,transport=servlet</param-value>
Where do I setup this MBean and what Invoker class should be used?
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Tim Fox
Priority: Minor
Fix For: Stable branch
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
12:20 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Pelle B commented on JBMESSAGING-1131:
--------------------------------------
Found that the MBean with name jboss.remoting:service=invoker,transport=servlet is
registered in the ServletServerInvoker.java class for version 2.2.2.SP8 of JBoss remoting
but not in version 2.4.0
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Tim Fox
Priority: Minor
Fix For: Stable branch
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
3:06 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Tim Fox updated JBMESSAGING-1131:
---------------------------------
Fix Version/s: Unscheduled
(was: Stable branch)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Tim Fox
Priority: Minor
Fix For: Unscheduled
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
2:08 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Tim Fox updated JBMESSAGING-1131:
---------------------------------
Fix Version/s: 1.4.0.SP3.CP05
(was: Unscheduled)
Assignee: Howard Gao (was: Tim Fox)
Servlet transport is not currently a supported transport for JBM (We've never tested
it), so I can't say whether it will or won't currently work.
However this is something we should certainly look at supporting for the next EAP CP.
(CP05)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Priority: Minor
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
2:10 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Tim Fox updated JBMESSAGING-1131:
---------------------------------
Priority: Major (was: Minor)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
2:01 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1131:
------------------------------------
Attachment: code_changes.zip
in jboss remoting (version 2.2.2.SP10):
ServletServerInvoker.processRequest(HttpServletRequest request, byte[] requestByte,
HttpServletResponse response)
I added the following line (see line 285 of ServletServerInvoker.java) :
invocationResponse = new InvocationResponse(invocationRequest.getSessionId(),
invocationResponse, isError,
responseMap);
I did this because I saw http invoker did this : see (line 368 ~ 373 of
CoyoteInvoker.java)
if (isRemotingUserAgent &&
((Boolean)receivedInvocationRequest.get()).booleanValue())
{
responseMap = ((ResponseMap) responseMap).getMap();
responseObject = new InvocationResponse(invocationRequest.getSessionId(),
responseObject, isError,
responseMap);
}
In JBoss Messaging 1.4, JMSWireFormat.java, I added the following line: (line 342, the
read() method)
int id ;
try
{
id = dis.readInt();
} catch (EOFException e) {
System.err.println("Someting wrong?
**********************************************");
return null;
}
I added this because I found in the example the jms server will receive an empty
ByteArrayInputStream and will cause the following packet.read(dis) to fail
(EOFException).
With the above changes, I can successfully run the servlet example as well as http
example.
I need JBoss Remoting guy to help review the code, and see if the changes are valid.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
1:19 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
Hi Tim,
Anyone in JBR I can ask for help on this?
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
9:32 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------
That would be me. :)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
3:22 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
Thanks Ron. :)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
4:25 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------
Howard,
Regarding the change to ServletServerInvoker, yes, that's appropriate. In fact,
it's one of several changes I made to ServletServerInvoker in upgrading it for
Remoting version 2.4/2.5. Now that the servlet transport is getting increased use in EAP,
I've created JBREM-1079 "Port fixes to ServletServerInvoker from branch 2.x to
branch 2.2".
I've already tagged release 2.2.2.SP11, which is intended for EAP 4.2.0.GA_CP06 / EAP
4.3.0.GA_CP04, so I'll do JBREM-1079 for Remoting 2.2.2.SP12 andEAP 4.2.0.GA_CP07 /
EAP 4.3.0.GA_CP05.
In the meantime, it looks like the only implication of failing to wrap the response in an
InvocationResponse is a different behavior in the case of an exception, which will be
returned rather than thrown. I don't know how that affects JBM.
-Ron
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
3:36 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
That's will be great. Thanks Ron. So JBM will update its JBoss remoting dependency to
1.1.1.SP12 and that will be fine.
JBM has registered its own marshaller/unmarshaller with JB remoting, when writing to the
stream, it replies on correct identification of the type of payload object. It presumes
that in case of JBM payload, the only possible types are InvocationRequest and
InvocationResponse. If the type is passed otherwise while the payload really belongs to
JBM request/response, the result will be out of control.
When reading from the stream (unmarshalling), the JBM unmarshaller assumes it can always
read a int from the inputstream passed in. This int is the ID JBM use to reconstruct its
own packet. If Remoting somehow passes a different inputstream (maybe some internal packet
that is not relevant to JBM) the JBM unmarshaller has no way to identify, that's why I
got EOFException and so I catch it in my code.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
12:47 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------
Hi Howard,
Just to make sure I understand, you're saying that the current state of JBM just
won't work with the current state of the servlet transport, because of the missing
InvocationResponse, right? Which means JBPAPP-1274 "Fix JBoss Messaging and JBoss
Remoting so that servlet transport can be used" will have to be pushed to the next CP
release.
-Ron
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
3:06 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
Hi Ron. Yes that's the current situation.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP05
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
4:32 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Clebert Suconic updated JBMESSAGING-1131:
-----------------------------------------
Fix Version/s: 1.4.0.SP3.CP06
1.4.3.GA
(was: 1.4.0.SP3.CP05)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
4:47 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------
I take it that JBM release 1.4.0.SP3.CP06 is for EAP 4.3.0.GA_CP05 (12/May/09) ?
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
4:52 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
Hi Ron, I think so.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
6:02 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------
I've attached EJB3-JBM-Servlet-Examle.zip to JBPAPP-1274 "Fix JBoss Messaging and
JBoss Remoting so that servlet transport can be used", which is an Eclipse project
with everything needed (as far as I can tell) to run JBM over the Remoting servlet and
sslservlet transports.
By the way, concerning "When reading from the stream (unmarshalling), the JBM
unmarshaller assumes it can always read a int from the inputstream passed in. This int is
the ID JBM use to reconstruct its own packet. If Remoting somehow passes a different
inputstream (maybe some internal packet that is not relevant to JBM) the JBM unmarshaller
has no way to identify, that's why I got EOFException and so I catch it in my
code." The fact that you got an empty InputStream is a Remoting issue, which
I've fixed.
I ran the example using EAP 4.3.0.GA_CP03, with an unmodified JBM. Hopefully, all
that's necessary now is to configure the servlet transport.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
6:13 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
That's great Ron. It probably means no code change at JBM side to make servlet
transport work. I'll verify with your fix. Thanks.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
11:06 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
Hi Ron, I ran successfully your example against JBoss 4.2.3 GA and latest 1.4 build from
Branch_1_4. I'm trying to extract the JBM stuff from your example and make it running.
So far failed duo to configure issue. I'll try to figure it out.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
12:17 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1131:
--------------------------------------
In order to ensure there are no further delays, Galder has kindly volunteered to help out
with this task over the following few weekends and evenings.
Thanks Galder!
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
12:45 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Galder Zamarreno updated JBMESSAGING-1131:
------------------------------------------
Comment: was deleted
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
6:50 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
the servlet transportn (including ssl servlet) works by examples. As JBPAPP-1274 will go
to next cp, I'll add the servlet example in to JBM 1.4 branch and close this issue
when finished.
Thanks Ron.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
4:14 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------
That sounds great, Howard.
I'd be curious how the "servlet" transport would do with the rest of the JBM
test suite. There used to be an "http" version of the test suite, including the
stress test suite, that I used to play with. It was for the Remoting "http"
transport, which is the same as the "servlet" transport on the client side
(org.jboss.remoting.transport.http.HTTPClientInvoker) but is a standalone server on the
server side (org.jboss.remoting.transport.coyote.CoyoteInvoker).
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
7:31 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
Hi Ron, just tried http-tests in JBM, found two failures concerning callback poll period.
for instance in test we pass in a sys property:
String pollPeriod = "654";
System.setProperty("jboss.messaging.callback.pollPeriod", pollPeriod);
later we check if this takes effect, and failed, it turns out the default value (5000) is
always used. The other tests is try to check if this parameter takes effect when
configured in the remoting config files.
See the RemotingConnectionConfigurationTest for details. I also tried your latest remoting
jar (included in your example EJB3-JBM-Servlet-Example) and got the same test failures.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
9:41 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------
Actually, the poll period should be irrelevant. Once upon a time,
org.jboss.remoting.callback.CallbackPoller would poll periodically for callbacks,
returning immediately if there were none. Then I implemented a blocking mechanism, in
which CallbackPoller asks for callbacks and blocks until either a callback is generated or
it times out. Blocking mode is configured by setting the parameter
"blockingMode" to "blocking".
RemotingConnectionConfigurationTest should be updated in a couple of ways:
1. testing for the value of pollPeriod doesn't make sense if blocking mode is being
used, and remoting-http-service.xml (which, if I remember correctly, is used by
RemotingConnectionConfigurationTest) now configures blocking mode;
2. the "servlet" transport should be added as an option, or it could just
replace the "http" transport.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
3:29 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1131:
-----------------------------------------
Thanks Ron. I will update the RemotingConnectionConfigurationTest. as for the servlet
transport test, I talked with Tim and Clebert and decide not to add it to JBM test suite
as it requires a container to be started and a servlet be deployed. So it should be part
of AS integration test suite. We'll try to make it in to AS later.
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
6:01 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao closed JBMESSAGING-1131.
-----------------------------------
Resolution: Done
done
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP06, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
4:22 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Clebert Suconic reopened JBMESSAGING-1131:
------------------------------------------
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP07, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
4:22 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Clebert Suconic updated JBMESSAGING-1131:
-----------------------------------------
Fix Version/s: 1.4.0.SP3.CP07
(was: 1.4.0.SP3.CP06)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP07, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
5:16 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1131:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP08
(was: 1.4.0.SP3.CP07)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.3.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
6:17 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1131:
------------------------------------
Fix Version/s: 1.4.4.GA
(was: 1.4.3.GA)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
8:42 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Jay Howell updated JBMESSAGING-1131:
------------------------------------
Priority: Blocker (was: Major)
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Priority: Blocker
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
7:07 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1131) Add configuration for Remoting servlet transport
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1131?page=com.atlassian.ji...
]
Howard Gao closed JBMESSAGING-1131.
-----------------------------------
Resolution: Done
done
Add configuration for Remoting servlet transport
------------------------------------------------
Key: JBMESSAGING-1131
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1131
Project: JBoss Messaging
Issue Type: Task
Reporter: Ron Sigal
Assignee: Howard Gao
Priority: Blocker
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Attachments: build.xml, code_changes.zip, messaging-servlet-service.xml,
remoting-servlet-service.xml, ServletExample.java, web.xml
In addition to the "http" transport, Remoting also has the http-based
"servlet" transport. The servlet transport is the same as the http transport on
the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but
they are different on the server side. In particular, CoyoteInvoker, the http transport
server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with
worker threads. But in the servlet transport, a
org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and
passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage,
which came up in a forum thread recently
(http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#... and
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only
one ServerSocket is used. In principle, it's the appropriate transport to use when
the server is running inside JBossAS. In fact, the wiki page
"Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from
socket to servlet. However, there have been a couple of problems. For one,
ServletServerInvoker has been a little behind CoyoteInvoker in its development, though
I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For
another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never
automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need
automated test for servlet server invoker"). However, I wanted to verify that
JBossMessaging can run with the servlet transport, so I created a servlet example,
parallel to the http example, along with the supporting configuration files, and it works.
--
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
5601
days inactive
6167
days old
46 comments
8 participants
participants (8)
-
Clebert Suconic (JIRA) -
David Smiley (JIRA)
-
Galder Zamarreno (JIRA)
-
Howard Gao (JIRA)
-
Jay Howell (JIRA)
-
Pelle B (JIRA)
-
Ron Sigal (JIRA)
-
Tim Fox (JIRA)