[jboss-user] [JBoss Messaging] - Re: Problems after Migration from WebSphere to JBoss (Broken

[dahm]

Hi,

here's the completx remoting-bisocket.xml:


  | 	<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="serverBindAddress">${jboss.bind.address}</attribute>
  | 					<attribute name="serverBindPort">14457</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>
  | 
  | 					<!--
  | 						Siehe Posting von Alphonse: https://www.spree.de/wbb3/index.php?page=Thread&postID=184&highlight=readybank#post184
  | 					-->
  | 					<attribute name="pingFrequency" isParam="true">60000</attribute>
  | 					<attribute name="pingWindowFactor" isParam="true">2</attribute>
  | 					<attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool
  | 					</attribute>
  | 					<!-- End immutable parameters -->
  | 
  | 					<attribute name="stopLeaseOnFailure" isParam="true">true</attribute>
  | 
  | 					<!-- Periodicity of client pings. Server window by default is twice this figure -->
  | 					<attribute name="clientLeasePeriod" isParam="true">10000</attribute>
  | 					<attribute name="validatorPingPeriod" isParam="true">10000</attribute>
  | 					<attribute name="validatorPingTimeout" isParam="true">5000</attribute>
  | 					<attribute name="registerCallbackListener">false</attribute>
  | 
  | 					<attribute name="timeout" isParam="true">0</attribute>
  | 
  | 					<!--
  | 						Number of seconds to wait for a connection in the client pool to become free Offenbar nicht mehr in JBoss-Remoting
  | 						2.5.1: 11:19:50,109 WARN [MicroSocketClientInvoker] numberOfRetries is no longer used <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>
  | 
  | 					<!-- The maximum time to wait before timing out on trying to write a message to socket for delivery -->
  | 					<attribute name="callbackTimeout">10000</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>
  | 

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

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