[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-1288) StreamServer for in-jvm connection should create a LocalServerInvoker
[
https://issues.jboss.org/browse/JBREM-1288?page=com.atlassian.jira.plugin...
]
Ron Sigal updated JBREM-1288:
-----------------------------
Assignee: Ron Sigal
Description:
When the org.jboss.remoting.Client method
public Object invoke(InputStream inputStream, Object param) throws Throwable;
or one of its variants is called, it calls new StreamServer(inputStream), which creates an
org.jboss.remoting.transport.Connector to serve the contents of the InputStream. To
determine the transport to be used, StreamServer looks for a system property
"remoting.stream.transport", and, if it doesn't exist, it uses
"socket" by default. However, if the InputStream is being sent to a server in
the same JVM, the "local" transport should be used.
StreamServer for in-jvm connection should create a
LocalServerInvoker
---------------------------------------------------------------------
Key: JBREM-1288
URL: https://issues.jboss.org/browse/JBREM-1288
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.5.4.SP1, 2.2.4
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.4.SP2, 2.2.4.SP1
When the org.jboss.remoting.Client method
public Object invoke(InputStream inputStream, Object param) throws Throwable;
or one of its variants is called, it calls new StreamServer(inputStream), which creates
an org.jboss.remoting.transport.Connector to serve the contents of the InputStream. To
determine the transport to be used, StreamServer looks for a system property
"remoting.stream.transport", and, if it doesn't exist, it uses
"socket" by default. However, if the InputStream is being sent to a server in
the same JVM, the "local" transport should be used.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira