Hi!

I have a strange problem at one client with a windows machine.

We are using Jbos  4.2.3 with  JBM 1.4.5 with remoting 2.2.3.sp1. Our software runs on multiple companies without any problems.
But there after the installation on the production machine we get the stack trace below.

Our Jboss is started with -b 0.0.0.0

The remoting configuration is also listed below. We are using the SSL Bisocket there like on other clients too.

We are not using external JMS clients. Only internally for some messaging with EJB3 based MDB.

The strange thing is, that the port of the invoker URL is not set.

I can not reproduce this in out development environments.

Has anyone an idea where to look at?

One difference between the testsystem there (which is working) and the productive environment is that they are using a DNS alias for that machine

If I test in my environment the invoker allways looks like

InvokerLocator [sslbisocket://MYCOMPUTERNAME:4457//?JBM_clien.....

but as you can see in the logfile the IP ist used there and no port is visible 

InvokerLocator [sslbisocket://IPADRESS//?JBM_clien.....

So, where is the port gone? Any hints?

thx in advance!! 
Markus Lutum

The invoker config:

<mbean code="org.jboss.remoting.transport.Connector" name="jboss.messaging:service=Connector,transport=sslbisocket" display-name="SSL Bisocket Transport Connector">
<attribute name="Configuration">
<config>
<invoker transport="sslbisocket">
<!-- 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">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="serverSocketFactory">jboss.messaging:service=ServerSocketFactory,type=SSL</attribute>
<attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
<!--the following parameters are useful when there is a firewall between client and server. Uncomment them if so.-->
<attribute name="numberOfCallRetries" isParam="true">5</attribute>
<attribute name="pingFrequency" isParam="true">30000</attribute>
<attribute name="pingWindowFactor" isParam="true">71582</attribute>
<attribute name="generalizeSocketException" isParam="true">true</attribute>
<!-- Now remoting supports socket write timeout configuration. Uncomment this if you need it. -->
<attribute name="writeTimeout" isParam="true">30000</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="failureDisconnectTimeout" isParam="true">0</attribute>
<attribute name="callbackErrorsAllowed">1</attribute>
<attribute name="registerCallbackListener">false</attribute>
<attribute name="useClientConnectionIdentity" isParam="true">true</attribute>
<attribute name="timeout" isParam="true">0</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>
<!-- The maximum time to wait before timing out on trying to write a message to socket for delivery -->
<attribute name="callbackTimeout">10000</attribute>

</invoker>

and here the stack trace of the problem:

09:41:41,109 ERROR [org.jboss.jms.client.JBossConnectionFactory] Failed to download and/or install client side AOP stack
org.jboss.jms.exception.MessagingNetworkFailureException
     at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:240)
     at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:205)
     at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
     at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$getClientAOPStack$aop(ClientConnectionFactoryDelegate.java:248)
     at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.getClientAOPStack(ClientConnectionFactoryDelegate.java)
     at org.jboss.jms.client.ClientAOPStackLoader.load(ClientAOPStackLoader.java:75)
     at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:192)
     at org.jboss.jms.client.JBossConnectionFactory.createXAQueueConnection(JBossConnectionFactory.java:142)
     at org.jboss.jms.client.JBossConnectionFactory.createXAQueueConnection(JBossConnectionFactory.java:136)
     at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupQueueConnection(JmsActivation.java:465)
     at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:437)
     at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:317)
     at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:635)
     at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
     at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
     at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslbisocket://158.168.230.227//?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&failureDisconnectTimeout=0&generalizeSocketException=true&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=5&numberOfRetries=10&pingFrequency=30000&pingWindowFactor=71582&socket.check_connection=false&stopLeaseOnFailure=true&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat&useClientConnectionIdentity=true&validatorPingPeriod=10000&validatorPingTimeout=5000&writeTimeout=30000]
     at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:640)
     at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:458)
     at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141)
     at org.jboss.remoting.Client.invoke(Client.java:1925)
     at org.jboss.remoting.Client.invoke(Client.java:786)
     at org.jboss.remoting.Client.invoke(Client.java:774)
     at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
     ... 15 more
Caused by: java.lang.IllegalArgumentException: port out of range:-1
     at java.net.InetSocketAddress.<init>(InetSocketAddress.java:118)
     at org.jboss.remoting.transport.sslbisocket.SSLBisocketClientInvoker.createSocket(SSLBisocketClientInvoker.java:122)
     at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:913)
     at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:602)
     ... 21 more