This discussion is archived
4 Replies Latest reply: Jul 8, 2013 1:40 AM by 22fae491-8625-4efd-b15e-0f579cd9fb0a RSS

jdeveloper 1.1.1.6.0 Fedora 17 - OVM 4.1.24

user329142 - oracle Newbie
Currently Being Moderated
I have a host machine with Fedora 17 64 bit where I installed JDeveloper 11.1.1.1.6.0.
In the same machine I've ridden a 64bit Linux over Oracle Virtual Box. On this machine I installed WebLogic Server 11g also.

When I try to connect jdev to weblogic in OVM for create a WLS's connection i get out the following error:

Testing JSR-160 Runtime ... failed.
Could not initialize class $ weblogic.rjvm.t3.ProtocolHandlerT3 ChannelInitializer
JSR-160 Testing DomainRuntime ... skipped.
Testing JSR-88 ... skipped.
Testing JSR-88-LOCAL ... skipped.
Testing JNDI ... skipped.
Testing JSR-160 Edit ... skipped.
Testing HTTP ... success.
Testing Server MBeans Model ... skipped.

I can access the console of WLS in OVM from the browser on the host machine.

I already also deleted the proxy from JDeveloper

Any ideas ...?

Thanks
  • 1. Re: jdeveloper 1.1.1.6.0 Fedora 17 - OVM 4.1.24
    Blueberry Coder Journeyer
    Currently Being Moderated
    Hi.

    Are you sure you are trying to connect to the right TCP port? If the firewall is enabled, does it allow the connections on port 7001 (or whichever you chose at install time)? You can list the firewall rules with the following command:
    iptables --list
    Best Regards,

    Frédéric.
  • 2. Re: jdeveloper 1.1.1.6.0 Fedora 17 - OVM 4.1.24
    user329142 - oracle Newbie
    Currently Being Moderated
    Thanks.

    This is can be helpfull...If i tray to connect with integrated WLS i get this error....

    Performing action About[ from oracle.ideri.navigator.DefaultNavigatorWindow ]
    Invoking command: [ from oracle.ideri.navigator.DefaultNavigatorWindow ]
    Performing action Preferences...[ from oracle.jdevimpl.help.HelpTopicEditor ]
    Invoking command: [ from oracle.jdevimpl.help.HelpTopicEditor ]
    Performing action Properties...[ from oracle.ideri.navigator.DefaultNavigatorWindow ]
    Uncaught exception
    java.lang.NoClassDefFoundError: Could not initialize class weblogic.rjvm.t3.ProtocolHandlerT3$ChannelInitializer
    weblogic.rjvm.t3.ProtocolHandlerT3.getDefaultServerChannel(ProtocolHandlerT3.java:42)
    weblogic.protocol.ServerChannelManager$SingletonMaker$1.getOutboundServerChannel(ServerChannelManager.java:393)
    weblogic.protocol.ServerChannelManager.findOutboundServerChannel(ServerChannelManager.java:288)
    weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:233)
    weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
    weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
    weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
    weblogic.jndi.Environment.getContext(Environment.java:315)
    weblogic.jndi.Environment.getContext(Environment.java:285)
    weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    jx.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    jx.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    jx.naming.InitialContext.init(InitialContext.java:223)
    jx.naming.InitialContext.<init>(InitialContext.java:197)
    weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)
    weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
    jx.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
    o.rc.asadapter.weblogic.connection.spi.Weblogic10Jsr160Provider.getPresentation(Weblogic10Jsr160Provider.java:67)
    o.rc.asadapter.connection.AppServerConnectionImpl$PM.getPresentation(AppServerConnectionImpl.java:171)
    o.rc.asadapter.weblogic.connection.spi.Weblogic10ServerMBeanModelImpl.getDomainRuntimeService(Weblogic10ServerMBeanModelImpl.java:59)
    o.rc.asadapter.weblogic.context.spi.AppDeploymentProvider.listBindingsImpl(AppDeploymentProvider.java:71)
    o.rc.asadapter.context.spi.AbstractContextProvider.listBindings(AbstractContextProvider.java:133)
    o.rc.asadapter.context.spi.DefaultMutableAppServerContext$ContextProviderSupport$3.method(DefaultMutableAppServerContext.java:384)
    o.rc.asadapter.context.spi.DefaultMutableAppServerContext$ContextProviderSupport$MethodCall.invoke(DefaultMutableAppServerContext.java:421)
    o.rc.asadapter.context.spi.DefaultMutableAppServerContext$ContextProviderSupport.listBindings(DefaultMutableAppServerContext.java:381)
    o.rc.asadapter.context.spi.DefaultMutableAppServerContext$ContextProviderSupport.access$500(DefaultMutableAppServerContext.java:314)
    o.rc.asadapter.context.spi.DefaultMutableAppServerContext.localListBindings(DefaultMutableAppServerContext.java:207)
    o.rc.asadapter.context.spi.AbstractEventDirContext.listBindings(AbstractEventDirContext.java:185)
    o.adf.rc.spi.jndi.AbstractDirContext.listBindings(AbstractDirContext.java:214)
    o.rc.asadapter.context.spi.DefaultAppServerManageableContext.getManageables(DefaultAppServerManageableContext.java:58)
    o.j.asnav.nodes.DefaultManageableFolder.loadChildren(DefaultManageableFolder.java:327)
    o.j.asnav.nodes.DefaultManageableFolder$4.run(DefaultManageableFolder.java:288)
    1;1)
  • 3. Re: jdeveloper 1.1.1.6.0 Fedora 17 - OVM 4.1.24
    Blueberry Coder Journeyer
    Currently Being Moderated
    Hum... I am not sure of what is going on. According to this WLS forum thread ({thread:id=890529}), you could have a configuration problem with your WebLogic Server instance. It is difficult to say more without having more information about your setup.

    Best Regards,

    Frédéric.
  • 4. Re: jdeveloper 1.1.1.6.0 Fedora 17 - OVM 4.1.24
    22fae491-8625-4efd-b15e-0f579cd9fb0a Newbie
    Currently Being Moderated

    this can be occurred by wrong binding of host name to your network ip address, if you are trying to connect to remote weblogic. check your host name and ip address binding

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points