[jboss-user] [JBoss Messaging] - Re: long live consumer stops working
bodrin
do-not-reply at jboss.com
Wed Jan 30 10:53:24 EST 2008
It is present. I haven't modified this configuration file at all, but I get:
> ERROR [ConnectionFactory] Parameter pingFrequency is not specified in the remoting congiguration
I have launched a debuger and these are all the params available at runtime:
| clientMaxPoolSize=50
| clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper
| dataType=jms
| marshaller=org.jboss.jms.wireformat.JMSWireFormat
| numberOfCallRetries=1
| numberOfRetries=1
| socket.check_connection=false
| timeout=0
| unmarshaller=org.jboss.jms.wireformat.JMSWireFormat
|
The remoting-bisocket-service.xml :
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Standard bisocket-based Remoting service deployment descriptor.
|
| $Id: remoting-bisocket-service.xml 3409 2007-12-04 21:32:54Z timfox $
| -->
|
| <server>
|
| <!-- Standard bisocket connector - the bisocket transport only opens connection from client->server
| so can be used with firewalls where only outgoing connections are allowed.
| For examples of HTTP and SSL transports see docs/examples -->
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.messaging:service=Connector,transport=bisocket"
| display-name="Bisocket Transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="bisocket">
|
| <!-- There should be no reason to change these parameters - warning!
| Changing them may stop JBoss Messaging working correctly -->
| <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="timeout" isParam="true">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4457</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
| <attribute name="numberOfCallRetries" isParam="true">1</attribute>
| <attribute name="pingFrequency" isParam="true">214748364</attribute>
| <attribute name="pingWindowFactor" isParam="true">10</attribute>
| <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
| <!-- End immutable parameters -->
|
| <!-- Periodicity of client pings. Server window by default is twice this figure -->
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
|
| <!-- Number of seconds to wait for a connection in the client pool to become free -->
| <attribute name="numberOfRetries" isParam="true">10</attribute>
|
| <!-- Max Number of connections in client pool. This should be significantly higher than
| the max number of sessions/consumers you expect -->
| <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
|
| <!-- Use these parameters to specify values for binding and connecting control connections to
| work with your firewall/NAT configuration
| <attribute name="secondaryBindPort">xyz</attribute>
| <attribute name="secondaryConnectPort">abc</attribute>
| -->
|
| </invoker>
| <handlers>
| <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
|
| </server>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124828#4124828
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124828
More information about the jboss-user
mailing list