[jira] Updated: (GERONIMO-2113) Geronimo doesn't start if restarted using another JDK
[ http://issues.apache.org/jira/browse/GERONIMO-2113?page=all ] Donald Woods updated GERONIMO-2113: --- Fix Version/s: 1.1.2 1.2 (was: 1.1.x) Affects Version/s: 1.1.1 1.2 Geronimo doesn't start if restarted using another JDK - Key: GERONIMO-2113 URL: http://issues.apache.org/jira/browse/GERONIMO-2113 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: transaction manager Affects Versions: 1.2, 1.1, 1.1.1 Reporter: Nellya Udovichenko Assigned To: David Jencks Fix For: 1.2, 1.1.2 Attachments: HOWLLog.patch, HOWLLog.patch There is a bug in HOWL. At Geronimo launching time the file content control sum is calculated by the function java.nio.ByteBuffer.hashCode(). Therefore, if hash code algorithms of various JDKs differ Geronimo doesn't start. The bug is repaired in howl-1.0.1 by the introducing of the new parameter adler32Checksum. If the parameter value is false the control sum is calculated by the function java.nio.ByteBuffer.hashCode() otherwise it is calculated using ADLER-32 algorithm. Attached patch adds the parameter to configs/j2ee-server/src/plan/plan.xml and to org.apache.geronimo.transaction.log.HOWLLog gbean with default value 'true'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2113) Geronimo doesn't start if restarted using another JDK
[ http://issues.apache.org/jira/browse/GERONIMO-2113?page=all ] Donald Woods updated GERONIMO-2113: --- Fix Version/s: 1.1.x Geronimo doesn't start if restarted using another JDK - Key: GERONIMO-2113 URL: http://issues.apache.org/jira/browse/GERONIMO-2113 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: transaction manager Affects Versions: 1.1 Reporter: Nellya Udovichenko Assigned To: David Jencks Fix For: 1.1.x Attachments: HOWLLog.patch There is a bug in HOWL. At Geronimo launching time the file content control sum is calculated by the function java.nio.ByteBuffer.hashCode(). Therefore, if hash code algorithms of various JDKs differ Geronimo doesn't start. The bug is repaired in howl-1.0.1 by the introducing of the new parameter adler32Checksum. If the parameter value is false the control sum is calculated by the function java.nio.ByteBuffer.hashCode() otherwise it is calculated using ADLER-32 algorithm. Attached patch adds the parameter to configs/j2ee-server/src/plan/plan.xml and to org.apache.geronimo.transaction.log.HOWLLog gbean with default value 'true'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2113) Geronimo doesn't start if restarted using another JDK
[ http://issues.apache.org/jira/browse/GERONIMO-2113?page=all ] Donald Woods updated GERONIMO-2113: --- Attachment: HOWLLog.patch The HOWLLog.java part of the patch had 2 typos in it. Attaching the updated patch file that can be applied against 1.1.1 and compiles cleanly. Geronimo doesn't start if restarted using another JDK - Key: GERONIMO-2113 URL: http://issues.apache.org/jira/browse/GERONIMO-2113 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: transaction manager Affects Versions: 1.1 Reporter: Nellya Udovichenko Assigned To: David Jencks Fix For: 1.1.x Attachments: HOWLLog.patch, HOWLLog.patch There is a bug in HOWL. At Geronimo launching time the file content control sum is calculated by the function java.nio.ByteBuffer.hashCode(). Therefore, if hash code algorithms of various JDKs differ Geronimo doesn't start. The bug is repaired in howl-1.0.1 by the introducing of the new parameter adler32Checksum. If the parameter value is false the control sum is calculated by the function java.nio.ByteBuffer.hashCode() otherwise it is calculated using ADLER-32 algorithm. Attached patch adds the parameter to configs/j2ee-server/src/plan/plan.xml and to org.apache.geronimo.transaction.log.HOWLLog gbean with default value 'true'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2113) Geronimo doesn't start if restarted using another JDK
[ http://issues.apache.org/jira/browse/GERONIMO-2113?page=all ] Nellya Udovichenko updated GERONIMO-2113: - Attachment: HOWLLog.patch Geronimo doesn't start if restarted using another JDK - Key: GERONIMO-2113 URL: http://issues.apache.org/jira/browse/GERONIMO-2113 Project: Geronimo Type: Bug Security: public(Regular issues) Components: transaction manager Versions: 1.1 Reporter: Nellya Udovichenko Attachments: HOWLLog.patch There is a bug in HOWL. At Geronimo launching time the file content control sum is calculated by the function java.nio.ByteBuffer.hashCode(). Therefore, if hash code algorithms of various JDKs differ Geronimo doesn't start. The bug is repaired in howl-1.0.1 by the introducing of the new parameter adler32Checksum. If the parameter value is false the control sum is calculated by the function java.nio.ByteBuffer.hashCode() otherwise it is calculated using ADLER-32 algorithm. Attached patch adds the parameter to configs/j2ee-server/src/plan/plan.xml and to org.apache.geronimo.transaction.log.HOWLLog gbean with default value 'true'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
