10 Replies Latest reply on Jun 2, 2003 7:48 AM by Gary Ratcliffe

    JNDI problem on AIX 4.3

    paulgammon Newbie

      Hi, I'm having difficulty confirming that JMS is working
      in my 3.2.1 JBoss installation on AIX with Java 1.3.1. I
      have written a simple test application that fails
      looking up OIL2ConnectionFactory. The following
      exception is thrown

      Exception in thread "main" javax.naming.NameNotFoundException: OIL2ConnectionFactory not bound
      at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:257)
      at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:232)
      at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:135)
      at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471)
      at javax.naming.InitialContext.lookup(InitialContext.java:359)
      at end_to_end.initialiseJMS(end_to_end.java:57)
      at end_to_end.main(end_to_end.java:16)


      Examing JNDIView in the jmx-console seems to show
      that a portion of the global JNDI namespace is
      missing. It looks as if the list method errored midway
      through. Below is all that is display

      +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
      +- invokers (class: org.jnp.interfaces.NamingContext)
      | +- olympus (class: org.jnp.interfaces.NamingContext)
      | | +- pooled (class: org.jboss.invocation.pooled.interfaces.PooledInvokerProxy)
      | | +- jrmp (class: org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy)
      | | +- http (class: org.jboss.invocation.http.interfaces.HttpInvokerProxy)
      +- jmx:olympus:rmi (class: org.jboss.jmx.adaptor.rmi.RMIAdaptorImpl)
      +- console (class: org.jnp.interfaces.NamingContext)
      | +- PluginManager (proxy: $Proxy27 implements interface org.jboss.console.manager.PluginManagerMBean)
      +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory)
      +- UserTransactionSessionFactory (class: org.jboss.tm.usertx.server.UserTransactionSessionFactoryImpl)
      +- jmx (class: org.jnp.interfaces.NamingContext)
      | +- invoker (class: org.jnp.interfaces.NamingContext)
      | | +- RMIAdaptor (proxy: $Proxy21 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor)
      | +- rmi (class: org.jnp.interfaces.NamingContext)
      | | +- RMIAdaptor (class: org.jboss.jmx.adaptor.rmi.RMIAdaptorImpl)
      +- ejb (class: org.jnp.interfaces.NamingContext)
      | +- mgmt (class: org.jnp.interfaces.NamingContext)
      | | +- MEJB (proxy: $Proxy28 implements interface javax.management.j2ee.ManagementHome,interface javax.ejb.Handle)

      I have confirmed that this JBoss installation works in
      Solaris and HP-UX 1.3 Java environments so I believe
      the test application and installation are OK. Java 1.4 is
      not available on AIX 4.3 so this is not an option. I
      have also tried disabling the JIT compiler.

      Any help appreciated.

      Paul Gammon

        • 1. Re: JNDI problem on AIX 4.3
          Adrian Brock Master

          Have you check the server.log for errors
          during bootup?

          Regards,
          Adrian

          • 2. Re: JNDI problem on AIX 4.3
            paulgammon Newbie

            Thanks for the reply.

            There are a number of exceptions thrown on startup.
            Below is a list of exceptions and the facilities that
            raise them.

            java.util.zip.ZipException: error in opening zip file
            -----------------------------------------------------
            org.jboss.resource.connectionmanager.RARDeployment
            org.jboss.mail.MailService
            org.jboss.tm.TransactionManagerService
            org.jboss.jbossweb
            org.jboss.jetty.JettyService

            java.lang.SecurityException: Invalid authentication attempt, principal=null
            ---------------------------------------------------------------------------
            org.jboss.mq.pm.jdbc2.PersistenceManager
            org.jboss.system.ServiceController

            javax.jms.InvalidDestinationException: This destination is not open!
            --------------------------------------------------------------------
            org.jboss.mq.server.jmx.Topic.testTopic
            org.jboss.mq.server.jmx.Topic.securedTopic
            org.jboss.mq.server.jmx.Topic.testDurableTopic
            org.jboss.mq.server.jmx.Queue.testQueue

            javax.management.InstanceNotFoundException: jboss.management.local:J2EEApplication=jms,J2EEServer=Local,j2eeType=ResourceAdapterModule,name=jms-ra.rar is not registered.
            -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
            org.jboss.management.j2ee.ResourceAdapterModule

            I have also tried using 3.2.0. The JNDIView did
            worked correctly and the ConnectionFactory was
            located. However, my test application failed with

            Exception in thread "main" javax.jms.JMSSecurityException: User: null is NOT authenticated

            This has all worked on HP-UX and Solaris.

            Do you know of any issues with JBoss and AIX ?

            Many Thanks

            • 3. Re: JNDI problem on AIX 4.3
              Adrian Brock Master

              What is the first error,
              post the stacktrace.

              The ZipException suggests you have a
              corrupted jar file?
              Are you sure this isn't a warning caused by unpacked
              deployments?

              Regards,
              Adrian

              • 4. Re: JNDI problem on AIX 4.3
                paulgammon Newbie

                Hi, I'm confident this isn't any sort of file corruption.
                We develop on multiple Unix boxes with AIX being
                our main fileserver and Solaris and HP-UX sharing
                the same filesystems via NFS. So, the identical set of
                files work on Solaris and HP-UX but not AIX. Stack
                trace is below

                java.util.zip.ZipException: error in opening zip file
                at java.util.zip.ZipFile.open(Native Method)
                at java.util.zip.ZipFile.(ZipFile.java:127)
                at java.util.jar.JarFile.(JarFile.java:138)
                at java.util.jar.JarFile.(JarFile.java:80)
                at sun.misc.URLClassPath$JarLoader.getJarFile(URLClassPath.java:526)
                at sun.misc.URLClassPath$JarLoader.(URLClassPath.java:491)
                at sun.misc.URLClassPath$2.run(URLClassPath.java:287)
                at java.security.AccessController.doPrivileged(Native Method)
                at sun.misc.URLClassPath.getLoader(URLClassPath.java(Compiled Code))
                at sun.misc.URLClassPath.getLoader(URLClassPath.java(Compiled Code))
                at sun.misc.URLClassPath.getResource(URLClassPath.java(Compiled Code))
                at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java(Compiled Code))
                at java.security.AccessController.doPrivileged(Native Method)
                at java.net.URLClassLoader.findClass(URLClassLoader.java(Compiled Code))
                at org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:401)
                at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
                at org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:242)
                at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:114)
                at org.jboss.mx.loading.LoadMgr.nextTask(LoadMgr.java:281)
                at org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:181)
                at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
                at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:822)
                at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:294)
                at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:321)
                at org.jboss.system.ServiceCreator.install(ServiceCreator.java:85)
                at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:155)
                at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:118)
                at org.jboss.system.ServiceController.install(ServiceController.java:225)
                at java.lang.reflect.Method.invoke(Native Method)
                at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java(Compiled Code))
                at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java(Compiled Code))
                at $Proxy5.install(Unknown Source)
                at org.jboss.deployment.SARDeployer.create(SARDeployer.java:183)
                at org.jboss.deployment.MainDeployer.create(MainDeployer.java:784)
                at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:639)
                at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
                at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
                at java.lang.reflect.Method.invoke(Native Method)
                at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java(Compiled Code))
                at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java(Compiled Code))
                at $Proxy6.deploy(Unknown Source)
                at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
                at org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
                at org.jboss.Main.boot(Main.java:150)
                at org.jboss.Main$1.run(Main.java:388)
                at java.lang.Thread.run(Thread.java:512)

                Regards
                Paul Gammon

                • 5. Re: JNDI problem on AIX 4.3
                  Adrian Brock Master

                  There is no context in the trace,
                  what are the logging lines before and after?

                  Regards,
                  Adrian

                  • 6. Re: JNDI problem on AIX 4.3
                    paulgammon Newbie

                    Hi, stack trace and context below

                    Regards
                    Paul Gammon

                    ================================================================================

                    JBoss Bootstrap Environment

                    JBOSS_HOME: /olympus/home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1

                    JAVA: /usr/java131/bin/java

                    JAVA_OPTS: -Dprogram.name=run.sh

                    CLASSPATH: /olympus/home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/bin/run.jar:/usr/java131/lib/tools.jar

                    ================================================================================

                    13:46:41,870 INFO [Server] Starting JBoss (MX MicroKernel)...
                    13:46:41,932 INFO [Server] Release ID: JBoss [WonderLand] 3.2.1 (build: CVSTag=JBoss_3_2_1 date=200305041533)
                    13:46:41,933 INFO [Server] Home Dir: /home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1
                    13:46:41,934 INFO [Server] Home URL: file:/home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/
                    13:46:41,934 INFO [Server] Library URL: file:/home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/lib/
                    13:46:41,935 INFO [Server] Patch URL: null
                    13:46:41,935 INFO [Server] Server Name: default
                    13:46:41,935 INFO [Server] Server Home Dir: /home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/server/default
                    13:46:41,936 INFO [Server] Server Home URL: file:/home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/server/default/
                    13:46:41,936 INFO [Server] Server Data Dir: /home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/server/default/data
                    13:46:41,936 INFO [Server] Server Temp Dir: /home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/server/default/tmp
                    13:46:41,936 INFO [Server] Server Config URL: file:/home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/server/default/conf/
                    13:46:41,936 INFO [Server] Server Library URL: file:/home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/server/default/lib/
                    13:46:41,937 INFO [Server] Root Deployemnt Filename: jboss-service.xml
                    13:46:41,940 INFO [Server] Starting General Purpose Architecture (GPA)...
                    13:46:43,074 INFO [ServerInfo] Java version: 1.3.1,IBM Corporation
                    13:46:43,075 INFO [ServerInfo] Java VM: Classic VM 1.3.1,IBM Corporation
                    13:46:43,075 INFO [ServerInfo] OS-System: AIX 4.3,ppc
                    13:46:43,123 INFO [ServiceController] Controller MBean online
                    13:46:43,539 INFO [MainDeployer] Creating
                    13:46:43,997 INFO [MainDeployer] Created
                    13:46:43,998 INFO [MainDeployer] Starting
                    13:46:43,998 INFO [MainDeployer] Started
                    13:46:44,163 INFO [JARDeployer] Creating
                    13:46:44,192 INFO [JARDeployer] Created
                    13:46:44,193 INFO [JARDeployer] Starting
                    13:46:44,193 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeployer@3bd37846
                    13:46:44,193 INFO [JARDeployer] Started
                    13:46:44,202 INFO [SARDeployer] Creating
                    13:46:44,264 INFO [SARDeployer] Created
                    13:46:44,265 INFO [SARDeployer] Starting
                    13:46:44,265 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeployer@1ad0f846
                    13:46:44,307 INFO [SARDeployer] Started
                    13:46:44,308 INFO [Server] Core system initialized
                    13:46:44,317 INFO [MainDeployer] Starting deployment of package: file:/home2/prcg/work/r4.3/jms/jboss/jboss-3.2.1/server/default/conf/jboss-service.xml
                    java.util.zip.ZipException: error in opening zip file
                    at java.util.zip.ZipFile.open(Native Method)
                    at java.util.zip.ZipFile.(ZipFile.java:127)
                    at java.util.jar.JarFile.(JarFile.java:138)
                    at java.util.jar.JarFile.(JarFile.java:80)
                    at sun.misc.URLClassPath$JarLoader.getJarFile(URLClassPath.java:526)
                    at sun.misc.URLClassPath$JarLoader.(URLClassPath.java:491)
                    at sun.misc.URLClassPath$2.run(URLClassPath.java:287)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at sun.misc.URLClassPath.getLoader(URLClassPath.java(Compiled Code))
                    at sun.misc.URLClassPath.getLoader(URLClassPath.java(Compiled Code))
                    at sun.misc.URLClassPath.getResource(URLClassPath.java(Compiled Code))
                    at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java(Compiled Code))
                    at java.security.AccessController.doPrivileged(Native Method)
                    at java.net.URLClassLoader.findClass(URLClassLoader.java(Compiled Code))
                    at org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:401)
                    at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
                    at org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:242)
                    at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:114)
                    at org.jboss.mx.loading.LoadMgr.nextTask(LoadMgr.java:281)
                    at org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:181)
                    at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
                    at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:822)
                    at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:294)
                    at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:321)
                    at org.jboss.system.ServiceCreator.install(ServiceCreator.java:85)
                    at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:155)
                    at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:118)
                    at org.jboss.system.ServiceController.install(ServiceController.java:225)
                    at java.lang.reflect.Method.invoke(Native Method)
                    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java(Compiled Code))
                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java(Compiled Code))
                    at $Proxy5.install(Unknown Source)
                    at org.jboss.deployment.SARDeployer.create(SARDeployer.java:183)
                    at org.jboss.deployment.MainDeployer.create(MainDeployer.java:784)
                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:639)
                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
                    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
                    at java.lang.reflect.Method.invoke(Native Method)
                    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java(Compiled Code))
                    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java(Compiled Code))
                    at $Proxy6.deploy(Unknown Source)
                    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
                    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
                    at org.jboss.Main.boot(Main.java:150)
                    at org.jboss.Main$1.run(Main.java:388)
                    at java.lang.Thread.run(Thread.java:512)
                    13:46:50,007 INFO [Log4jService] Creating
                    13:46:50,010 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
                    13:46:54,112 INFO [Log4jService] Created
                    13:46:54,114 INFO [WebService] Creating
                    13:46:54,116 INFO [WebService] Created
                    13:46:54,123 INFO [LocalJBossServerDomain] Creating
                    13:46:54,148 INFO [LocalJBossServerDomain] Created
                    13:46:54,149 INFO [NamingService] Creating
                    13:46:54,149 INFO [NamingService] Created
                    13:46:54,225 INFO [JNDIView] Creating
                    13:46:54,225 INFO [JNDIView] Created
                    13:46:54,226 INFO [SecurityConfig] Creating
                    13:46:54,226 INFO [SecurityConfig] Created
                    13:46:54,227 INFO [XMLLoginConfig] Creating
                    13:46:54,227 INFO [XMLLoginConfig] Created
                    13:46:54,228 INFO [JaasSecurityManagerService] Creating
                    13:46:54,228 INFO [JaasSecurityManagerService] Created
                    13:46:54,229 INFO [EARDeployer] Creating
                    13:46:54,240 INFO [EARDeployer] Created
                    13:46:54,241 INFO [BeanShellSubDeployer] Creating
                    13:46:54,270 INFO [BeanShellSubDeployer] Created
                    13:46:54,271 INFO [URLDeploymentScanner] Creating
                    13:46:54,284 INFO [AbstractDeploymentScanner$ScannerThread] Running
                    13:46:54,285 INFO [URLDeploymentScanner] Created
                    13:46:54,318 INFO [Log4jService] Starting
                    13:46:54,318 INFO [Log4jService] Started
                    13:46:54,319 INFO [WebService] Starting
                    13:46:54,347 INFO [WebService] Started WebServer with address: 10.1.11.12:8083
                    13:46:54,347 INFO [WebService] Using RMI server codebase: http://olympus:8083/
                    13:46:54,347 INFO [WebService] Started
                    13:46:54,348 INFO [LocalJBossServerDomain] Starting
                    13:46:54,348 INFO [LocalJBossServerDomain] Started
                    13:46:54,370 INFO [NamingService] Starting
                    13:46:54,372 INFO [NamingService] Starting jnp server

                    • 7. Re: JNDI problem on AIX 4.3
                      Adrian Brock Master

                      It still doesn't show the jar file with the problem.
                      Try looking in server/default/log/server.log
                      for debug messages.

                      Regards,
                      Adrian

                      • 8. Re: JNDI problem on AIX 4.3
                        alan shields Newbie

                        I've just come up against what I believe is a related problem under AIX.

                        Basically using a configuration that run's fine under OSX when I run on a particular AIX system I get the following in the server.log file

                        2003-05-30 14:37:50,213 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Re
                        connect failed: JMS provider failure detected
                        javax.jms.JMSSecurityException: User: null is NOT authenticated
                        at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.ja
                        va:181)
                        at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSe
                        curityInterceptor.java:40)
                        at org.jboss.mq.server.TracingInterceptor.authenticate(TracingIntercepto
                        r.java:589)
                        at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.ja
                        va(Compiled Code))
                        at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:302)
                        at org.jboss.mq.Connection.authenticate(Connection.java:759)
                        at org.jboss.mq.Connection.(Connection.java:233)
                        at org.jboss.mq.Connection.(Connection.java:264)
                        at org.jboss.mq.SpyConnection.(SpyConnection.java:59)
                        at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnection
                        Factory.java:116)
                        at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:12
                        5)
                        at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java(
                        Compiled Code))
                        at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContaine
                        rInvoker.java(Compiled Code))
                        at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.o
                        nException(JMSContainerInvoker.java(Compiled Code))
                        at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.o
                        nException(JMSContainerInvoker.java(Compiled Code))
                        at org.jboss.ejb.plugins.jms.JMSContainerInvoker$1.run(JMSContainerInvok
                        er.java:835)


                        This repeats every 5-10 seconds until I shut down jboss.

                        As far as I can tell whichever SubjectSecurityManager is obtained by org.jboss.mq.security.SecurityManager seems to be returning false for isValid(principal,passwordChars) when principal is null.

                        I'm assuming that principal=null is correct as org.jboss.mq.Connection calls authenticate with username and password null.

                        Any body else seen/solved this before?

                        As an aside the reason I was playing on this particular AIX machine was an attempt to reproduce a problem whereby JNDI failed if /etc/hosts contained an invalid entry for the name returned by the hostname command. (due to the way HACMP was set up) As far As I can tell jboss calls gethostname and then looks up that name in order to connect to JNDI. Any idea why it can't just lookup and connect to "localhost"?

                        • 9. Re: JNDI problem on AIX 4.3
                          Adrian Brock Master

                          These problems are unrelated except
                          thay are both in AIX.

                          The first shows a corrupted jar file,
                          the second that you are trying to use
                          an anonymous connection.

                          You'll need something like the following
                          in jboss.xml for the mdb.

                          <message-driven>
                          <ejb-name>DurableTopicBean</ejb-name>
                          <destination-jndi-name>topic/testDurableTopic</destination-jndi-name>
                          <mdb-user>john</mdb-user>
                          <mdb-passwd>needle</mdb-passwd>
                          <mdb-subscription-id>DurableSubscriberExample</mdb-subscription-id>
                          </message-driven>

                          Regards,
                          Adrian

                          • 10. Re: JNDI problem on AIX 4.3
                            Gary Ratcliffe Newbie

                            I've been looking at the security related and ZIP exception problems inconjunction with Paul, the original poster (we work at the same company).

                            With regards to the security problem:
                            This is being caused by a conflict with the IBM installed JAAS support. Our installation is IBM's JVM 1.3.1 for AIX 4.3 with the (optional) JAAS jar's present in the JRE ext directory.

                            If you enabled tracing for security within JBOSS you will get some additional information:


                            javax.security.auth.login.LoginException: unable to find LoginModule class: org.jboss.resource.security.ConfiguredIdentityLoginModule
                            at javax.security.auth.login.LoginContext.invoke(LoginContext.java:643)
                            at javax.security.auth.login.LoginContext.access$000(LoginContext.java:124)
                            at javax.security.auth.login.LoginContext$3.run(LoginContext.java:543)
                            at java.security.AccessController.doPrivileged(Native Method)
                            .....

                            I believe this is because the IBM JAAS classes that are trying to load the login module are only looking in the JRE lib and ext directories.

                            This causes a number of problems including the default datasource using hypersonic.

                            If the IBM JAAS support is removed everything is fine.

                            I've seen some other reports of this problem on the JBoss forums and on other web sites.

                            With regards to the ZIP file problem. It is highly unlikely that the JAR's are corrupt since they work on all the other platforms. I've have seen reports of problems with the IBM JRE and ZIPExceptions but nothing conclusive. One suggestion is that IBM are throwing a ZIPException for a condition that Sun throw a IOException for.


                            Note: The testing we have been doing is with the same set of JBoss files and configurations on a number of different platforms.