10 Replies Latest reply on Apr 13, 2005 3:39 AM by garu

    IIOP initializing error of JBoss 4.0

    xyz

      I downloaded and installed the newly released JBoss 4.0 on my Mac G5 running Gentoo Linux ppc64 of 2004.2. I got an error "java.lang.ExceptionInInitializerError" caused by org.omg.CORBA.INITIALIZE: cannot instantiate org.jboss.iiop.SunJDK141IsLocalBugFix vmcid: 0x0 minor code: 0 ..
      But actually the server was up and running.
      My jdk in ibm jdk 1.4.2 for ppc64. Any help is much appreciated.


      Dehua

        • 1. Re: IIOP initializing error of JBoss 4.0
          dimitris

           

          /**
           * There is a bug in Sun's implementation of the method javax.rmi.CORBA.Util.isLocal().
           * Stubs generated with the rmic tool call this method to check is the call is a local invocation,
           * which they can optimize. However, Sun's implementation of isLocal() tries to cast the stub to a proprietary
           * class. This is against the rules. Since the ORB is pluggable ("-Dorg.omg.CORBA.ORBClass=...), Sun's
           * implementation of a standard (javax.rmi) method should not assume that the stubs are Sun stubs.
           *
           * @author <a href="mailto:reverbel@ime.usp.br">Francisco Reverbel</a>
           * @version $Revision: 1.1 $
           *
           **/


          This was a bug fix for a Sun JDK bug that you wouldn't need if you use IBM's VM. I don't know exactly how this class gets instantiated, but as you said you're probably Ok :)

          Franscisco, any comment?

          Regards
          /Dimitris

          • 2. Re: IIOP initializing error of JBoss 4.0

            In iiop-service.xml
            add the following configuration to the CorbaORB service

            <attribute "SunJDK141IsLocalBugFix">false</attribute>
            


            • 3. Re: IIOP initializing error of JBoss 4.0
              xyz

              Thank you.
              I tried to add the attribute to CorbaORB service, but got the following error:

              00:07:34,023 ERROR [MainDeployer] Could not initialise deployment: file:/usr/local/jboss-4.0.0/server/default/deploy/iiop-service.xml
              org.jboss.deployment.DeploymentException: Element type "attribute" must be followed by either attribute specifications, ">" or "/>".; - nested throwable: (org.xml.sax.SAXParseException: Element type "attribute" must be followed by either attribute specifications, ">" or "/>".)


              I tried also to use false, while with error:

              00:12:46,755 INFO [ServiceConfigurator] Problem configuring service jboss:service=CorbaORB
              org.jboss.deployment.DeploymentException: No Attribute found with name: SunJDK141IsLocalBugFix

              Any ideas?

              Dehua

              • 4. Re: IIOP initializing error of JBoss 4.0
                xyz

                Sorry for the inconvenience, some words are missing.
                I tried also to use false, while with error:

                When use 'attribute name="......" false /attribute', the error is:
                00:12:46,755 INFO [ServiceConfigurator] Problem configuring service jboss:service=CorbaORB
                org.jboss.deployment.DeploymentException: No Attribute found with name: SunJDK141IsLocalBugFix

                • 5. Re: IIOP initializing error of JBoss 4.0

                  I only managed to make 2 mistakes in one line of configuration.
                  It should be

                  <attribute name="SunJDK14IsLocalBugFix">false</attribute>
                  


                  1) It needs a name=
                  2) It is JDK14IsLocal not JDK141IsLocal

                  • 6. Re: IIOP initializing error of JBoss 4.0
                    xyz

                    Yes, I was stupid to make such error. Now the problem has gone away.

                    Thank you very much.

                    Dehua

                    • 7. Re: IIOP initializing error of JBoss 4.0
                      garu

                      Running 4_0_2_RC1 with JDK 1.5.0_02 i'm getting a sligthly different problem:

                      2005-04-12 08:52:57,278 DEBUG [org.jboss.iiop.CorbaORBService] Ignoring sunJDK14IsLocalBugFix=true due to inability to load org.jboss.iiop.SunJDK14IsLocalBugFix
                      java.lang.ClassNotFoundException: Unexpected error during load of: org.jboss.iiop.SunJDK14IsLocalBugFix, msg=com/sun/corba/se/internal/iiop/ShutdownUtilDelegate
                      


                      Setting sunJDK14IsLocalBugFix to false, seems to fix the problem.
                      Can i safely run with this configuration?
                      Thanks, Gabriele.

                      • 8. Re: IIOP initializing error of JBoss 4.0
                        dimitris
                        • 9. Re: IIOP initializing error of JBoss 4.0

                          Dimitris, please stop answering user questions in the dev forums,
                          especially FAQs.

                          • 10. Re: IIOP initializing error of JBoss 4.0
                            garu

                            Adrian,
                            i'm sorry if i violated the forum constraints, i usually keep the open source projects i'm using, checked out in my machine and normally i refrain from asking questions if i'm able to find myself the aswers by looking into the code and the doc.

                            But in this case none of the conditions in the faq were met:
                            1- there it is mentioned java.lang.ExceptionInInitializerError but i get java.lang.ClassNotFoundException, even if the class do exists into the jboss-iiop.jar
                            2- there are mentioned java 1.3 and 1.4 and i'm using 1.5
                            3- the faq says that sunJDK14IsLocalBugFix=false must be specified for NON Sun VM's but i'm using the Sun jdk

                            So i felt that a question was worth for at least a couple of reasons:
                            1- i'm planning and experimenting with the migration of a large set of applications from BEA to jboss and i want to be sure the EJB infrastructure is not impaired in any sense by this problem.
                            2- there must be something different in the combination 4_0_2_RC1/jdk 1.5, given the different behaviour, so, since more and more people will be using 4.0 with jdk 1.5, perhaps it's worth for you to investigate and update the doc accordingly to prevent similar questions.

                            Thanks for your attention and to Dimitris for his answer, Gabriele