-
1. Re: Invalid authentication attempt, principal=null error...
clebert.suconic Aug 8, 2008 3:39 PM (in response to pkorros)look at this thread here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=139025&postdays=0&postorder=asc&start=10
It seems related to me.
Try setting up your security config as mentioned on that thread. Maybe that would solve your problem. -
2. Re: Invalid authentication attempt, principal=null error...
pkorros Aug 13, 2008 3:13 AM (in response to pkorros)Thanks for your reply,
I will try to increase the jaas default cache timeout and see what happens. -
3. Re: Invalid authentication attempt, principal=null error...
clebert.suconic Aug 13, 2008 10:53 AM (in response to pkorros)I would advice you to use the Database.
-
4. Re: Invalid authentication attempt, principal=null error...
pkorros Sep 16, 2008 5:20 AM (in response to pkorros)hi,
I changed the jboss messaging login configuration to use the database and despite that i am still getting the same exception ('java.lang.SecurityException: Invalid authentication attempt, principal=null') almost every day in our production server.
What should I try next? Any ideas, please? -
5. Re: Invalid authentication attempt, principal=null error...
clebert.suconic Sep 16, 2008 6:33 PM (in response to pkorros)Any ideas, please?
Trace Logs?
Testcase replicating the issue? -
6. Re: Invalid authentication attempt, principal=null error...
pkorros Sep 17, 2008 1:52 AM (in response to pkorros)I have tried in the past to consistently reproduce the problem without any success. The problem is random and sometimes it appears many times in a day and sometimes it takes weeks to appear.
I will enable tracing at the org.jboss.resource.connectionmanager package and see if this gives me any more insight in what is going wrong. -
7. Re: Invalid authentication attempt, principal=null error...
clebert.suconic Sep 17, 2008 10:42 AM (in response to pkorros)You should add trace on org.jboss.jms.server.plugin (for the JDBCJMSUserManagerService) and mainly org.jboss.security.
I *believe* there is something ignoring possible exceptions on org.jboss.security. Maybe some config is affecting it under load. (what about datasource limits?)
I'm hoping the trace on org.jboss.security would reveal any exceptions eaten.