Cannot start application deployed using Weblogic console after stop

Hello all,
I have deployed an ear file using Weblogic console. If the app. is running, I can press stop and get the 404 error...after that I press start, and get a 503 error. Right after the app is deployed, and started, it always comes up fine. But when the application is running, I must click stop, start, stop, start to get the app to start.
To start the app. I select, start and then "servicing all requests". To stop the app, I select stop and then "Force stop now". I have implemented a subclass of ServletContextListener to handle the start and stop. These methods do get called.
The 503 did not cause any errors to be found in the weblogic.log, stdout.log or access.log.
Does anyone have an idea how to start the app after it is stopped the first time?
Thanks in advance.
-PD
Edited by pauladecker at 10/01/2007 1:47 PM

Hi,
As you see this error.
[J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.webcenter.framework, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.sdp.client, exact-match: false].
there is some miss match in library reference.
Please check with your weblogic-application.xml file.
Regards,
Kal

Similar Messages

Problem with CORBA application deployed using Java Web Start 1_6_0.

Java Web Start fans and experts:
We have been using Java Web Start to deploy the client side of a CORBA-based application since the inception of Java Web Start ... including Java Web Start 1.0 right up through the present.
With Java Web Start 1_6_0, we see evidence that Web Start is "tinkering with" the IOR that CORBA uses to communicate. In all previous versions of Java Web Start, independent of the JRE which the application uses, the stringified IOR have been the same size regardless of whether the application is deployed locally or via Java Web Start. With Java Web Start 1_6_0, the stringified IOR is much longer than the "real" IOR (again, regardless of the JRE used by the application itself). To me this smells like a bug in Java Web Start 1_6_0. Has anyone else observed this behavior?
Here are some specifics .... I've run the same client application with various JREs both with and without Java Web Start as the deployment mechanism. The application was compiled and runs against servers that are running JDK 1_5_0_09.
Here is the summary of my results from a Linux box running various JREs, various versions of Java Web Start, and also running as a non-JWS deployed application. I've listed the length of the stringified IOR in each case.
JRE 1.5.0 non-JWS client: stringified IOR length = 344
JRE 1.6.0 non-JWS client: stringified IOR length = 344 ... this, I think, excludes the JRE as the cause of these problems.
Java WS 1.5.0, JRE 1.5.0 JWS client: stringified IOR length = 344
Java WS 1.5.0, JRE 1.6.0 JWS client: stringified IOR length = 344
Java WS 1.6.0, JRE 1.6.0 JWS client: stringified IOR length = 1568
Java WS 1.6.0, JRE 1.5.0 JWS cleint: stringified IOR length = 1568
In all cases, the stringified IOR length is determined by the service receiving the message and is always running JRE 1_5_9_09 and is
always the same 344 characters in length UNLESS it was deployed
using Java Web Start 1_6_0, in which case it in nearly 5 times as big!
To me, it sure looks as if there is a problem with Java Web Start 1_6_0 to be adding so much to the stringified IOR. Note: it's hard to tell how different the underlying IOR is in the JWS 1_6_0 case because, unlike most other ORBs, the Sun ORB doesn't have a tool to extract the IOR into a human readable structure. However, I can think of no good reason why the identical application deployed using Java Web Start 1_6_0 should have a stringified IOR length that is different than that of the same application deployed in non-JWS form or should differ from the behavior seen in all previous releases of Java Web Start.
Any clues or suggestions? Has anyone else observed this behavior?
Thanks,
John

Hi.
I got a different problem. My Corba application works in JRE 1.6, but doesn't works in JRE 1.5.X. I got an unexpected error and my console shows:
getSubjectX500Principal NoSuchMethodError: java.lang NoSuchMethodError
#### Java Web Start Error:
#### null
Can you help me?

Can't start WebLogic Server with SP6 and jdk1.2.2 using WebLogic Console

Hi All,
I am trying to install WebLogic 5.1 with SP6 under Windows NT 4.0 with SP6. My goal is to run JSP/Servlets. After going through all the steps described in SP6 Readme I am getting th following exception:
ava.lang.reflect.InvocationTargetException: java.lang.NoSuchMethodError: weblogic.boot.ServerClassLoader: method getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
 at weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:140)
 at weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:112)
 at weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:104)
 at weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(RecursiveReloadOnModifyClassLoader.java:53)
 at weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<init>(RecursiveReloadOnModifyClassLoader.java:149)
 at weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextImpl.java:1408)
 at weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:518)
 at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java, Compiled Code)
 at weblogic.t3.srvr.HttpServer.start(HttpServer.java:388)
 at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
 at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
 at java.lang.reflect.Method.invoke(Native Method)
 at weblogic.Server.startServerDynamically(Server.java:99)
 at weblogic.Server.main(Server.java:65)
 at weblogic.Server.main(Server.java:55)
The installation document is pretty bad intermixing different types of installations. Where can I find steps or what do I need to do to get WebLogic to run with JDK1.2.2 if I want to start it up from WebLogic console only?
Thanks,
Mark.

Try rather using the 1.4 version available here: http://java.sun.com/j2ee/1.4/
and use this dedicated forum: http://forum.java.sun.com/forum.jsp?forum=136
-Alexis

Profiling of Application deployed in weblogic

Hi All,
I am looking for a profiling a application deployed in weblogic.
I used jvisualvm & Jconsole. But I am looking for visual tool which can show the class/reference like jvisualvm does under profile section.
But for my weblogic, it is not showing any reference.
I guess either i need to give special java option while starting weblogic or need to use some other profiler.
Any help will be appreciated.

Hi,
You can use JRockit Mission Control to profile your application on weblogic.
http://www.oracle.com/technetwork/middleware/jrockit/overview/index-090630.html

NPE when starting application deployed to Glassfish

Hi,
When I starting application deployed to glassfish I get the following error:
[#|2012-09-25T15:02:22.209+0200|FINEST|glassfish3.1.2|oracle.adf.share.http.ServletADFContext|_ThreadID=23;_ThreadName=Thread-2;ClassName=oracle.adf.share.http.ServletADFContext;MethodName=resetThreadContext;|Reset thread|#]
[#|2012-09-25T15:02:22.209+0200|CONFIG|glassfish3.1.2|oracle.adf.model.servlet.ADFBindingFilter|_ThreadID=23;_ThreadName=Thread-2;|ADF web request|#]
[#|2012-09-25T15:02:22.210+0200|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=23;_ThreadName=Thread-2;|StandardWrapperValve[Faces Servlet]: PWC1406: Servlet.service() for servlet Faces Servlet threw exception
java.lang.NullPointerException
at oracle.adfinternal.view.faces.partition.FeatureHandler._startFeaturesChildElement(FeatureHandler.java:178)
at oracle.adfinternal.view.faces.partition.FeatureHandler.startElement(FeatureHandler.java:76)
at org.allcolor.xml.parser.CShaniSaxParser.parseStartTag(CShaniSaxParser.java:1375)
at org.allcolor.xml.parser.CXmlParser.parseSTARTTag(CXmlParser.java:1405)
at org.allcolor.xml.parser.CXmlParser.parse(CXmlParser.java:682)
at org.allcolor.xml.parser.CShaniSaxParser.parse(CShaniSaxParser.java:767)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at oracle.adfinternal.view.faces.partition.FeatureUtils._parseFeatures(FeatureUtils.java:146)
at oracle.adfinternal.view.faces.partition.FeatureUtils._parseFeatures(FeatureUtils.java:89)
at oracle.adfinternal.view.faces.partition.FeatureUtils.loadFeatures(FeatureUtils.java:48)
at oracle.adfinternal.view.faces.partition.PartitionManager._createPartitionManager(PartitionManager.java:282)
at oracle.adfinternal.view.faces.partition.PartitionManager.init(PartitionManager.java:108)
at oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator.init(RegistrationConfigurator.java:153)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:399)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:205)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.getExternalContext(GlobalConfiguratorImpl.java:328)
at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit.<init>(FacesContextFactoryImpl.java:84)
at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:62)
at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:498)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:173)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:180)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)
|#]
The application runs fine on weblogic.
I have no idea how to debug this issue.
Few other applications runs fine on glassfish.
I tested on GlassFish Server Open Source Edition 3.1.2.2, windows 64, JDK 1.6.0_24
Best Regards,
Miroslaw

I fixed the problem myself.
My application contained a xml-apis.jar in which SAX parser has been set to non-Oracle implementation, removing this jar fixes the problem.
Miroslaw

Can you reload web application from the Weblogic console?

 Good day, eh!
 Can you reload all your jsp/servlet classes of your
 web application from the Weblogic console?
 A one big button labeled 'Reload application' would be very
 good property in Weblogic
 Thanks for Your answers
 - hoser


Hi,
 I agree it is a much needed feature. Suppose I just change an init
 param of one application in the web.xml, I don't want to take down the
 15 other webapps running on my server just to be able to have that web
 app restart and re-read is configuration. Of course, I could program
 some servlet that allows changing application attributes and to enable
 restarting, but really this a)does not cover all the cases (i.e. addind
 an EBJ reference binding to web.xml) b) should be provided by the app
 server, not programmed by every little programmer again & again.
 Mathieu
 Jeff Nowakowski wrote:
 >
 > The URL you give refers to redeploying EJBs, not web applications. Being
 > able to redeploy a web application would be a very convenient feature.
 >
 > -Jeff
 >
 > Gene Chuang <[email protected]> wrote in message news:[email protected]...
 > > Button is already there!
 > >
 > > http://www.weblogic.com/docs51/techdeploy/hotdeploy.html#consoledeployejb
 > >
 > > Gene
 > >
 > > "hoser" <[email protected]> wrote in message
 > > news:[email protected]...
 > > >
 > > > Good day, eh!
 > > >
 > > > Can you reload all your jsp/servlet classes of your
 > > > web application from the Weblogic console?
 > > >
 > > > A one big button labeled 'Reload application' would be very
 > > > good property in Weblogic
 > > >
 > > > Thanks for Your answers
 > > >
 > > > - hoser
 > >
 > >

Using Weblogic Console Extension tag library...

Now i am working with weblogic 8.1
I am using Weblogic Console Extension Example...downloaded from dev2dev.bea.com...
at that example console Jsp program is as below for
the development of node...
 
<wl:node
label='<%="My Console Extension"%>'
icon='/images/folder.gif'
expanded='true'>
</wl:node>
 
But i want two folder icons...for open folder...and closed folder...
 
i have gifs...but how i modify this
jsp...or tag library...any one can help me...
 
raju

"Otherwise let me know tools that can tell me threads, memory, cpu, etc and provide notification, etc." -- Hi, I'm familiar with a third-party tool that is suitable for larger deployments, it collects the data you mention for Weblogic instances and also does performance monitoring at the cluster level. Here is a description of their WebLogic integration pack -- http://www.evidentsoftware.com/products/clearstone-for-weblogic/. Hope this helps.

Monitering web users at real time using weblogic console?

Is there a way to monitor web users at real time using weblogic console.
I want to see no. of active HTTP sessions, no. of HTTP requests at any
point of time, opening and closing of a session...etc..
thanks in advance

See recent discussion in "servlet" newsgroup.
Cameron Purdy, LiveWater
"Manjunath Kalmani" <[email protected]> wrote in message
news:[email protected]..
Is there a way to monitor web users at real time using weblogic console.
I want to see no. of active HTTP sessions, no. of HTTP requests at any
point of time, opening and closing of a session...etc..
thanks in advance

I cannot start my MacBook Pro 15" even after many try's.

I cannot start my MacBook Pro 15" even after many try's. Could it be due to not ejecting my external hard drive, or have just installed the airport express. Urgent help would be appreciated.

Run throught this list of fixes
..Step by Step to fix your Mac

Error While Starting WebLogic Console after SSM Configuration

Hi,
I have installed Oracle Entitlement Server 10.1.4.3, and have Admin Server and WebLogic SSM running in separate homes on Windows XP Pro machine.
Have followed standard documentation and completed the steps for Configuring SSMs using ConfigTool (http://download.oracle.com/docs/cd/E12890_01/ales/docs32/installssms/SSM_Configs.html).
Followed by that while securing the WebLogic Server as per documentation - http://download.oracle.com/docs/cd/E12890_01/ales/docs32/integrateappenviron/configWLS.html, am unable to access the Console app. WebLogic domain is startingup properly, but unable to access the Console.
Following is the error stack in Admin server log:
####<24-Nov-2010 14:43:42 o'clock GMT> <Info> <Health> <ldndwm291637> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1290609822769> <BEA-310002> <85% of the total memory in the server is free>
####<24-Nov-2010 14:48:55 o'clock GMT> <Info> <WorkManager> <ldndwm291637> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290610135628> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
####<24-Nov-2010 14:48:59 o'clock GMT> <Error> <HTTP> <ldndwm291637> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290610139535> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
java.lang.IllegalAccessError: tried to access method com.bea.utils.misc.ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com.bea.utils.misc.ProcessUtil
 at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
 at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
 at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
 at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
 at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
 at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
 at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
 at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:182)
 at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:131)
 at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:75)
 at javax.servlet.GenericServlet.init(GenericServlet.java:241)
 at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:36)
 at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
 at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
 at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
 at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
 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)
>
####<24-Nov-2010 14:48:59 o'clock GMT> <Error> <J2EE> <ldndwm291637> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290610139550> <BEA-160001> <Error deploying Internal Application: weblogic.application.ModuleException: [HTTP:101216]Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
java.lang.IllegalAccessError: tried to access method com.bea.utils.misc.ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com.bea.utils.misc.ProcessUtil
 at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
 at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
 at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
 at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
 at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
 at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
 at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
 at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:182)
 at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:131)
 at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:75)
 at javax.servlet.GenericServlet.init(GenericServlet.java:241)
 at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:36)
 at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
 at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
 at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
 at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
 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)
weblogic.application.utils.StateChangeException: weblogic.application.ModuleException: [HTTP:101216]Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
java.lang.IllegalAccessError: tried to access method com.bea.utils.misc.ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com.bea.utils.misc.ProcessUtil
 at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
 at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
 at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
 at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
 at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
 at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
 at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
 at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:182)
 at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:131)
 at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:75)
 at javax.servlet.GenericServlet.init(GenericServlet.java:241)
 at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:36)
 at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
 at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
 at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
 at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
 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)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:109)
 at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
 at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
 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)
Caused By: weblogic.application.ModuleException: [HTTP:101216]Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
java.lang.IllegalAccessError: tried to access method com.bea.utils.misc.ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com.bea.utils.misc.ProcessUtil
 at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
 at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
 at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
 at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
 at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
 at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
 at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
 at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:182)
 at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:131)
 at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:75)
 at javax.servlet.GenericServlet.init(GenericServlet.java:241)
 at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:36)
 at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
 at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
 at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
 at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
 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)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1399)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
 at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
 at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
 at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
 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)

Did you ever find a resolution for this? I have run into the same issue while upgrading from 10.3.1 to 10.3.3.
####<Jan 17, 2011 8:14:40 PM EST> <Error> <HTTP> --<SERVER-NAME>-- <AdminServer> <ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1295313280200> <BEA-101093> <Problem occurred while dispatching servlet request.
weblogic.management.DeploymentException:
 at weblogic.application.internal.BackgroundDeploymentService.OnDemandURIAccessed(BackgroundDeploymentService.java:166)
 at weblogic.servlet.internal.OnDemandManager.loadOnDemandURI(OnDemandManager.java:106)
 at weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTTP.java:327)
 at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:177)
 at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:901)
 at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
 at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:215)
 at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:177)
 at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused By: java.lang.IllegalAccessError: tried to access method com/bea/utils/misc/ProcessManager.vloadProcess(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/util/Vector; from class com/bea/utils/misc/ProcessUtil
 at com.bea.utils.misc.ProcessUtil.getPropValues(Unknown Source)
 at com.bea.p13n.license.LicenseHelper.getLicensePropertyValues(LicenseHelper.java:259)
 at com.bea.netuix.servlets.services.LightNetUIxServices.getRestrictedPortalLimit(LightNetUIxServices.java:140)
 at com.bea.netuix.servlets.manager.UIServlet.reinitInternal(UIServlet.java:177)
 at com.bea.netuix.servlets.manager.UIServlet.initInternal(UIServlet.java:164)
 at com.bea.netuix.servlets.manager.UIServlet.access$100(UIServlet.java:60)
 at com.bea.netuix.servlets.manager.UIServlet$ServletLifecycleListenerImpl.init(UIServlet.java:555)
 at com.bea.netuix.util.ServletLifecycleListener.initOrReinitInternal(ServletLifecycleListener.java:131)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:252)
 at com.bea.netuix.util.ServletLifecycleService.addServletLifecycleListener(ServletLifecycleService.java:183)
 at com.bea.netuix.servlets.manager.UIServlet.init(UIServlet.java:135)
 at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:77)
 at javax.servlet.GenericServlet.init(GenericServlet.java:242)
 at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.init(MBeanUtilsInitSingleFileServlet.java:37)
 at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:100)
 at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:84)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3127)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:489)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
 at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:374)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
 at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
 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)
>
Edited by: user13712701 on Jan 18, 2011 1:46 PM

Please help me about jdeveloper application deployment for weblogic

At the beginning I just thought after developing an adf application then just deploy it as a .ear file and deploy it in the weblogic console and everything will be ok.But in fact I got a lot of problems. Then I got a tutorial for that and I do what it said step by step but some new problems occured. This is the tutorial I mentioned: [How-To: ADF Deployment Guide|http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.htm]
Now could somebody tell how did you deploy your adf application?
Here is the errors I got.
This is the install packege and the OS I use:
1. CentOS 6.3_x64 + jdeveloper11123.jar(include wls10.3.5) + adr(package name is ofm_appdev_generic_11.1.1.6.0_disk1_1of1.zip)[and just now I used a solaris11 vm from oracle and install jdeveloper11.1.2.3, the same probem occured as in CentOS.]
2. Win7_x64 + jdeveoper11123.exe(include wls10.3.5) + adr mentioned above
Here is the problems I get:
in the case 1,after I install the jdeveloper(using sun jdk 1.7), the weblogic seems to be well though I didn't configure a domain.But after I open an
application(which I get from the oracle jdeveloper tutorial demo,which works well in my Win7 env) and I run it, the integrated weblogic can't get
started. Firstly in the console it said the -jrocket identifier is not recognized, then I modify the setDomainEnv.sh and the startWebLogic.sh file in the
integrated wls domain (the one in the .jdeveloper directer) to set the JAVA_VM variable to -server.After that another problem came out: when the
wls goes to status "starting",it is blocked and I turn to the system monitor it shows that a java thread using more than 1GB of memory of my system
and occupy 150% of my cpu(it's a double-core computer). I wait for about 5 minutes when a error came said "PermSize is too small".then I modify the
setDomainEnv.sh file again to set the PermSize to be 1024m and MaxPermSize to be 2048.(the variable name is something like that, maybe not the
exactly right. I think you can understand which one it is.) But the problem is still there.
then in the case 2.Firstly the jdev and the integrated wls works well, but when i deploy an application which works well to a ear file and deploy it to a
standalone wls(10.3.5) it never works.the error is something referrence/dependences libraries is not found.Then I tried to new a server connection to
the standalone wls and I got the tutorial [how_to_deploy_adf|http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.html] , as the tutorial said I patch my standalone
wls with the adr and everything goes ok, no error reported.Then I tried the new server in the new machine under the manage of the adminserver and apply the
adf template in the localhost:port/em console. But after I restart the new server(by the console and then by the stop+startweblogic.bat file) the server is running
while the application in the new server is just "Unavailable". I tried this for three times in three computer, two of them are running win7,the other one is running winxp.
I don't know what is wrong and I am totally a newbie about this. Somebody please help me.Thanks a lot!
regard,Neo.

Neo,
there are a couple of problems. First of all, jdev comes with it'S own jdk bundled in the product (jdk 1.6_x). Next thing is if you use JDev 11.1.2.3.0 to build an application you must use a wls 10.3.5 or 10.3.6 where you need to install the correct runtime onto. In your case you first install adf runtime 11.1.1.6.0 and then you need to install two patches which update the adf runtime to 11.1.2.3.0. These spathes are only available via support.oracle.com, meaning you need asupport contract to get them.
More information you can find in my blog http://tompeez.wordpress.com/2011/09/14/jdeveloper-versions-vs-weblogic-server-versions/
The rest of your problems go away once you have installed the right adf runtime on your server.
Timo

Application deployed on weblogic requires ssl to access another website

Hi all,
I'll illustrate my problem below. I have an application deployed on WL9.2. Within this application, there is a link to a https website. When I click on the link (within the application), I get an error message "[Security:090477]Certificate chain received from a.b.c.d - a.b.c.d was not trusted causing SSL handshake failure." a.b.c.d is the ip of the https website.
When I access the same https website from my desktop's browser, I am prompted to accept a certificate. Once I accepted the cert, I can access the website.
I reckon I have to install the certificate somewhere in my weblogic server, but where ? Is it to the JAVA_HOME/jre/lib/security/cacerts where my WL server is installed on? If yes, how do i append the certificate to the file? I tried to open the file, it is not human readable.
Any advise?

by using keytool u can able to create a key store ,create a certificate and sign the certificate.after doiing all these things u have to configure to particular server on which u need.
1.open the admin console see the servers and select one server on which u need to enable ssl
2.in tabs panel u r able to see the KEYSTORE tab,click that
3.give the required parameters
4.dont give any values to trust fields
while doing this u will get A promt llike FOR THIS U HAVE TO CONFIGURE SSL ALSO for that follow the steps
1.go to ssl tab beside the keystore tab
2.give required parameter and enable the ssl atribute.
after doing all once restart the admin server then u will get response through https......

BI Beans application deploy to Weblogic Server Error

Who can help me to resolve this error?
I follow the "Deploying Applications to BEA WebLogic ServerVersion 9.0.3" document from OTN web site, but i use the BEA weblogic server 6.1,not weblogic server 7.0.
When i deploy the BI Beans application to BEA WLS6.1, then happen the follow error message, every consultants can help me,please.
**************Error Message************
Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionImpl::connect: -ConnectionBean-Server: is going to connect - (DriverType=MDM)
Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionImpl::connect: -ConnectionBean-MDMDriver: Connected Successfully: Time=200ms
Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionImpl::connect: -ConnectionBean-Server: is going to connect - (DriverType=PERSISTENCE)
Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.drivers.persistence.PersistenceConnectionDriverImpl::connect: -ConnectionBean-PersistenceDriver is going to connect
Fri Mar 07 10:23:30 CST 2003 TRACE: In
oracle.dss.connection.server.drivers.persistence.PersistenceConnectionDriverImpl::connect: (ServiceName=null; Prinicipal=Local User; Username=null)
Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.persistence.storagemanager.bi.BIFileStorageManagerImpl::init: [Initializing oracle.dss.persistence.storagemanager.bi.BIFileStorageManagerImpl, env:{global_environment={locale_helper=oracle.dss.persistence.LocaleHelper@22e15b, persistence_errorhandler=oracle.dss.util.DefaultErrorHandler@792a41}, Connection Status=2, java.naming.security.principal=Local User, java.naming.factory.url.pkgs=weblogic.jndi.factories, securityDriverManager=oracle.dss.appmodule.server.DSSApplicationModuleImpl@4532ba, path=bidefs/BIBeanPrjBIDesigner2/, am=oracle.dss.appmodule.server.DSSApplicationModuleImpl@4532ba, Driver Type=PERSISTENCE, java.naming.factory.initial=oracle.dss.persistence.persistencemanager.server.InitPersistenceManagerFactory, mm=true, object_name=Connection_1, SET_ON_MID_TIER=NO, sm_driver=oracle.dss.persistence.storagemanager.bi.BIFileStorageManagerImpl}
Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionImpl::disconnect: -ConnectionBean-Server: is going to disconnect
Fri Mar 07 10:23:30 CST 2003 TRACE: In oracle.dss.connection.server.drivers.mdm._92.MDMConnectionDriverImpl_92::connect: -ConnectionBean-MDMDriver is disconnected from OLAPI
<2003/3/7 上午10時23分30秒> <Error> <HTTP> <[WebAppServletContext(8339407,Defaul
tWebApp,/DefaultWebApp)] null
oracle.dss.persistence.persistencemanager.common.PersistenceManagerRuntimeException: BIB-14122: The specified StorageManager could not be created.
oracle.dss.bicontext.BICannotProceedException: BIB-14820 根路徑不存在。
at oracle.dss.persistence.persistencemanager.server.PersistenceManagerSupport.loadStorageAdapterFromXML(PersistenceManagerSupport.java:442)
at oracle.dss.persistence.persistencemanager.server.PersistenceManagerSupport.<init>(PersistenceManagerSupport.java:145)
at oracle.dss.persistence.persistencemanager.server.PersistenceManagerImpl.<init>(PersistenceManagerImpl.java:99)
at oracle.dss.persistence.persistencemanager.server.InitPersistenceManagerFactory.getInitialContext(InitPersistenceManagerFactory.java:29)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:83)
at oracle.dss.persistence.persistencemanager.server.InitialPersistenceManager.<init>(InitialPersistenceManager.java:103)
at oracle.dss.connection.server.drivers.persistence.PersistenceConnectionDriverImpl.connect(PersistenceConnectionDriverImpl.java:147)
at oracle.dss.connection.server.ConnectionImpl.connect(ConnectionImpl.java:279)
at oracle.dss.connection.client.Connection.connect(Connection.java:401)
at oracle.dss.connection.client.Connection.connect(Connection.java:320)
at oracle.dss.metadataManager.client.MetadataManager.setConnectionObjects(MetadataManager.java:3985)
at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:852)
at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:792)
at oracle.dss.datautil.client.XMLManagerFactory.createQueryManager(XMLManagerFactory.java:187)
at oracle.dss.datautil.client.ManagerFactoryImpl.lookupQueryManager(ManagerFactoryImpl.java:176)
at oracle.dss.datautil.client.ManagerFactoryImpl.lookupMetadataManager(ManagerFactoryImpl.java:219)
at oracle.dss.datautil.client.ManagerFactoryImpl.lookupManager(ManagerFactoryImpl.java:128)
at biServlet.LoginOperation.initializeMetadataManager(LoginOperation.java:425)
at biServlet.LoginOperation.run(LoginOperation.java:166)
at biServlet.DefaultApplicationImpl.login(DefaultApplicationImpl.java:473)
at biServlet.AbstractControllerImpl.preRequestProcess(AbstractControllerImpl.java:1396)
at my.BIController1.preRequestProcess(BIController1.java:358)
at biServlet.AbstractControllerImpl.processRequest(AbstractControllerImpl.java:1498)
at biServlet.AbstractControllerImpl.doGet(AbstractControllerImpl.java:262)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

What can I do with the following exception?
D:\bea_home\user_projects\mydomain>echo off
CLASSPATH=D:\bea_home\jdk131_03\lib\tools.jar;D:\bea_home\weblogic700\server\lib
\weblogic_sp.jar;D:\bea_home\weblogic700\server\lib\weblogic.jar;d:\oraids\jlib\
bigraphbean.jar;d:\oraids\jlib\LW_PfjBean.jar;d:\oraids\jlib\bigraphbean-nls.zip
;D:\jdev\jlib\bigraphbean.jar;D:\jdev\jlib\LW_PfjBean.jar;D:\jdev\jlib\bigraphbe
an-nls.zip;D:\jdev\jdev\lib\ext\weblogic.jar
PATH=.;D:\bea_home\weblogic700\server\bin;D:\bea_home\jdk131_03\bin;d:\oraids\bi
n;d:\oraids\jdk\jre\bin;d:\oraids\jdk\jre\bin\classic;d:\oraids\jdk\jre\bin\clas
sic;d:\oraids\jlib;d:\oraids\bin;D:\oracle\ora92\bin;C:\Program Files\Oracle\jre
\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINNT\system32;C:\WINNT;C:\W
INNT\System32\Wbem;d:\notes\;D:\ULTRAE~1
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
D:\bea_home\user_projects\mydomain>"D:\bea_home\jdk131_03\bin\java" -server -Xms
32m -Xmx200m -Dweblogic.security.SSL.trustedCAKeyStore=D:\bea_home\weblogic700\s
erver\lib\cacerts -Djava.ext.dirs=D:\bea_home\jdk131_03\jre\lib\ext;D:\bea_home\
weblogic700\samples\server\jdbc -Dweblogic.Name=myserver -Dbea.home="D:\bea_home
" -Dweblogic.management.username= -Dweblogic.management.password= -Dweblogic.Pro
ductionModeEnabled= -Djava.security.policy="D:\bea_home\weblogic700\server\lib\w
eblogic.policy" weblogic.Server
<2003-9-11 下午06时34分46秒> <Info> <Security> <090065> <Getting boot identity f
rom user.>
Enter username to boot WebLogic server:admin
Enter password to boot WebLogic server:
Starting WebLogic Server...
<2003-9-11 下午06时34分58秒> <Notice> <Management> <140005> <Loading configurati
on D:\bea_home\user_projects\mydomain\.\config.xml>
<2003-9-11 下午06时35分06秒> <Notice> <Security> <090082> <Security initializing
using realm myrealm.>
<2003-9-11 下午06时35分06秒> <Notice> <WebLogicServer> <000327> <Starting WebLog
ic Admin Server "myserver" for domain "mydomain">
<2003-9-11 下午06时35分25秒> <Notice> <Management> <141052> <Application Poller
started for development server.>
<2003-9-11 下午06时35分28秒> <Notice> <WebLogicServer> <000354> <Thread "SSLList
enThread.Default" listening on port 7002>
<2003-9-11 下午06时35分29秒> <Notice> <WebLogicServer> <000354> <Thread "ListenT
hread.Default" listening on port 7001>
<2003-9-11 下午06时35分29秒> <Notice> <Management> <141030> <Starting discovery
of Managed Server... This feature is on by default, you may turn this off by pas
sing -Dweblogic.management.discover=false>
<2003-9-11 下午06时35分30秒> <Notice> <WebLogicServer> <000331> <Started WebLogi
c Admin Server "myserver" for domain "mydomain" running in Development Mode>
<2003-9-11 下午06时35分30秒> <Notice> <WebLogicServer> <000365> <Server state ch
anged to RUNNING>
<2003-9-11 下午06时35分30秒> <Notice> <WebLogicServer> <000360> <Server started
in RUNNING mode>
Thu Sep 11 18:38:03 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionIm
pl::connect: -ConnectionBean-Server: is going to connect - (DriverType=MDM)
Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionIm
pl::connect: -ConnectionBean-MDMDriver: Connected Successfully: Time=1342ms
Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionIm
pl::connect: -ConnectionBean-Server: is going to connect - (DriverType=PERSISTEN
CE)
Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.connection.server.drivers.pers
istence.PersistenceConnectionDriverImpl::connect: -ConnectionBean-PersistenceDri
ver is going to connect
Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.connection.server.drivers.pers
istence.PersistenceConnectionDriverImpl::connect: (ServiceName=null; Prinicipal
=Local User; Username=null)
Thu Sep 11 18:38:04 CST 2003 TRACE: In oracle.dss.persistence.storagemanager.bi.
BIFileStorageManagerImpl::init: [Initializing oracle.dss.persistence.storagemana
ger.bi.BIFileStorageManagerImpl, env:{global_environment={locale_helper=oracle.d
ss.persistence.LocaleHelper@6351a2, persistence_errorhandler=oracle.dss.util.Def
aultErrorHandler@496f0}, Connection Status=2, java.naming.security.principal=Loc
al User, java.naming.factory.url.pkgs=weblogic.jndi.factories, securityDriverMan
ager=oracle.dss.appmodule.server.DSSApplicationModuleImpl@517ead, path=bidefs/we
blogicBIDesigner1/, am=oracle.dss.appmodule.server.DSSApplicationModuleImpl@517e
ad, Driver Type=PERSISTENCE, java.naming.factory.initial=oracle.dss.persistence.
persistencemanager.server.InitPersistenceManagerFactory, mm=true, object_name=Co
nnection_1, SET_ON_MID_TIER=NO, sm_driver=oracle.dss.persistence.storagemanager.
bi.BIFileStorageManagerImpl}
<2003-9-11 下午06时38分04秒> <Error> <HTTP> <101017> <[ServletContext(id=4561108
,name=webapp.war,context-path=/weblogic_app)] Root cause of ServletException
java.lang.NoSuchMethodError
at oracle.dss.thin.beans.CaboErrorHandler.error(CaboErrorHandler.java:10
2)
at oracle.dss.addins.jspTags.PresentationTag.doStartTag(PresentationTag.
java:191)
at jsp_servlet.__untitled1._jspService(__untitled1.java:140)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1058)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:401)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:445)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:5412)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:744)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3086)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2544)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
>
Thu Sep 11 19:08:26 CST 2003 TRACE: In oracle.dss.connection.server.ConnectionIm
pl::connect: -ConnectionBean-Server: is going to connect - (DriverType=PERSISTEN
CE)
Thu Sep 11 19:08:26 CST 2003 TRACE: In oracle.dss.connection.server.drivers.pers
istence.PersistenceConnectionDriverImpl::connect: -ConnectionBean-PersistenceDri
ver is going to connect
Thu Sep 11 19:08:26 CST 2003 TRACE: In oracle.dss.connection.server.drivers.pers
istence.PersistenceConnectionDriverImpl::connect: (ServiceName=null; Prinicipal
=Local User; Username=null)
Thu Sep 11 19:08:26 CST 2003 TRACE: In oracle.dss.persistence.storagemanager.bi.
BIFileStorageManagerImpl::init: [Initializing oracle.dss.persistence.storagemana
ger.bi.BIFileStorageManagerImpl, env:{global_environment={locale_helper=oracle.d
ss.persistence.LocaleHelper@72d194, persistence_errorhandler=oracle.dss.util.Def
aultErrorHandler@496f0}, Connection Status=2, java.naming.security.principal=Loc
al User, java.naming.factory.url.pkgs=weblogic.jndi.factories, securityDriverMan
ager=oracle.dss.appmodule.server.DSSApplicationModuleImpl@517ead, path=bidefs/we
blogicBIDesigner1/, am=oracle.dss.appmodule.server.DSSApplicationModuleImpl@517e
ad, Driver Type=PERSISTENCE, java.naming.factory.initial=oracle.dss.persistence.
persistencemanager.server.InitPersistenceManagerFactory, mm=true, object_name=Co
nnection_1, SET_ON_MID_TIER=NO, sm_driver=oracle.dss.persistence.storagemanager.
bi.BIFileStorageManagerImpl}
<2003-9-11 下午07时08分26秒> <Error> <HTTP Session> <100025> <Unexpected error i
n HTTP session timeout callback
java.lang.NoSuchMethodError
at oracle.dss.thin.beans.CaboErrorHandler.error(CaboErrorHandler.java:10
2)
at oracle.dss.addins.thin.common.BaseThinSession.cleanup(BaseThinSession
.java:307)
at oracle.dss.addins.thin.common.BaseThinSession.valueUnbound(BaseThinSe
ssion.java:159)
at weblogic.servlet.internal.session.SessionData.removeAttribute(Session
Data.java:588)
at weblogic.servlet.internal.session.SessionData.removeAttribute(Session
Data.java:552)
at weblogic.servlet.internal.session.SessionData.remove(SessionData.java
:747)
at weblogic.servlet.internal.session.MemorySessionContext.invalidateSess
ion(MemorySessionContext.java:51)
at weblogic.servlet.internal.session.SessionContext$SessionInvalidator$I
nvalidationAction.run(SessionContext.java:523)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:744)
at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.c
leanupExpiredSessions(SessionContext.java:444)
at weblogic.servlet.internal.session.SessionContext.deleteInvalidSession
s(SessionContext.java:81)
at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.t
rigger(SessionContext.java:392)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.j
ava:181)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:744)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(Schedul
edTrigger.java:167)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigg
er.java:161)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:3
8)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
>

Using weblogic console without jdk

Hi,
          We are not allowed to have compilers installed in our production environment. Thus we have to remove the jdk that is shipped with the weblogic installation and only use the jre. For our own applications we precompile the JSP pages at build time, so we don't need the jdk.
          The problem is that the weblogic admin console is also built with JSPs. Does anyone know if it is possible to tell weblogic to install the admin console with pre-compiled JSPs? Or is there another way to use the console whithout having the jdk installed?
          Best regards
          Orjan

Hi.
I need a bit more detail. What exactly do you mean when you say you have
multihomed the server with 5 different web sites? What is your configuration?
How are you connecting to a specific instance? With a java program or
browser? What URL are you using?
A single instance of WLS will bind to only 1 IP address using the
weblogic.system.bindAddr property. Are you starting 5 instances of the server,
each binding to a unique IP address? Having a multihomed machine does not mean
that a single instance of WLS is listening for incoming requests on all IP
addresses.
Thanks,
Michael
Tim Nields wrote:
I am currently running Weblogic 5.10. I have successfully managed to
multihome the server with 5 different websites. However I am running into
problems when attempting to connect to a specific instance. The error that
I am receiving is:
Cannot Connect:
Unknown NamingException, class= javax.naming.NamingException
I have a mirrored machine and I am able to connect using the weblogic
console, but I can't connect to a single one on the other. Can anyone
please offer some help as to why this would be occuring.
Thanks in advance.
Tim Nields--
Michael Young
Developer Relations Engineer
BEA Support

Unable to access application set in admin console after upgrade to 7.0 M

Hi Experts
I am unable to access the Application Set through BPC Administration after upgrading our development server to version 7.0 SP3. I followed the instructions as per the Upgrade guide, and there was no issues during the installation. But when trying to access the application set i receive the following error message on step 9 ( 9/10) of during the connection.
Error message: Subquery returned more than 1 value. This is not
permitted when the subquery follows =, !=, <, <= , >, >= or when the
subquery is used as an expression.
I have done all of the steps outlined as per SAP Note 1242962, but i still receive the error message. I tried to do a SQL Profiler trace, but i have been unable to find the query which returns more than one record.
Any help is appreciated
Kind Regards
Daniel

Interesting that you ask about upgrade vs uninstall/reinstall.
We were running BPC 5.1
We have also re-installed the Admin client to be the new version.
We have been working with an outside consulting firm to manage our system upgrade/install.
Our dev and qa environments were uninstalled then reinstalled.
When we went to production, our system was intially upgraded. I do not know why this route was chosen when that was not what was completed on dev/qa. On our production 'upgrade', we are still working through issues. We then uninstalled iis, sqlserver reporting services, both .net 1.1 and 2.0, and the BPC application. Then reinstall everything and we were getting the same errors.
Our error was at Progress 10/10 Create Database Schema and check Application server collation.
Error Message: Object Reference not set to an instance of an object.
We are able to access the appShell and test copies of the appShell, we were not able to access any custom appSets which were created prior to the upgrade, nor are we able to access any appSets that were created as a copy of the custom appSet after the upgrade.
When logged with SAP, we were directed toward note Note 1331040 - Cannot log into 7M Admin console after restore from version5 noting that we needed to do the following changes:
Note that you will need to change the following:
INSERT INTO tblDefaults VALUES ('_GLOBAL','Prev_AppSet_Version','','','7.0.112')
INSERT INTO tblDefaults VALUES ('_GLOBAL','Curr_AppSet_Version','','','7.0.112')
to
INSERT INTO tblDefaults VALUES ('_GLOBAL','Prev_AppSet_Version','','','7.0.113')
INSERT INTO tblDefaults VALUES ('_GLOBAL','Curr_AppSet_Version','','','7.0.113')
The reason is because '7.0.113' means 7 MS SP04 while '7.0.112' means SP03.
There are 8 steps in this note, for us, only the first 2 were needed. I have asked SAP to create new note/update existing accordingly.
With the table entry, we were able to successfully access our app set.
Hope our experiences can help you out.
Thanks,
Becky Zick

Cannot start application deployed using Weblogic console after stop

Similar Messages

Maybe you are looking for