Weblogic error Page

Is there a way to change the Weblogic error page (404,500,...)?

By default we removed the "pumpkin" page. Many customers are not interested
in having the term WebLogic displayed by default. But, you should still be
able to change this error Page. The way to do this is inside of your Web
application deployment descriptor Web.XML.
Michael Girdley
BEA Systems
Learning WebLogic? http://learnweblogic.com
"vr" <[email protected]> wrote in message
news:3a9e78d9$[email protected]..
>
I can't remember if it was in WebLogic 4.5 or 5.1, but we used to get a404
weblogic error page with a gold background and a graphic symbol of "w" for
weblogic. Now in WebLogic 6.0 we just get a plain white page with black
text for the 404 error. Is that available at all in WebLogic 6.0? Ifnot,
how can we get it? It seems like in the previous versions of WebLogicthey
allowed you to customize you error pages if you wanted in
weblogic.properties
I can't find any reference to doing that in WL 6.0 through the Console
(never mind that I can't find an actual weblogic.properties or equivalentto
alter manually). So any insight/suggestions on this issue?
Thanks,
V

Similar Messages

WebLogic Error Pages

How can you replace the default WebLogic generated error pages (401,403,500) with custom error pages for all deployed applications?
WL 10.3.3
Edited by: SK Jennings on Oct 26, 2010 12:24 PM

Hi,
May be the following link would answer your question
Re: How to show an error Page in Weblogic when the server is down
Hope this helps you.
Regards,
Ravish Mody

How to show an error Page in Weblogic when the server is down

Hi ,
I heard that every container has the facility to show an error page when the server is down and (when the request has arrived at that time ).
Please tell me how to configure this in BEA weblogic ??
Thanks .

Hi,
From my understanding weblogic dose not provide the thing which you are asking for, reason is given below.
- An application is deployed only on managed server one (MS-1)
- Now if the request comes to the server (MS-1) when it was running and then for some reason MS-1 goes down then weblogic server would be able to send any response back to the client as its down.
- Hence nothing can be done as the request object is been lost when the server goes down or even cant redirect to an error page as for doing that too the server has to be up and running.
However there are other way round which can help you overcome this issue as shown below
- Use Clusters with few managed servers in it which gives you high availability and load-balancing.
- Use any web servers like Apache in front of weblogic servers.
Using the above things you can also use customized HTTP Error Responses with error-page element in web.xml and create your own error pages which can be re-directed for the web server side also. For more information go through the below links
Topic: Customizing HTTP Error Responses
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webapp/configurejsp.html#wp157884
Topic: error-page
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/webapp/web_xml.html#1017571
Topic: ErrorPage
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1155425
Hope above information helps you.
Regards,
Ravish

How do I create custom HTTP Error Pages for a Weblogic Server

I need to be able to display custom HTTP error pages such as a 404 from my Weblogic
Server when my web application is not deployed.
Is this possible?
I have seen some suggestions about putting something like:
<error-page>
<error-code>404</error-code>
<location>Error404.jsp</location>
</error-page>
in the web.xml for my web application but I can't see how that would work since
the web application would not be deployed. I need to set these messages at the
server level.
Any help would be appreciated!
thanks

Your CategoryAxis id="ha_ccm" uses categoryField="period", and this is the label for the your series (i.e. "Quarter 4/2010"). You cannot have multiple categoryFields for the CategoryAxis; it can only use one data field for the labels. You can use data tips and/or label functions to show the individual series' values on the columns.
Also:
Your labelField in the ColumnSeries are set to a ColumnSet name instead of a field name in your dataprovider.
Font must be embedded if you set ColumnChart.showLabelVertically="true".

Error pages in Weblogic 10.3

I have no problem with error pages by error-type defined in web.xml, but by exception-type does not seem to work. Are there any additinal steps in this configuration?

 <error-page>
 <exception-type>java.lang.Exception</exception-type>
 <location>/Error.jsp</location>
 </error-page> and in Error.jsp add,
<%@ page isErrorPage="true" %>
<html>
<head>
<title>Exception occurred</title>
</head>
<body>
<%= exception.toString() %>
</body>
</html>

JSP error page does not displayed on its own, includes in the original JSP

Problem Description: - Exceptions in a Condition cause pages to fail to render.
The actual issue is, the JSP error page does not displayed on its own, included in the original JSP Page when exception occurs.
Problem Cause: As per the JSP specification when jsp content reached the buffer size (default 8KB) the page being flushed (Part of condent displays). The default �autoFlush� value is true.
When the page buffer value is default size (8KB), and if any exception occurs after flushing the part of the content, instead of redirecting into error page, the error page content included in the original page.
If i specify autoFlush="false" and with default buffer size, at the runtime if the buffer size is reached, i am getting stackoverflow error.
To solve the above problem we can make it autoFlush=�false� and buffer=�100KB�. But we can�t predict the actual size of the page.
I found in one of the weblogic forum as no solution for this issue. Ref.
http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_clfydoc&answerpage=solution&page=wls/S-10309.htm
Please provide me any solution to resolve the problem.

Error-Page tags work best with an error.html pages. If you have an error.jsp page what I would do, and I have, is wrap my classes and jsp pages in a try catch block where you forward to the error jsp page and display anything you want. YOu can also do this with if else statements. I have used the tomcat error pages before but when I've implemented them I used java.lang.Exception as the error to catch not Throwable. I don't know if this would make a difference or have anything to do with your problem.

Using error pages in web.xml

 Having a few problems with error pages and web.xml with browsers caching the error
 pages and strange errors coming out of weblogic.servlet.intenal.WebAppServletContext
 I'm trying to set a web app up so that all http errors and all exceptions are
 routed thruogh predefined resources. For now, I'm simply send 400 errors to 400.html
 and the ServletException, IOException and RuntimeException to respective html
 pages.
 What I'm finding is that the error codes work fine but the exceptions are only
 be routed to the correct error page for the first call to the servlet after server
 restart.
 So for example, I have my servlet throwing a ServletException as a test case.
 The weblogic server log shows that ServletException is thrown, and the correct
 error page for ServletExceptions is shown.
 If I change the Servlet code to throw IOException in place of SevletException,
 the weblogic.log shows that IOExceptyion is being thrown (so the servlet has deployed
 successfully), however the Servletxception error page is shown on the browser.
 I'm using IE6 and I've changed the setting such that a new page is requested every
 time using the tools-internet options-temp internet files-settings option to "check
 for new versions of stored pages: Every visit to the page".
 Despite this, the servlet exception error page still appears.
 If you clear the cache from the temp intenet files->delete files IE option, the
 correct errror page will be shown so it appears that the browser cache is being
 used after all.
 everytime I delete the temp intenet files I get the correct error page on the
 first request after but then not after that.
 I have implemented the service method for this test to throw the exceptions -
 does this make a differecne?
 As a test, I have moved the imlpementation to the doGet method instead bu I now
 get a strange eror from weblogic comlpaining about an arrayOutOfBoundsException
 because eror codes in the web.xml are not supported! - see error above.
 Any help is appreciated


Have you tried setting pragama no cache?
 <META HTTP-EQUIV="Pragma" CONTENT="no-cache">
 cheersmbg"Aaton" <[email protected]> wrote in message
 news:[email protected]...
 >
 > Having a few problems with error pages and web.xml with browsers caching
 the error
 > pages and strange errors coming out of
 weblogic.servlet.intenal.WebAppServletContext
 >
 > I'm trying to set a web app up so that all http errors and all exceptions
 are
 > routed thruogh predefined resources. For now, I'm simply send 400 errors
 to 400.html
 > and the ServletException, IOException and RuntimeException to respective
 html
 > pages.
 >
 > What I'm finding is that the error codes work fine but the exceptions are
 only
 > be routed to the correct error page for the first call to the servlet
 after server
 > restart.
 >
 > So for example, I have my servlet throwing a ServletException as a test
 case.
 > The weblogic server log shows that ServletException is thrown, and the
 correct
 > error page for ServletExceptions is shown.
 >
 > If I change the Servlet code to throw IOException in place of
 SevletException,
 > the weblogic.log shows that IOExceptyion is being thrown (so the servlet
 has deployed
 > successfully), however the Servletxception error page is shown on the
 browser.
 >
 > I'm using IE6 and I've changed the setting such that a new page is
 requested every
 > time using the tools-internet options-temp internet files-settings option
 to "check
 > for new versions of stored pages: Every visit to the page".
 >
 > Despite this, the servlet exception error page still appears.
 >
 > If you clear the cache from the temp intenet files->delete files IE
 option, the
 > correct errror page will be shown so it appears that the browser cache is
 being
 > used after all.
 >
 > everytime I delete the temp intenet files I get the correct error page on
 the
 > first request after but then not after that.
 >
 > I have implemented the service method for this test to throw the
 exceptions -
 > does this make a differecne?
 >
 > As a test, I have moved the imlpementation to the doGet method instead bu
 I now
 > get a strange eror from weblogic comlpaining about an
 arrayOutOfBoundsException
 > because eror codes in the web.xml are not supported! - see error above.
 >
 > Any help is appreciated

How to Config Special Error Page for TIME OUT ONLY

We can config our own error page for webdynpro applications by using
transaction code SICF. thus the customizing error page will show when
program meet some errors. these errors type include ABAP runtime
dump/page time out etc.
Here is my question, is there any configuration or enhancement can
effect on ONLY ONE error type.which means the customizing error page
shows only time out error occurred.for other errors show the standard
error page.
Thanks a lot for your help.

I need to setup a situation, that is display a custom error page which say "under maintenance" if no back-end WebLogic Server instance reached.In the Apache HTTP Server v2.2 you can use the ErrorDocument directive: http://httpd.apache.org/docs/2.0/mod/core.html#errordocument
For example in httpd.conf,
ErrorDocument 503 /Test.html
Test.html is placed in the DocumentRoot (http://httpd.apache.org/docs/2.0/mod/core.html#documentroot)
Regards
Fabian

ClientAbortException problem on error page

Hi
I am trying to solve the mistery that has been bugging me for a while now.
We have the same J2EE app deployed on 4 servers. The application is for content management.
One server is for development, one for QA, and other 2 for production. All servers have same hardware and same software installed. All servers rund the same J2EE SDK with Sun's App Server 8.1PE...
Now, the mistery....I only get the follwoing exception on the 2 production serversThe error page works fine on other servers and it is the same JSP page on all servers....I cannot figure out why I am getting this error and what is the error supposed to mean..
[#|2004-09-02T08:23:56.703-0400|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.container.web|_Th
readID=11;|org.apache.catalina.core.StandardHostValve@ce41cc: Exception Processing ErrorPage[errorCode=404, location=/error404.jsp]
ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
 at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:421)
 at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:444)
 at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:363)
 at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:345)
 at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java:559)
 at org.apache.coyote.tomcat5.CoyoteResponseFacade$1.run(CoyoteResponseFacade.java:259)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFacade.java:254)
 at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:362)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:210)
 at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:180)
 at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
 at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:582)
 at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
 at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
 at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
 at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
 at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
 at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
 at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:161)
 at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
 at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:16
6)
 at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:979)
 at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:211)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:692)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11P
rotocol.java:647)
 at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:691)
 at java.lang.Thread.run(Thread.java:534)
|#]

Hi. I am also same kind of problem. I ahve a simple JSP in my Struts 2 Application. Server used is weblogic. As soon as i click on the Calender Image. The Socket write erro is thrown. I a m not able to under stand as to why socket write error is happening, as inly a simple javascript function call happens on click of that image.
JSP Cal code:
value="<s:date name='remitFileSetup.effcvStartDt' format='MM/dd/yyyy'/>" size='10' maxlength='10'/><a id="Date1" href="#"><img onclick="javascript:callSelf('Date1','startdate','true','divMesReg1')" valign="bottom" src="<s:url value="/images/cal.gif"/>"
method implementation:
function call(cButton, cOutput, cSingle,divId) {
var MA = [];
 //alert("HI 1");
 //to convert cSingle into boolean
 if(cSingle=='false')
 cSingle=false;
else{
 cSingle=true;
function closed(cal) {
// here we'll write the output; this is only for example. You
// will normally fill an input field or something with the dates.
var el = document.getElementById(cOutput);
// reset initial content.
//el.innerHTML = "";
 if(cSingle==true) {
 el.value="";
// Reset the "MA", in case one triggers the calendar again.
// CAREFUL! You don't want to do "MA = [];". We need to modify
// the value of the current array, instead of creating a new one.
// Calendar.setup is called only once! :-) So be careful.
MA.length = 0;
// walk the calendar's multiple dates selection hash
for (var i in cal.multiple) {
var d = cal.multiple;
//alert("HI 2");
// sometimes the date is not actually selected, that's why we need to check.
if (d) {
//this is to check that the newly selected date is not a repetition of of the date already
// selected in the textbox
var tempOlddate=trim(el.value);
var flagTest="true";
if(tempOlddate.indexOf(d.print("%m/%d/%Y"))==-1)
var tmpoldDt=el.value;
 // OK, selected. Fill an input field. Or something. Just for example,
// we will display all selected dates in the element having the id "output".
var x=el.value;
var y= x.substring(x.length-2,x.length);
//alert(y);
//alert("n"+y.indexOf("\n"));
//alert("br"+y.indexOf(" "));
if(trim(y)=="" )
 el.value +=d.print("%m/%d/%Y") + " ";
else if(y.indexOf("\n")!= -1 )
 el.value +=d.print("%m/%d/%Y") + " ";
 else if(y.indexOf("/>")!=-1)
 el.value +=d.print("%m/%d/%Y") + " ";
 else{
 el.value +=" "+ d.print("%m/%d/%Y") + " ";
// and push it in the "MA", in case one triggers the calendar again.
MA[MA.length] = d;
 var vararray= new Array();
var temp= el.value;
 vararray = temp.split(" ");
 el.value="";
 for(i=0; i<vararray.length-1; i++) {
el.value+=vararray[i];
if(i < vararray.length) {
 el.value+="\n";
 if(cSingle==true) {
 if(vararray.length>2){
 //alert('User cant select more than one date.');
 document.getElementById(divId).style.display="inline";
 el.value="";
 else {
 document.getElementById(divId).style.display="none";
cal.hide();
return true;
 //alert("HI 4");
Calendar.setup({
align : "BR",
showOthers : true,
multiple : MA, // pass the initial or computed array of multiple dates to be initially selected
onClose : closed,
button : cButton,
singleMulti : cSingle
 //alert("HI 3");
ERROR:
org.apache.struts2.views.jsp.ComponentTagSupport.doStartTag(ComponentTagSupport.java:54)
 at jsp_servlet.__404._jsp__tag4(__404.java:270)
 at jsp_servlet.__404._jspService(__404.java:135)
 at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
 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:283)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
 at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:530)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
 at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:710)
 at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:559)
 at weblogic.servlet.FileServlet.findSource(FileServlet.java:265)
 at weblogic.servlet.FileServlet.doGetHeadPost(FileServlet.java:188)
 at weblogic.servlet.FileServlet.service(FileServlet.java:170)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
 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:283)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
 at org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:413)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
 at org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:111)
 at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
 at org.apache.struts2.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:99)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
 at javawebparts.filter.AppAvailabilityFilter.doFilter(AppAvailabilityFilter.java:485)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
 at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3242)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Substituting default error pages.

Hi Starfish:
I have a problem with error pages.
I'm using weblgoic7 sp1 now.
I write code in web.xml in order
to catch http error:
<error-page>
<error-code>404</error-code>
<location>/error.jsp<location>
</error-page>
I put error.jsp in my war file.
First time when 404 happended, it
can show my own error.jsp. But since
second time, error.jsp doesn't work.
it will display the weblogic's default
error page. It can't display error.jsp
until I restart my weblogic server.
Did you have the same problem?
sherry

[att1.html]

Use of error page resulting in could not deserialize session data exception

 We have recently converted classes that store objects in the HTTP Session to implement
 serializable.
 Our application uses an error page set up in our web.xml for 500 errors.
 It also uses filters.
 When our application throws an exception and allows the server to handle it
 via the error page setup, we end up with the exception we threw, plus a number
 of
 "Could not deserialize session data" exceptions in the stack trace.
 In general, the exceptions can be traced to lines in code that attempt to reference
 one of our "serializable" session objects to get user info for logging purposes.
 Problem is, other applications that do not use error pages to handle exceptions
 do not throw these types of exceptions in the wl-domain.log and they use the same
 classes.
 Does anyone know why this happens when using error pages and what we need to do
 to correct it?
 We are using Weblogic 8.1sp2.
 Thanks!!
 Example of the stack trace messages:
 ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
 <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
 <Could not deserialize session data.
 java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
 at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
 at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
 at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
 at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
 at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
 at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
 at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >
 ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
 <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
 <Could not deserialize session data.
 java.io.NotSerializableException: java.util.Vector$1
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
 at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
 at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
 at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
 at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
 at doh.stuff.OurHTML.<init>(OurHTML.java:57)
 at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
 at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
 at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
 at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >


 We have recently converted classes that store objects in the HTTP Session to implement
 serializable.
 Our application uses an error page set up in our web.xml for 500 errors.
 It also uses filters.
 When our application throws an exception and allows the server to handle it
 via the error page setup, we end up with the exception we threw, plus a number
 of
 "Could not deserialize session data" exceptions in the stack trace.
 In general, the exceptions can be traced to lines in code that attempt to reference
 one of our "serializable" session objects to get user info for logging purposes.
 Problem is, other applications that do not use error pages to handle exceptions
 do not throw these types of exceptions in the wl-domain.log and they use the same
 classes.
 Does anyone know why this happens when using error pages and what we need to do
 to correct it?
 We are using Weblogic 8.1sp2.
 Thanks!!
 Example of the stack trace messages:
 ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
 <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
 <Could not deserialize session data.
 java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
 at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
 at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
 at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
 at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
 at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
 at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
 at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >
 ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
 <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
 <Could not deserialize session data.
 java.io.NotSerializableException: java.util.Vector$1
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
 at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
 at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
 at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
 at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
 at doh.stuff.OurHTML.<init>(OurHTML.java:57)
 at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
 at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
 at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
 at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >

Global error page for portal project

Hi
This is regarding weblogic 8.1.
We have a portal project which contains several portlets. For handling exceptions
in a page flow we have a global error page at the project root level and each
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed in the portlet
context. How can we make this error page to take up the whole screen and display
it outside of the portlet context so that all other links within the portal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
Sameer

Sameer,
Please post this question to the weblogic.developer.interest.portal
newsgroup.
Thanks
Raj Alagumalai
WebLogic Workshop Support
"Sameer Dalal" <[email protected]> wrote in message
news:3f4bd37f$[email protected]..
>
Hi
This is regarding weblogic 8.1.
We have a portal project which contains several portlets. For handlingexceptions
in a page flow we have a global error page at the project root level andeach
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed inthe portlet
context. How can we make this error page to take up the whole screen anddisplay
it outside of the portlet context so that all other links within theportal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
Sameer

Global Error page in portal

Hi
This is regarding weblogic portal 8.1.
We have a portal project which contains several portlets. For handling exceptions
in a page flow we have a global error page at the project root level and each
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed in the portlet
context. How can we make this error page to take up the whole screen and display
it outside of the portlet context so that all other links within the portal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
Sameer

Also, you could do this:
* @jpf:catch type="Exception" method="handleAllExceptions"
* @jpf:exception-handler
* @jpf:forward name="errorPage" path="/error.jsp" redirect="true"
protected Forward handleAllExceptions( Exception e, String actionName,
String message, FormData form )
return new Forward( "errorPage" );
In this case, handleAllExceptions() will redirect to the error page, which
will bring you out of the portal.
Rich
"Subbu Allamaraju" <subbuATbeaDOTcom> wrote in message
news:3f4cdefa$[email protected]..
Sameer,
The portal rendering framework renders the error page inside portlet
windows to address the most common scenario, where failure in a given
portlet won't stop users from interacting with other portlets.
Here are the options you've to address your use case:
- Handle the exception in the pageflow itself, and do a sendRedirect()
to the error page. This would bypass rendering of other portlets, and
user will be redirected to the error page.
- If the source of the exception is the JSP, you'll have to add some
javascript in the error page to do a redirect or, better yet, replace
the markup.
Subbu
Sameer Dalal wrote:
Hi
This is regarding weblogic portal 8.1.
We have a portal project which contains several portlets. For handling
exceptions
in a page flow we have a global error page at the project root level andeach
portlet redirects to this error page /error.jsp in case of any errors.
When the user is redirected to this error page the page is displayed inthe portlet
context. How can we make this error page to take up the whole screen anddisplay
it outside of the portlet context so that all other links within theportal (books
and pages) are not displayed to the user.
In all cases, the redirection to the error page occurs from a page flow.
Thanks in advance,
Sameer

How to display ECID in an error page

Hello everyone,
I have a very simple servlet-based application that I am deploying to Oracle Fusion Middleware (version 11.1.1.4). I also have an error page directive in my web.xml that displays a user-friendly page (i.e. "call the helpdesk") when my servlet sends HTTP 400/500 responses (which I do intentionally on certain error conditions).
In order to help in diagnosis of the problems, I'd like to include something in the error page that the user could quote to the help desk to assist them in finding the specific log messages (which my servlet has duly logged) related to the request. The obvious thing to use would be the ECID of the request. However, I cannot, after looking through lots of documentation, figure out how to display the ECID in the error page. As my request is going through WebCache, I've tried turning on the diagnostics from the webcache (which the docs seem to say will cause the information to be included in either the response headers or the HTML body), but this doesn't seem to work.
I appreciate any pointers, especially pointers to the docs!
Thanks,
John

Looks like another option might be to make an API call like this in your JSP or Java code:
<%= weblogic.diagnostics.context.DiagnosticContextHelper.getContextId() %>In order for this to work, I had to have a WLDF System Module targeted at the Server AND the Instrumentation checkbox had to be enabled.
It returns null if you don't have WLDF configured or instrumentation enabled and gives a value like this if you have it enabled:
7673164398dde610:249290ac:13091aea873:-7fff-000000000000000dFound it here:
http://download.oracle.com/docs/cd/E21764_01/web.1111/e13714/config_prog_intro.htm#i1072698

Error pages do not come up.

 Hi all,
 I am using weblogic server 5.1 (Service Pack 5)
 I have the following line in weblogic.properties
 weblogic.httpd.errorPage.500=/errorPage.html
 When the servlet returns an error using response.sendError(500) the error page does not come up. Weblogic does not complain about anything but shows a blank page.
 What am I missing?
 Thanks
 Radha


 Yes, My html pages are located in the Document root directory.
 Radha
 Kumar Allamraju <[email protected]> wrote:
 >I just tried with SP5 and everything works fine as expected. i.e. WLS throws errorPage.
 >Is your error page located in WLS's document root?
 >
 >--
 >Kumar
 >
 >Radha Srinivasan wrote:
 >
 >> Hi all,
 >> I am using weblogic server 5.1 (Service Pack 5)
 >> I have the following line in weblogic.properties
 >> weblogic.httpd.errorPage.500=/errorPage.html
 >> When the servlet returns an error using response.sendError(500) the error page does not come up. Weblogic does not complain about anything but shows a blank page.
 >> What am I missing?
 >> Thanks
 >> Radha
 >

Weblogic error Page

Similar Messages

Maybe you are looking for