Refresh Servlets in WLS 7

          We recently upgraded from a 6 to 7 weblogic environment, and I cannot get my servlets
          to reload without stopping and restarting the server. I have tried everything
          and this problem is driving me crazy.
          I had the same problem in 6 but was able to figure it out after reading some similar
          posts -- but there isn't enough material posted on 7 yet. Specifically, I have
          a servlet displaying as a portlet (by having the content URL as /servlet.SurveyServlet
          and mapping *.SurveySurvlet) but it is not refreshing when I change and recompile
          the code.
          What pitfalls are there when trying to avoid having a servlet cached?
          Please help...
          Laura

Some developer adds all WEB-INF/classes in classpath because some third party lib
 like early version of Cocoon uses its own classloader. Just check your system
 classpath in Weblogic start script to remove any unwanted paths. Or check your
 weblogic configuration to make sure auto deploy is enabled.
 "Laura Cardinal" <[email protected]> wrote:
 >
 >What could be in my system classpath that would cause the servlet to
 >not refresh?
 >
 >-Laura
 >
 >
 >>Admin Console: YourDomain->Applications->Check Auto Deployed enabled.
 >>
 >>If it does not work, DEployments->Web Applications->Your application->redeploy
 >>each time you update something.
 >>
 >>If none works, you have something in system classpath which prevents
 >>reload.
 >>
 >>
 >>"Laura Cardinal" <[email protected]> wrote:
 >>>
 >>>We recently upgraded from a 6 to 7 weblogic environment, and I cannot
 >>>get my servlets
 >>>to reload without stopping and restarting the server. I have tried
 >>everything
 >>>and this problem is driving me crazy.
 >>>
 >>>I had the same problem in 6 but was able to figure it out after reading
 >>>some similar
 >>>posts -- but there isn't enough material posted on 7 yet. Specifically,
 >>>I have
 >>>a servlet displaying as a portlet (by having the content URL as /servlet.SurveyServlet
 >>>and mapping *.SurveySurvlet) but it is not refreshing when I change
 >>and
 >>>recompile
 >>>the code.
 >>>
 >>>What pitfalls are there when trying to avoid having a servlet cached?
 >>>
 >>>Please help...
 >>>Laura
 >>>
 >>
 >

Similar Messages

When to refresh Servlet data from Data Base

Hello all,
I have a servlet that retrive few hundreds thousands records from data base table.
The data in data base table being updated once or twice in every week.
Since same servlet instance serve all users, that access the servlet many times a day.
I would like to avoid retriving the data from data base on each servlet access.
and make the users use same data already retrieved and kept in servlet members.
First, what is the best way to avoid data retrive from data base on each servlet access?
and how could I have some kind of trigger that will refresh servlet data from data base every few days?
Thanks in advance for every idea.
Ami

Java_A wrote:
Thanks Saish for your reply.
I'm not using DAO in my application but retrive the data from BI data base using a web service. response time querying the BI data base is not quick enuogh.
Since, I wouldn't want to query the BI server on each servlet access.
Because the data I retrived at the begining using the web service contains all required data for all servlet requests, I thought to store the data (~200K rows) once in the servlet which will be using for all requests.
Why not store the results locally in your own database after you fetch them?
This still leave me with the questions: in which event should I query the BI data, and also when or in which event should I update the data again from BI server?
Query at startup, an user demand, when data becomes stale. It depends on your requirements.
>
Thanks
Ami- Saish

Problem in servlet engine (WLS 7.0) with the chunked transfer

Hi,
          While using jakarta-slide on weblogic 7.0, I encountered the following
          problem while uploading files using WebDAV servlet deployed on WLS:
          "**** This file has a corrupted %%EOF marker, or garbage after the
          %%EOF."
          Is this is a problem with the way that WLS servlet engine is handling
          chunked transfers ?
          According to the change request 084847, "For chunked
          transfer, WebLogic Server was including a hexadecimal number which
          other
          servlet engines used to ignore. This has been fixed WLS 6.1 sp 4."
          Is this fixed in WLS 7.0 ? I could not find this in the resolved bugs
          list for WLS 7 SP1. If this has not been fixed in 7.0, any idea when
          this fix would make it to WLS 7.0 ?
          Any pointers would be of great help.
          Thanks,
          Jeeji.


Hi,
          While using jakarta-slide on weblogic 7.0, I encountered the following
          problem while uploading files using WebDAV servlet deployed on WLS:
          "**** This file has a corrupted %%EOF marker, or garbage after the
          %%EOF."
          Is this is a problem with the way that WLS servlet engine is handling
          chunked transfers ?
          According to the change request 084847, "For chunked
          transfer, WebLogic Server was including a hexadecimal number which
          other
          servlet engines used to ignore. This has been fixed WLS 6.1 sp 4."
          Is this fixed in WLS 7.0 ? I could not find this in the resolved bugs
          list for WLS 7 SP1. If this has not been fixed in 7.0, any idea when
          this fix would make it to WLS 7.0 ?
          Any pointers would be of great help.
          Thanks,
          Jeeji.

Order of startup servlets in WLS 5.1

 Is there any way to set the order in which servlets are started up using ServletStartup.
 I have something similar to this in my weblogic.properties file -
 weblogic.system.startupClass.StartServletA=weblogic.servlet.utils.ServletStartup
 weblogic.system.startupArgs.StartServletA=servlet=ServletA weblogic.system.startupClass.StartServletB=weblogic.servlet.utils.ServletStartup
 weblogic.system.startupArgs.StartServletB=servlet=ServletB
 I'd like ServletA to load first and then ServletB, but ServletB always seems to
 load first.
 Any ideas?
 Thanks...
 ps - using WLS 5.1, SP6


If, for some reason, you do not deploy your application as a webapp,
 you can use ServletStartup:
 http://www.weblogic.com/docs51/classdocs/API_servlet.html#128566
 > Dimitri,
 > Thanks for the response. But wouldn't this restrict me to only
 > servlets that are deployed within a WebApp? would the servlet
 > run even when the webApp is not deployed?
 > Modou.
 > Dimitri Rakitine <[email protected]> wrote:
 >>The portable way is to specify load-on-startup in the
 >>web.xml - 5.1sp7 or 8
 >>supports this (but not before).
 >>
 >>Modou <[email protected]> wrote:
 >>
 >>> Hi,
 >>> I would like to know if:
 >>> 1) a servlet can be used as a startup class in WLS 5.1.
 >>If so,
 >>> are there any restriction on what can be done inside
 >>this servlet?
 >>> Or
 >>
 >>> 2) can we load a servlet from a startup class? if so?
 >>how?
 >>
 >>> any ideas?
 >>
 >>> regards,
 >>> Modou.
 >>
 >>--
 >>Dimitri
 Dimitri

Is it possible to connect a servlet on WLS 6.1 to a server WLE 4.5?

Hi all,
Is it possible to connect a servlet java client on WLS 6.1 to a server CORBA
on WLE 4.5?
I have many problem, this connection doesn't!
The configuration is ok! But when the client java call
Tobj_Bootstrap bootstrap = BootstrapFactory.getClientContext("mypool");
the return is always null...
in the config.xml I define
<WLECConnectionPool MaximumPoolSize="5" MinimumPoolSize="2"
Name="mypool" PrimaryAddresses="//host:1570"
UserName="wrap" WLEDomain="wrap"/>
..the same code worked perfectly on the Web Logic Server 4.5...
Please help me!!!
Thank you very much!
Gisy

These 'warnings' are usually pop-unders from a web page you've visited (i.e. they stay behind the page you're viewing so you don't see them until later).
They claim to have scanned your computer and found viruses: this is complete rubbish and a scam - aimed really at Windows users (the details given are often applicable only to windows).
You don't have any viruses: there are no Mac viruses in the wild. There are trojans and malware, but in all cases you have to actually install them (usually they try to make you think you are installing something else) and you would have had to give your admin password to do so.
You were right to stop the download. Never ever download or click any links on anything of this nature. Unless you have specific anti-virus software installed (which would identify itself in any warning) no warning of this nature can be genuine: it's an attempt to get you to install malware, some of which can be very nasty.

No overloaded servlets in WLS?

We are getting ready to migrate from OAS to WLS and I ran into an issue while loading our JWS app WAR into WLS. From what I can tell from the below log, WLS sees repeat init-param service descriptors with different parameters as duplicates. This worked fine in OAS - is there a setting in WLS to allow this, or do we have to rename the services so they are unique?
[EDIT - I found this OLD post by Rob Woollen saying this should be fixed in the next version... but obviously this was not fixed, or at least does not work in the present version.
Re: successfully Deployable CE web desktop war in 8.1 fails to Deploy in 9.
Posted: Jul 7, 2006 1:14 PM in response to: BEAGuest in response to: BEAGuest
Click to report abuse... Click to reply to this thread Reply
The problem is most likely that you have a duplicate entry in your servlet-mappings in the web.xml. WLS 8.1 ignored this, but 9 is not allowing it. 9 should be patched to allow it, but I don't believe it's been fixed yet.
-- Rob]
From web.xml:
 <init-param>
 <param-name>SessionCommand: createWorkspace</param-name>
 <param-value>com.l3.cvc.service.server.workspace.WorkspaceUtil.createWorkspace(HttpSession,String, String, String)</param-value>
 </init-param>
 <init-param>
 <param-name>SessionCommand: createWorkspace</param-name>
 <param-value>com.l3.cvc.service.server.workspace.WorkspaceUtil.createWorkspace(HttpSession,String, String, String, Long)</param-value>
 </init-param>
From AdminServer.log:
<BEA-160197> <Unable to load descriptor C:\Oracle\Middleware\user_projects\domains\cvc_domain\servers\AdminServer\upload\Dev.war/WEB-INF/web.xml of module Dev.war. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
 at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:161)
 at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
 at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
 at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
 at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
 at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
 at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
 at weblogic.servlet.utils.WarUtils.getWebAppBean(WarUtils.java:124)
 at weblogic.application.compiler.WARModule.processLibraries(WARModule.java:413)
 at weblogic.application.compiler.WARModule.merge(WARModule.java:457)
 at weblogic.application.compiler.flow.SingleModuleMergeFlow.proecessModule(SingleModuleMergeFlow.java:17)
 at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
 at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:70)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
 at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:97)
 at weblogic.application.compiler.ReadOnlyWarMerger.merge(ReadOnlyWarMerger.java:28)
 at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:88)
 at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:42)
 at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:70)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
 at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:97)
 at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157)
 at weblogic.utils.compiler.Tool.run(Tool.java:158)
 at weblogic.utils.compiler.Tool.run(Tool.java:116)
 at weblogic.application.compiler.AppMerge.merge(AppMerge.java:170)
 at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:88)
 at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:63)
 at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:181)
 at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createLazyDeployableObject(WebLogicDeployableObjectFactoryImpl.java:156)
 at weblogic.deploy.api.tools.SessionHelper.inspect(SessionHelper.java:661)
 at com.bea.console.actions.app.install.Flow$2.execute(Flow.java:470)
 at com.bea.console.utils.DeploymentUtils.runDeploymentAction(DeploymentUtils.java:5022)
 at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:467)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870)
 at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
 at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
 at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
 at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
 at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
 at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
 at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
 at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
 at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64)
 at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184)
 at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50)
 at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58)
 at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87)
 at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2121)
 at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:261)
 at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
 at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
 at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
 at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
 at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:159)
 at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:263)
 at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:416)
 at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:135)
 at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
 at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686)
 at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
 at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106)
 at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
 at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
 at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
 at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:227)
 at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:332)
 at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
 at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
 at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
 at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
 at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
 at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
 at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:389)
 at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
 at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
 at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:253)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
 at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
 at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:131)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
 at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: com.bea.xml.XmlException: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.ParamValueBeanImpl@fba1b127(/[rpcServlet]/InitParams[SessionCommand: createWorkspace])"
 at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)
 at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:539)
 at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:381)
 at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
 at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
 at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:185)
 at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
 at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
 at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
 at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
 at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
 at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
 at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
 ... 123 more

It looks to me that there is no absolute prescription for how this must be handled in the Servlet specification or in the xsd of the web.xml file.
The Servlet API shows that the call to get an init parameter returns a String, not any type of Collection or array.
java.lang.String getInitParameter(java.lang.String name)
Which to me, indicates that the (unstated?) intention is to have unique name/value pairs. If you are having multiple values defined with the same parameter name, which would you expect to be returned on the getInitParameter call? The first? The last? Or it doesn't matter as long as it's consistent? Still, it's non-standard behaviour.
But then I checked the behaviour on GlassFish 3.1.1 and WLS 12.1.1.
On GlassFish the application does deploy and doesn't throw an error. It returns the first name value that was specified in web.xml when getInitParameter is called.
On the latest WLS release (12c, 12.1.1.0) it followed the same model as GlassFish: deployed, returned first entry of the given name.
I think both those observations, particularly the latter, would give you a valid case with Oracle Support if you open a service request to get this addressed on the release you are using.
-steve-

How to refresh Servlet

Hi Friends
I have done a mistake in servlet file,compiled it and uploaded on Jakarta-tomcat server.
Now i have taken care of this mistake and again compiled and uploadedthis servlet on the same jakarta-tomcat server.
But the change is not reflected,I am getting the same error again and again.
How to refresh this servlet.
Here are my limitations-
1)I can not shut down the server
2)I can not delete the work folder or it's contents
Any help?
Thanks in advance

If it is tomcat 4.1 then you can use its adminitrator jsp page to make your context(webapp) reloadable. This in turn will make chages to your your server file and will add the context back to tomcat without stopping it.
Regards

Servlet, ejb, wls 510, ClassCastException

Hello,
 I have an Entity Bean deployed in WLS 5.1.0.
 I wrote a standalone application that obtains the initial context, does a
 lookup, get back
 a home interface, then the business interface (using narrow...), and calls
 business methods...
 Everything works fine...
 BUT....
 The SAME code within a servlet (doGET) does NOT work and throws a
 ClassCastException.
 Is there any issues using EJBs from Servlets?
 Thank you a lot.
 --Thierry
 PS: Here is the code.
 import javax.servlet.http.*;
 import javax.servlet.*;
 import javax.naming.*;
 import javax.ejb.*;
 import javax.rmi.*;
 import org.zol.webstore.ejbs.person.*;
 import java.util.*;
 public final class TestServlet extends HttpServlet {
 * Method init, called when the servlet is initialized
 public void init(ServletConfig sc) throws ServletException {
 System.err.println("@@@@@@@@@@@@ init "+sc);
 * doPost
 * @param req
 * @param res
 protected void doGet(HttpServletRequest req, HttpServletResponse res)
 throws java.io.IOException {
 ServletOutputStream sos = null;
 System.err.println("@@@@@@@@@@@@ doGet ");
 try{
 sos = res.getOutputStream();
 sos.println("<HTML><BODY>");
 sos.println("Test "+new Date()+" ");
 InitialContext initialContext = getInitialContext();
 System.err.println("@@@@@@@@@@@@ Got ic "+initialContext);
 Object pO = initialContext.lookup("person.PersonEntityHome");
 sos.println(" pO: "+pO);
 System.err.println("@@@@@@@@@@@@ Got Object PO ");
 System.err.println("@@@@@@@@@@@@ Checking if we can narrow
 PersonEntityHome");
 Object toNarrow = PortableRemoteObject.narrow(pO,
 PersonEntityHome.class);
 System.err.println("@@@@@@@@@@@@ YES!!!");
 PersonEntityHome pehome = (PersonEntityHome) toNarrow; // FAILS
 sos.println(" pehome: "+pehome);
 System.err.println("@@@@@@@@@@@@ Got PE HOME ");
 sos.println("</BODY></HTML>");
 } catch (Exception eee) {
 sos.println(eee.getMessage());
 eee.printStackTrace();
 public InitialContext getInitialContext() {
 InitialContext ic = null;
 try {
 Hashtable h = new Hashtable();
 h.put(Context.INITIAL_CONTEXT_FACTORY,
 "weblogic.jndi.WLInitialContextFactory");
 h.put(Context.PROVIDER_URL, "t3://localhost:7001");
 ic = new InitialContext(h);
 } catch (Exception e) {
 e.printStackTrace();
 return ic;


Doesn't that mean that you can't hot deploy the EJB now?
 -rrc
 Thierry Janaudy wrote:
 > Put the classes in the WEBLOGICCLASSPATH...
 > And now it does work....
 >
 > Thank you Thierry,
 >
 > Your Welcome.
 >
 > Thierry
 >
 > Thierry Janaudy <[email protected]> wrote in message
 > news:[email protected]...
 > > Hello,
 > >
 > > I have an Entity Bean deployed in WLS 5.1.0.
 > > I wrote a standalone application that obtains the initial context, does a
 > > lookup, get back
 > > a home interface, then the business interface (using narrow...), and calls
 > > business methods...
 > > Everything works fine...
 > >
 > > BUT....
 > >
 > > The SAME code within a servlet (doGET) does NOT work and throws a
 > > ClassCastException.
 > > Is there any issues using EJBs from Servlets?
 > >
 > > Thank you a lot.
 > > --Thierry
 > >
 > > PS: Here is the code.
 > > --------------------------------------------------------------------------
 > --
 > > ----------------
 > >
 > > import javax.servlet.http.*;
 > > import javax.servlet.*;
 > > import javax.naming.*;
 > > import javax.ejb.*;
 > > import javax.rmi.*;
 > > import org.zol.webstore.ejbs.person.*;
 > > import java.util.*;
 > >
 > > public final class TestServlet extends HttpServlet {
 > >
 > > /**
 > > * Method init, called when the servlet is initialized
 > > */
 > > public void init(ServletConfig sc) throws ServletException {
 > > System.err.println("@@@@@@@@@@@@ init "+sc);
 > > }
 > >
 > > /**
 > > * doPost
 > > * @param req
 > > * @param res
 > > */
 > > protected void doGet(HttpServletRequest req, HttpServletResponse res)
 > > throws java.io.IOException {
 > > ServletOutputStream sos = null;
 > >
 > > System.err.println("@@@@@@@@@@@@ doGet ");
 > >
 > > try{
 > > sos = res.getOutputStream();
 > >
 > > sos.println("<HTML><BODY>");
 > > sos.println("Test "+new Date()+" ");
 > >
 > > InitialContext initialContext = getInitialContext();
 > >
 > > System.err.println("@@@@@@@@@@@@ Got ic "+initialContext);
 > >
 > > Object pO = initialContext.lookup("person.PersonEntityHome");
 > > sos.println(" pO: "+pO);
 > >
 > > System.err.println("@@@@@@@@@@@@ Got Object PO ");
 > >
 > > System.err.println("@@@@@@@@@@@@ Checking if we can narrow
 > > PersonEntityHome");
 > > Object toNarrow = PortableRemoteObject.narrow(pO,
 > > PersonEntityHome.class);
 > >
 > > System.err.println("@@@@@@@@@@@@ YES!!!");
 > >
 > > PersonEntityHome pehome = (PersonEntityHome) toNarrow; // FAILS
 > >
 > > sos.println(" pehome: "+pehome);
 > >
 > > System.err.println("@@@@@@@@@@@@ Got PE HOME ");
 > >
 > > sos.println("</BODY></HTML>");
 > > } catch (Exception eee) {
 > > sos.println(eee.getMessage());
 > > eee.printStackTrace();
 > > }
 > > }
 > >
 > >
 > > public InitialContext getInitialContext() {
 > > InitialContext ic = null;
 > >
 > > try {
 > > Hashtable h = new Hashtable();
 > > h.put(Context.INITIAL_CONTEXT_FACTORY,
 > > "weblogic.jndi.WLInitialContextFactory");
 > > h.put(Context.PROVIDER_URL, "t3://localhost:7001");
 > > ic = new InitialContext(h);
 > > } catch (Exception e) {
 > > e.printStackTrace();
 > > }
 > >
 > > return ic;
 > > }
 > > }
 > >
 > >
 Russell Castagnaro
 Chief Mentor
 SyncTank Solutions
 http://www.synctank.com
 Earth is the cradle of mankind; one does not remain in the cradle forever
 -Tsiolkovsky

Refreshing servlet context data

I am binding few lists to the servlet context as they are required application wide,when init() method of one of the servlets is called.
Now I have requirement to refresh this data on daily basis without restarting the server.How this can be done?

If it's daily then you can create a java.util.TimerTask and apply it to a java.util.Timer to run every 24 hours.
Cheers,
Anthony

How to access Servlets in WLS examples

 I am trying to access Servlets stored in myserver/servletclasses/examples/servlets
 directory. .class files are here. When I tried to access a servlet in a browser,
 I am getting error. Can any one help me?


 In Weblogic 5.1, each example (souce code) in $WL_HOME/examples) comes with a very
 good and detail instruction. Read these instructions will definitely help you
 to understand Weblogic 5.1. Weblogic 6 is a little bit different, but most instructions
 are still useful.
 "magunta" <[email protected]> wrote:
 >
 >I am trying to access Servlets stored in myserver/servletclasses/examples/servlets
 >directory. .class files are here. When I tried to access a servlet in
 >a browser,
 >I am getting error. Can any one help me?

Automatic refreshing servlets

For servlets to reload its changes whenever they have been changed is defined by including the code below in server.xml:
<Context path="/bookstore" docBase="webapps/bookstore" debug="0" reloadable="true" />
But this does not seems to work everytime whenever there's changes in the servlets code.
Anyone who has tried this before?
Can we always see the updated changes made to the servlets without restarting the Jakarta tomcat Server?

I have changed some codes in one of the servlets which wasn't meant to work but it is still pointing to the old servlet although I have opened in a new window.

Hot Deploy Servlet in JAR file problem

I've been playing with hot deploying servlets in WLS 5.1. I have SP2
          installed. I have things working fine with individual servlet class files. I
          decided to try hot deploying with jar files.
          I created a servlet, added it to a jar file, and then added the jar file to
          the 'weblogic.http.servlet.classpath'. I then restarted the server. I
          started the console and was able to hot deploy the servlet. So far so good.
          My next test is what failed. I modified the servlet, and rebuilt the jar
          file. I went back to the console, selected the servlet and hit the redeploy
          button. I went back to the browser and hit refresh - nothing, still the old
          servlet.
          It appears that WLS isn't reloading the jar file and the updated servlet.
          Everything works with individual class files.
          Does anyone know how I can cause the reload of updated servlets embedded
          within a jar file?
          Weblogic group - If there is no way now, will support be added soon?
          Thanks,
          Rick


Hi,
          If I use weblogic.servlet.ServletServlet to try just the servlet , It
          works correctly.But When I develop it in a web application , there is a lot
          of hypelink to this servlet,thus I can't use the relative path reference to
          that servlet.I try to set the name of weblogic.servlet.ServletServlet same
          as the webapp,It doesn't work,how do I solve this problem?
          Thank you
          Pan
          Subject: Re: Hot deploy Servlet in webapp
          > http://www.weblogic.com/docs51/classdocs/API_servlet.html#134798
          >
          > It even explains why you shouldn't use it in production environment.
          >
          > Dimitri

Same Servlet/JSP is executing again and again

 Hello,
 We have some JSPs which do a lot of processing and is 'alive' for a long period
 of time. If we use the JSP with small amouts of data, it is fine. But when we
 use the JSP with lot of data, it seems to 'go in a loop'.
 It is processing the data again and again and again and brings down our server.
 We do not think it is the code that is wrong - as it processes perfectly if the
 data is small or when our server is not busy. This problem happens if the data
 is lot and the server is also busy. The JSP seems to be executing again and again.
 Is there some type of 'refresh' logic in weblogic that refreshes the JSP/servlet
 and makes it 'execute' again and again.
 We are using WL 6.1
 Thanks,
 Oleg.


there is no refresh logic in wls unless u specify it.
 please check the code for any "refresh"ing the page
 SP
 "Oleg" <[email protected]> wrote in message
 news:[email protected]..
 >
 > Hello,
 > We have some JSPs which do a lot of processing and is 'alive' for a long
 period
 > of time. If we use the JSP with small amouts of data, it is fine. But
 when we
 > use the JSP with lot of data, it seems to 'go in a loop'.
 > It is processing the data again and again and again and brings down our
 server.
 > We do not think it is the code that is wrong - as it processes perfectly
 if the
 > data is small or when our server is not busy. This problem happens if the
 data
 > is lot and the server is also busy. The JSP seems to be executing again
 and again.
 >
 > Is there some type of 'refresh' logic in weblogic that refreshes the
 JSP/servlet
 > and makes it 'execute' again and again.
 > We are using WL 6.1
 >
 > Thanks,
 > Oleg.

How to use java security in a servelt with weblogic as a servlet engine?

Hi,
i want to use standard java security with a user defined permission in
servlet with wls 5.1 (Win nt) as a servelt engine.
WL-Home: f:\weblogic
Server: f:\weblogic\elan
Servlet: f:\weblogic\elan\elan\ServletGropsTest.class
The Servlet is registered in weblogic.properties:
weblogic.httpd.register.elan.ServletGropsTest=elan.ServletGropsTest
i've added this to the weblogic.policy:
grant codebase "file:f:/weblogic/elan/elan/" {
permission java.security.AllPermission;
The servlet code is:
SecurityManager m = System.getSecurityManager();
if (m != null) m.checkPermission(new AndisPermission("x","y"));
WLS throws the permission-exception:
Do Jul 18 11:54:54 GMT+02:00 2002:<E> <ServletContext-General> Servlet
failed with Exception
java.security.AccessControlException: access denied
(elan.AndisPermission x y)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java,
Compiled Code)
at java.lang.Exception.<init>(Exception.java, Compiled Code)
at java.lang.RuntimeException.<init>(RuntimeException.java,
Compiled Cod
at elan.ServletGropsTest.doGet(ServletGropsTest.java, Compiled
Code)
can anyone help?
regards
Andy

ran_t wrote:
...I am using java 1.3.Why are you using an utterly obsolete version of Java?
My program using log4j jar.
When i put the log4j.jar in a path that include spaces like "c:\Program files\",Try it as c:\Program%20files\

Servlets in one machine and static html pages in another machine

We have one technical problem concerning WebLogic Server 5.1. Our customer
 wants to install two WLS servers in two machines. Let's call these machines
 and WLS instances A, which is a front end machine, and B, which is a back
 end machine. WLS A has all the static html pages and is open to public. WLS
 B has all servlets and business logic (EJB components...) and is open only
 to machine A. We are wondering if it is possible to configure WLS A so that
 when the client's browser requests a static html page and there is a link to
 a servlet in WLS B, the http requests goes from the client's browser first
 to WLS A, which sends the same request to WLS B, which runs the request in a
 servlet and sends the response to WLS A, which sends the response back to
 the client's browser. In that way the client allways thinks that it is
 communucating with WLS A and is unaware of the existance of the WLS B. We
 are wondering if this is possible with WLS configuration and if it is, how
 this can be done.
 Sami Elomaa


Use ProxyServlet:
 http://www.weblogic.com/docs51/admindocs/http.html#proxy
 btw, why don't you let WLS A serve html and servlets, and let WLS B serve
 EJBs... it's more logical that way. Well, I'm kinda biased because that's
 how we do it... ;-)
 Gene Chuang
 Teach the world. Join Kiko!
 http://www.kiko.com/profile/join.jsp?refcode=TAF-gchuang
 "Sami Elomaa" <[email protected]> wrote in message
 news:[email protected]...
 > We have one technical problem concerning WebLogic Server 5.1. Our customer
 > wants to install two WLS servers in two machines. Let's call these
 machines
 > and WLS instances A, which is a front end machine, and B, which is a back
 > end machine. WLS A has all the static html pages and is open to public.
 WLS
 > B has all servlets and business logic (EJB components...) and is open only
 > to machine A. We are wondering if it is possible to configure WLS A so
 that
 > when the client's browser requests a static html page and there is a link
 to
 > a servlet in WLS B, the http requests goes from the client's browser first
 > to WLS A, which sends the same request to WLS B, which runs the request in
 a
 > servlet and sends the response to WLS A, which sends the response back to
 > the client's browser. In that way the client allways thinks that it is
 > communucating with WLS A and is unaware of the existance of the WLS B. We
 > are wondering if this is possible with WLS configuration and if it is, how
 > this can be done.
 >
 > Sami Elomaa
 >
 >

Refresh Servlets in WLS 7

Similar Messages

Maybe you are looking for