You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Donald Woods (JIRA)" <de...@geronimo.apache.org> on 2006/09/05 22:50:24 UTC

[jira] Commented: (GERONIMO-2113) Geronimo doesn't start if restarted using another JDK

    [ http://issues.apache.org/jira/browse/GERONIMO-2113?page=comments#action_12432672 ] 
            
Donald Woods commented on GERONIMO-2113:
----------------------------------------

You're having problems with the updated Aug. 4th patch file that was created against the 1.1.1 branch?
Not sure how the above is an error, as I use TortoiseSVN on Windows....  What command are you using to apply the patch file?


> 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