The modifications I'm making to remoting-service.xml don't appear to be picked 
up by the client

I'm still seeing exceptions like:

ERROR 2007-02-19 14:23:24,687 [Manager Queue Six.1.1] 
org.jboss.jms.client.container.ExceptionInterceptor: Caught RuntimeException
org.jboss.remoting.CannotConnectException: Can not get connection to server. 
Problem establishing socket connection for InvokerLocator 
[socket://172.26.1.240:4457/?clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&serializationtype=jboss&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat]
        at 
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:510)
        at 
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1414)
        at org.jboss.remoting.Client.invoke(Client.java:511)
        at 
org.jboss.jms.client.delegate.DelegateSupport.invoke(DelegateSupport.java:111)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate$acknowledge_354868566256058116.invokeNext(ClientSessionDelegate$acknowledge_354868566256058116.java)
        at 
org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:182)
        at 
org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate$acknowledge_354868566256058116.invokeNext(ClientSessionDelegate$acknowledge_354868566256058116.java)
        at 
org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate$acknowledge_354868566256058116.invokeNext(ClientSessionDelegate$acknowledge_354868566256058116.java)
        at 
org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate$acknowledge_354868566256058116.invokeNext(ClientSessionDelegate$acknowledge_354868566256058116.java)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate.acknowledge(ClientSessionDelegate.java)
        at 
org.jboss.jms.client.container.SessionAspect.handlePostDeliver(SessionAspect.java:215)
        at 
org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect6.invoke(SessionAspect6.java)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate$postDeliver_5319211143798977162.invokeNext(ClientSessionDelegate$postDeliver_5319211143798977162.java)
        at 
org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:182)
        at 
org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate$postDeliver_5319211143798977162.invokeNext(ClientSessionDelegate$postDeliver_5319211143798977162.java)
        at 
org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate$postDeliver_5319211143798977162.invokeNext(ClientSessionDelegate$postDeliver_5319211143798977162.java)
        at 
org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate$postDeliver_5319211143798977162.invokeNext(ClientSessionDelegate$postDeliver_5319211143798977162.java)
        at 
org.jboss.jms.client.delegate.ClientSessionDelegate.postDeliver(ClientSessionDelegate.java)
        at 
org.jboss.jms.client.remoting.MessageCallbackHandler.postDeliver(MessageCallbackHandler.java:162)
        at 
org.jboss.jms.client.remoting.MessageCallbackHandler.callOnMessage(MessageCallbackHandler.java:137)
        at 
org.jboss.jms.client.remoting.MessageCallbackHandler$ListenerRunner.run(MessageCallbackHandler.java:722)
        at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown 
Source)
        at java.lang.Thread.run(Thread.java:534)
Caused by: java.net.SocketException: Can not obtain client socket connection 
from pool. Have waited 30 seconds for available connection (50 in use)
        at 
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:776)
        at 
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:506)
        ... 29 more


It should not be waiting for only 30 seconds (i've set numberOfRetries to 600 
i.e. 10 minutes) and there should be more than 50 connections in use (i've set 
clientMaxPoolSize to 100). 

My remoting-service.xml is as follows:


  | <?xml version="1.0" encoding="UTF-8"?>
  | 
  | <!--
  |      Messaging Remoting service deployment descriptor.
  | 
  |      $Id: remoting-service.xml 1576 2006-11-17 04:22:42Z ron_sigal $
  |  -->
  | 
  | <server>
  | 
  |    <mbean code="org.jboss.remoting.transport.Connector"
  |           name="jboss.messaging:service=Connector,transport=socket"
  |           display-name="Socket transport Connector">
  |       <attribute name="Configuration">
  |          <config>
  |             <invoker transport="socket">
  |                <attribute name="marshaller" 
isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
  |                <attribute name="unmarshaller" 
isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
  |                <attribute name="serializationtype" 
isParam="true">jboss</attribute>
  |                <attribute name="dataType" isParam="true">jms</attribute>
  |                <attribute name="socket.check_connection" 
isParam="true">false</attribute>
  |                <attribute name="timeout">1800000</attribute>
  |                <attribute 
name="serverBindAddress">${jboss.bind.address}</attribute>
  |                <attribute name="serverBindPort">4457</attribute>
  |                <attribute name="leasePeriod">20000</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="numberOfRetries">600</attribute>
  |                <attribute name="clientMaxPoolSize">100</attribute>
  |             </invoker>
  |             <handlers>
  |                <handler 
subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
  |             </handlers>
  |          </config>
  |       </attribute>
  |       <depends>jboss.messaging:service=NetworkRegistry</depends>
  |    </mbean>
  | </server>
  | 

Is the jboss client aware of the server settings?

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

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4018665
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to