Weblogic RMI error

Dear all,
I am using weblogic rmi. When I run the client, the following error
appeared:
java.rmi.UnmarshalException: failed to unmarshal class
java.lang.Object; nested
exception is:
java.lang.ClassNotFoundException: Hello_WLStub
--------------- nested within: ------------------
weblogic.rmi.MarshalException: Remapped jndi exception
- with nested exception:
[java.rmi.UnmarshalException: failed to unmarshal class
java.lang.Object; nested
exception is:
java.lang.ClassNotFoundException: Hello_WLStub]
at weblogic.rmi.Naming.toWeblogicRmiException(Naming.java:289)
at weblogic.rmi.Naming.lookup(Naming.java:78)
at HelloClient.main(HelloClient.java:40)
Server and client are 2 separate machine.However, when I copy
Hello_WLStub.class to the client machine, it runs without problem.
When weblogic do not download the stub class to client instead?
Moreover, I found that all my startup classes must be placed inside
E:\bea\wlserver6.0, otherwise those startup classes will not work. How
to change this default location?Thanks!

Similar Messages

Error when trying to acess a remote bean ??(weblogic.rmi.UnmarshalException

hi,
i have a component (with weblogic 5.1) one one system (say A).
I have an application on other systen (say B) which must connect to that component and insert data in the database.
when i am trying to acces
i get this error...
Exception javax.naming.CommunicationException [Root exception is weblogic.rmi.UnmarshalException: Unmarshalling return
- with nested exception:
[java.lang.ClassNotFoundException: class com.fn.trading.TDorderVettingSessionEJBHomeImpl_ServiceStub previously not found]]
My Bean class Name is TDorderVettingSessionEJB.class in a package com.fn.trading..
when i am running the application on the same system A the code is working. but giving priblem when accessed with system B.
i tried to copy the bean class files in the system B also and kept in classpath..but still it did not work...
regards
sowjanya

Set property weblogic.system.enableUnsafeClassloading=true

Encountering Java RMI error trying to install IDM 11.1.1.6

Hi all,
I'm completely stumped trying to install Oracle identity management 11.1.1.6 from the download here
http://www.oracle.com/technetwork/middleware/id-mgmt/downloads/index.html
I am on RHEL 5.5 x64, clean install into a Xen VM, all the latest updates applied.
What I have done so far is as follows.
Install GI and DB 11.2.0.3.0 for a single instance using ASM
Set up some ASM disk groups using iSCSI attached storage
Create a database using DBCA
Install RCU 11.1.1.6 and create the necessary repository schema for IDM
Install Sun JDK 1.6.0_38
Install Weblogic server 10.3.6 - downloaded from eDelivery
Carry out a software only installation of IDM
Use $MW_HOME/Oracle_IDM1/common/bin/config.sh to create a Weblogic domain which supports IDM
Run $MW_HOME/Oracle_IDM1/bin/config.sh to try and configure IDM
Sadly at this last step I am encountering an RMI error from the weblogic admin server whien specifying which components I want to configure - the installer is connecting to the running server but I get an RMI exception in the logs, the installer reports INST-5194: Unable to connect to the Oracle WebLogic Middleware Administration Server and it won't go any further. Full error stack follows. Anyone got any suggestions? I'm really scratching my head here.
####<Jan 8, 2013 9:44:12 AM GMT> <Warning> <RMI> <perses> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <c973505a4484734b:-5669ab43:13c160fd34d:-8000-0000000000000019> <1357638252608> <BEA-080003> <RuntimeException thrown by rmi server: javax.management.remote.rmi.RMIConnectionImpl.getAttribute(Ljavax.management.ObjectName;Ljava.lang.String;Ljavax.security.auth.Subject;)
java.lang.NullPointerException.
java.lang.NullPointerException
 at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:768)
 at weblogic.management.mbeanservers.internal.JMXContextInterceptor.getMBeanContextLoader(JMXContextInterceptor.java:475)
 at weblogic.management.mbeanservers.internal.JMXContextInterceptor.getAttribute(JMXContextInterceptor.java:146)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
 at java.security.AccessController.doPrivileged(Native Method)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
 at java.security.AccessController.doPrivileged(Native Method)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
 at java.security.AccessController.doPrivileged(Native Method)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
 at java.security.AccessController.doPrivileged(Native Method)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
 at weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:299)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:279)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$5$1.run(JMXConnectorSubjectForwarder.java:326)
 at java.security.AccessController.doPrivileged(Native Method)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$5.run(JMXConnectorSubjectForwarder.java:324)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.getAttribute(JMXConnectorSubjectForwarder.java:319)
 at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1431)
 at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:74)
 at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1295)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1394)
 at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:630)
 at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
 at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
 at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>

Did you manage to solve this issue?
I'm running into the exact same error, but installing 11.1.1.7.0 on Windows 2003
Haven't found anything on MOS yet :(
Kind regards,
Rob
Edited by: rgouw on 10-apr-2013 1:10

RMI Error when trying to connect to remote server

We are getting an RMI error (below) when trying to connect to a remote weblogic 9 server with mission control.
We are running a portal application on the app server. If we connect using mission control before the app starts then mission control connects successfully.
If we wait until the portal application is running then we get the following error when we try to connect:
Could not open Management Console for UAT Live (1).
java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
 java.lang.ClassNotFoundException: com.vignette.monitor.framework.VgnMBeanInfo (no security manager: RMI class loader disabled)
java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
 java.lang.ClassNotFoundException: com.vignette.monitor.framework.VgnMBeanInfo (no security manager: RMI class loader disabled)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:162)
 at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
 at javax.management.remote.rmi.RMIConnectionImpl_Stub.getMBeanInfo(Unknown Source)
 at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getMBeanInfo(RMIConnector.java:1031)
 at com.jrockit.console.rjmx.RJMXConnection.getMBeanInfos(RJMXConnection.java:262)
 at com.jrockit.console.rjmx.RJMXConnection.getMBeanInfos(RJMXConnection.java:297)
 at com.jrockit.console.rjmx.RJMXConnectorModel.initializeAttributeInfos(RJMXConnectorModel.java:294)
 at com.jrockit.console.rjmx.RJMXConnectorModel.<init>(RJMXConnectorModel.java:99)
 at com.jrockit.console.rjmx.RJMXConnectorModel.<init>(RJMXConnectorModel.java:113)
 at com.jrockit.mc.console.ui.actions.StartConsole$1.preConnect(StartConsole.java:36)
 at com.jrockit.mc.browser.utils.PreConnectJob.run(PreConnectJob.java:73)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.ClassNotFoundException: com.vignette.monitor.framework.VgnMBeanInfo (no security manager: RMI class loader disabled)
 at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:371)
 at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165)
 at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620)
 at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247)
 at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197)
 at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
 at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
 at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:290)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:139)
 ... 11 more
thanks

As poorem suggested, I would check that the time is the same on both the identity and vcac appliances. It has been a while since I posted this question but I believe that did get me past that specfic error. I changed the timezone on each and made sure the times were correct and the same.

Weblogic Console error while logging in

Hi,
I have been facing an error while I try to log in from the console. The server started succesfully but when I tried to log in, wl threw the exception below:
<Jun 8, 2011 3:00:14 PM EEST> <Warning> <RMI> <BEA-080009> <Error thrown by RMI server: weblogic.management.remote.iiop.IIOPServerImpl@a78299 invoking: newClient(Ljava.lang.Object;)>
<Jun 8, 2011 3:00:14 PM EEST> <Error> <Console> <BEA-240003> <Console encountered the following error java.lang.NullPointerException
 at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
 at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
 at com.bea.console.utils.MBeanUtils.lookupMBeanServerConnection(MBeanUtils.java:3209)
 at com.bea.console.utils.MBeanUtils.getDomainRuntimeMBeanServerConnection(MBeanUtils.java:1623)
 at com.bea.console.utils.MBeanUtils.getDomainRuntimeServiceMBean(MBeanUtils.java:1699)
 at com.bea.console.utils.MBeanUtilsInitializer.initMBeanUtils(MBeanUtilsInitializer.java:70)
 at com.bea.console.utils.MBeanUtilsInitializer.access$000(MBeanUtilsInitializer.java:20)
 at com.bea.console.utils.MBeanUtilsInitializer$1.run(MBeanUtilsInitializer.java:49)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Jun 8, 2011 3:00:14 PM EEST> <Error> <Console> <BEA-240003> <Console encountered the following error Error when initilize JMX connection>
<Jun 8, 2011 3:00:24 PM EEST> <Error> <Console> <BEA-240003> <Console encountered the following error java.lang.RuntimeException: weblogic.management.provider.EditFailedException:
 at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205)
 at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222)
 at weblogic.management.remote.iiop.IIOPServerImpl_1032_WLStub.newClient(Unknown Source)
 at javax.management.remote.rmi.RMIConnector.getConnection(Unknown Source)
 at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
 at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
 at com.bea.console.utils.MBeanUtils.lookupMBeanServerConnection(MBeanUtils.java:3209)
 at com.bea.console.utils.MBeanUtils.getDomainEditMBeanServerConnection(MBeanUtils.java:1636)
 at com.bea.console.utils.MBeanUtils.getEditServiceMBean(MBeanUtils.java:1493)
 at com.bea.console.utils.MBeanUtilsInitializer.initMBeanUtils(MBeanUtilsInitializer.java:71)
 at com.bea.console.utils.MBeanUtilsInitializer.initMBean(MBeanUtilsInitializer.java:34)
 at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:214)
 at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
 at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
 at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
 at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
 at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
 at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
 at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
 at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
 at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
 at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686)
 at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.renderInternal(ScopedContentCommonSupport.java:266)
 at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.render(StrutsStubImpl.java:107)
 at com.bea.netuix.servlets.controls.content.NetuiContent.preRender(NetuiContent.java:292)
 at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:428)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:727)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
 at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:146)
 at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
 at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
 at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
 at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:168)
 at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
 at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
 at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:211)
 at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:196)
 at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
 at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.management.provider.EditFailedException:
 at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1715)
 at weblogic.management.provider.internal.EditAccessImpl.getDomainBeanWithoutLock(EditAccessImpl.java:1158)
 at weblogic.management.mbeanservers.edit.internal.EditServiceMBeanImpl.getDomainConfiguration(EditServiceMBeanImpl.java:61)
 at weblogic.management.mbeanservers.edit.internal.EditServerService.registerAllMBeans(EditServerService.java:172)
 at weblogic.management.mbeanservers.edit.internal.EditServerService.access$100(EditServerService.java:45)
 at weblogic.management.mbeanservers.edit.internal.EditServerService$1$1.run(EditServerService.java:128)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.management.mbeanservers.edit.internal.EditServerService$1.accessed(EditServerService.java:125)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServer.triggerAccessCallback(WLSMBeanServer.java:90)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServer.getClassLoaderRepository(WLSMBeanServer.java:521)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$18.run(JMXConnectorSubjectForwarder.java:993)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$18.run(JMXConnectorSubjectForwarder.java:991)
 at java.security.AccessController.doPrivileged(Native Method)
 at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.getClassLoaderRepository(JMXConnectorSubjectForwarder.java:991)
 at javax.management.remote.rmi.RMIConnectionImpl$3.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.management.remote.rmi.RMIConnectionImpl.getClassLoaderRepository(Unknown Source)
 at javax.management.remote.rmi.RMIConnectionImpl.access$000(Unknown Source)
 at javax.management.remote.rmi.RMIConnectionImpl$1.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.management.remote.rmi.RMIConnectionImpl.<init>(Unknown Source)
 at weblogic.management.remote.iiop.IIOPServerImpl.makeClient(IIOPServerImpl.java:69)
 at javax.management.remote.rmi.RMIServerImpl.doNewClient(Unknown Source)
 at javax.management.remote.rmi.RMIServerImpl.newClient(Unknown Source)
 at weblogic.management.remote.iiop.IIOPServerImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
 ... 72 more
Caused by: org.xml.sax.SAXParseException: Attribute "xmlns:xsi" was already specified for element "domain".
 at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
 at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanAttribute(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source)
 at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
 at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
 at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
 at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
 at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
 at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
 at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
 at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
 at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:106)
 at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:70)
 at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:64)
 at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1878)
 at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromPending(EditAccessImpl.java:1768)
 at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1701)
 ... 98 more
>
Any ideas about it?

The core problem is: when I try to change, add or remove something from weblogic console, under weblogic domain/ pending folder, weblogic itself is creating a config.xml file with the changes that has been made but the content of it is wrong. It creates wrong xml files like, it includes 2 xsi attributes in it, it adds xmlns to each element in the xml file and the new one: it gives a different error when I try to add a new datasource. The error is
Console encountered the following error com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
Any ideas ?

Critical Weblogic server error

Hello,
I use Weblogic server to run my application. I get the below error very rarely. After restarting the server, the application works fine, but I would like to find the reason. I have pasted the errors displayed in browser and log files. Can any one help me?
Error at log file :
<Oct 2, 2009 7:00:20 AM EDT> <Error> <Security> <BEA-090060> <The AccessDecision class "weblogic.security.providers.realmadapter.AuthorizationProviderImpl" returned an error: java.lang.SecurityException: Realm Adapter ACL Mapping Failed.>
<Oct 2, 2009 7:00:20 AM EDT> <Warning> <RMI> <BEA-080005> <Exception thrown by rmi server: weblogic.jndi.internal.RootNamingNode.lookup(Ljava.lang.String;Ljava.util.Hashtable;)
weblogic.jndi.internal.AdminModeAccessException: Unable to resolve 'ReportEJBHome'. Resolved ''; remaining name ''.
weblogic.jndi.internal.AdminModeAccessException: Unable to resolve 'ReportEJBHome'. Resolved ''; remaining name ''
 at weblogic.jndi.internal.AdminModeHandler.checkLookup(AdminModeHandler.java:108)
 at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:170)
 at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
 at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)
 at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
 at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:439)
 at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:61)
 at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:983)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Error message at browser :
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
When I receive the above error, I could find the below messages missing in log file but I am not able to sort it out.
<Oct 2, 2009 4:03:45 AM EDT> <Info> <Deployer> <BEA-149059> <Module Mailer.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:45 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MailerBeanHome.>
<Oct 2, 2009 4:03:45 AM EDT> <Info> <Deployer> <BEA-149060> <Module Mailer.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:45 AM EDT> <Info> <Deployer> <BEA-149059> <Module Report.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name ReportEJBHome.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149060> <Module Report.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149059> <Module ReportRequestCriteria.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name ReportRequestCriteria.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149060> <Module ReportRequestCriteria.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149059> <Module ReportRequestDirectory.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name ReportRequestDirectoryJNDIName.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149060> <Module ReportRequestDirectory.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149059> <Module ReferenceData.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name ReferenceDataJNDIName.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149060> <Module ReferenceData.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149059> <Module User.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name User.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149060> <Module User.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149059> <Module UserInfo.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name UserInfo.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149060> <Module UserInfo.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:46 AM EDT> <Info> <Deployer> <BEA-149059> <Module Utility.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name Utility.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149060> <Module Utility.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149059> <Module ApplicationStatus.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name ApplicationStatus.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149060> <Module ApplicationStatus.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149059> <Module JMSReportSubmit.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <EJB> <BEA-010223> <EJB Deployed Message Driven Bean: LRSeSpecialsReportSubmitErrorEJB>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <EJB> <BEA-010223> <EJB Deployed Message Driven Bean: LRSeSpecialsReportSubmitMessageDrivenEJB>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149060> <Module JMSReportSubmit.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149059> <Module MxMRateCard.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MxMRateCard.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149060> <Module MxMRateCard.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149059> <Module MxMReport.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MxMReport.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149060> <Module MxMReport.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149059> <Module MxMReportRequestCriteria.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MxMReportRequestCriteria.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149060> <Module MxMReportRequestCriteria.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149059> <Module MxMReportSpecification.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MxMReportSpecificationJNDIName.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149060> <Module MxMReportSpecification.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149059> <Module MSRRateCard.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MSRRateCard.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149060> <Module MSRRateCard.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:47 AM EDT> <Info> <Deployer> <BEA-149059> <Module MSRReport.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MSRReportEJBHome.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149060> <Module MSRReport.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149059> <Module MSRReportSpecification.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MSRReportSpecificationJNDIName.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149060> <Module MSRReportSpecification.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149059> <Module MSRReportRequestCriteria.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MSRReportRequestCriteria.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149060> <Module MSRReportRequestCriteria.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149059> <Module MMRRateCard.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MMRRateCard.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149060> <Module MMRRateCard.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149059> <Module MMRReport.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MMRReportEJBHome.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149060> <Module MMRReport.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149059> <Module MMRReportRequestCriteria.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MMRReportCriteria.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149060> <Module MMRReportRequestCriteria.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:48 AM EDT> <Info> <Deployer> <BEA-149059> <Module MMRReportSpecification.jar of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:49 AM EDT> <Info> <EJB> <BEA-010009> <EJB Deployed EJB with JNDI name MMRReportSpecification.>
<Oct 2, 2009 4:03:49 AM EDT> <Info> <Deployer> <BEA-149060> <Module MMRReportSpecification.jar of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:49 AM EDT> <Info> <Deployer> <BEA-149059> <Module especials of application eSpecials is transitioning from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
<Oct 2, 2009 4:03:49 AM EDT> <Info> <Deployer> <BEA-149060> <Module especials of application eSpecials successfully transitioned from STATE_PREPARED to STATE_ADMIN on server LRSeSpecialsServer.>
Regards,
Deepak
Edited by: user10340833 on Nov 5, 2009 10:29 AM

Hi,
a quick search on Google produced this VM tuning document:
http://javaeesupportpatterns.blogspot.pt/2011/07/weblogic-permgen-space.html
Frank

Weblogic ConfigurationException Error

Hello,
I have a big problem
My System is
OS : Windows 2000 Server
EJB Server : Weblogic 5.1.0 and SP5
JDK1.2.2
My Configuration is
C:\weblogic\bin>wlconfig
WebLogic startup settings are presently:
CLASSPATH Prefix
d:\java\jdk122\lib\db.jar;d:\java\jdk122\lib\dt.jar;d:\java\
jdk122\lib\tools.jar;d:\java\j2ee\lib\j2ee.jar;d:\java\jswdk-1.0.1\lib;d:\ja
va\j
dk122\lib\xlnclient.jar;d:\java\jdk122\lib\xlnserver.jar;d:\java\jdk122\lib\
XlnW
ebServlet.jar;d:\java\jsdk20\lib\jsdk.jar;.;c:\weblogic\lib\weblogic510sp5bo
ot.j
ar
CLASSPATH
d:\java\jdk122\lib\db.jar;d:\java\jdk122\lib\dt.jar;d:\java\
jdk122\lib\tools.jar;d:\java\j2ee\lib\j2ee.jar;d:\java\jswdk-1.0.1\lib;d:\ja
va\j
dk122\lib\xlnclient.jar;d:\java\jdk122\lib\xlnserver.jar;d:\java\jdk122\lib\
XlnW
ebServlet.jar;d:\java\jsdk20\lib\jsdk.jar;.;c:\weblogic\lib\weblogic510sp5bo
ot.j
ar;d:\java\jdk122\lib\tools.jar;d:\java\jdk122\jre\lib\rt.jar;d:\java\jdk122
\jre
\lib\i18n.jar;C:\weblogic\license;C:\weblogic\classes\boot;C:\weblogic\class
es;C
:\weblogic\lib\weblogicaux.jar;C:\weblogic\eval\cloudscape\lib\cloudscape.ja
r
JAVA_HOME d:\java\jdk122
WEBLOGIC_LICENSEDIR C:\weblogic\license
WEBLOGIC_HOME C:\weblogic
system properties:
java.security.manager
java.security.policy==C:\weblogic\weblogic.policy
weblogic.system.home=C:\weblogic
java.compiler=symcjit
weblogic.class.path=c:\weblogic\lib\weblogic510sp5.jar;c:\we
blogic\license;c:\weblogic\classes;c:\weblogic\myserver\serverclasses;c:\web
logi
c\lib\weblogicaux.jar
INITIAL_HEAP 64 MB
MAX_HEAP 64 MB
SERVERCLASSPATH
d:\java\jdk122\lib\db.jar;d:\java\jdk122\lib\dt.jar;d:\java\
jdk122\lib\tools.jar;d:\java\j2ee\lib\j2ee.jar;d:\java\jswdk-1.0.1\lib;d:\ja
va\j
dk122\lib\xlnclient.jar;d:\java\jdk122\lib\xlnserver.jar;d:\java\jdk122\lib\
XlnW
ebServlet.jar;d:\java\jsdk20\lib\jsdk.jar;.;c:\weblogic\lib\weblogic510sp5bo
ot.j
ar;d:\java\jdk122\jre\lib\rt.jar;d:\java\jdk122\jre\lib\i18n.jar;C:\weblogic
\cla
sses\boot;C:\weblogic\eval\cloudscape\lib\cloudscape.jar
Type "wlconfig -help" for program usage.
My Weblogic Version is
D:\job\develop\trade>java weblogic.Admin t3://localhost:7001 VERSION
WebLogic Build: 5.1.0 Service Pack 5 08/17/2000 07:21:55 #79895
My Weblogic Server log is
Mon 8 Mon 28 16:07:02 GMT+09:00 2000: <RMI> Registry started
Mon 8 Mon 28 16:07:02 GMT+09:00 2000: <EJB> Enterprise JavaBeans
initializing
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <EJB JAR deployment
D:/job/develop/trade/
yTrader.jar>
EJB home interface: 'TraderHome' deployed bound to the JNDI name:MyTrader'
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <EJB JAR deployment
D:/job/develop/bank/M
Bank.jar> EJB home interface: 'BankHome' deployed bound to the JNDI name:
'MyBak'
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <EJB> 2 EJB jar files loaded,
containing EJBs
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <EJB> 2 deployed, 0 failed to
deploy.
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <HTTP> Log rotation is size based
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <ZAC> ZAC ACLs initialized
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <ZAC> ZAC packages stored in local
directry exports
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <ListenThread> Listening on port:
7001
<NT Performance Pack> NATIVE: created IoCompletionPort successfully.
IoPort=0x000028c
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <SSLListenThread> Listening on
port: 7002
Mon 8Mon 28 16:07:04 GMT+09:00 2000: <WebLogicServer> WebLogic Server
started
Sample program is weblogic sample program
Source URL is
http://www.weblogic.com/docs51/examples/ejb/basic/statefulSession/index.html
Trader.java, TraderBean.java, TraderHome.java,
TraderResult.java,ProcessingErrorException.java, Client.java
I have got the error message after running Client program
D:\job\develop\trade>java Client "t3://localhost:7001"
Beginning statefulSession.Client...
The client was unable to lookup the EJBHome. Please make sure
that you have deployed the ejb with the JNDI name MyTrader on the WebLogic
server at t3://localhost:7001
javax.naming.ConfigurationException.
Root exception is weblogic.rmi.server.ExportException: A description for
TraderBeanHomeImpl was found but it could not be
read due to: [Failed to find a stub for [class TraderBeanHomeImpl]
implements at
least one interface [interface TraderHome] which extends Remote.]
weblogic.rmi.StubNotFoundException: Failed to find a stub for [class
TraderBeanH
omeImpl] implements at least one interface [interface TraderHome] which
extends
Remote.
at
weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManage
r.java, Compiled Code)
at
weblogic.rmi.extensions.BasicDescriptor.<init>(BasicDescriptor.java,
Compiled Code)
at
weblogic.rmi.extensions.BasicRuntimeDescriptor.<init>(BasicRuntimeDes
criptor.java, Compiled Code)
at
weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManage
r.java, Compiled Code)
at
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManag
er.java, Compiled Code)
at
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManag
er.java, Compiled Code)
at
weblogic.rmi.internal.OIDManager.getRequestDispatcher(OIDManager.java
at
weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.
ava:76)
at
weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WL
tub.java:246)
at weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java,
Compi
ed Code)
at javax.naming.InitialContext.lookup(InitialContext.java:354)
at Client.lookupHome(Client.java:149)
at Client.<init>(Client.java:44)
at Client.main(Client.java:82)
Please help me !!!!
Thanks

In your client, when you look up the bean, the JNDI name should be "MyTrader",
not statelessSession.Client
Look at client.java in /examples/ejb/basic/statelessSession example,
In weblogic-ejb-jar.xml the jndi name is specified as follows:
<jndi-name>statelessSession.TraderHome</jndi-name>
and in the client program we look up the bean as follows:
JNDI_NAME=statelessSession.TraderHome
Object home = ctx.lookup(JNDI_NAME);
Make sure you are doing the same.
Kumar
"±è¼®" wrote:
Hello,
I have a big problem
My System is
OS : Windows 2000 Server
EJB Server : Weblogic 5.1.0 and SP5
JDK1.2.2
<snipped>
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <EJB JAR deployment
D:/job/develop/trade/
yTrader.jar>
EJB home interface: 'TraderHome' deployed bound to the JNDI name:MyTrader'
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <EJB JAR deployment
D:/job/develop/bank/M
Bank.jar> EJB home interface: 'BankHome' deployed bound to the JNDI name:
'MyBak'
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <EJB> 2 EJB jar files loaded,
containing EJBs
Mon 8 Mon 28 16:07:03 GMT+09:00 2000: <EJB> 2 deployed, 0 failed to
deploy.
Sample program is weblogic sample program
Source URL is
http://www.weblogic.com/docs51/examples/ejb/basic/statefulSession/index.html
Trader.java, TraderBean.java, TraderHome.java,
TraderResult.java,ProcessingErrorException.java, Client.java
I have got the error message after running Client program
D:\job\develop\trade>java Client "t3://localhost:7001"
Beginning statefulSession.Client...
The client was unable to lookup the EJBHome. Please make sure
that you have deployed the ejb with the JNDI name MyTrader on the WebLogic
server at t3://localhost:7001
javax.naming.ConfigurationException.
Root exception is weblogic.rmi.server.ExportException: A description for
TraderBeanHomeImpl was found but it could not be
read due to: [Failed to find a stub for [class TraderBeanHomeImpl]
implements at
least one interface [interface TraderHome] which extends Remote.]
weblogic.rmi.StubNotFoundException: Failed to find a stub for [class
TraderBeanH
omeImpl] implements at least one interface [interface TraderHome] which
extends
Remote.
at
weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManage
r.java, Compiled Code)
at
weblogic.rmi.extensions.BasicDescriptor.<init>(BasicDescriptor.java,
Compiled Code)
at
weblogic.rmi.extensions.BasicRuntimeDescriptor.<init>(BasicRuntimeDes
criptor.java, Compiled Code)
at
weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManage
r.java, Compiled Code)
at
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManag
er.java, Compiled Code)
at
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManag
er.java, Compiled Code)
at
weblogic.rmi.internal.OIDManager.getRequestDispatcher(OIDManager.java
at
weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.
ava:76)
at
weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WL
tub.java:246)
at weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java,
Compi
ed Code)
at javax.naming.InitialContext.lookup(InitialContext.java:354)
at Client.lookupHome(Client.java:149)
at Client.<init>(Client.java:44)
at Client.main(Client.java:82)
Please help me !!!!
Thanks

OIM 11G WEBLOGIC START ERROR

Hi,
I am getting the following error when I start the IDM SERVER. PLEASE HELP ME.
[2010-09-15T16:51:20.481+04:00] [OJDL] [NOTIFICATION:16] [ODL-52001] [oracle.core.ojdl.FileLogWriter] [org: Oracle] [host: idmapps] [nwaddr: 127.0.0.1] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: idmadmin] deleting log file: oim_server1-diagnostic-13.log, size: 10326620 bytes
[2010-09-15T16:51:20.474+04:00] [oim_server1] [ERROR] [] [oracle.adf.share.config.ADFMDSConfig] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: OracleSystemUser] [ecid: 0000IgLSkCKFw000jzwkno1CZz2V0001Ww,0] [APP: wsm-pm] [dcid: 11d1def534ea1be0:55762d10:12b1249e448:-7ffd-0000000000001930] MDSConfigurationException encountered in parseADFConfigurationMDS-01330: unable to load MDS configuration document [[
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
ORA-06550: line 1, column 12:
PLS-00201: identifier 'MDS_INTERNAL_SHREDDED.GETREPOSITORYVERSION' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
ORA-06550: line 1, column 12:
PLS-00201: identifier 'MDS_INTERNAL_SHREDDED.GETREPOSITORYVERSION' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
 at oracle.mds.config.PConfig.loadFromBean(PConfig.java:695)
 at oracle.mds.config.PConfig.<init>(PConfig.java:504)
 at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:692)
 at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:749)
 at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:407)
 at oracle.mds.core.MDSInstance.getMDSConfigFromDocument(MDSInstance.java:2011)
 at oracle.mds.core.MDSInstance.createMDSInstanceWithCustomizedConfig(MDSInstance.java:1171)
 at oracle.mds.core.MDSInstance.getOrCreateInstance(MDSInstance.java:571)
 at oracle.adf.share.config.ADFMDSConfig.parseADFConfiguration(ADFMDSConfig.java:137)
 at sun.reflect.GeneratedMethodAccessor546.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at oracle.adf.share.config.ADFConfigImpl.getResultFromComponent(ADFConfigImpl.java:443)
 at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.java:508)
 at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.java:491)
 at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.java:547)
 at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.java:542)
 at oracle.adf.share.config.ADFContextMDSConfigHelperImpl.getMDSInstance(ADFContextMDSConfigHelperImpl.java:274)
 at oracle.adf.share.ADFContext.getMDSInstanceAsObject(ADFContext.java:1210)
 at oracle.wsm.repository.mds.MDSInstanceFactory.getMDSInstance(MDSInstanceFactory.java:92)
 at oracle.wsm.policymanager.bean.AbstractBean.<init>(AbstractBean.java:92)
 at oracle.wsm.policymanager.bean.DocumentManagerBean.<init>(DocumentManagerBean.java:100)
 at oracle.wsm.policymanager.bean.ejb.DocumentManagerEJB.<init>(DocumentManagerEJB.java:41)
 at oracle.wsm.policymanager.bean.ejb.DocumentManager_ookznn_Impl.<init>(DocumentManager_ookznn_Impl.java:42)
 at sun.reflect.GeneratedConstructorAccessor451.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
 at java.lang.Class.newInstance0(Class.java:355)
 at java.lang.Class.newInstance(Class.java:308)
 at com.bea.core.repackaged.springframework.jee.spi.EjbComponentCreatorBrokerImpl.getBean(EjbComponentCreatorBrokerImpl.java:69)
 at weblogic.ejb.container.injection.EjbComponentCreatorImpl.getBean(EjbComponentCreatorImpl.java:68)
 at weblogic.ejb.container.manager.BaseEJBManager.createNewBeanInstance(BaseEJBManager.java:216)
 at weblogic.ejb.container.manager.BaseEJBManager.allocateBean(BaseEJBManager.java:231)
 at weblogic.ejb.container.manager.StatelessManager.createBean(StatelessManager.java:303)
 at weblogic.ejb.container.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:201)
 at weblogic.ejb.container.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:127)
 at weblogic.ejb.container.manager.StatelessManager.preInvoke(StatelessManager.java:148)
 at weblogic.ejb.container.internal.BaseRemoteObject.preInvoke(BaseRemoteObject.java:230)
 at weblogic.ejb.container.internal.StatelessRemoteObject.__WL_preInvoke(StatelessRemoteObject.java:41)
 at oracle.wsm.policymanager.bean.ejb.DocumentManager_ookznn_IRemoteDocumentManagerImpl.retrieveDocuments(DocumentManager_ookznn_IRemoteDocumentManagerImpl.java:604)
 at oracle.wsm.policymanager.bean.ejb.DocumentManager_ookznn_IRemoteDocumentManagerImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
 at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
 at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
 at oracle.wsm.policymanager.bean.ejb.DocumentManager_ookznn_IRemoteDocumentManagerImpl_1033_WLStub.retrieveDocuments(Unknown Source)
 at oracle.wsm.policymanager.client.DocumentManagerDelegate$9.run(DocumentManagerDelegate.java:346)
 at oracle.wsm.policymanager.client.DocumentManagerDelegate$9.run(DocumentManagerDelegate.java:343)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
 at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
 at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
 at weblogic.security.Security.runAs(Security.java:61)
 at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
 at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
 at oracle.wsm.policymanager.client.DocumentManagerDelegate.retrieveDocuments(DocumentManagerDelegate.java:342)
 at oracle.wsm.policymanager.accessor.BeanAccessor.updateCache(BeanAccessor.java:1139)
 at oracle.wsm.policymanager.accessor.BeanAccessor.fetchDocuments(BeanAccessor.java:590)
 at oracle.wsm.policymanager.accessor.BeanAccessor.access$300(BeanAccessor.java:111)
 at oracle.wsm.policymanager.accessor.BeanAccessor$MissingDocsFetcherTask.run(BeanAccessor.java:165)
 at oracle.wsm.common.scheduler.TimerManagerWrapper$TimerListenerImpl.timerExpired(TimerManagerWrapper.java:62)
 at weblogic.timers.internal.commonj.ListenerWrap.timerExpired(ListenerWrap.java:37)
 at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
For the first error and looking from WebLogic perspective "<EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was: java.lang.OutOfMemoryError." because MAXPERMSIZE in the start<servername>.cmd|SH is configured to small for the application. Normal solution should be increase MAXPERMSIZE . But you are also getting this "<BEA-010216> <The Message-Driven EJB: oimKernelQueueMDB is throwing exception when processing the messages." I recommend you to open an SR in Oracle Metalink to solve these errors.
regards,
Thiago L Guimaraes.

Weblogic.rmi.internal.LocalServerRefMissing

I am Attempting to serialize and deserialize a stateful session
bean. The deserialization seems to be the problem. I have
figured out that the line throwing the error is the "readObject"
line.
A similar problem was reported on Jan 31 2002, but the solution
suggested deals with the "getEJBObject" line. I have tryed to
implement this solution, as you can see below, but since the
error I am getting is thrown before getting to that line, it
makes no difference.
The Exception I am getting is an "InvalidClassException".
The message reads as follows = "weblogic.rmi.internal.
LocalServerRefMissing no-arg constructor for class".
As far as the "no-arg constructor" error goes, as I understand
it I should not be having that problem. My Session bean
implements the SessionBean interface and does not explicitly
extend anything, so by default it extends Object, right?!
Object has a no-args constructor, so there should be no problem.
My code is as follows:
---SERIALIZATION---
Handle msaHandle = contributions.getHandle();
ObjectOutputStream toFile = new ObjectOutputStream(
new FileOutputStream(handleFile));
toFile.writeObject(msaHandle);
toFile.close();
---DESERIALIZATION---
ObjectInputStream fromFile = new ObjectInputStream(
new FileInputStream(handleFile));
Handle msaHandle = (Handle) fromFile.readObject();
//MsaSession contributions =
(MsaSession) msaHandle.getEJBObject();
MsaSession contributions = (MsaSession) javax.rmi.PortableRemote
Object.narrow(msaHandle.getEJBObject(), MsaSession.class);
fromFile.close();
I have tried to print "classname" (available in the
InvalidClassException class), but only get null as the value.
Anyone have any ideas?
Matthew

I am Attempting to serialize and deserialize a stateful session
bean. The deserialization seems to be the problem. I have
figured out that the line throwing the error is the "readObject"
line.
A similar problem was reported on Jan 31 2002, but the solution
suggested deals with the "getEJBObject" line. I have tryed to
implement this solution, as you can see below, but since the
error I am getting is thrown before getting to that line, it
makes no difference.
The Exception I am getting is an "InvalidClassException".
The message reads as follows = "weblogic.rmi.internal.
LocalServerRefMissing no-arg constructor for class".
As far as the "no-arg constructor" error goes, as I understand
it I should not be having that problem. My Session bean
implements the SessionBean interface and does not explicitly
extend anything, so by default it extends Object, right?!
Object has a no-args constructor, so there should be no problem.
My code is as follows:
---SERIALIZATION---
Handle msaHandle = contributions.getHandle();
ObjectOutputStream toFile = new ObjectOutputStream(
new FileOutputStream(handleFile));
toFile.writeObject(msaHandle);
toFile.close();
---DESERIALIZATION---
ObjectInputStream fromFile = new ObjectInputStream(
new FileInputStream(handleFile));
Handle msaHandle = (Handle) fromFile.readObject();
//MsaSession contributions =
(MsaSession) msaHandle.getEJBObject();
MsaSession contributions = (MsaSession) javax.rmi.PortableRemote
Object.narrow(msaHandle.getEJBObject(), MsaSession.class);
fromFile.close();
I have tried to print "classname" (available in the
InvalidClassException class), but only get null as the value.
Anyone have any ideas?
Matthew

Java.lang.ClassCastException: Cannot narrow remote object weblogic.rmi.inte

Hi,
I am trying to deploy ejb3.0 on weblogic 10 server. I am able to find the JNDI name of the stateless session bean correctly, but getting an exception while narrowing it down. My ejb3.0 client is a standalone java client. I am trying to access the stateless session ejb3.0 bean.Please help me. i have been trying it for many days.
thanks in advance,
Sanjeev
[sanpraka@localhost certEjb]$ java -cp ./:/usr/weblogic/bea/wlserver_10.0/server/lib/weblogic.jar:/usr/weblogic/bea/wlserver_10.0/server/lib/wlclient.jar com.titan.clients.Client
Object is weblogic.rmi.internal.BasicRemoteRef - hostID: '5337880647112897730S:127.0.0.1:[7001,7001,-1,-1,-1,-1,-1]:wl_server:examplesServer', oid: '302', channel: 'null'
java.lang.ClassCastException: Cannot narrow remote object weblogic.rmi.internal.BasicRemoteRef - hostID: '5337880647112897730S:127.0.0.1:[7001,7001,-1,-1,-1,-1,-1]:wl_server:examplesServer', oid: '302', channel: 'null' to com.titan.travelagent.TravelAgentRemote
at weblogic.corba.server.naming.ReferenceHelperImpl.narrow(ReferenceHelperImpl.java:206)
at weblogic.rmi.extensions.PortableRemoteObject.narrow(PortableRemoteObject.java:88)
at weblogic.iiop.PortableRemoteObjectDelegateImpl.narrow(PortableRemoteObjectDelegateImpl.java:32)
at javax.rmi.PortableRemoteObject.narrow(Unknown Source)
at com.titan.clients.Client.main(Client.java:24)
[sanpraka@localhost certEjb]$

We have a similar problem. We have a web application (on server A) that invokes an EJB on a remote server (server B). This works fine, until we deploy another web application to server A at which point the existing web application starts to throw java.lang.ClassCastException when narrowing the remote EJB interface. The exception starts to be thrown at the moment the latter web application is deployed - start is not required.
The latter web application contains (actually in APP-INF/lib) the old version of the EJB remote interface, that somehow gets to be loaded into the classpath of the existing web application. The solution is to delete the old version of the EJB remote interface from APP-INF/lib of the latter web application (we didn't need it anyway), but it would be interesting to know in which circumstances classes can get mixed between enterprise applications.
I failed to reproduce the error in simple scenario, so this does not happen always.

Getting :java.lang.ClassCastException: weblogic.rmi.internal.MethodDescript

Hi I am getting the following exception:
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
     at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:186)
     at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:300)
     at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:901)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:361)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
     at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1181)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:110)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
     at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
can any body explain the Cause for this exception and what will be the impact on the server.
but if i restart the server the error is not coming

Hi I am getting the following exception:
java.lang.ClassCastException: weblogic.rmi.internal.MethodDescriptor
     at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:186)
     at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:300)
     at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:901)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:361)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
     at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1181)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:110)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
     at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
can any body explain the Cause for this exception and what will be the impact on the server.
but if i restart the server the error is not coming

Weblogic JNDI error

Am unable to start jms subscriberes.
i get below error
javax.naming.NameNotFoundException: While trying to lookup 'TOPIC.XYZ didn't find subcontext 'TOPIC'. Resolved ''
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I checked my settings in the code and am using the correct TOPIC name .
Any suggestions would be very helpful
Thanks,
Vij

newbiejava wrote:
I checked my settings in the code and am using the correct TOPIC name .
Any suggestions would be very helpfulI'm not promising that I'll be one of the individuals to try to help, but for starters don't you think what you posted so far is completely insufficient? Don't you think showing what you think is the relevant code and configuration would be more relevant than just saying you already think you're doing it right?
All that's left for someone remote so far, is to say: Well obviously you're doing something wrong. But since we don't know what you're really doing, we can't tell you.

Weblogic problem,weblogic.rmi.extensions.RemoteRuntimeException: Unexpected

hello，everyone.
I have a problem.please help me.
My application is running on weblogic 9.2. My oracle is oracle10g. system:linux redhat4.
my weblogic's log have a problem.
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
at weblogic.jdbc.rmi.SerialStatement.close(SerialStatement.java:109)
at com.goldpalm.common.jdbc.DBController.releaseConn(DBController.java:273)
at com.goldpalm.sale.team.TeamXml.exeTeamLog(TeamXml.java:762)
at jsp_servlet._ctssale.__teamline_show._jspService(__teamline_show.java:264)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:230)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at filters.AuthFilter.doFilter(AuthFilter.java:95)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3200)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1844)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Hi
Looking at the error stack trace, you are getting this error when trying to close the statement object from your own java code (not weblogic code...) - DBController.releaseConn(...)
at com.goldpalm.common.jdbc.DBController.releaseConn(DBController.java:273)
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
at weblogic.jdbc.rmi.SerialStatement.close(SerialStatement.java:109)
at com.goldpalm.common.jdbc.DBController.releaseConn(DBController.java:273)
at com.goldpalm.sale.team.TeamXml.exeTeamLog(TeamXml.java:762)
Well check the code you have at this location. Usually the way we release/close the db resources are like first close ResultSet, then Statement, then Connection. But if you close connection first, then try to close the Statement object, it throws errors like what you see.
I am giving 2 methods code snippet. One method is caleld like closeAll(..). This method gets called in finally block of all other db methods that does the actual db code to connect and get data etc etc.
// Sample main method that does all db stuff...This is just code snippet only and NOT the full code. Focus on try catch finally block
public static void getCustomerProfile(long custId) throws Exception {
     Connection aConnection = getConnection();
     CallableStatement aCallableStatement = null;
     ResultSet aResultSet = null;
     try {
          aCallableStatement = aConnection.prepareCall("{ call someFunction(?, ?) }");
          aCallableStatement.execute();
          aResultSet = (ResultSet) aCallableStatement.getObject("variable_name_from_sp");
          while(aResultSet.next()) {
               // get all data for each record etc...
     } catch (Exception e) {
          e.printStackTrace();
          throw e;
     } finally {
          closeAll(aConnection, aCallableStatement, aResultSet);
// While closing RS, Statment, Connection, enclose them in their own try/catch block and ofcourse check for nulls first
public static void closeAll(Connection aConn, Statement aStmt, ResultSet aRS) {
     if (aRS != null) {
          try {
               aRS.close();
          } catch (Exception e) {
               System.out.println("Not Able To Close The ResultSet");
               //e.printStackTrace();
     if (aStmt != null) {
          try {
               aStmt.close();
          } catch (Exception e) {
               System.out.println("Not Able To Close The Statement");
               //e.printStackTrace();
     if (aConn != null) {
          try {
               aConn.close();
          } catch (Exception e) {
               System.out.println("Not Able To Close The Connection");
               //e.printStackTrace();
}Thanks
Ravi Jegga

StuckThreadMaxTime,"weblogic.rmi.internal.dgc.DGCClientImpl$HeartBeat@53ce6

Hi guys!
I am having a problem suddenly with weblogic application server on aix box. I am getting error after couple of users login.managed Server is getting shutdown. Here is the description of the error.
<weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '47' for queue: 'weblogic.kernel.Default' has been busy for "717" seconds working on the request "weblogic.rmi.internal.dgc.DGCClientImpl$HeartBeat@53ce690f", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
Please suggest something to fix this problem.can you explain how we can check thread dumps in weblogic on unix environment.
-Chandu

Paul Eddington wrote:
Thanks for the response.
We don't have any connection pools defined.
The application we have deployed gets information from the DB all the time. But it makes it's own connection. We connect to an Oracle 9i DB running on a different server. We are running on AIX 5.3 servers.
Thanks again
PaulHi. nevermind about the pool question. If/when you get that sort of message you want to get a thread
dump of the server or find the log where it shows the full stacktrace of that thread. The message
simply says a thread has been busy or hanging longer than the WLS limit (configurable). The thread
could be hung on a lock, waiting for the DBMS, in an infinite loop, os simply not done yet with
some job that is taking more than the stuck-thread-limit. WLS doesn't actually know what the
thread is doing...
Joe

Questions on Weblogic RMI

Hi
          I've a few questions on WL RMI that I couldn't figure out from the
          documentation.
          Suppose I have a cluster containing Weblogic servers server1 and server2.
          Server1 hosts an RMI object o1 that is bind to the cluster wide JNDI tree.
          O1 implements remote interface i1 that has a method m1 which takes as an
          argument an object o2 implementing remote interface i2. That is:
          public class o1 implements i1 {...}
          public interface i1 extends weblogic.rmi.Remote {
          public void m1 (i2 _o2);
          public class o2 implements i2 {...}
          public interface i2 extends weblogic.rmi.Remote {...}
          Now if inside server2 I create o2 using the default constructor, lookup a
          reference to o1 and call method m1, will o2 get passed by value or by
          reference? Is there any way to control this? What if I don't use the
          constructor to create the object but the object is hosted in server2 and I
          get a reference to the object using JNDI lookup? In short, how does WL RMI
          decide when to pass an object by reference and when by value.
          I'm trying to increase the scalability of a system by distributing its
          modules as RMI objects to several machines running Weblogic server, and I
          need to know the details on how WL RMI works. The documentation seems to be
          rather inadequate...
          Thanks for reading this far :)
          - Juha


Actually, O2 will always be passed by reference because it is an RMI object
          (i.e., it implements weblogic.rmi.Remote). If O2 were a non-RMI object, it would
          be passed by value if O1 is in a different process and by reference if O1 and O2
          are in the same process.
          Edwin Marcial wrote:
          > My 2 cents on this:
          >
          > I believe in this case, since O2 is a remote object, it will get passed by
          > reference. If it were not a remote object, it would be passed by value.
          >
          > Edwin
          >
          > "Juha Lindström" wrote:
          >
          > > Hi
          > >
          > > I've a few questions on WL RMI that I couldn't figure out from the
          > > documentation.
          > > Suppose I have a cluster containing Weblogic servers server1 and server2.
          > > Server1 hosts an RMI object o1 that is bind to the cluster wide JNDI tree.
          > > O1 implements remote interface i1 that has a method m1 which takes as an
          > > argument an object o2 implementing remote interface i2. That is:
          > >
          > > public class o1 implements i1 {...}
          > >
          > > public interface i1 extends weblogic.rmi.Remote {
          > > public void m1 (i2 _o2);
          > > }
          > >
          > > public class o2 implements i2 {...}
          > >
          > > public interface i2 extends weblogic.rmi.Remote {...}
          > >
          > > Now if inside server2 I create o2 using the default constructor, lookup a
          > > reference to o1 and call method m1, will o2 get passed by value or by
          > > reference? Is there any way to control this? What if I don't use the
          > > constructor to create the object but the object is hosted in server2 and I
          > > get a reference to the object using JNDI lookup? In short, how does WL RMI
          > > decide when to pass an object by reference and when by value.
          > >
          > > I'm trying to increase the scalability of a system by distributing its
          > > modules as RMI objects to several machines running Weblogic server, and I
          > > need to know the details on how WL RMI works. The documentation seems to be
          > > rather inadequate...
          > >
          > > Thanks for reading this far :)
          > >
          > > - Juha

Weblogic RMI error

Similar Messages

Maybe you are looking for