6 Replies Latest reply on Aug 27, 2002 8:47 AM by kristofvcl

    jboss catalina problem

    kristofvcl

      First of all I'm not sure this is a good spot for posting this but because I still consider myself as a beginner so


      We use jboss 3.0 with catalina 4.03
      When deploying we use a earfile containing a war, jar and application.xml

      The strange thing is that the first time we start the server everything works.
      If we delete the catalina\works dir for the application before restarting the jboss it also works.

      But when you restart the jboss without removing the works dir we get an java.lang.linkageerror loader constraints violated when linking on one of our class files.

      We checked the jar and war for this file and it contained exactly the same class file.

      We then tried it on the jboss2.4.4 with catalina and it works. Also when we adjust the ear for working on a seperate jboss 2.4.4 and catalina 4.0.3 it als works.

      It seems the problem has something to do with the catalinaSX or the catalina with jboss.

      Is there someone who has a solution or is this a bug?

      Regards

      Kristof

        • 1. Re: jboss catalina problem

          Have you tried this with 3.0.1?

          Regards,
          Adrian

          • 2. Re: jboss catalina problem
            joelvogt

            I've also had problems with 4.03, 4.04 seemed to be a better build.

            • 3. Re: jboss catalina problem
              kristofvcl

              Now i've tried it with the 3.01 and catalina 4.04.
              This time my datasource isn't bound.
              When I check the startup of the server I only see the DefaultDS name that is bound.
              I see the hsql and my datasource service but there names aren't bound.
              The service worked on jboss3.0
              Is there a change nescessary for binding the name in 3.01?

              • 4. Re: jboss catalina problem
                kristofvcl

                After checking the startup of JBOSS (3.01 with catalina 4.04)I encountered the following :

                Cause: Incomplete Deployment listing:
                Packages waiting for a deployer:


                Incompletely deployed packages:

                MBeans waiting for classes:

                MBeans waiting for other MBeans:
                [ObjectName: jboss.jca:service=LocalTxCM,name=Wdcis
                state: CONFIGURED
                I Depend On: jboss.jca:service=LocalTxDS,name=Wdcis
                jboss.jca:service=LocalTxPool,name=Wdcis
                jboss.jca:service=CachedConnectionManager
                jboss.security:name=JaasSecurityManager
                jboss.jca:service=RARDeployer

                This part didn't occur in the jboss3.0.

                I found on the net (sourceforge) that there are a bunch of people who are having the same problem.

                Does this mean that it is a bug or is there something I missed?

                I noticed that the LocalTxCM,name=Wdcis is the same as LocalTxDS,name=Wdcis. Is that a problem?

                • 5. Re: jboss catalina problem

                  I think the ObjectName for Jaas changed.

                  Try
                  jboss.security:service=JaasSecurityManager

                  Regards,
                  Adrian

                  • 6. Re: jboss catalina problem
                    kristofvcl

                    Thank you.
                    Both problems are solved now.

                    Regards

                    Kristof