-
2. Re: com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_9] - Could not get unique port.
marcos_aps Feb 2, 2011 8:09 AM (in response to nickarls)Nicklas Karlsson wrote:
Any help in http://community.jboss.org/thread/2124?tstart=0 ?
Unfortunately it didn't help. As I said I would like to know where I can see the port configured for arjuna and how I can configure another port for arjuna and what ports you recommend. Thank you anyway, Nicklas.Marcos
-
3. Re: com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_9] - Could not get unique port.
nickarls Feb 2, 2011 8:16 AM (in response to marcos_aps)The thread speaks of jbossjta-properties.xml but since it should default to "any available port", there might be other, underlying issues.
-
4. com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_9] - Could not get unique port.
marcos_aps Feb 2, 2011 8:22 AM (in response to nickarls)Nicklas Karlsson wrote:
The thread speaks of jbossjta-properties.xml but since it should default to "any available port", there might be other, underlying issues.
I saw this configuration in jbossjta-properties.xml:<property name="com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort" value="0"/>
So, does this configuration mean that it should default to any available port?
-
5. Re: com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_9] - Could not get unique port.
marcos_aps Feb 2, 2011 8:32 AM (in response to nickarls)There's also this error message in the log:
2011-02-02 08:33:43,877 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=TransactionManager
2011-02-02 08:33:43,877 DEBUG [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Starting jboss:service=TransactionManager
2011-02-02 08:33:43,877 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
2011-02-02 08:33:43,877 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Setting up property manager MBean and JMX layer
2011-02-02 08:33:43,986 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_7] - Failed to create server socket on port: 0
2011-02-02 08:33:43,986 WARN [org.jboss.system.ServiceController] Problem starting service jboss:service=TransactionManager
com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_9] - Could not get unique port.
at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start(TransactionStatusManager.java:197)
at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.<init>(TransactionStatusManager.java:78)
at com.arjuna.ats.arjuna.coordinator.TxControl.<clinit>(TxControl.java:312)
at com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService(TransactionManagerService.java:139)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
-
6. com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_9] - Could not get unique port.
nickarls Feb 2, 2011 8:32 AM (in response to marcos_aps)Try an explicit port, 666 or something.
-
7. com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_9] - Could not get unique port.
marcos_aps Feb 2, 2011 9:06 AM (in response to nickarls)According to the error above, is JBoss trying to use port 0?
Marcos
-
8. com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_9] - Could not get unique port.
nickarls Feb 2, 2011 3:43 PM (in response to marcos_aps)So it appears, try assigning a port for it.
-
9. Re: com.arjuna.ats.arjuna.exceptions.FatalError: [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_9] - Could not get unique port.
marcos_aps Feb 3, 2011 6:26 AM (in response to nickarls)Problem solved: after restarting the server (Windows Server 2003) the problem was gone. This server was really not well installed and configured. I suppose that lots of ports were being catched and JBoss could not find an available port to use, but of course it could be another problem.
Thank you.
Marcos