Calling rmi running in Weblogic 6.x from Jboss 4.0.5GA

Hi all,
Recently i have a project that needs me to call a remote ejb which is running in Weblogic 6.x. It is using Weblogic's proprietary protocol known as "t3". If i include weblogic.jar (i believe this version of weblogic doesn't deliver its client lib wlclient.jar) in my war file's WEB-INF/lib, i get this error:
2007-06-30 17:32:33,462 ERROR (GqsClient.java:93) - TestProject: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
I've tried to put it in server/default/lib but that throws another exception.
My test code:
Properties jndiProperties = new Properties();
jndiProperties.setProperty( Context.INITIAL_CONTEXT_FACTORY,
MY_INITIAL_CONTEXT_FACTORY );
jndiProperties.setProperty( Context.PROVIDER_URL, MY_PROVIDER_URL );
Context initialContext;
initialContext = new InitialContext( jndiProperties );
Object homeInt = initialContext.lookup( MY_EJB );
objectHome = ( SomeObjectHome ) PortableRemoteObject
.narrow( homeInt, SomeObjectHome.class );
objectRemote = objectHome.create();
Have i done anything wrong in the codes?
Where should i put my weblogic.jar?
org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.test.service.TestRmiClient]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: methods with same signature getEJBMetaData() but incompatible return types: [interface javax.ejb.EJBMetaData, interface javax.ejb.EJBMetaData]
java.lang.IllegalArgumentException: methods with same signature getEJBMetaData() but incompatible return types: [interface javax.ejb.EJBMetaData, interface javax.ejb.EJBMetaData]
        at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:669)
        at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
        at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
        at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
        at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
        at weblogic.rmi.internal.ProxyStub.newInstance(ProxyStub.java:69)
        at weblogic.rmi.internal.OIDManager.resolveObject(OIDManager.java:242)
        at weblogic.common.internal.ChunkedObjectInputStream.resolveObject(ChunkedObjectInputStream.java:81)
        at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.resolveObject(ChunkedObjectInputStream.java:328)
        at java.io.ObjectInputStream.checkResolve(ObjectInputStream.java:1352)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
        at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:139)
        at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:152)
        at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
        at weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:233)
        at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:264)
        at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
        at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
        at $Proxy15.lookup(Unknown Source)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:342)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at com.dhl.apis.litetrace.service.GqsClient.init(GqsClient.java:84)
        at com.dhl.apis.litetrace.service.GqsClient.<init>(GqsClient.java:57)
        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:494)
        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:172)
        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:52)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:490)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:366)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:234)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:144)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:283)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:321)
        at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:139)
        at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:252)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:190)
        at com.dhl.apis.common.spring.context.CustomContextLoaderListener.contextInitialized(CustomContextLoaderListener.java:30)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
        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:585)
        at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
        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:585)
        at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
        at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
        at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
        at org.jboss.web.WebModule.startModule(WebModule.java:83)
        at org.jboss.web.WebModule.startService(WebModule.java:61)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:1
12:05:02,781 INFO [STDOUT] 55)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy10.start(Unknown Source)
        at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy11.start(Unknown Source)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy7.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.start(Unknown Source)
        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
        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:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy5.deploy(Unknown Source)
        at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
        at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
        at org.jboss.Main.boot(Main.java:200)
        at org.jboss.Main$1.run(Main.java:490)
        at java.lang.Thread.run(Thread.java:595)Message was edited by:
jinchuriki

put weblogic.jar in tomcats classpath
Gary Bartlett wrote:
Question -
Can anyone point me at documentation that will help me
understand what jar files are required to allow access EJB's that are deployed in
Weblogic 6.1 from a Servlet that is running under Tomcat.
I am currently getting the following exception:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory.
Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1394)
Thanks,
Gary Bartlett

Similar Messages

Calling a bean in weblogic 4.5 from a servlet which is in Iplanet webserver4.1

while Calling a bean in weblogic 4.5 from a servlet which is in Iplanet webserver4.1 sometimes the servlet is not able to call the bean. There is no error logged in webserver. This is happening very rarely and when it happens I have to shut and restart IplanetWS.
Can anyone tell me some solution or reason
Regards
Nitin

We did receive a 4.5.1 / 5.1 interoperability patch - but it wasn't quite 'seamless'.
We never tried to use it.
SOAP? Isn't that around 50 times slower than RMI?
Mike
"Gary Mui" <[email protected]> wrote:
We ran into this issue last fall and got some feedback from weblogic
support. They originally said that it could be done (as well as different
versions talking to one another via JMS) but it turned out that they
were
incorrect and ended up saying that it is not possible. Before 6.0 went
GA,
BEA said that there would be a interoperability patch to do this, but
I've
never seen nor heard of anything regarding it. As a workaround, we
implemented 4.5.1 / 6.0 communication via SOAP.
Mike Reiche wrote in message <3b1bcaec$[email protected]>...
I have the same question - and more. Last year we were told that wecould
not use
RMI (and ejbs) between 4.5.1 and 5.1. Which seems kinda weird becauseI've
heard
of people using WL ejbs from Tomcat. This issue has caused us to avoidusing
WL ejbs in any future development which has any chance of ever beingused
by any
app server (WL included) that is not under the direct control of thedata
center.
I've been trying to convince the Architecture team here that we canuse WL
EJBs
and we can call them from other app servers - but can't seem to getany
supporting
statement from BEA (maybe I haven't tried hard enough).
Anyway, a response from BEA would be appreciated.
- Mike
"Madhu K" <[email protected]> wrote:
Is it possible to call a (stateless session) bean deployed in weblogic
6.0
from a bean in weblogic 5.1? I have two versions of weblogic running
on two
different hosts and I have to call a bean that is running in 6.0 from
5.1.
Are there any limitations?
Appreciate any feedback/suggestions.
Thanks,
Madhu

Can we call a bean in Weblogic 6.0 from Weblogic 5.1

Is it possible to call a (stateless session) bean deployed in weblogic 6.0
from a bean in weblogic 5.1? I have two versions of weblogic running on two
different hosts and I have to call a bean that is running in 6.0 from 5.1.
Are there any limitations?
Appreciate any feedback/suggestions.
Thanks,
Madhu

Cross posted to 'misc' - please follow up on that newsgroup.
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.misc&utag=
Mike
"Madhu K" <[email protected]> wrote:
Is it possible to call a (stateless session) bean deployed in weblogic
6.0
from a bean in weblogic 5.1? I have two versions of weblogic running
on two
different hosts and I have to call a bean that is running in 6.0 from
5.1.
Are there any limitations?
Appreciate any feedback/suggestions.
Thanks,
Madhu

Calling EJB deployed on Weblogic 10.3 from WebSphere Application Server 6

Hi,
We are trying to call an EJB(2.1) deployed in Weblogic 10.3 from WebSphere Application Server 6.
The problem is that the jars containing Weblogic's initial context factory are compiled with JDK5. (Client jar was built as per [http://download.oracle.com/docs/cd/E15051_01/wls/docs103/client/jarbuilder.html] .)
WebSphere is still running on JDK1.4.
Therefore when trying to get the InitialContext to lookup up the bean we get major/minor version errors because of the compiler level mismatch.
Has anyone faced a scenario like this and come up with a solution?
Are there 1.4 jars for Weblogic 10.3 out there?
Any help?
Thanks

Hi Dan,
Yes I am using EJB 3. I saw this thread earlier also but :
1. In my case I am not calling the EJB 3.0 methods directly. I am using a java client (Cataloged as a Java Class Library) which does the lookup and calls the EJB methods. (I am not cataloging and calling the EJB 3.0 methods directly).
2. It is working perfectly fine when the EJB is deployed in Weblogic 10.0 or 10.2.
I am very much new to this so please bear with my small and silly questions! Thanks a lot for you help !
Cheers !
Rajat

Calling a WebLogic web service from a WebLogic web application

We would like to call a WebLogic web service from WebLogic web application. The current architecture looks like:
LoadBalancer--->iPlanet-1/iPlanet-2--->Firewall--->WebLogic-AppServer-1/WebLogic-AppServer-2
The web application and web service are in the same WebLogic cluster. We would prefer that the web services do not get published externally.
Does the WebLogic web application need to make a call back outside the firewall to the load balancer?
Is there a way the web services can be called locally with load balancing?
Can web service calls be made over the t3 protocol?
Thanks,
Mike

I think one solution is to use a Java proxy to call the Web services.
In the Java proxy you can have a method that accepts the user/pass and sets them correctly for the Web service.
Then you expose that Java proxy as a data control (right click, create data control) - and then create a page that invokes that method.
(For the basics of working with a POJO data control see: http://blogs.oracle.com/shay/2009/07/java_class_data_control_and_ad.html )

Call another WebLogic's EJBs from resource adapter?

          Is it possible to call another WebLogic's EJBs from a resource adapter?
          A call to the javax.naming.InitialContext(Hashtable environment) results in a
          VersioningError:
          weblogic.common.internal.VersioningError: Incompatible service packs in CLASSPATH:
          (BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 , 6.1.4.0)
          not compatible with
          (BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
          at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
          at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
          at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
          at weblogic.kernel.Kernel.initialize(Kernel.java:122)
          at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
          at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
          at java.lang.Class.newInstance0(Native Method)
          at java.lang.Class.newInstance(Class.java:232)
          at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          at javax.naming.InitialContext.init(InitialContext.java:217)
          at javax.naming.InitialContext.<init>(InitialContext.java:193)
          at java.lang.reflect.Constructor.newInstance(Native Method)
          I'm not sure it will always be possible to match the version, although here upgrading
          the SP3 to SP4 will probably be done soon.
          Does anyone have experience with this?
          Or better: is there any documentation on this issue?


          Hi Hans,
          Here is the link for Weblogic SP3 / SP4 vulnerability and comparison for
          http://216.239.53.104/search?q=cache:RqqaQ3HZdwoJ:www.nipc.gov/cybernotes/2003/cyberissue2003-06.pdf+Versioning+Error+in+BEA+weblogic+6.1+SP3+and+SP4&hl=en&ie=UTF-8
          Hope this will help you.
          Let me know if u have any further problems.
          rgds
          KSK
          "Hans Bausewein" <[email protected]> wrote:
          >
          >
          >Is it possible to call another WebLogic's EJBs from a resource adapter?
          >
          >A call to the javax.naming.InitialContext(Hashtable environment) results
          >in a
          >VersioningError:
          >
          >weblogic.common.internal.VersioningError: Incompatible service packs
          >in CLASSPATH:
          >(BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 ,
          >6.1.4.0)
          >not compatible with
          >(BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
          > at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
          > at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
          > at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
          > at weblogic.kernel.Kernel.initialize(Kernel.java:122)
          > at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
          > at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
          > at java.lang.Class.newInstance0(Native Method)
          > at java.lang.Class.newInstance(Class.java:232)
          > at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
          > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          > at javax.naming.InitialContext.init(InitialContext.java:217)
          > at javax.naming.InitialContext.<init>(InitialContext.java:193)
          > at java.lang.reflect.Constructor.newInstance(Native Method)
          >
          >
          >
          >I'm not sure it will always be possible to match the version, although
          >here upgrading
          >the SP3 to SP4 will probably be done soon.
          >
          >Does anyone have experience with this?
          >
          >Or better: is there any documentation on this issue?
          >

HT1766 I have an I pad Mini. Since i down loaded the new update ISO 7, my I Pad is not running certain media files either from Chrome or Safari browser. I called technical support but they failed to provide any help stating the media files may not be comp

I have an I pad Mini. Since i down loaded the new update ISO 7, my I Pad is not running certain media files either from Chrome or Safari browser. I called technical support but they failed to provide any help stating the media files may not be compctable with new soft ware. I do bnot agree with their finding because i have I phone with ISO 7 updated soft ware and same files run on my I phone but not on I Pad. This was working fine before updating new software. This device is useless for me if i can not watch the program that i bought this for. I want device to replaced or taken back by the company. Thank you

Here are the iPad Mini specifications:
iPad mini - Technical SpecificationsNov 1, 2012
The specifications explain exactly what types of files are supported under "TV and Video".

Run 2 Weblogic domains from the same console

Hi
I have a question.
Currently now i have 2 domains, each domain was installed with Admin server and managed servers.
I have 1 nodemanager.
During the installation of the domains i had to provide different ports for the weblogic instances, so i have 2 different consoles to access the WL to manage domains.
The question:
Is there any way to handle and admin 2 different domains (which running on the same machine) from same WL console ?
Thanks

We do not have a way to administer two weblogic domains from same console.
But,I think you can install Oracle Enterprise Manager to manage your middleware infrastructure.

Cannot run WebLogic Integration Samples from QuickStart

I have installed the full WebLogic platform on an Intel box running Red Hat Linux
8.0. From QuickStart I am unable to run the WebLogic Integration Samples. Everything
else seems to work as expected.
The error message that results when attempting to run the Integration samples
is as follows:
RunSamples execution failed: /usr/local/bea/weblogic700/samples/integration/samples/lib/RunSamples.xml:106:
Cannot execute switchdb pointbase

Dear Micha,
Did you maintain the host file in Drivers\etc file:
hope this will solve the problem
If you did not add them plz add the hosts as follows:
      102.54.94.97     rhino.acme.com          # source server
       38.25.63.10     x.acme.com              # x client host
      (your PI server IP)   server Id name
And also check your Java web start version.
download the correct version for sun website.
Best Regards
Praveen K Kurni

I need to call the Run continously button programmatically from MFC application .

I have create Labview application from sample VI and with help of VirtualInstrument class I am to access the methods like Run ,SetControlValue and getControlvalue .But for VI we have Run continously button also .how do I programmatically call the Run continously button opteration from my applciation using VI methods.

"Run Continuously" is not something that should be used in an application. (There are very few legitimate uses for continuous run, e.g. to quickly play with a few input parameters while debugging a subVI independent of the main application. The equivalent in your case would be to just place the run invocation in a loop and call it repeatedly. This is definitely not the way to do it!)
Why don't you simply place a big while loop around all the code inside the VI that needs to run continuously?
See also THIS recent discussion.
LabVIEW Champion . Do more with less code and in less time .

Call one session EJB3 from jboss to weblogic 10

Hi everyone.
I have a big problem. I have a session ejb3 in a weblogic server. I need start this session from jboss server.The code I used is as follows:
Environment env = new Environment();
     env.setInitialContextFactory(weblogic.jndi.Environment.DEFAULT_INITIAL_CONTEXT_FACTORY);
     env.setProviderURL("t3://ip:7001");
     env.setSecurityPrincipal("weblogic");
     env.setSecurityCredentials("cajamar1");
     Hashtable props = env.getProperties();
I copied all the libraries that I have been asking in the JBOSS server. In the end I managed to work but when I do the lookup on my session I get this error message.
++14:51:46,939 ERROR [STDERR] 09-sep-2010 14:51:46 weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport preProcess++
++ADVERTENCIA: Error pre-processing class com.gh.conn.GHBackEndConnectorInterface with weblogic.ejb.container.deployer.RemoteBizIntfClas++
++sPreProcessor@b1c3bc3'++
++java.lang.NoSuchMethodError: <init>++
++at weblogic.ejb.container.deployer.RemoteBizIntfClassPreProcessor.preProcess(RemoteBizIntfClassPreProcessor.java:52)++
++at weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport.preProcess(ClassPreProcessor.java:102)++
++at weblogic.utils.classloaders.GenericClassLoader.doPreProcess(GenericClassLoader.java:341)++
++at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.enhanceClass(RemoteBizIntfClassLoader.java:143)++
++at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.loadClass(RemoteBizIntfClassLoader.java:129)++
++at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:67)++
++at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.readObject(RemoteBusinessIntfProxy.java:234)++
++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:585)++
++at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)++
++at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)++
++at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)++
++at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)++
++at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)++
++at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)++
++at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)++
++at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)++
++at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)++
++at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)++
Any help on the issue. Thanks for all.

Hi,
Please make sure that you have generated the Client Side Artifacts of your EJB3.0 App and Placed then at the JBoss side (Client side). Please refert to ": *http://weblogic-wonders.com/weblogic/2010/04/02/generating-ejb3-clientjar/*
Also make sure that you have "weblogic.jar" file at Cleint Application Side.
Thanks
Jay SenSharma

Cannot run BEA WebLogic 8.1 SP 3 with JDK 1.6

Hi,
Im using BEA Weblogic 8.1 SP3 trying to run a sample where a Robot from Kapow Mashup Server is called from a WebService hosted in the server.
The thing is that I keep getting a EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder (I attach the full exception below). I realised that by default the server uses the JDK which comes with the software (version 1.4) and that the class java.lang.StringBuilder is only available from JDK 1.5 onwards.
I have JDK 1.6 in my system, so in WebLogic -> Tools -> Application Properties -> JDK Home, I set that folder but still same exception occurs.
Through the Configuration Wizard I create a new “Basic WebLogic Server Domain” and in the step to configure the Java SDK I set the JDK 1.6 folder. However, when I try to start that server I get this error.
JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=;C:\bea\WEBLOG~1\server\lib\weblogic_knex_patch.jar;C:\bea\WEBLOG~1\common\lib\log4j.jar;C:\bea\WEBLOG~1\server\lib\debugging.jar;C:\bea\WEBLOG~1\server\lib\knex.jar;C:\bea\WEBLOG~1\javelin\lib\javelin.jar;C:\bea\WEBLOG~1\server\lib\wlw-lang.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\ant\ant.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\lib\rt.jar;;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient+ssl.jar;C:\bea\WEBLOG~1\server\lib\xbean.jar;C:\bea\WEBLOG~1\server\lib\wlxbean.jar;C:\bea\WEBLOG~1\server\lib\xqrl.jar;C:\bea\WEBLOG~1\server\lib\netui\netui-compiler.jar;C:\bea\WEBLOG~1\server\lib\wli.jar;C:\bea\WEBLOG~1\server\lib\fop.jar;C:\bea\WEBLOG~1\integration\adapters\sample\lib\sample-eis.jar;
PATH=C:\bea\WEBLOG~1\server\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\bin;C:\Archivos de programa\PC Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\Archivos de programa\Archivos comunes\Adobe\AGL;c:\Archivos de programa\Microsoft SQL Server\90\Tools\binn\;c:\matlab6p5\bin\win32;C:\Nokia\Update_Manager\bin;C:\Archivos de programa\QuickTime\QTSystem\;C:\Sun\jwsdp-2.0\jwsdp-shared\bin;C:\Archivos de programa\Kapow Mashup Server 6.3\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\bea\WEBLOG~1\server\bin\oci920_8
* To start WebLogic Server, use a username and *
=== Debugging ===
This window is necessary for debugging code using WebLogic Workshop
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
Listening for transport dt_socket at address: 8453
Starting WLS with line:
C:\ARCHIV~1\Java\JDK16~1.0_1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.configuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=C:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
Listening for transport dt_socket at address: 8453
<27-abr-2009 11H22' CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 11.0-b15 from Sun Microsystems Inc.>
<27-abr-2009 11H22' CEST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<27-abr-2009 11H22' CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Integration 8.1 SP3 Wed Jun 30 14:05:38 PDT 2004 405464>
Stopping the Weblogic Workshop debugger...
Debugger Stopped.
Stopping Pointbase server...
Pointbase server stopped.
If I modify the settings of this new domain an pick a BEA Supplied SDKs, everything works just fine.
Someone can give a hand on that? It seems like Bea WebLogic 8.1 and JDK 1.6 are not compatible. Completely stacked here.
Regards.
Full Exception
EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder
at robosuite.wizard.jws5a1dbbea00000001.ApiKapowIN.toString(ApiKapowIN.java:141)
at java.lang.String.valueOf(String.java:2131)
at java.lang.StringBuffer.append(StringBuffer.java:370)
at com.bea.wlw.runtime.core.context.WlwThreadContext.logInvoke(WlwThreadContext.java:363)
at com.bea.wlw.runtime.core.context.WlwThreadContext.startInvocation(WlwThreadContext.java:608)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:414)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:153)
at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62)
at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:160)
at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
at com.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:49)
at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executePostRequest(HttpServerHelper.java:713)
at com.bea.wlw.runtime.core.dispatcher.HttpServer.doPost(HttpServer.java:49)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6456)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Even if it is a very naive question but I just cannot get it worked, what do you mean by using jdk 1.5 on client side?
I guess client side is completely out of WLS so the jdk to be used on the client side is not set in the environment.
However, the Exception Im getting is on the server side, when it tries to run the code automatically generated from Kapow Mashup Server 6.3. That code is embedded in a jar file, but it seems it makes a call to the java.lang.StringBuilder class which as said before, it is only available from jdk 1.5 onwards.
Should I contact Kapow Mashup Server support to see how the sample code is generated or I am missing something?
Regards.

Java Stored Procedure calling HTTP Servlet in Weblogic

I am currently working on an e-commerce application for a brick-n-mortar electronics store. The store currently has an Oracle database that contains all of the products the store sells. The e-commerce site will have a separate Oracle database. Both database are Oracle 9i release 2 databases. The e-commerce site will be using BEA's Weblogic as its application server. I need to move data from the store db into the e-commerce db. The actual moving of the data is not the issue. The issue comes from needing to call several methods on a Stateless Session EJB, loaded on the Weblogic server, to perform backend processing. I wanted to make a JNDI call from a Java Stored Procedure but with Release 2, this option is no longer supported. The release notes (http://otn.oracle.com/tech/java/htdocs/9idb2_java.html) indicated that the JVM now supports calling out to Servlets using HTTP Client from a Java Stored Procedure.
Has anyone done this? Is there any sample code available?
Thanks for any help.

I am currently working on an e-commerce application for a brick-n-mortar electronics store. The store currently has an Oracle database that contains all of the products the store sells. The e-commerce site will have a separate Oracle database. Both database are Oracle 9i release 2 databases. The e-commerce site will be using BEA's Weblogic as its application server. I need to move data from the store db into the e-commerce db. The actual moving of the data is not the issue. The issue comes from needing to call several methods on a Stateless Session EJB, loaded on the Weblogic server, to perform backend processing. I wanted to make a JNDI call from a Java Stored Procedure but with Release 2, this option is no longer supported. The release notes (http://otn.oracle.com/tech/java/htdocs/9idb2_java.html) indicated that the JVM now supports calling out to Servlets using HTTP Client from a Java Stored Procedure.
Has anyone done this? Is there any sample code available?
Thanks for any help. Hi,
sorry we have not yet formally documented this but here is a code snippet
Kuassi
/* HttpCallout - simple test to callout to static pages from Java Stored
Procedures */
import java.io.IOException;
import java.io.InputStream;
import HTTPClient.HTTPConnection;
import HTTPClient.HTTPResponse;
import HTTPClient.AuthorizationInfo;
public class HttpCallout {
public static void main(String[] argv) throws InterruptedException {
HttpCallout t = new HttpCallout(argv);
t.run();
private String[] argv ;
HttpCallout(String[] argv) {
this.argv = argv;
void initSSL() {
public void run() {
try {
if ( argv.length == 0 ) {
System.out.println("HttpCallout " +
"protocol " +
"host " +
"port " +
"page ");
return;
// process arguments
int argc = 0;
String protocol = argv[argc++];
String host = argv[argc++];
int port = Integer.parseInt(argv[argc++]);
String page = argv[argc++];
// Debugging - don't set for now
// System.setProperty("HTTPClient.log.mask", "3");
// noop
initSSL();
// Grab HTTPConnection
HTTPConnection con = new HTTPConnection(protocol, host, port);
con.setTimeout(20000);
con.setAllowUserInteraction(false);
// Grab Response
HTTPResponse rsp = con.Get(page);
byte[] data = rsp.getData();
if ( data == null ) {
System.out.println("no data");
} else {
System.out.println("data length " + data.length);
System.out.println(new String(data));
catch ( Throwable ex ) {
ex.printStackTrace();

Errors in calling rmi methods

iPlanet6.1 is throwing following exceptions during rmi calls. Seems to be it is having problem in establishing t3 connections to the weblogic.
java.rmi.ConnectException: Connection to: 'wlserver1' over: 't3' g
ot an error or timed out
at weblogic.rjvm.ConnectionManager.ensureConnectionEstablished(Connectio
nManager.java:1272)
at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.jav
a:1316)
at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:348)
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRe
f.java:97)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:125)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
=======
java.rmi.ConnectException: Attempt to sendMsg using a closed connection
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundR
equest.java:85)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
We have to restart iplanet whenever we get this problem and then it works fine for 40min - 1hr and it repeats the problem again. But we could make t3 connections and call rmi methods on the appserver by a test program running out of webserver without any problem at the same time when iplanet was having problems.
Did anybody face this problem before?
Thanks.
Ashok

es5f2000 wrote:
jschell wrote:
That works?I dunno. The below definitely works, but like I said, I've only
ever done it with one output parameter (and that has always
been a ResultSet).
String callableQuery = "{?= call my_package.my_call(?, ?)}"
Yes I have done that and at least in terms of my code it wasn't just a result set.
But not with two.

How to protect an application running on weblogic through OAM

I have a requirement where in I need to protect an application (URL/root) deployed on weblogic through Oracle Access Manager.
Here's what I did:
Installed webgate on the Host where the application is deployed.
Configured the webgate on Access System Console.
Configured the policy domain -
a) Mentioned the Resource type and URL to be protected
b) Authentication Type (Basic)
c) Autherization Rules (Anyone can acess)
Issue: When I try to access the application http://<hostname>:7001/myapp
I expect the webgate/OAM to intercept this request and challenge the user with the basic authentication
but the request is carried through and the Home page of myapp is displayed.
Do I need to do some configurations in the webserver (httpd.conf) or deployment descriptors in the application server to get the authentication?
The application above can also be substituted with Oracle Identity Manager, where I'm getting the same result. I'm able to view OIM Home page without prior authentication. I tried protecting with the following pattern <host variation>/xlWebApp
I am new to Oracle Access Manager and looking for some guidance.
Thanks

Hi Joe,
1. Please elaborate step2 or guide me to a link where I can configure reverse proxy from Apache Webserver to weblogic. I think here's where I'm going wrong.
For more details on proxy refer to these links:
http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs90/plugins/apache.html#119517
OHS to Weblogic Reverse Proxy configuration Problem
After this configuration, won't I be able to access the application /myapp running on weblogic through port 7001 and will I have access to it only on port 80 (web s erver default port)?
You will be able to access the application through 7001, but the request will not be intercepted by OAM. The request will be processed directly by your myApp.
2. I did some reading and found some instructions on using weblogic SSPI plugin. Is this required at all? When is this used?
You can use SSPI Connector if you want to protect the weblogic port. i.e., OAM intercepts the request when you access the application on 7001 port.
Hope this helps
Hrushi

Calling rmi running in Weblogic 6.x from Jboss 4.0.5GA

Similar Messages

Maybe you are looking for