[jboss-user] [Remoting] - Re: Multiple problems with ServerInvokerServlet and HttpNami

[ron.sigal@jboss.com]

Hi Martin,

I'm glad you solved at least part of the problem.  I can add a couple of points.

anonymous wrote : 
  | 2. Exeption handling
  | Due to a bug in JBOSS remoting I downloaded the latest version of remoting in order to catch remote exceptions on my client. The tutorials say that there is a client-side switch: NO_THROW_ON_ERROR.
  | Where do I have to set this command within my configuration? 
  | 

NO_THROW_ON_ERROR probably isn't what you want.  As of Remoting version 2.2.2.SP2 (available from the repository at http://repository.jboss.com/jboss/remoting/2.2.2.SP2/ 
(though you might as well go for 2.2.2.SP3 at http://repository.jboss.com/jboss/remoting/2.2.2.SP3-brew/),
the fix to JIRA issue JBREM-813 "ServletServerInvoker should return an exception instead of just an error message" (http://jira.jboss.com/jira/browse/JBREM-813), allows you configure the server to return the actual exception thrown by the application code.  You need to configure this behavior: in $SERVER_HOME/server/default/deploy/ejb3.deployer/META-INF/jboss-service.xml, change the line


  | <attribute name="InvokerLocator">socket://${jboss.bind.address}:3873</attribute>
  | 

to


  | <attribute name="InvokerLocator">socket://${jboss.bind.address}:3873/?return-exception=true</attribute>
  | 

anonymous wrote : 
  | 3. Compression
  | I want to compress traffic between server and client. On the server side I use following configuration:
  | 

There seems to be a problem using the compression marshaller in the Application Server.  I'm looking into it:  JIRA issue JBREM-677: "Compression marshalling fails intermittently."

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111071#4111071

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111071