Bi Beans Loosing Stylesheet On Weblogic 8.1

Deploying a Bi Beans JSP application on Weblogic 8.1.
After logging-in when it opens a catalog page (Open1.jsp) application looses stylesheet reference. Weblogic console throws following error
<Aug 20, 2004 6:13:38 PM GMT-06:00> <Warning> <HTTP Session> <BEA-100061> <Web a
pplication: ServletContext(id=1752285,name=ea,context-path=/ea) tried to place a
non-serializable attribute: bisession1 into the session: BmTp20FSiNYrU5W0WQy5Ly
k7S19M5TGT0FBVCysAaZJpjE3ptcGm!-934773592!1093047209234. This attribute will be
lost upon redeployment. This message is logged only once per session.>
<Aug 20, 2004 6:13:42 PM GMT-06:00> <Error> <HTTP> <BEA-101046> <[ServletContext
(id=1752285,name=ea,context-path=/ea)] null
oracle.cabo.share.config.DirectoryUnavailableException: contextPath is null
at oracle.cabo.share.config.ConfigurationImpl.getPath(Unknown Source)
at oracle.cabo.ui.RootRenderingContext._getDefaultStyleProvider(Unknown
Source)
at oracle.cabo.ui.RootRenderingContext.getProperty(Unknown Source)
at oracle.cabo.ui.ServletRenderingContext.getProperty(Unknown Source)
at oracle.cabo.ui.laf.base.StyleSheetRenderer.prerender(Unknown Source)
at oracle.cabo.ui.BaseRenderer.render(Unknown Source)
at oracle.cabo.ui.laf.base.StyleSheetRenderer.render(Unknown Source)
at oracle.cabo.ui.BaseUINode.render(Unknown Source)
at oracle.cabo.ui.BaseUINode.render(Unknown Source)
at oracle.dss.addins.jspTags.BIBodyTag.doStartTag(BIBodyTag.java:48)
at jsp_servlet.__open1._jspService(__open1.java:249)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:387)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:431)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6310)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3622)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
<Aug 20, 2004 6:13:42 PM GMT-06:00> <Error> <HTTP> <BEA-101046> <[ServletContext
(id=1752285,name=ea,context-path=/ea)] null
oracle.cabo.share.config.DirectoryUnavailableException: contextPath is null
at oracle.cabo.share.config.ConfigurationImpl.getPath(Unknown Source)
at oracle.cabo.ui.RootRenderingContext._getDefaultImageProvider(Unknown

I did a reinstallation and the problem didnt re-occur. So one neednt work on this problem.
Priya

Similar Messages

Calling Local Stateless session bean from Spring in weblogic 10.3

We are in the process of upgrading to Weblogic 10.3 from OC4J (OAS). We are using Spring and Stateless Session EJB 3 Local beans (Don't ask me why, it is decided before I came to the project).
Previously (OC4J):
-> There is no ejb-jar.xml. EJBs are configured with annotation @Stateless. No "name" or "mappedName" are defined.
Spring POJOs access EJBs by using "EJBMODULENAME_<<EJBBeanClass>>Local" as JNDI Name. I think this strange JNDI name is what OC4J assigns when there is no explicit JNDI name defined.
Sample Spring Bean configuration -
<bean name="securityEJB" class="org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean" lazy-init="true">
          <property name="jndiName">
               <value>myapp-ejb_SecurityEJBImplLocal</value>
          </property>
          <property name="resourceRef">
               <value>false</value>
          </property>
          <property name="businessInterface">
               <value>my.package.SecurityEJB</value>
          </property>
     </bean>
I understand that weblogic 10.x doesn't give any global JNDI name (JNDI tree is empty) and also looked at the blog, Link: [http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html]
So far I have tried,
1. @EJB annotation works but, I don't want to add @EJB annotations in the entire application. Since we are using Spring and EJB3, I am trying to avoid mixing them -
2. java:comp/env is supposed to work (since it is a local session bean), but it doesn't for me.
I haven't added weblogic-ejb-jar.xml as I don't think it is going to help, as there is no global JNDI name defined. Am I missing some thing?
Thx

Hi,
if you don't want to use @EJB to inject the EJB, then you'll need declare the EJB reference in deployment descriptor.
Here is an example copied from EJB3 spec:
<ejb-local-ref>
<description>
This is a reference to the local business interface
of an EJB 3.0 session bean that provides a payroll
service.
</description>
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
<local>com.aardvark.payroll.Payroll</local>
</ejb-local-ref>
then you can lookup the local ejb from "java:comp/env/ejb/Payroll".

How to create Entity Bean (CMP) using JDeveloper & Weblogic

Hi,
Using : JDeveloper9i (9.0.2.829)
When i am inside the EJB Wizard (Step 1 of 3), the input field 'CMP Provider' shows only Oracle9iAS CMP Provider.
How should i make my entity take 'Weblogic' as CMP provider for my beans using JDeveloper. I have my tables in Oracle personal db. I was able to succesfuly add a Weblogic/Db connection under respective connections node.
Should i need to do something more so that i am given an option of choosing Weblogic as CMP provider.
thanks for the advance help
regds
srikanth

Currently there is no specific option for WebLogic CMP provider.
You need to manually add the WebLogic CMP deployment descriptor to the project containing
EJB Entity beans and deploy to WebLogic.
raghu
JDev Team

Possible to create a JAX-WS, session-bean-based webservice for WebLogic 10?

All,
sorry - but I'm going a bit crazy here. I have been unable to figure out the secret hand-shakes for developing a session-bean-based web service that will run properly under Weblogic 10.0. There are examples out there on how to create webservices that exists within a war file - but none that I can find that reside within a session bean (an ear file).
I can't even figure out how to do with this Bea Workshop for WebLogic Platform 10.0! Is this possible? I can't find any examples anywhere on how to do this. I must be missing something...
Does WebLogic 10.0 support web services within session beans? I've figured out how to do this with JBoss, Sun App Server, and Glassfish - but no luck so far with WebLogic.
If anyone can please point me in the proper direction it would be very appreciated. My company likes WebLogic, but we have to be able to do this in order to continue using it.
Thanks,
-john

Yeah - I've tried that. Everything builds fine - but when I deploy to WebLogic 10, I get the stack below. It looks like it is looking for the class examples.webservices.jaxws.jaxws.SayHello - but there isn't such a class in the example...
Any thoughts? I'm completely stuck!
<Apr 16, 2007 4:15:45 PM PDT> <Error> <HTTP> <BEA-101216> <Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>
<Apr 16, 2007 4:15:45 PM PDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1176765341457' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
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:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
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:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
Truncated. see log file for complete stacktrace
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>
<Apr 16, 2007 4:15:46 PM PDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WL6_ear'.>
<Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WL6_ear'.>
<Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
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:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
Truncated. see log file for complete stacktrace
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>

Message redelivery with non-transactional message bean JMS standard or weblogic standard?

It is my understanding (or maybe my assumption) that a message is
          re-queued only if the transaction attribute of a container-managed
          message bean is set to "Required" and the message is PERSISTENT. So if
          it's set to "NotSupported", and thus, message receival is not within a
          transaction, the message would be un-queued and thus never be
          redelivered, should a failure occur within the bean. I discovered that
          even if the message bean is set as "NotSupported", should a failure
          occur within the bean, the message is re-queued to be received again
          at a later time.
          I'm very confused as to whether this mechanism is a JMS standard, or a
          feature of Weblogic. Well, maybe I'm just confused about message
          delivery/re-delivery. I understand that the JMS standard requires
          guaranteed delivery of a message to a receiver. Does this mean a
          message is only considered delivered if an acknowledgement is
          received, regardless of the transaction level? In other words, is the
          JMS standard that a message is considered delivered only if
          acknowledgement is indicated through the container, regardless of the
          transaction level of the message bean itself?


You're right on the second part. That is, a JMS message is not considered to
          be "delivered" until it is acknowledged. There are a number of ways to make
          this happen when programming to the raw JMS API -- a look at the Javadoc for
          JMS or a good JMS book should clarify how to do this.
          With a message-driven bean, the EJB container acknowledges the message after
          you've successfully returned from the "onMessage" method. If you throw a
          RuntimeException from the "onMessage" method, or if it's an MDB with a
          transaction mode of "Required" and you call "setRollbackOnly" on the
          "MessageDrivenContext" object -- then your message will be redelivered.
          Regardless of how a message is acknowledged, if it's not acknowledged then
          it will be redelivered. This has nothing to do with whether the message is
          persistent. The difference is that if a message is persistent, then the JMS
          server is required to keep a copy on stable storage until the message is
          acknowledged so that if the JMS server itself crashes, the message will not
          be lost. For a non-persistent message, on the other hand, if the JMS server
          crashes, then the message may be lost.
          greg
          "Justin" <[email protected]> wrote in message
          news:[email protected]...
          > It is my understanding (or maybe my assumption) that a message is
          > re-queued only if the transaction attribute of a container-managed
          > message bean is set to "Required" and the message is PERSISTENT. So if
          > it's set to "NotSupported", and thus, message receival is not within a
          > transaction, the message would be un-queued and thus never be
          > redelivered, should a failure occur within the bean. I discovered that
          > even if the message bean is set as "NotSupported", should a failure
          > occur within the bean, the message is re-queued to be received again
          > at a later time.
          >
          > I'm very confused as to whether this mechanism is a JMS standard, or a
          > feature of Weblogic. Well, maybe I'm just confused about message
          > delivery/re-delivery. I understand that the JMS standard requires
          > guaranteed delivery of a message to a receiver. Does this mean a
          > message is only considered delivered if an acknowledgement is
          > received, regardless of the transaction level? In other words, is the
          > JMS standard that a message is considered delivered only if
          > acknowledgement is indicated through the container, regardless of the
          > transaction level of the message bean itself?

Stateless session beans and idle timeouts (weblogic 10.3.1)

Need clarification about stateless session beans and the idle-timeout-seconds setting.
Situation is this – we have a process that is timing out due to an API call to a very slow Authentication server.
I am trying to resolve this with a code change, but need to further other understand what the server is actually doing.
We have a session bean which calls another which is calling a util class that does all the work and returns the results back up to the initial session bean. I have left out the ejbName in these examples (it’s irrelevant here).
Example:
SessionBean1 // basically called just once a day
@Session(defaultTransaction = Constants.TransactionAttribute.SUPPORTS,
enableCallByReference = Constants.Bool.TRUE,
type = Session.SessionType.STATELESS,
transTimeoutSeconds = "0",
initialBeansInFreePool = "0",
maxBeansInFreePool = "20")
Methods
@RemoteMethod() public boolean getUserList(String adminGroup) {
Map usrList = getUserList(adminGroup);
Private Map getUserList(String adminGroup) {
     return SessionBean2.getUsers(adminGroup);
SessonBean2
@Session(defaultTransaction = Constants.TransactionAttribute.SUPPORTS,
enableCallByReference = Constants.Bool.TRUE,
type = Session.SessionType.STATELESS,
transTimeoutSeconds = "0",
initialBeansInFreePool = "3",
maxBeansInFreePool = "20")
Method
@RemoteMethod() public Map getUsers(String adminGroup) throws RemoteException {
return javaUtilClass.getUsers(adminGroup);
JavaUtilClass
Method
public Map getUsers(String adminGroup) throws RemoteException {
     // This is where the work happens, calling the Authentication server to get a complete
     // list of users for an admin group. When the user list is around 1500 entries, this can
     // take an hour. Did I mention this server is very slow? It’s about this threshold of 1500
     // that causes the timeout.
     return Map of users
First thought, just bump the idle-timeout-seconds setting for the session beans (from the default 600), but that would be a temporary solution until the user list grew larger.
Second thought, refactor the call to the Authentication Server API to get the user list in blocks of data (say 400 at a time) and decreasing the call/response time between the method getUsers and the API call. This would still occur in the JavaUtilClass, so I am unsure this would make a difference. The session beans would still be idle and subject to timeout, correct?
Would setting initialBeansInFreePool to 1 in SessionBean1 make any difference?
Or should I be looking at replicating the re-factored method from the JavaUtilClass in SessionBean1 where the user list is being used so that the API calls come back to it and keep it 'active'?
Thanks for any advice you could give me on this.

Hi
regarding timeouts, there are two ways:
1.- Changing the settings in the JTA WebLogic domain , called "Timeout Seconds". This will affect globally to all EJB deployed in the domain.
or
2.- Specified directly in the bean with a weblogic annotation, like this:
@TransactionTimeoutSeconds(value = 300)I hope this will help you.
Regards.
Felipe

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)
>

Deploying beans w/o restarting weblogic. (NOT EJB)

Hi
I want to know, if it is possible to deploy( or changed bean) simple java
beans without restarting weblogic. whenever I do any small change, I need to
restart my weblogic. Can't we something similiar to hot deployment.

I am having this problem with WL6.0.
Whenever I redeploy a .war file I always get a "ClassNotFoundException".
The only way I know of to resolve this is to stop and restart the server.
The following are the steps I use to deploy:
1) Rebuild the .war file with the changed files
2) Copy the .war file to the config/<domain>/applications directory
This, if I understand it correctly, should automatically redeploy the
changes. I have the "AutoUpdateInterval" set to 3000 ms and enabled in the
Console. I also changed the logging to show messages at the Info level.
When the copy is complete, I see messages that the application is
undeployed, but redeployment messages never follow. If I go to the console,
I see that the application is marked undeployed. When I check "Deploy"
and click Apply, I get an error that the file could not be found. If I then
undeploy and then deploy the application it deploys fine.
This is when I start getting the ClassNotFoundException.
I don't think this is how it is supposed to be working. Is this a known
problem, or do I have something configured wrong.
Thanks,
Maury
"Ashish Jain" <[email protected]> wrote in message
news:[email protected]...
I am using ver5.1, sp6..
and i am not deploying them in any particular jar etc etc.
In my one of my JSP, i am including them using useBean jsp tag.
i know, i can't reload if they r in classpath, but if i put in different
path, ofcourse i get NoClassDefFoundError error.
thanks
ashish
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]...
Yes this is possible.
You'll need to tell me a little more about your environment. What
version of WLS are you using?
Also, how do you deploy these classes? Are they part of a WAR, EJB-JAR
or stand-alone.
You will not be able to redeploy anything that is in the $CLASSPATH or
the weblogic.class.path (in 4.5.x or 5.1).
-- Rob
Ashish Jain wrote:
I mean, Simple Java Bean, (Utility Class)
To explain more, I am using MVC arctitecture, and while developing
controller class, whenever i do a small change, to reflect those
changes, i
need to restart weblogic. And I am deploying more than 100 EJBs, u can
imagine the time i have to wait to see even a small change.
thanks
ashish
"Kumar Allamraju" <[email protected]> wrote in message
news:[email protected]...
You mean EJB or "Simple JAVA Bean" used as a utility class forservlets/jsp's
Kumar
Ashish Jain wrote:
Hi
I want to know, if it is possible to deploy( or changed bean)
simple
java
beans without restarting weblogic. whenever I do any small change,
I
need to
restart my weblogic. Can't we something similiar to hot
deployment.
>>>>
>>
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com

Error while creating stub and skel for bean using ejbc from weblogic

I had created a sample ejb , home remote and bean every thing is ok.....i have generated the configuration xml files using the marathon tool in weblogic.....but when i perform ejbc ...
d:\>java weblogic.ejbc temp.jar sample.jar
During the compilation the compiler is raising an error stating :
ERROR: Error creating descriptor from jar file temp.jar:
ERROR: Error from ejbc: [EJB:010120]Error: The deployment descriptor 'META-INF/ejb-jar.xml' was not found in 'temp.jar'. Please add this file to the JAR and try again
it produces the above error........in linux fedora......
can any body solve my problem..........

its solved ......
actually linux os is very much case sencitve........asi was trying command on the fat file system which i am accesing from linux is the culprit over here......
i copied the same thing to the linux ext system it worked..............

Stateless Bean imposing webservice in Weblogic 10

Hi..
Is it possible to implement Stateless bean webservice using jwsc task and deploying both services(ejb and webservice) as EAR???.
If anybody knows please let me know what are the steps to follow.
Thanks in advance and your help is appreciated........

Hi,
if you don't want to use @EJB to inject the EJB, then you'll need declare the EJB reference in deployment descriptor.
Here is an example copied from EJB3 spec:
<ejb-local-ref>
<description>
This is a reference to the local business interface
of an EJB 3.0 session bean that provides a payroll
service.
</description>
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
<local>com.aardvark.payroll.Payroll</local>
</ejb-local-ref>
then you can lookup the local ejb from "java:comp/env/ejb/Payroll".

How to lookup a EJB 3.0 session bean which is deployed in WebLogic 10.3

Now Jdeveloper 11.1.1, is giving WebLogic server 10.3.
With internal WebLogic server, when I created a Sample client, it generated code as:
private static Context getInitialContext() throws NamingException {
    Hashtable env = new Hashtable();
    // WebLogic Server 10.x connection details
    env.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
    env.put(Context.PROVIDER_URL, "t3://127.0.0.1:7101");
    return new InitialContext( env );
public static void main(String [] args) {
    try {
        final Context context = getInitialContext();
        DefaultSession defaultSession = (DefaultSession)context.lookup("property-DefaultSession#com.vs.property.model.session.DefaultSession");
    } catch (Exception ex) {
}How to update the above code to lookup the EJB 3.0 session beans with an external WebLogic server 10.3?
Is there any documentation available on how to install weblogic, troubleshoot, debug, WebLogic server 10.3?
regds
-raju

Raju,
Hi, to start, here is a tutorial on a quickstart web application using an EJB 3.0 stateless session bean that fronts a container managed EclipseLink JPA entity manager on WebLogic 10.3, you will find references there to other general WebLogic documentation.
[http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial]
using @EJB injection on the client instead of a JNDI lookup as below
[http://edocs.bea.com/wls/docs103/ejb30/annotations.html#wp1417411]
1) in your second env.put I noticed that your t3 port is 7101, I usually use the default 7001 - but It looks like this port is valid for the JDeveloper embedded version of WebLogic server runs - just verify that it matches the port of your server.
2) your name#qualified-name lookup looks ok. Verify that the jndi-name element is set in your weblogic-ejb-jar.xml for non injection clients like the following
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>ApplicationService</ejb-name>
<jndi-name>ApplicationService</jndi-name>
3) as a test outside of your application - launch the WebLogic admin console and goto the testing tab of your bean in [Home > Summary of Deployments > "application" > "session bean name"
thank you
/michael : http://www.eclipselink.org

XML Beans and Weblogic Server 8.1

Hi,
Does anyone know if XML beans is shipped with Weblogic 8.x (or is it only part
of the Weblogic Workshop) ?
Thanks,
Arun

Greg,
The classes required for running these command line tools are all there, but
we have not put the script files in the version bundled with WebLogic
server. Its very likely to be part of the next service pack release.
Meanwhile, you can always run the classes from the command line, or write
your own script. For instance, the dumpxsb.cmd has the following:
set cp=
set cp=%cp%;%XMLBEANDIR%\xbean.jar
java -classpath %cp% com.bea.xbean.tool.XsbDumper %*
So you can always write this on your own, or just run the concerned class
from the command line.
Let me know if you have any further queries.
Regards,
Anurag
"Greg" <[email protected]> wrote in message news:1061965730.933286@ns1...
Hi,
Is it possible to use the version of xmlbeans bundled with workshop in a
standalone sense? Are all the command line tools there? If so can yougive
a pointer to where abouts in the Workshop download to look for this.
The reason I ask is noting the following I saw -:
Note: XQuery is currently only available with the version of XMLBeans
included with WebLogic Platform. We hope to add these capabilities to the
stand-alone version soon.
Greg
"Raj Alagumalai" <[email protected]> wrote in message
news:[email protected]..
Arun,
WebLogic Platform 8.1 GA which includes Workshop does contain an
xmlbeans
implementation.
We also have a stand alone implementation which is available on dev2dev.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Arun" <[email protected]> wrote in message
news:3f38da48$[email protected]..
Thanks. But what we have found out from BEA is that it does not shipwith Weblogic
Server. You have to download it separately.
"Dmitri Colebatch" <[email protected]> wrote:
Does anyone know if XML beans is shipped with Weblogic 8.x (or is it
only part of the Weblogic Workshop) ?yes, it is shipped in Platform 8.1 (I'm pretty sure its shipping in
Server
8.1
too). Although the version is slightly older than the version
available
on the
dev2dev site.
cheers
dim

Bean Ids in weblogic console

Does anybody know how the identifier of a Session Bean shown in the
weblogic console is built? I know the ones of the Entity Beans are built
using the toString method of the primary key class, but what about the
Session Beans?
Thanks in advance,
Xavi

We are facing the same problem. I have an EAR that has a packed WAR containing two EJBs. One of them can be configured without a problem, but the other one cannot. The same exception is thrown. Interestingly, we have the same application on our test server environment and there it works without a problem.

XML Beans and Weblogic 7

Hi - I am interested to use the XML Beans development kit - but I only have a
WebLogic 7 app server to work with. Is there a way to get around the requirement
for xqrl.jar to run the examples such as the easypo example? I found myself getting
compilation errors for the src files that were generated by the schema compiler
complaining about not being able to find some com.bea.xquery classes which I am
assuming reside in this jar (xqrl.jar). Is it required that I download the whole
WLS 8.1 platform just to get this jar? Thanks for any advice.

Greg,
The classes required for running these command line tools are all there, but
we have not put the script files in the version bundled with WebLogic
server. Its very likely to be part of the next service pack release.
Meanwhile, you can always run the classes from the command line, or write
your own script. For instance, the dumpxsb.cmd has the following:
set cp=
set cp=%cp%;%XMLBEANDIR%\xbean.jar
java -classpath %cp% com.bea.xbean.tool.XsbDumper %*
So you can always write this on your own, or just run the concerned class
from the command line.
Let me know if you have any further queries.
Regards,
Anurag
"Greg" <[email protected]> wrote in message news:1061965730.933286@ns1...
Hi,
Is it possible to use the version of xmlbeans bundled with workshop in a
standalone sense? Are all the command line tools there? If so can yougive
a pointer to where abouts in the Workshop download to look for this.
The reason I ask is noting the following I saw -:
Note: XQuery is currently only available with the version of XMLBeans
included with WebLogic Platform. We hope to add these capabilities to the
stand-alone version soon.
Greg
"Raj Alagumalai" <[email protected]> wrote in message
news:[email protected]..
Arun,
WebLogic Platform 8.1 GA which includes Workshop does contain an
xmlbeans
implementation.
We also have a stand alone implementation which is available on dev2dev.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Arun" <[email protected]> wrote in message
news:3f38da48$[email protected]..
Thanks. But what we have found out from BEA is that it does not shipwith Weblogic
Server. You have to download it separately.
"Dmitri Colebatch" <[email protected]> wrote:
Does anyone know if XML beans is shipped with Weblogic 8.x (or is it
only part of the Weblogic Workshop) ?yes, it is shipped in Platform 8.1 (I'm pretty sure its shipping in
Server
8.1
too). Although the version is slightly older than the version
available
on the
dev2dev site.
cheers
dim

Weblogic not finding javax.naming classes when instantiating bean

Hello,
          I am developing a JSP which contains a JavaBean.
          This bean is a wrapper for a session EJB, the getProperty() methods in
          the bean call methods on the EJB's remote interface.
          I have tested this bean as a stand alone application by adding a
          main(String[] args) method to it and it works.
          However, when adding the bean to the JSP, the JSP does not show in the
          browser, I get a n internal server error 500 instead.
          It seems that Weblogic is not finding the javax.naming.NamingException
          class when instantiating the bean.
          When looking at the weblogic log, I see the following stack trace:
          Fri Aug 18 15:12:06 EDT 2000:<E> <ServletContext-General> Servlet failed
          with Exception
          java.lang.NoClassDefFoundError: javax/naming/NamingException
          at java.lang.ClassLoader.resolveClass0(Native Method)
          at java.lang.ClassLoader.resolveClass(ClassLoader.java:579)
          at
          weblogic.utils.classloaders.GenericClassLoader.reallyLoadClass(GenericClassLoader.java,
          Compiled Code)
          at
          weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java,
          Compiled Code)
          at
          weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java,
          Compiled Code)
          at java.beans.Beans.instantiate(Beans.java:194)
          at java.beans.Beans.instantiate(Beans.java:55)
          at weblogic.servlet.jsp.JspLexer.processBeanTag(JspLexer.java:1138)
          at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(JspLexer.java,
          Compiled Code)
          at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1554)
          at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
          at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
          Code)
          at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
          at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
          at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
          at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
          at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
          Compiled Code)
          at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
          Code)
          at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
          at weblogic.servlet.jsp.JspStub.checkForReload(JspStub.java:92)
          at
          weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:191)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
          at
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
          at
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
          at
          weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
          Any idea on how to fix this?
          Thanks for any help,
          David


          yes, weblogicaux.jar is definitely in the weblogic.class.path. i've even tried starting the server from the command line, declaring the classes there. my "trade.xml" document has the URI set as "http://localhost:7001/BizTalkServer". when i enter this on the "BizClient.jsp" form, i get the error discussed below. however, if i enter "http://localhost:7001", even though this is not the explicit location of the BizTalk server, the server returns:
          Thank you! Your trade has been recieved. A BizTalk document has been sent to http://localhost:7001/ with the following information: etc...............
          So there appears to be something wrong with the "/BizTalkServer" setup on my machine. Any ideas?
          Kumar Allamraju <[email protected]> wrote:
          >Make sure weblogicaux.jar is in your weblogic.class.path
          >
          >i.e -Dweblogic.class.path=$WL_HOME/lib/weblogicaux.jar:$WL_HOME/classes etc etc...
          >
          >--
          >Kumar
          >
          >Mike Bachers wrote:
          >
          >> I'm currently struggling with a similar problem, although as a newcomer to WL I'm having some trouble figuring it out. I'm trying to run the BizTalk server example (http://www.weblogic.com/docs51/examples/xml/biztalk/index.html) under Windows 2000 and JDK1.2.2. I'm able to proceed without problems until I submit the form on the "BizClient.jsp" page. At this point, I receive this error:
          >> ------------------------------------------------
          >> There was a problem connecting to the BizTalk server. Exception caught: java.io.FileNotFoundException: Response: '500' for url: 'http://localhost:7001/BizTalkServer'
          >> ------------------------------------------------
          >>
          >> At the same time, the WL console spits this out:
          >> ------------------------------------------------
          >> java.lang.NoClassDefFoundError: javax/naming/NamingException
          >> ....
          >> ------------------------------------------------
          >>
          >> I know this class is in the weblogicaux.jar, and it's included in my classpath. I think David's fix (see below) is getting at my problem, too, but I'm not sure. Anyone relate?
          >>
          >> "David R. Heffelfinger" <[email protected]> wrote:
          >> >Figured it out. The problem was that the beans were in a directory
          >> >in the JAVA_CLASSPATH in weblogic.properties. Moved the directory to
          >> >WEBLOGIC_CLASSPATH and the problem went away.
          >> >
          >> >David
          >> >
          >> >"David R. Heffelfinger" wrote:
          >> >
          >> >> Hello,
          >> >>
          >> >> I am developing a JSP which contains a JavaBean.
          >> >> This bean is a wrapper for a session EJB, the getProperty() methods in
          >> >> the bean call methods on the EJB's remote interface.
          >> >>
          >> >> I have tested this bean as a stand alone application by adding a
          >> >> main(String[] args) method to it and it works.
          >> >>
          >> >> However, when adding the bean to the JSP, the JSP does not show in the
          >> >> browser, I get a n internal server error 500 instead.
          >> >> It seems that Weblogic is not finding the javax.naming.NamingException
          >> >> class when instantiating the bean.
          >> >>
          >> >> When looking at the weblogic log, I see the following stack trace:
          >> >>
          >> >> Fri Aug 18 15:12:06 EDT 2000:<E> <ServletContext-General> Servlet failed
          >> >> with Exception
          >> >>
          >> >> java.lang.NoClassDefFoundError: javax/naming/NamingException
          >> >>
          >> >> at java.lang.ClassLoader.resolveClass0(Native Method)
          >> >>
          >> >> at java.lang.ClassLoader.resolveClass(ClassLoader.java:579)
          >> >>
          >> >> at
          >> >> weblogic.utils.classloaders.GenericClassLoader.reallyLoadClass(GenericClassLoader.java,
          >> >> Compiled Code)
          >> >>
          >> >> at
          >> >> weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java,
          >> >> Compiled Code)
          >> >>
          >> >> at
          >> >> weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java,
          >> >> Compiled Code)
          >> >>
          >> >> at java.beans.Beans.instantiate(Beans.java:194)
          >> >>
          >> >> at java.beans.Beans.instantiate(Beans.java:55)
          >> >>
          >> >> at weblogic.servlet.jsp.JspLexer.processBeanTag(JspLexer.java:1138)
          >> >>
          >> >> at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(JspLexer.java,
          >> >> Compiled Code)
          >> >>
          >> >> at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1554)
          >> >>
          >> >> at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
          >> >>
          >> >> at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
          >> >> Code)
          >> >>
          >> >> at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
          >> >>
          >> >> at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
          >> >>
          >> >> at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
          >> >>
          >> >> at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
          >> >>
          >> >> at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
          >> >> Compiled Code)
          >> >>
          >> >> at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
          >> >> Code)
          >> >>
          >> >> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
          >> >>
          >> >> at weblogic.servlet.jsp.JspStub.checkForReload(JspStub.java:92)
          >> >>
          >> >> at
          >> >> weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:191)
          >> >>
          >> >> at
          >> >> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
          >> >>
          >> >> at
          >> >> weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
          >> >>
          >> >> at
          >> >> weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
          >> >>
          >> >> at
          >> >> weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
          >> >>
          >> >> at
          >> >> weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
          >> >>
          >> >> at
          >> >> weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
          >> >>
          >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
          >> >>
          >> >> Any idea on how to fix this?
          >> >>
          >> >> Thanks for any help,
          >> >> David
          >> >
          >

Bi Beans Loosing Stylesheet On Weblogic 8.1

Similar Messages

Maybe you are looking for