Invalid authentication attempt, principal=null error...

[pkorros]

Our production server after running for many weeks without problems, suddenly started to throw the following SecurityException every time the system tries to connect to a jms queue.
A reboot solved the problem but i am trying to find a better solution.

I had the same problem before, when running with JBossMQ but I was able to solve it by disabling the SecurityInterceptor in the jbossmq-service.xml.

Can this be done with the JBoss Messaging implementation?


java.lang.SecurityException: Invalid authentication attempt, principal=null
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getSubject(BaseConnectionManager2.java:589)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:395)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:389)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:144)

[clebert.suconic]

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.

[pkorros]

Thanks for your reply,

I will try to increase the jaas default cache timeout and see what happens.

[clebert.suconic]

I would advice you to use the Database.

[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?

[clebert.suconic]

Any ideas, please?

Trace Logs?
Testcase replicating the issue?

[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.

[clebert.suconic]

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.