2 Replies Latest reply on Jul 9, 2003 6:17 PM by blueser

    Problems regarding temporary queues + Security Problems

    lauerc

      Hi,

      I'm trying to port a application from WebLogic server to JBoss, everythings works fine by now, except of JMS.
      One thing is that whenever I'm trying to create a temporary queue I'm getting a warning like that:

      "No SecurityMetadadata was available for JMS_TQ2 adding default security conf"

      The other, more nasty thing is that from time to time
      JBoss starts to throw the following exception:

      "javax.jms.JMSSecurityException: User: null is NOT authenticated"

      There seems only one way to be to fix the problem: Restarting JBoss. I've tryed to explicitely set the authentification data by defining the mdb-user and mdb-passwd attributes in the jboss.xml configuration and the createQueueConnection method, but that doesn't help, now the exception is:

      "javax.jms.JMSSecurityException: User: guest is NOT authenticated"

      Has anyone an idea, what the problems are, and how to fix them?

      Best regards,
      Christian

        • 1. Re: Problems regarding temporary queues + Security Problems
          lauerc

          It seems the problem regarding the JMSSecurityException has been fixed in 3.2.2 RC1. I have thested our application on that release and could not reproduce the misbehaviour, great job guys!

          • 2. Re: Problems regarding temporary queues + Security Problems
            blueser

            Hi lauerc,

            we're having _the exact same_ problems you described. I am glad to hear that 3.2.2RC1 seemed to improve things, but I am a bit concerned about using a RC version -- this would go directly for production. What has been your experience with it so far?

            Also, have you experienced any side-effects with 3.2.1? I will try to explain here what is happenning:

            sometimes, our application simply starts generating errors to some specific requests that used to work just fine. When we check JBoss log, the errors seem to start piling up after the errors you report below. A side-effect to this is that http://[host]:8080/jmx-console doesn't show _anything_.

            Have you (or anybody else) been through anything similar?

            TIA

            Andre