1 2 3 Previous Next 36 Replies Latest reply on Oct 2, 2009 11:31 AM by peterj

    Unauthenticated caller null N sqlException

      Hi All
      I have JBoss 5.1.0 GA and I want to connect the DB2 database.
      I have made the required changes in db2-ds.xml,hsqldb-persistance-service.xml,web.xml.
      But wen I run the run.bat .........it shows the folowing errors..
      Please can u help me.......how to avoid these errors....(these are associasted with the JAAS)

      Thanks in advance..



      DEPLOYMENTS MISSING DEPENDENCIES:
      Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentMan
      ager,service=EJB3_endpoint" is missing the following dependencies:
      Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentM
      anager,service=EJB3" (should be in state "Configured", but is actually in state
      "**ERROR**")
      Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementVie
      w,service=EJB3_endpoint" is missing the following dependencies:
      Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementV
      iew,service=EJB3" (should be in state "Configured", but is actually in state "**
      ERROR**")
      Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileServic
      e,service=EJB3" is missing the following dependencies:
      Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecurePr
      ofileService,service=EJB3>" (should be in state "Described", but is actually in
      state "** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deploye
      rs.spi.management.ManagementView' **")
      Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileServic
      e,service=EJB3_endpoint" is missing the following dependencies:
      Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileServ
      ice,service=EJB3" (should be in state "Configured", but is actually in state "Pr
      eInstall")
      Deployment "jboss.jca:name=JmsXA,service=ConnectionFactoryBinding" is missing
      the following dependencies:
      Dependency "jboss.jca:name=JmsXA,service=TxCM" (should be in state "Create",
      but is actually in state "Configured")
      Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" is missing
      the following dependencies:
      Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create"
      , but is actually in state "Configured")
      Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionPool" is missing the
      following dependencies:
      Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" (should b
      e in state "Create", but is actually in state "Configured")
      Deployment "jboss.jca:name=JmsXA,service=TxCM" is missing the following depend
      encies:
      Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionPool" (should be i
      n state "Create", but is actually in state "Configured")
      Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFac
      tory" is missing the following dependencies:
      Dependency "jboss.messaging:service=PostOffice" (should be in state "Create"
      , but is actually in state "Configured")
      Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create"
      , but is actually in state "Configured")
      Deployment "jboss.messaging.connectionfactory:service=ClusteredConnectionFacto
      ry" is missing the following dependencies:
      Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create"
      , but is actually in state "Configured")
      Dependency "jboss.messaging:service=PostOffice" (should be in state "Create"
      , but is actually in state "Configured")
      Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" is mi
      ssing the following dependencies:
      Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create"
      , but is actually in state "Configured")
      Dependency "jboss.messaging:service=PostOffice" (should be in state "Create"
      , but is actually in state "Configured")
      Deployment "jboss.messaging.destination:name=DLQ,service=Queue" is missing the
      following dependencies:
      Dependency "jboss.messaging:service=PostOffice" (should be in state "Create"
      , but is actually in state "Configured")
      Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create"
      , but is actually in state "Configured")
      Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is mis
      sing the following dependencies:
      Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create"
      , but is actually in state "Configured")
      Dependency "jboss.messaging:service=PostOffice" (should be in state "Create"
      , but is actually in state "Configured")
      Deployment "jboss.messaging:service=PostOffice" is missing the following depen
      dencies:
      Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create"
      , but is actually in state "Configured")
      Deployment "jboss.messaging:service=ServerPeer" is missing the following depen
      dencies:
      Dependency "jboss.messaging:service=PersistenceManager" (should be in state
      "Create", but is actually in state "**ERROR**")
      Deployment "jboss.mq:service=DestinationManager" is missing the following depe
      ndencies:
      Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create"
      , but is actually in state "Configured")

      DEPLOYMENTS IN ERROR:
      Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentMan
      ager,service=EJB3" is in error due to the following reason(s): **ERROR**, java.l
      ang.SecurityException: Unauthenticated caller:null
      Deployment "jboss:service=KeyGeneratorFactory,type=HiLo" is in error due to th
      e following reason(s): java.lang.SecurityException: Unauthenticated caller:null
      Deployment "jboss.messaging:service=PersistenceManager" is in error due to the
      following reason(s): **ERROR**, java.sql.SQLException: java.lang.UnsatisfiedLin
      kError: no db2jdbc in java.library.path
      Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProf
      ileService,service=EJB3>" is in error due to the following reason(s): ** UNRESOL
      VED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management
      .ManagementView' **
      Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementVie
      w,service=EJB3" is in error due to the following reason(s): **ERROR**, java.lang
      .SecurityException: Unauthenticated caller:null

        • 1. Re: Unauthenticated caller null N sqlException
          peterj

          Why did you modify hsqldb-persistance-service.xml? Are you try to use DB2 for DefaultDS? You do not have to do that just to use DB2 in your app - all you need is the db2-ds.xml file.

          **ERROR**, java.sql.SQLException: java.lang.UnsatisfiedLin
          kError: no db2jdbc in java.library.path


          Did you place the DB2 JDBC JAR file in common/lib?

          Also, what you posted is from the deployment report printed after deployment is complete - this information is not as helpful as the first exception stack trace in the console log, though you will have to either redirect stdout to a file or increase your command line buffer size (mine is at 9000 lines) to prevent the log from scrolling off the buffer.

          Also, please do not color large blocks of text.

          • 2. Re: Unauthenticated caller null N sqlException

            U mean that I should not make any changes in the hsqldb-persistence-service.xml. And the changes should be -ds.xml. fine.........


            And I have placed the all the jars in default/lib. Is it necessory to put it in the common/lib as well..?

            • 3. Re: Unauthenticated caller null N sqlException
              peterj

              Placing the JDBC driver JAR files in server/default/lib is acceptable.

              Wait a minute, I re-read the error mesage. Looks like you are not use a type-4 JDBC driver (pure Java), that instead you are using a type-2 (requires native C library). In that case you must either change your PATH (Windows) or LD_LIBRARY_PATH (Linux) env var to include the directory containing the C library required by the driver.

              • 4. Re: Unauthenticated caller null N sqlException

                Yhank You Peter

                The sqlException has gone(its dead)....as you said path was missing.

                But rest 3 errors are "Unauthenticated caller: null" are still live. so can u look into it...suggest me what might be the problem. Its urgent please...

                • 5. Re: Unauthenticated caller null N sqlException
                  peterj

                  Try this. In a clean JBoss AS installation, add your db2-ds.xml file to the server/default/deploy directory and that start the app server and see if you get any errors. (I suspect that you changed some other file that is causing the security issue - starting with a clean copy of JBoss AS should clear that up.) If this also causes an error. do another clean install of JBoss AS and run it (without adding your db2-ds.xml file).

                  • 6. Re: Unauthenticated caller null N sqlException

                    Hi Peter

                    Hey........it worked....:-)

                    No error messages.....Only I made changes in the db2-ds.xml(bold letters). This is my xml file

                    -------------------

                    <?xml version="1.0" encoding="UTF-8"?>

                    <!-- ===================================================================== -->
                    <!-- -->
                    <!-- JBoss Server Configuration -->
                    <!-- -->
                    <!-- ===================================================================== -->

                    <!-- See http://www.jboss.org/community/wiki/Multiple1PC for information about local-tx-datasource -->
                    <!-- $Id: db2-ds.xml 88948 2009-05-15 14:09:08Z jesper.pedersen $ -->



                    <local-tx-datasource>
                    <jndi-name>V320MCLDEV</jndi-name>
                    <connection-url>jdbc:db2://172.20.1.196:50000:V320MCLDEV</connection-url>

                    <!-- DB2 Universal Driver Note connection URL is in form of
                    jdbc:db2://host:port:dbname

                    Default port for Type 4 driver is 50000

                    Note, host and port must be specified if using Type 4 driver. And be forewarned, no native
                    XA support is provided with Type 4; you must set a DB property calling for Type 2 to get XA

                    <driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>
                    <connection-url>jdbc:db2://[hostname]:[port]/databasename"</connection-url>

                    Please see http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0512kokkat/
                    or the DB2 JDBC application developers manual.
                    -->

                    <driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>
                    <user-name>Mydb2username</user-name>
                    Password
                    <min-pool-size>0</min-pool-size>

                    <!-- New org.jboss.resource.adapter.jdbc.vendor.DB2ExceptionSorter

                    <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DB2ExceptionSorter</exception-sorter-class-name>

                    -->

                    <!-- sql to call when connection is created
                    <new-connection-sql>some arbitrary sql</new-connection-sql>
                    -->

                    <!-- sql to call on an existing pooled connection when it is obtained from pool
                    <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
                    -->

                    <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->



                    <type-mapping>DB2</type-mapping>

                    </local-tx-datasource>



                    ----------------------------------------------------------

                    and I want to check for the deployment...I have deploy.ear folder in the server/default/deploy/ which has ear(jar+war).

                    1. shall I place one jsp file in ear and restart the server ?and I should get it wen I give the appropriate url. Is it how I should check for the deployment..?

                    2. changes in the db2.ds.xml are enough to connect to db2 database
                    or any other changes have to be done..?

                    Peter...Please help...

                    • 7. Re: Unauthenticated caller null N sqlException
                      peterj

                      Please do not use large blocks of bold or colored text. That kind of highlighting should be reserved for pointing out specific items (like you did for the things you changed in the *-ds.xml file). Also, use the 'code' tags when posting xml text.

                      2) Maybe. If your settings are correct, that is all you need. But you will not know that until the first time your app attempts to get a connection.

                      1) Place the whole EAR (jar+war) into the deploy directory. Then start the app server. If you get any exceptions, post the full stack trace for only the first exception. And don't bold or color anything!

                      • 8. Re: Unauthenticated caller null N sqlException

                        Hi Peter

                        Sorry for using the large block and colored text.

                        After starting the server I have given the following URL

                        URL:
                        http://localhost:8080/V320DEV/UAD028.jsp

                        And It gave me 404 message,even though UAD028.jsp is present in my EAR.

                        HTTP Status 404 - /V320DEV/UAD028.jsp

                        --------------------------------------------------------------------------------

                        type Status report

                        message /V320DEV/UAD028.jsp

                        description The requested resource (/V320DEV/UAD028.jsp) is not available.


                        --------------------------------------------------------------------------------

                        JBoss Web/2.1.3.GA


                        What may be the problem....?


                        • 9. Re: Unauthenticated caller null N sqlException
                          peterj

                          1) What is the name of the WAR file?

                          2) Are you setting the context name in application.xml? If so, what are you setting it to?

                          3) Are you setting the context name in jboss-web.xml? If so, what are you setting it to?

                          4) Where is the UAD028.jsp file located within the WAR file?

                          • 10. Re: Unauthenticated caller null N sqlException

                            Hi Peter

                            1) What is the name of the WAR file?
                            =MCAppWAR.war

                            2) Are you setting the context name in application.xml? If so, what are you setting it to?
                            =Yes..I am setting it to V320dev


                            3) Are you setting the context name in jboss-web.xml? If so, what are you setting it to?
                            =NO..I have not set..

                            C:\Jboss 5.1.0\jboss-5.1.0.GA\server\default\deploy\admin- console.war\WEB-INF\jboss-web.xml
                            <context-root>admin-console</context-root>

                            C:\Jboss 5.1.0\jboss-5.1.0.GA\server\default\deploy\jmx-console.war\WEB-INF\jboss-web.xml
                            NO context root is present

                            4) Where is the UAD028.jsp file located within the WAR file?
                            = MCAppWAR.war/UAD/UAD028.jsp

                            • 11. Re: Unauthenticated caller null N sqlException
                              peterj

                              The URL should be http://localhost:8080/V320dev/UAD/UAD028.jsp

                              Also, URLs tend to be case-sensitive.

                              • 12. Re: Unauthenticated caller null N sqlException

                                Hi Peter.

                                yestrday when I run the run.bat ..... it has stopped at initialising recovery manager...did not proceed further.. (which was perfectly running showing the msg"sercer started successfully" )

                                Even I tried once restarting the system..still the same..
                                What might be the problem....I did not made any changes...

                                Calling C:\Jboss 5.1.0\jboss-5.1.0.GA\bin\run.conf.bat
                                ===============================================================================

                                JBoss Bootstrap Environment

                                JBOSS_HOME: C:\Jboss 5.1.0\jboss-5.1.0.GA

                                JAVA: C:\jdk1.5.0\bin\java

                                JAVA_OPTS: -Dprogram.name=run.bat -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun
                                .rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg
                                .jboss.resolver.warning=true -server

                                CLASSPATH: C:\Jboss 5.1.0\jboss-5.1.0.GA\bin\run.jar

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

                                14:32:21,785 INFO [ServerImpl] Starting JBoss (Microcontainer)...
                                14:32:21,896 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build:
                                SVNTag=JBoss_5_1_0_GA date=200905221053)
                                14:32:21,896 INFO [ServerImpl] Bootstrap URL: null
                                14:32:21,912 INFO [ServerImpl] Home Dir: C:\Jboss 5.1.0\jboss-5.1.0.GA
                                14:32:21,912 INFO [ServerImpl] Home URL: file:/C:/Jboss%205.1.0/jboss-5.1.0.GA/

                                14:32:21,912 INFO [ServerImpl] Library URL: file:/C:/Jboss%205.1.0/jboss-5.1.0.
                                GA/lib/
                                14:32:22,055 INFO [ServerImpl] Patch URL: null
                                14:32:22,118 INFO [ServerImpl] Common Base URL: file:/C:/Jboss%205.1.0/jboss-5.
                                1.0.GA/common/
                                14:32:22,213 INFO [ServerImpl] Common Library URL: file:/C:/Jboss%205.1.0/jboss
                                -5.1.0.GA/common/lib/
                                14:32:22,324 INFO [ServerImpl] Server Name: default
                                14:32:22,372 INFO [ServerImpl] Server Base Dir: C:\Jboss 5.1.0\jboss-5.1.0.GA\s
                                erver
                                14:32:22,483 INFO [ServerImpl] Server Base URL: file:/C:/Jboss%205.1.0/jboss-5.
                                1.0.GA/server/
                                14:32:22,578 INFO [ServerImpl] Server Config URL: file:/C:/Jboss%205.1.0/jboss-
                                5.1.0.GA/server/default/conf/
                                14:32:22,689 INFO [ServerImpl] Server Home Dir: C:\Jboss 5.1.0\jboss-5.1.0.GA\s
                                erver\default
                                14:32:22,784 INFO [ServerImpl] Server Home URL: file:/C:/Jboss%205.1.0/jboss-5.
                                1.0.GA/server/default/
                                14:32:22,895 INFO [ServerImpl] Server Data Dir: C:\Jboss 5.1.0\jboss-5.1.0.GA\s
                                erver\default\data
                                14:32:22,990 INFO [ServerImpl] Server Library URL: file:/C:/Jboss%205.1.0/jboss
                                -5.1.0.GA/server/default/lib/
                                14:32:23,086 INFO [ServerImpl] Server Log Dir: C:\Jboss 5.1.0\jboss-5.1.0.GA\se
                                rver\default\log
                                14:32:23,197 INFO [ServerImpl] Server Native Dir: C:\Jboss 5.1.0\jboss-5.1.0.GA
                                \server\default\tmp\native
                                14:32:23,292 INFO [ServerImpl] Server Temp Dir: C:\Jboss 5.1.0\jboss-5.1.0.GA\s
                                erver\default\tmp
                                14:32:23,450 INFO [ServerImpl] Server Temp Deploy Dir: C:\Jboss 5.1.0\jboss-5.1
                                .0.GA\server\default\tmp\deploy
                                14:32:34,013 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/J
                                boss%205.1.0/jboss-5.1.0.GA/server/default/conf/bootstrap.xml
                                14:32:40,420 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.pl
                                ugins.cache.CombinedVFSCache]
                                14:32:40,531 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache
                                : null]]
                                14:32:42,879 INFO [CopyMechanism] VFS temp dir: C:\Jboss 5.1.0\jboss-5.1.0.GA\s
                                erver\default\tmp
                                14:32:45,480 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.

                                14:33:02,669 INFO [ServerInfo] Java version: 1.5.0,Sun Microsystems Inc.
                                14:33:02,716 INFO [ServerInfo] Java Runtime: Java(TM) 2 Runtime Environment, St
                                andard Edition (build 1.5.0-b64)
                                14:33:02,826 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0-b64,Su
                                n Microsystems Inc.
                                14:33:02,920 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
                                14:33:02,983 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128M -X
                                mx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dg
                                c.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djava.endorsed.di
                                rs=C:\Jboss 5.1.0\jboss-5.1.0.GA\lib\endorsed
                                14:33:03,376 INFO [JMXKernel] Legacy JMX core initialized
                                14:33:27,348 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@eeabe8[
                                domain=default, server=default, name=default]
                                14:35:41,083 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
                                /
                                14:37:39,674 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
                                14:37:39,690 INFO [NativeServerConfig] 3.1.2.GA
                                14:37:44,858 INFO [AttributeCallbackItem] Owner callback not implemented.
                                14:37:48,849 INFO [LogNotificationListener] Adding notification listener for lo
                                gging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss
                                .mx.server.MBeanServerImpl@1e6696c[ defaultDomain='jboss' ]
                                14:48:49,356 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFS
                                DeploymentContext@352322{vfsfile:/C:/Jboss%205.1.0/jboss-5.1.0.GA/server/default
                                /deploy/profileservice-secured.jar/}
                                14:48:49,418 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFS
                                DeploymentContext@352322{vfsfile:/C:/Jboss%205.1.0/jboss-5.1.0.GA/server/default
                                /deploy/profileservice-secured.jar/}
                                14:48:49,418 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFS
                                DeploymentContext@352322{vfsfile:/C:/Jboss%205.1.0/jboss-5.1.0.GA/server/default
                                /deploy/profileservice-secured.jar/}
                                14:48:49,434 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFS
                                DeploymentContext@352322{vfsfile:/C:/Jboss%205.1.0/jboss-5.1.0.GA/server/default
                                /deploy/profileservice-secured.jar/}
                                14:49:15,589 INFO [JMXConnectorServerService] JMX Connector server: service:jmx
                                :rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
                                14:49:16,339 INFO [MailService] Mail Service bound to java:/Mail
                                14:49:25,453 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.
                                jboss.managed.api.annotation.ManagementComponent
                                14:49:25,891 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.
                                jboss.managed.api.annotation.ManagementComponent
                                14:49:26,219 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
                                version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
                                14:49:26,219 INFO [TransactionManagerService] Setting up property manager MBean
                                and JMX layer
                                14:49:27,016 INFO [TransactionManagerService] Initializing recovery manager




                                • 13. Re: Unauthenticated caller null N sqlException
                                  peterj

                                  Try this: delete the directories server/default/data, server/default/tmp and server/default/work. Then try starting the app server.

                                  I don't know why the recovery manager is handing, but deleting the above directories should give you a clean start.

                                  • 14. Re: Unauthenticated caller null N sqlException

                                    HI Peter

                                    Thanks for all the suggestions you are providing...

                                    I have 3 questions..!
                                    (I need your email ID pls..mine is "ravi.rachannavar@tcs.com" because some time jboss forum is not opening for me. Pls)

                                    1.I deleted data,temp and work folder from the server/default and it successfully started...but next time those folders were recreated..and it is again hanging. is there any permanent solution for this.

                                    2. Even after starting I gave the url you suggested.it displayed 404 error file not found. how can I do the successfull deployment..?

                                    3. how to do the clustering in JBoss 5.1.0 GA ?

                                    1 2 3 Previous Next