[jboss-user] [Remoting] - Re: CompressingMarshaller and clientConnectAddress
klauserber
do-not-reply at jboss.com
Mon Sep 24 10:14:47 EDT 2007
Thank you Ron for your help.
With the first solution, the client can not connect, because it get's the wrong connect address. With the second solution, the application is working but with no compression (analysed with wireshark).
In other words: The configurations have no effect. What is wrong with my configuration?
Here is the whole thing again:
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <attribute name="Configuration">
| <config>
| <invoker transport="socket">
| <attribute name="numAcceptThreads">1</attribute>
| <attribute name="maxPoolSize">360</attribute>
| <attribute name="clientMaxPoolSize" isParam="true">50</attribute>
| <attribute name="timeout" isParam="true">60000</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">3873</attribute>
| <attribute name="clientConnectAddress">###THE_CLIENT_CONNECT_ADDRESS###</attribute>
| <attribute name="backlog">200</attribute>
| <attribute name="marshaller">org.jboss.remoting.marshal.compress.CompressingMarshaller</attribute>
| <attribute name="unmarshaller">org.jboss.remoting.marshal.compress.CompressingUnMarshaller</attribute>
| </invoker>
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087936#4087936
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087936
More information about the jboss-user
mailing list