[jira] Updated: (GERONIMO-3913) NPE in org.apache.geronimo.security.SubjectId.hashCode() caused by incorrect JAVA_HOME or JRE_HOME

2008-07-23 Thread Joe Bohn (JIRA)
[ https://issues.apache.org/jira/browse/GERONIMO-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3913: --- Fix Version/s: (was: 2.0.x) 2.0.3 NPE in

[jira] Updated: (GERONIMO-3913) NPE in org.apache.geronimo.security.SubjectId.hashCode() caused by incorrect JAVA_HOME or JRE_HOME

2008-03-31 Thread toby cabot (JIRA)
[ https://issues.apache.org/jira/browse/GERONIMO-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] toby cabot updated GERONIMO-3913: - Attachment: bug-3913-2.0.2-patch.txt The problem was that

[jira] Updated: (GERONIMO-3913) NPE in org.apache.geronimo.security.SubjectId.hashCode() caused by incorrect JAVA_HOME or JRE_HOME

2008-03-31 Thread toby cabot (JIRA)
[ https://issues.apache.org/jira/browse/GERONIMO-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] toby cabot updated GERONIMO-3913: - Attachment: g2-trace.txt Here's what the stack trace looks like now. It's still fugly but

[jira] Updated: (GERONIMO-3913) NPE in org.apache.geronimo.security.SubjectId.hashCode() caused by incorrect JAVA_HOME or JRE_HOME

2008-03-31 Thread toby cabot (JIRA)
[ https://issues.apache.org/jira/browse/GERONIMO-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] toby cabot updated GERONIMO-3913: - Patch Info: [Patch Available] NPE in org.apache.geronimo.security.SubjectId.hashCode()