2 Replies Latest reply on Feb 29, 2004 7:48 PM by tsagovic

    Connecting to CORBA server from JBOss

    tsagovic Newbie

      Hi everyone,
      I have a simple application that tries to connect to a CORBA server from JBoss ( no it is a simple Class called from a servlet, but the intention is to call the CORBA server from a SLSB that is now simply returning a dump varialble).
      When I try to lunch it via my browser, It simply hangs for ever, and no errors are printed.
      I have however seen the following WArning when the server starts.

      2004-02-29 17:20:16,667 WARN [org.jboss.ejb.EjbModule] Could not load the org.jboss.resource.connectionmanager.CachedConnectionInterceptor interceptor for this container
      javax.management.InstanceNotFoundException: jboss.jca:service=CachedConnectionManager is not registered.
       at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:354)
       at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:442)
       at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.<init>(CachedConnectionInterceptor.java:72)
       at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
       at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
       at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
       at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
       at java.lang.Class.newInstance0(Class.java:308)
       at java.lang.Class.newInstance(Class.java:261)
       at org.jboss.ejb.EjbModule.addInterceptors(EjbModule.java:804)
       at org.jboss.ejb.EjbModule.initializeContainer(EjbModule.java:690)
       at org.jboss.ejb.EjbModule.createStatelessSessionContainer(EjbModule.java:494)
       at org.jboss.ejb.EjbModule.createContainer(EjbModule.java:449)
       at org.jboss.ejb.EjbModule.createService(EjbModule.java:279)
       at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
       at $Proxy12.create(Unknown Source)
       at org.jboss.system.ServiceController.create(ServiceController.java:310)
       at org.jboss.system.ServiceController.create(ServiceController.java:243)
       at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
       at $Proxy10.create(Unknown Source)
       at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:522)
       at org.jboss.deployment.MainDeployer.create(MainDeployer.java:776)
       at org.jboss.deployment.MainDeployer.create(MainDeployer.java:768)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:631)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
       at $Proxy6.deploy(Unknown Source)
       at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:302)
       at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:476)
       at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
       at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
       at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
       at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
       at $Proxy0.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:394)
       at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
       at $Proxy4.start(Unknown Source)
       at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:632)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
       at $Proxy5.deploy(Unknown Source)
       at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
       at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
       at org.jboss.Main.boot(Main.java:150)
       at org.jboss.Main$1.run(Main.java:388)
       at java.lang.Thread.run(Thread.java:534)
      

      Any clue about it? How can I call a CORBA server from JBoss?
      BTW, I tried to put Jacrob.jar which I am using as ORB impl in my client in the /default/deploy/{MyApplication.war}/WEB-INF/lib but that caused problems, and since Jacorb is only in the ALL server lib. directory, I just deleted from my app. Lib dir. and put it in default server lib dir. That solved the problem, but It seems there are other warnings concerning other *.jar files used by JBoss as well. Should there be only 1 jar file? Shouln't I put the *.jars I need under my apps WEB-INF/lib?

      I am sorry if this is the wrong forum.
      Thank you in advance!

        • 1. Re: Connecting to CORBA server from JBOss
          Adrian Brock Master

          Looks like you deleted transaction-service.xml?

          Regards,
          Adrian

          • 2. Re: Connecting to CORBA server from JBOss
            tsagovic Newbie

            Hi Adrian,
            transaction-service.xml is indeed under the deploy dir.
            I noticed that there are many warnings that say something like a jar file is referencing another, and the later could not be found. I though that this might not be a problem, since tomcat and jboss for example both use log4j, so it is placed in only one place, even if other jar files reference to it as if it were in the same dir. Is this right?

            I have also noticed the following warning:

            WARN [org.jboss.web.tomcat.tc4.EmbeddedTomcatService] Unable to invoke setDelegate on class loader:org.jboss.web.tomcat.tc4.WebCtxLoader$ENCLoader@178aae1
            

            What is happening I don't remember I have ever deleted any conf. file/ jar, and have a clean installation. The only thing that I have done is to the JAR files required in my application under its lib. dir. (and these files might also be already in use by tomcat), Does this create problems? Should all the *.jar files put under the shared Lib dir?
            It sometimes also happen that I can not remove my application directory, because some file is in use, and need to shut down JBoss and restart it.
            Any idea?
            Thank you very much!