1 Reply Latest reply on Apr 14, 2009 12:05 PM by Adrian Brock

    User: guest is NOT authenticated

    Chris Milburn Newbie

      We have 14 Jboss 4.2.2 systems running on the same server, at midnight they all simultaneously update their runDate in the database (Oracle) and occasionally (twice a week ?) they produce this error, any idea what might cause this ??
      The only thing I can think is some kind of limit to number of sessions connecting to the underlying oracle database.
      Thanks,
      Chris Milburn.

      [00:00:04,090,JMSHelper] sendMessageToQueue
      javax.jms.JMSException: Could not create a session: org.jboss.resource.JBossResourceException: Unable to setup connection; - nested throwable: (javax.jms.JMSSecurityException: User: guest is NOT authenticated) at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:403) at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:144) at com.rolfeandnolan.merlin.utility.jmshelper.JMSHelper.sendMessageToQueue(JMSHelper.java:159) at com.rolfeandnolan.merlin.ejb.eventmanager.EventManagerEJB.createEvent(EventManagerEJB.java:131) at sun.reflect.GeneratedMethodAccessor171.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at

        • 1. Re: User: guest is NOT authenticated
          Adrian Brock Master

          Since this is really a security problem, you'll want to enable TRACE logging
          for org.jboss.security to find out what the real error message is.

          "javax.jms.JMSSecurityException: User: guest is NOT authenticated"
          is just a generic error message. We don't want to help attackers know they've
          guessed a real user id by giving them too much detail in the error message. :-)

          GUESS: (you'd be better off asking in the security form once you know the real problem):

          JBossMQ authenticates users against a database table by default.

          Does changing the "runDate" also cause the connections to the database to become broken? e.g. because some 'timeout" processing is based on that date?

          If so, have you configured your datasource to check for invalid/broken connections?
          Or try flushing the pool of the datasource when you change the date.