You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Karsten Voges (JIRA)" <de...@geronimo.apache.org> on 2006/02/08 13:17:00 UTC
[jira] Created: (GERONIMO-1602) Switching from Tomcat causes error
in JAAS module: "Unable to instantiate login module"
Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
---------------------------------------------------------------------------------------
Key: GERONIMO-1602
URL: http://issues.apache.org/jira/browse/GERONIMO-1602
Project: Geronimo
Type: Bug
Components: security, Tomcat
Versions: 1.0
Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
Reporter: Karsten Voges
Attachments: geronimo-JAAS-login-error.txt
I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
For Tomcat I do the following:
in catalina.properties I set
#######JAAS
java.security.auth.login.config=${catalina.base}/conf/login.config
and the login.config looks like this:
MyApp {
de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
};
I tried to use a special geronimo-web.xml where I set the
<context-priority-classloader>true</context-priority-classloader>
But I still get the same error:
javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
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-1602) Switching from Tomcat causes error
in JAAS module: "Unable to instantiate login module"
Posted by "Karsten Voges (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1602?page=all ]
Karsten Voges updated GERONIMO-1602:
------------------------------------
Attachment: geronimo-JAAS-login-error.txt
> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1602
> URL: http://issues.apache.org/jira/browse/GERONIMO-1602
> Project: Geronimo
> Type: Bug
> Components: security, Tomcat
> Versions: 1.0
> Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
> Reporter: Karsten Voges
> Attachments: geronimo-JAAS-login-error.txt
>
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
> de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
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] Commented: (GERONIMO-1602) Switching from Tomcat causes
error in JAAS module: "Unable to instantiate login module"
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1602?page=comments#action_12426363 ]
Aaron Mulder commented on GERONIMO-1602:
----------------------------------------
The issue that David Jencks was talking about was resolved in Geronimo 1.1. But I'm not sure how adding the classes to the web application will help make them available to the security realm. Karsten, can you confirm whether you still have a problem in Geronimo 1.1?
> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1602
> URL: http://issues.apache.org/jira/browse/GERONIMO-1602
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security, Tomcat
> Affects Versions: 1.0
> Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
> Reporter: Karsten Voges
> Attachments: geronimo-JAAS-login-error.txt
>
>
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
> de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
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] Commented: (GERONIMO-1602) Switching from Tomcat causes
error in JAAS module: "Unable to instantiate login module"
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1602?page=comments#action_12450348 ]
Vamsavardhana Reddy commented on GERONIMO-1602:
-----------------------------------------------
I have tested the following scenario in server built from branches\1.1.
I have created a login module (MyOwnLoginModule) & a principal class (MyPrincipal) and placed the jar in WEB-INF\lib directory. I have added a security realm gbean to geronimo-web.xml and configured the application to authenticate against this realm. The application deploys and runs fine. If I use GeronimoUserPrincipal in the login-module class and in role-mapping the security part works fine. Problem is with using "MyPrincipal". The login is succeeding, but, the authorization is not working as expected. I guess the problem is due to classLoaders.
Having the loginmodule and principal classess in WEB-INF\classes dir or in a jar under WEB-INF\lib did not make a difference.
> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1602
> URL: http://issues.apache.org/jira/browse/GERONIMO-1602
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security, Tomcat
> Affects Versions: 1.0
> Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
> Reporter: Karsten Voges
> Fix For: 1.1.x
>
> Attachments: geronimo-JAAS-login-error.txt
>
>
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
> de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
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] Commented: (GERONIMO-1602) Switching from Tomcat causes
error in JAAS module: "Unable to instantiate login module"
Posted by "Karsten Voges (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1602?page=comments#action_12365559 ]
Karsten Voges commented on GERONIMO-1602:
-----------------------------------------
thanks for clarifying and providing a workaround. Still, I am looking forward to a general solution.
> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1602
> URL: http://issues.apache.org/jira/browse/GERONIMO-1602
> Project: Geronimo
> Type: Bug
> Components: security, Tomcat
> Versions: 1.0
> Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
> Reporter: Karsten Voges
> Attachments: geronimo-JAAS-login-error.txt
>
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
> de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
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] Commented: (GERONIMO-1602) Switching from Tomcat causes
error in JAAS module: "Unable to instantiate login module"
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1602?page=comments#action_12454590 ]
Vamsavardhana Reddy commented on GERONIMO-1602:
-----------------------------------------------
In continuation to my previous comment, I tried loading MyPrincipal in the same classloader as GeronimoUserPrincipal. Even that didn't help :o( I am sure it is a classloader problem. The code where the principals are to be matched has problems. I have put a println() in MyPrincipal.equals() method but it was never called. I think the principal is getting rejected even before the name is to be compared.
> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1602
> URL: http://issues.apache.org/jira/browse/GERONIMO-1602
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security, Tomcat
> Affects Versions: 1.0
> Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
> Reporter: Karsten Voges
> Fix For: 1.1.x
>
> Attachments: geronimo-JAAS-login-error.txt
>
>
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
> de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
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] Closed: (GERONIMO-1602) Switching from Tomcat causes error
in JAAS module: "Unable to instantiate login module"
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-1602.
----------------------------------
Resolution: Cannot Reproduce
I think the code and classloaders surrounding this problem have changed enough so that the report is no longer relvant. No one seems to have complained about similar problems recently.
> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1602
> URL: https://issues.apache.org/jira/browse/GERONIMO-1602
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security, Tomcat
> Affects Versions: 1.0
> Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
> Reporter: Karsten Voges
> Fix For: 1.1.x
>
> Attachments: geronimo-JAAS-login-error.txt
>
>
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
> de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-1602) Switching from Tomcat causes error
in JAAS module: "Unable to instantiate login module"
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1602?page=all ]
Aaron Mulder updated GERONIMO-1602:
-----------------------------------
Fix Version/s: 1.1.x
> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1602
> URL: http://issues.apache.org/jira/browse/GERONIMO-1602
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security, Tomcat
> Affects Versions: 1.0
> Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
> Reporter: Karsten Voges
> Fix For: 1.1.x
>
> Attachments: geronimo-JAAS-login-error.txt
>
>
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
> de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
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] Commented: (GERONIMO-1602) Switching from Tomcat causes
error in JAAS module: "Unable to instantiate login module"
Posted by "Karsten Voges (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522986 ]
Karsten Voges commented on GERONIMO-1602:
-----------------------------------------
Sorry for not replying earlier. I have switched companies, so I cannot test the problem anymore. Sorry.
> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1602
> URL: https://issues.apache.org/jira/browse/GERONIMO-1602
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security, Tomcat
> Affects Versions: 1.0
> Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
> Reporter: Karsten Voges
> Fix For: 1.1.x
>
> Attachments: geronimo-JAAS-login-error.txt
>
>
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
> de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-1602) Switching from Tomcat causes
error in JAAS module: "Unable to instantiate login module"
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1602?page=comments#action_12365557 ]
David Jencks commented on GERONIMO-1602:
----------------------------------------
This is a known problem, that gbeans in a web plan cannot use the classes in the war, and in fact the war classes are not in the configuration classloader. The only solution at the moment is to move or copy the classes to a jar outside the war and use a dependency element to that jar in the plan that contains the login gbeans.
We might be able to solve this problem in the 1.1 release but the code is not yet written.
See GERONIMO-289
> Switching from Tomcat causes error in JAAS module: "Unable to instantiate login module"
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1602
> URL: http://issues.apache.org/jira/browse/GERONIMO-1602
> Project: Geronimo
> Type: Bug
> Components: security, Tomcat
> Versions: 1.0
> Environment: Windows XP Prof, JDK 1.5.0_06, Geronimo 1.0 (Tomcat, .zip)
> Reporter: Karsten Voges
> Attachments: geronimo-JAAS-login-error.txt
>
> I have a problem with porting a Tomcat application to Geronimo. The error stacktrace is attached.
> I deployed the war without any deployment plan and the app seams to be working (JSPs work and the startup-servlet works as well)
> But the JAASLoginModule was missing, so I could not log in. -> so far no Problem!
> Afterwards I configured a security realm with the console and after a restart my app does not complain about a missing LoginModule but throws the attached error stacktrace.
> For Tomcat I do the following:
> in catalina.properties I set
> #######JAAS
> java.security.auth.login.config=${catalina.base}/conf/login.config
> and the login.config looks like this:
> MyApp {
> de.jato.security.auth.module.JatoServletLoginModule Sufficient loginServlet="/login/login.jsp";
> };
> I tried to use a special geronimo-web.xml where I set the
> <context-priority-classloader>true</context-priority-classloader>
> But I still get the same error:
> javax.security.auth.login.LoginException: org.apache.geronimo.common.GeronimoSecurityException: Unable to instantiate login module
> Caused by: java.lang.ClassNotFoundException: de.jato.security.auth.module.JatoServletLoginModule
> Am I doing something wrong? The class is in the war I deployed, and everything works fine in Tomcat.
--
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