[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3119) Multiple WAR in EAR verification, example, and document

[ https://jira.jboss.org/jira/browse/JBSEAM-3119?page=com.atlassian.jira.pl... ] Martin Gainty commented on JBSEAM-3119: --------------------------------------- port conflicts with arjuna transaction manager apparently jboss-jta.properties entries of <property name="com.arjuna.ats.internal.arjuna.utils.SocketProcessIdPort" value="11000"/> <!-- The maximum number of ports to try starting from the value specified by the property com.arjuna.ats.internal.arjuna.utils.SocketProcessIdPort. Any non-numeric or value less than 1 will defautl to 1. --> <property name="com.arjuna.ats.internal.arjuna.utils.SocketProcessIdMaxPorts" value="1000"/> are totally ignored..and produce this message in server.log 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:185) using arjuna's build.xml Im trying to compile arjuna now but running around in circles trying to get HP classbuilder task running <taskdef name="classpath-builder" classname="com.hp.mw.buildsystem.ant.ClasspathBuilder" classpathref="com.arjuna.buildsystem.classpath"/> there seems to be a hard dependency to JDK 1.4 or JDK 1.5 which needs to be updated to 1.6 asap thanks, martin- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira