[JBoss JIRA] Created: (JBAS-9373) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
10:25 a.m.
Arjuna service creating an anonymous localhost binding outside of standalone.xml
configuration.
-----------------------------------------------------------------------------------------------
Key: JBAS-9373
URL: https://issues.jboss.org/browse/JBAS-9373
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transaction Manager Integration (Arjuna)
Affects Versions: 7.0.0.Beta3
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when the
standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:31 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9373) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/JBAS-9373?page=com.atlassian.jira.plugin....
]
Jonathan Halliday commented on JBAS-9373:
-----------------------------------------
We don't make it possible to override that interface at an AS server instance level as
it is not permitted to have different servers running SocketProcessId on different
interfaces. To do so would invalidate its purpose. The only guaranteed way to achieve the
desired behaviour is not to allow users to configure it - they can't be trusted to
ensure all server instances use a consistent value. If you don't like it, use a
process id implementaiton other than the socket based one.
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: JBAS-9373
URL: https://issues.jboss.org/browse/JBAS-9373
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transaction Manager Integration (Arjuna)
Affects Versions: 7.0.0.Beta3
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:05 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-9373) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/JBAS-9373?page=com.atlassian.jira.plugin....
]
Scott Stark updated JBAS-9373:
------------------------------
Issue Type: Enhancement (was: Bug)
Let's change this to a feature request to get the configuration of the process id
exposed via the domain model.
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: JBAS-9373
URL: https://issues.jboss.org/browse/JBAS-9373
Project: JBoss Application Server
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Transaction Manager Integration (Arjuna)
Affects Versions: 7.0.0.Beta3
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:05 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9373) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/JBAS-9373?page=com.atlassian.jira.plugin....
]
Jonathan Halliday commented on JBAS-9373:
-----------------------------------------
I'm of the opinion this should not be exposed to users, for the same reason we
don't support user selection of the interface - it's too easy for a cut-n-paste
error to screw things up in interesting and difficult to detect ways. Change the
implementation we ship if you must, but don't make it user configurable.
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: JBAS-9373
URL: https://issues.jboss.org/browse/JBAS-9373
Project: Legacy JBoss Application Server 6
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Transaction Manager Integration (Arjuna)
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 a.m.
New subject: [JBoss JIRA] Commented: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Scott Stark commented on AS7-648:
---------------------------------
Mark Little indicated that the initDefaultProcess in the
com.arjuna.ats.arjuna.utils.Utility class is where the Uid implementation is chosen. That
method queries the
com.arjuna.ats.arjuna.common.CoreEnvironmentBean.getProcessImplementation:
/**
* Returns the class name of the Process implementation to use.
*
* Default: "com.arjuna.ats.internal.arjuna.utils.SocketProcessId"
* Equivalent deprecated property:
com.arjuna.ats.internal.arjuna.utils.processImplementation
*
* @return the name of a class implemeting Process.
*/
public String getProcessImplementation()
{
return processImplementation;
}
The proper way to implement this would be to add a processImplementation attribute to the
org.jboss.as.txn.TransactionSubsystemProviders as7 integration layer's parsing of the
urn:jboss:domain:transactions:1.0/core-environment, for example something based on the jdk
uuids:
<subsystem xmlns="urn:jboss:domain:transactions:1.0">
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager"/>
<core-environment socket-binding="txn-socket-process-id"
process-implementation="java-uuid" />
</subsystem>
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:55 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Scott Stark edited comment on AS7-648 at 5/13/11 11:55 AM:
-----------------------------------------------------------
The Process interface the getProcessImplementation is looking for is:
{{
public interface Process
{
/**
* @return the process id. This had better be unique between processes on
* the same machine. If not we're in trouble!
* @since JTS 2.1.
*/
public int getpid ();
}
}}
was (Author: starksm64):
The Process interface the getProcessImplementation is looking for is:
public interface Process
{
/**
* @return the process id. This had better be unique between processes on
* the same machine. If not we're in trouble!
* @since JTS 2.1.
*/
public int getpid ();
}
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:55 a.m.
New subject: [JBoss JIRA] Commented: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Scott Stark commented on AS7-648:
---------------------------------
The Process interface the getProcessImplementation is looking for is:
public interface Process
{
/**
* @return the process id. This had better be unique between processes on
* the same machine. If not we're in trouble!
* @since JTS 2.1.
*/
public int getpid ();
}
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:57 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Scott Stark edited comment on AS7-648 at 5/13/11 11:56 AM:
-----------------------------------------------------------
The Process interface the getProcessImplementation is looking for is:
{code:title=Bar.java|borderStyle=solid}
public interface Process
{
/**
* @return the process id. This had better be unique between processes on
* the same machine. If not we're in trouble!
* @since JTS 2.1.
*/
public int getpid ();
}
{code}
was (Author: starksm64):
The Process interface the getProcessImplementation is looking for is:
{{
public interface Process
{
/**
* @return the process id. This had better be unique between processes on
* the same machine. If not we're in trouble!
* @since JTS 2.1.
*/
public int getpid ();
}
}}
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:01 p.m.
New subject: [JBoss JIRA] Commented: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Jonathan Halliday commented on AS7-648:
---------------------------------------
The proper way to implement this would be to add a
processImplementation attribute to the org.jboss.as.txn.TransactionSubsystemProviders as7
integration layer's parsing of the urn:jboss:domain:transactions:1.0/core-environment
com.arjuna.* code is NOT part of the public platform API and
com.arjuna.ats.arjuna.utils.Process should not be visible to platform users. An
enumeration over existing implementations may be feasible at the config level, although I
continue to recommend against it.
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:56 a.m.
New subject: [JBoss JIRA] Assigned: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Scott Stark reassigned AS7-648:
-------------------------------
Assignee: Scott Stark (was: Jonathan Halliday)
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Scott Stark
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 p.m.
New subject: [JBoss JIRA] Commented: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Scott Stark commented on AS7-648:
---------------------------------
See the changes in:
https://github.com/starksmjboss/jboss-as/commit/71465bf8af1baeb28f0093dd5...
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Scott Stark
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:53 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Scott Stark edited comment on AS7-648 at 5/23/11 1:52 AM:
----------------------------------------------------------
See the changes in:
https://github.com/starksmjboss/jboss-as/commits/master
was (Author: starksm64):
See the changes in:
https://github.com/starksmjboss/jboss-as/commit/71465bf8af1baeb28f0093dd5...
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Scott Stark
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:24 p.m.
New subject: [JBoss JIRA] Updated: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Scott Stark updated AS7-648:
----------------------------
Git Pull Request: https://github.com/jbossas/jboss-as/pull/39
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Scott Stark
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:25 p.m.
New subject: [JBoss JIRA] Closed: (AS7-648) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
[
https://issues.jboss.org/browse/AS7-648?page=com.atlassian.jira.plugin.sy...
]
Jason Greene closed AS7-648.
----------------------------
Resolution: Done
Arjuna service creating an anonymous localhost binding outside of
standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: AS7-648
URL: https://issues.jboss.org/browse/AS7-648
Project: Application Server 7
Issue Type: Enhancement
Components: Transactions
Reporter: Scott Stark
Assignee: Scott Stark
Time Spent: 6 hours
Remaining Estimate: 0 minutes
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when
the standalone.xml configuration has specified a loopback-address other than
localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface
and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status:
'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at
com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at
com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at
com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at
com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5510
days inactive
5564
days old
13 comments
3 participants
participants (3)
-
Jason Greene (JIRA) -
Jonathan Halliday (JIRA)
-
Scott Stark (JIRA)