Session Handling in Weblogic Portal 9.2

Hi All,
I have posted a strange problem that i have been facing. It was that my previously visited page was getting rendered when i used to perform some action on my current page.
I attributed this to some caching that might be happening. I want to know if every page that we visit in an application gets cached ? May be due to caching, the earlier page is getting displayed.
Are these portlets or pages getting cached in the session? Any workaround by which i can clear the cache of all the previously visited pages?

By default, the session timeout seconds is 3600, ie, an hour.
          In case you have specified weblogic-application.xml or weblogic.xml, you can add a descriptor "session-descriptor" to set session-timeout seconds.
          Here is a sample to set the timeout to 2 hours.
          file: weblogic.xml
          <?xml version="1.0" encoding="ISO-8859-1"?>
          <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90">
          <session-descriptor>
          <timeout-secs>7200</timeout-secs>
          </session-descriptor>
          </weblogic-web-app>
          For more detail about session descriptor, please refer to
          http://e-docs.bea.com/wls/docs92/webapp/weblogic_xml.html#wp1071982
          Thanks,
          -Fred.

Similar Messages

Different session handling of weblogic on SP2 and SP3

          I have set up 2 weblogic servers which are using the same cookie name, and having
          the same webapp name, on the same physical machine thus
          http://127.0.0.1:7220/test (Server A).
          http://127.0.0.1:9999/test (Server B).
          Using Weblogic 6.1 Service Pack 2
          1. Access Server A
          - Server A generate a new Session ID "123456...."
          2. Redirect Link from Server A to Server B
          3. Access Server B
          - Server B generate a new Session ID "987654..."
          4. Redirect Link from Server B to Server A
          5. Access Server A
          - Reused the same session ID "123456...."
          Using Weblogic 6.1 Service Pack 3
          1. Access Server A
          - Server A generate a new Session ID "123456...."
          2. Redirect Link from Server A to Server B
          3. Access Server B
          - Server B generate a new Session ID "987654..."
          4. Redirect Link from Server B to Server A
          5. Access Server A
          - Regenerate a new session ID "ABCDEFGHI...."
          Why weblogic server handle session differently in SP2 and SP3??


I think this was a bug in SP3. You could raise a support ([email protected]) call to
          confirm.
          Rick Bongpipat wrote:
          > "Rick Bongpipat" <[email protected]> wrote:
          > >
          > >I have set up 2 weblogic servers which are using the same cookie name,
          > >and having
          > >the same webapp name, on the same physical machine thus
          > >
          > >http://127.0.0.1:7220/test (Server A).
          > >http://127.0.0.1:9999/test (Server B).
          > >
          > >Using Weblogic 6.1 Service Pack 2
          > >
          > >1. Access Server A
          > >- Server A generate a new Session ID "123456...."
          > >2. Redirect Link from Server A to Server B
          > >3. Access Server B
          > >- Server B generate a new Session ID "987654..."
          > >4. Redirect Link from Server B to Server A
          > >5. Access Server A
          > >- Reused the same session ID "123456...."
          > >
          > >Using Weblogic 6.1 Service Pack 3
          > >
          > >1. Access Server A
          > >- Server A generate a new Session ID "123456...."
          > >2. Redirect Link from Server A to Server B
          > >3. Access Server B
          > >- Server B generate a new Session ID "987654..."
          > >4. Redirect Link from Server B to Server A
          > >5. Access Server A
          > >- Regenerate a new session ID "ABCDEFGHI...."
          > >
          > >Why weblogic server handle session differently in SP2 and SP3??
          >
          > In relation to previous question.
          >
          > I have 3 qns about session creation behaviour:
          >
          > 1. When a web container receives a session cookie (eg. JSESSIONID) whose session
          > id does not exists in this
          > server, should the server create a new session ?
          >
          > 2. If a session is to be created because there is a session cookie, then should
          > the new session id
          > be the one sent or should it be a newly generated session id ?
          >
          > 3. If a new session id is to be generated, then should the new session id be used
          > to overwrite that in the cookie
          > and send it back to the client ?
          Rajesh Mirchandani
          Developer Relations Engineer
          BEA Support

New iview Window Session Handling in Enterprise Portal

Hi All,
We are using Webdynpro iviews and SAP Transaction iviews at ITC for portal implementation. We are opening the iviews in New window using "Launch in Separate Window". We have the following issues
- When I log off from Portal , the webdynpro iview session is killed automatically - No issues.
- When I close the portal window WITH OUT LOGOFF, then webdynpro iview session is still existing
- In case of SAP Transaction iview irrespective whether the Portal is logged off or closed , transaction iview session exists.
- When I log off from the Transaction iview , I still see the same window in opened status ,but blank.
Would appreciate any suggestions on these at the earliest.
Thanks in advance.
Regards,
Sreeram

Hi Sunil,
thanks for the new link, but this msg is posted by my team mate here ). Any ways I dont see any replies having a solution for this as of now..Let me wait from some more replies. Thanks any ways.
Regards,
Sreeram

Error handling in weblogic portal 7.0

Could any one suggest how to handle the errors in portal. Currently I am forwarding
all the errors in webflow to /framework/error/error.jsp using portal proxy node.
But what happen if my portal page have 3 portlets and all the portlets got some
excetion then all the portlets load the error.jsp page. I just want to display
single friendly message to the user.
Is there any way to do this. Is there any way so that I define a error portal
page and forward to this page when there is exception.
Ajay

Thank you seenu
Now I have started working on project ...
it has too complicated directory structures and too much
technologies mixed up ...
I have to do an enhancement module ... in portal 7.0
is there any mailing lists for discussion of portals
so that i can subscribe to it and get help when necessary...

How to reset the JSF Portlet session state in weblogic portal 10.3

Hi All,
We are implementing our application with the jsf1.2 with 10.3.0 portal framework.
in a tab i placed my jsf portlet, it will navigate up to 4 pages. We do have some other tabs too in our application. So when i navigate to other tabs and when i comeback to the jsf portlet tab i am resetting the portlet state to first page by onDeactivation portal event.
But the problem when the user within the tab and navigate to pages if he clicks again the tab it is not redirecting to start page.
I know we do have refresh action in our pageflows .. but how to reset the jsf portlet to start page when it is not deactivating. Please do help me..
Thanks in advance...
Edited by: Siddu4u on Oct 10, 2011 8:33 PM

Hello,
This documentation should help you to use the import tool in the Portal Admin Console:
http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14245/deployment.htm#i1047336
Kevin

Unique session key weblogic portal 9.2

Hi,
Is there a way I can generate unique session key to ensure correct session is tracking between every desktop with different user.
Is this right way to handle session in weblogic portal 9.2?

Hi
what exactly do you want to do? A session does have an id which is guaranteed unique while the server is running (you dont need to do anything special for this). HttpSession.getId.
Note However normally this value gets stored as a cookie on the browser (with the default name of JSESSIONID) and you must ensure that different webapps on the same domain dont overwrite this value
regards
deepak

Coherence integration with oracle weblogic portal for Session management

Could you please let me know how to configure coherence integration with oracle weblogic portal for Session management. Its very urgent. please help.

Please take a look at the following web page -
http://coherence.oracle.com/display/COH35UG/Coherence*Web+Session+Management+Module
-Luk

Weblogic portal session data lost

Hi,
I have a peculiar scenario where the data set in the HttpSession gets lost intermittently. I could not really figure out a pattern where this occurs.It occurs any where in the application.
I have a session listener tied to the Session which does not get triggered when the session data is lost in this manner. This makes me to believe that the session itself is not getting killed. but only the data gets lost.
I am using Weblogic Portal Server 8.1 sp5 on UNIX server.
Any help is greatly appreciated.
Thanks
Raj

Well, we use the standard authentication:
[url http://edocs.bea.com/wlp/docs81/javadoc/com/bea/p13n/security/Authentication.html#login(java.lang.String,%20java.lang.String,%20javax.servlet.http.HttpServletRequest)]
Hope it will work in your case. Good luck.
Edited by pecanov at 07/05/2007 1:41 PM

Weblogic Portal session related issue

Technogies Used: Java,Spring webflow and Oracle Weblog portal 10.3.2
Problem description:
In our sprint portal application,the main page has 'SSN' and 'Access code' text box fields with search button,user gave value only for SSN box and it took him to access code page with appropriate error message in child window.
After that user closed the child window and gave valid values for both 'SSN' and Access code fields,but still the same error page is getting displayed instead of valid results page.
Please advice

Hi,
Proliferation refers to the process by which changes made to the Library instance of a portal asset are pushed into user-customized instances of that asset which means that when any changes are made to the portlet in source and if you want to propagate that change to the destination, that time if that portlet is used in a desktop where many users are provided an option to customize that desktop only that particular time at destination if you change the Portal Resources Proliferation of Updates Configuration setting to either Asynchronous or off propagation will be faster because that time propagation utility will not change for each user. If the value is synchronous it changes for each user and hence some delay that too it will happen during commit operation only but not during download operation.
So I feel, Proliferation may not be useful for your case.
We need to find why downloading source is taking 3 hrs and destination is taking 8 hrs.
Please let me know whether you are running downloadsource and downloaddestination.
I suggest run downloadSource in source machine itself and downloadDestination on the destination Machine itself so that you can reduce the network latency.
Thanks & Regards,
Murali.
===========

Error on running the .portal on the weblogic portal server 10.3.2 using jsf

Hi,
This are the below file that i have included in the project
login.jspx
<jsp:root version="1.2" xmlns:jsp="http://java.sun.com/JSP/Page"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:ice="http://www.icesoft.com/icefaces/component">
<jsp:directive.page contentType="text/html;charset=utf-8" />
<f:view>
<ice:outputDeclaration doctypeRoot="HTML"
doctypePublic="-//W3C//DTD HTML 4.01 Transitional//EN"
doctypeSystem="http://www.w3.org/TR/html4/loose.dtd" />
<html>
<head>
<title>ICEfaces,Login Portlet</title>
<link rel="stylesheet" type="text/css"
href="./xmlhttp/css/rime/rime.css" />
</head>
<body>
<ice:portlet>
<ice:outputText value="Welcome to ICEfaces." />
<ice:form>
<ice:outputText value="Username" />
<ice:inputText id="name_t" value="#{Login.userName}"></ice:inputText>
<ice:outputText value="Password"/>
<ice:inputText id="password_t" value="#{Login.password}"></ice:inputText>
<ice:commandButton action="#{Login.checkUserPass}" value="OK"></ice:commandButton>
</ice:form>
</ice:portlet>
</body>
</html>
</f:view>
</jsp:root>
faces-config.xml
<?xml version="1.0" encoding="UTF-8"?>
<faces-config
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"
version="1.2">
<application>
<view-handler>
com.icesoft.faces.facelets.D2DFaceletViewHandler
</view-handler>
<locale-config>
<supported-locale>de</supported-locale>
<supported-locale>en</supported-locale>
</locale-config>
</application>
<managed-bean>
<managed-bean-name>Login</managed-bean-name>
<managed-bean-class>com.pack.login.Login</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>userName</property-name>
<property-class>java.lang.String</property-class>
<value></value>
</managed-property>
<managed-property>
<property-name>password</property-name>
<property-class>java.lang.String</property-class>
<value></value>
</managed-property>
</managed-bean>
<navigation-rule>
<from-view-id>/login.jspx</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/success.iface</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>failure</from-outcome>
<to-view-id>/failure.iface</to-view-id>
</navigation-case>
</navigation-rule>
</faces-config>
portlet.xml
<?xml version="1.0" encoding="UTF-8"?>
<faces-config
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"
version="1.2">
<application>
<view-handler>
com.icesoft.faces.facelets.D2DFaceletViewHandler
</view-handler>
<locale-config>
<supported-locale>de</supported-locale>
<supported-locale>en</supported-locale>
</locale-config>
</application>
<managed-bean>
<managed-bean-name>Login</managed-bean-name>
<managed-bean-class>com.pack.login.Login</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>userName</property-name>
<property-class>java.lang.String</property-class>
<value></value>
</managed-property>
<managed-property>
<property-name>password</property-name>
<property-class>java.lang.String</property-class>
<value></value>
</managed-property>
</managed-bean>
<navigation-rule>
<from-view-id>/login.jspx</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/success.iface</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>failure</from-outcome>
<to-view-id>/failure.iface</to-view-id>
</navigation-case>
</navigation-rule>
</faces-config>
Login.java
package com.pack.login;
import javax.faces.application.FacesMessage;
import javax.faces.context.FacesContext;
public class Login {
public String getUserName() {
return userName;
public void setUserName(String userName) {
this.userName = userName;
public String getPassword() {
return password;
public void setPassword(String password) {
this.password = password;
private String userName;
private String password;
public String checkUserPass(){
FacesContext facesContext = FacesContext.getCurrentInstance();
if("icefaces".equals(getUserName()) && "icefaces".equals(getPassword())) {
return"success";
FacesMessage facesMessage = new FacesMessage(
"You have entered an invalid user name and/or password");
facesContext.addMessage("Login", facesMessage);
return "failure";
What are the classes or interfaces that we need to use to render the content and to the process the action in jsf-portlet + icefaces libraris + weblogic portal server 10.3.2
I have created the .portal file and i have included the instance of the .portlet file in the portal page. When i run .portal file on the server it will throw the below exception.
<Warning> <netuix> <BEA-423319> <A default JSP response character encoding was not found for webapp [Portal]. Defaulting to [UTF-8]. You can override this default response character encoding for all portals in netuix-config.xml or for each portal or desktop in each portal or desktop definition.>
12, 2010 9:57:05 AM com.sun.faces.lifecycle.Phase doPhase
SEVERE: JSF1054: (Phase ID: RENDER_RESPONSE 6, View ID: /login.jspx) Exception thrown during phase execution: javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl@18fddac]
<Error> <netuix> <BEA-423405> <An exception [java.lang.NullPointerException] was thrown while rendering the content at [login.jspx].
javax.faces.FacesException: java.lang.NullPointerException
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:128)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at com.bea.portlet.adapter.faces.FacesContentStubImpl.render(FacesContentStubImpl.java:354)
at com.bea.netuix.servlets.controls.content.FacesContent.beginRender(FacesContent.java:424)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at com.sun.faces.renderkit.RenderKitImpl.createResponseWriter(RenderKitImpl.java:188)
at com.icesoft.faces.renderkit.D2DRenderKit.createResponseWriter(D2DRenderKit.java:87)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:194)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
at org.apache.myfaces.portlet.faces.application.PortletViewHandlerImpl.renderView(PortletViewHandlerImpl.java:257)
Truncated. see log file for complete stacktrace
>
<Error> <netuix> <BEA-423137> <There was an error loading the requested URI /login.jspx.>
Login Error opening /login.jspx.
The source of this error is:
javax.faces.FacesException: java.lang.NullPointerException
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:128)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at com.bea.portlet.adapter.faces.FacesContentStubImpl.render(FacesContentStubImpl.java:354)
at com.bea.netuix.servlets.controls.content.FacesContent.beginRender(FacesContent.java:424)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:399)
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.run(Lifecycle.java:326)
at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:488)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:152)
at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
at jsp_servlet._framework._skeletons._bighorn.__flowlayout._jspService(__flowlayout.java:175)
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:292)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:148)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:399)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:168)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:465)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:291)
at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:231)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:216)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:275)
at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:719)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.bea.content.manager.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:178)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at com.sun.faces.renderkit.RenderKitImpl.createResponseWriter(RenderKitImpl.java:188)
at com.icesoft.faces.renderkit.D2DRenderKit.createResponseWriter(D2DRenderKit.java:87)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:194)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
at org.apache.myfaces.portlet.faces.application.PortletViewHandlerImpl.renderView(PortletViewHandlerImpl.java:257)
at com.bea.portlet.adapter.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:77)
at com.icesoft.faces.application.D2DViewHandler.renderView(D2DViewHandler.java:151)
at com.icesoft.faces.application.D2DViewHandler.renderView(D2DViewHandler.java:151)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:109)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
... 71 more
I have created the .portal file and i have included the instance of the .portlet file in the portal page. When i run .portal file on the server it will throw the below exception.
<Warning> <netuix> <BEA-423319> <A default JSP response character encoding was not found for webapp [Portal]. Defaulting to [UTF-8]. You can override this default response character encoding for all portals in netuix-config.xml or for each portal or desktop in each portal or desktop definition.>
12, 2010 9:57:05 AM com.sun.faces.lifecycle.Phase doPhase
SEVERE: JSF1054: (Phase ID: RENDER_RESPONSE 6, View ID: /login.jspx) Exception thrown during phase execution: javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl@18fddac]
<Error> <netuix> <BEA-423405> <An exception [java.lang.NullPointerException] was thrown while rendering the content at [login.jspx].
javax.faces.FacesException: java.lang.NullPointerException
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:128)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at com.bea.portlet.adapter.faces.FacesContentStubImpl.render(FacesContentStubImpl.java:354)
at com.bea.netuix.servlets.controls.content.FacesContent.beginRender(FacesContent.java:424)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at com.sun.faces.renderkit.RenderKitImpl.createResponseWriter(RenderKitImpl.java:188)
at com.icesoft.faces.renderkit.D2DRenderKit.createResponseWriter(D2DRenderKit.java:87)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:194)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
at org.apache.myfaces.portlet.faces.application.PortletViewHandlerImpl.renderView(PortletViewHandlerImpl.java:257)
Truncated. see log file for complete stacktrace
>
<Error> <netuix> <BEA-423137> <There was an error loading the requested URI /login.jspx.>
Login Error opening /login.jspx.
The source of this error is:
javax.faces.FacesException: java.lang.NullPointerException
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:128)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at com.bea.portlet.adapter.faces.FacesContentStubImpl.render(FacesContentStubImpl.java:354)
at com.bea.netuix.servlets.controls.content.FacesContent.beginRender(FacesContent.java:424)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:399)
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.run(Lifecycle.java:326)
at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:488)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:152)
at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
at jsp_servlet._framework._skeletons._bighorn.__flowlayout._jspService(__flowlayout.java:175)
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:292)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:148)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:399)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:168)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:465)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:291)
at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:231)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:216)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:275)
at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:719)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.bea.content.manager.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:178)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at com.sun.faces.renderkit.RenderKitImpl.createResponseWriter(RenderKitImpl.java:188)
at com.icesoft.faces.renderkit.D2DRenderKit.createResponseWriter(D2DRenderKit.java:87)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:194)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
at org.apache.myfaces.portlet.faces.application.PortletViewHandlerImpl.renderView(PortletViewHandlerImpl.java:257)
at com.bea.portlet.adapter.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:77)
at com.icesoft.faces.application.D2DViewHandler.renderView(D2DViewHandler.java:151)
at com.icesoft.faces.application.D2DViewHandler.renderView(D2DViewHandler.java:151)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:109)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
... 71 more
Thanks in advance.

First you install a JDK6 version after which you can install your WebLogic and Forms, Reports...
A step-by-step example is presented here: http://middlewaremagic.com/weblogic/?p=7265
Look in the 'Install WebLogic' section. Note that you probably do not have to create a separate user,
also you can use HotSpot instead of JRockit.

Query- IPC using JSF Portlets in WebLogic Portal

The question is how to pass data when doing InterPortlet Communication using Local JSF portlets in Weblogic Portal.
I will eloborate on the particular scenario we have below.
Two JSF portlets are build (both are not using Java Page Flows). The first porltet has a table of data. When the user clicks on one of the items in the table (which is coded using <h:commandLink/> option), the second portlet should show some details on the item clicked.
For example:
If there is a list of books in first portlet, when clicking on one of the book name, the details of book should come up in the second portlet.
To achieve this, faces event was enabled in first portlet with requestAttrPersistence option set to session.
For example :
<netuix:content>
<netuix:facesContent contentUri="/bookList.faces" requestAttrPersistence="session">
<netuix:facesEvents>
<netuix:facesEvent action="/bookDetails.faces" eventName="bookDetailEvent"/>
</netuix:facesEvents>
</netuix:facesContent>
</netuix:content>
The second portlet was configured to handle faces events, particularly the bookDetailEvent.
Example:
<netuix:handleFacesEvent eventLabel="handleFacesEvent1" eventName="bookDetailEvent" fromSelfInstanceOnly="false" onlyIfDisplayed="true" sourceDefinitionLabels="JSFPortlet_1" sourceDefinitionWildcard="this">
<netuix:invokeFacesAction action="/bookDetails.faces"/>
</netuix:handleFacesEvent>
Going by this method, how can we find the particular book whose detail has to be shown? As in JSF, we dont directly access the request attributes, what is the ideal way to pass data from one page to other?
Please help on this.

i am also having the same problem.I tried by passing _nfls=false but it didn't work.Can you suuggest where do i need to set this or any other parametrs such as this programmatically?

Clustering weblogic portal 10.3 with apache plugin

Hi,
we have configured a weblogic portal 10.3 cluster with two managed servers. We are using the apache 2.2 plugin module for dispatching.
It seems for us that the plugin is not working correctly. It dispatches all request only to one server (we have tested it from different client machines). When we kill one of the managed servers the plugin dispatches to the other server which is correct.
In our test case we have produced a lot of load with two jmeter instances from two machines. All requests are dispachted to one managed server. After the first server runs in an out of memory, the plugin dispachted to the second managed server until this runs also in an out of memory. Therefor we have no real load balancing.
Here is our httpd.conf configuration:
<VirtualHost 149.191.201.135:80>
ServerName localhost
# ServerAlias adportal adportal.eu.xxx.com
RewriteEngine on
RewriteRule ^/$ /adp_war/appmanager/ad01/ad01 [R]
LimitRequestBody 12582912
CustomLog "|d:/apache/bin/rotatelogs.exe d:/apache/logs/adportal_access.log 864000" common
<IfModule mod_weblogic.c>
WeblogicCluster sis26.eu.xxx.com:8031,sis27.eu.xxx.com:8031
MatchExpression *.jsp
MatchExpression *.do
MatchExpression *.portal
MatchExpression *.htm
MatchExpression *.html
MatchExpression *.jpg
MatchExpression *.gif
ConnectTimeoutSecs 300
ConnectRetrySecs 1
MaxPostSize 12582912
SecureProxy Off
Debug ON
WLLogFile d:/apache/debug/global_proxy.log
WLTempDir "d:/apache/debug\temp"
DebugConfigInfo On
</IfModule>
<Location ~ "/adp_war/(appmanager|portals|portlets|resources|showImage|ShowBinary|framework)">
SetHandler weblogic-handler
</Location>
</VirtualHost>
Has anyone an idea?
By the way we have also tested it with the apache 2.0 plugin which also isn't working.

Hi,
Were do we set the listen address.
Even we have the same problem. I have one physical that has the admin server and manager server and other server with just the manager server.
We have the apache proxy server infront of these clustered server. Our server goes down very frequently even without activity.
Some time we get the following error but some time there is no exception in the logs.
####<Nov 6, 2009 10:05:57 PM CST> <Error> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257566757265> <BEA-000337> <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "634" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@2c88d39[
POST /spmlws/OIMProvisioning HTTP/1.1
SOAPAction: http://xmlns.oracle.com/OIM/provisioning/processRequest
Content-Type: text/xml; charset="UTF-8"
User-Agent: OIM AD Pwd Sync/1.0
Content-Length: 1313
Connection: Keep-Alive
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-18 "[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
java.io.FileOutputStream.writeBytes(FileOutputStream.java:???)
java.io.FileOutputStream.write(FileOutputStream.java:260)
java.io.BufferedOutputStream.write(BufferedOutputStream.java:100)
^-- Holding lock: java.io.BufferedOutputStream@214ef14[thin lock]
java.io.PrintStream.write(PrintStream.java:428)
^-- Holding lock: java.io.PrintStream@214ed9e[thin lock]
sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:191)
sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:271)
sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276)
sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:120)
^-- Holding lock: java.io.OutputStreamWriter@19de784[thin lock]
java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:49)
org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:292)
org.apache.log4j.WriterAppender.append(WriterAppender.java:147)
org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:201)
^-- Holding lock: org.apache.log4j.ConsoleAppender@19de688[thin lock]
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:50)
org.apache.log4j.Category.callAppenders(Category.java:181)
^-- Holding lock: org.apache.log4j.spi.RootCategory@19de3c9[fat lock]
org.apache.log4j.Category.forcedLog(Category.java:372)
org.apache.log4j.Category.error(Category.java:300)
com.thortech.util.logging.Logger.error(Unknown Source)
com.oracle.xl.spmlws.framework.logger.OraLogger.log(Unknown Source)
com.oracle.xl.spmlws.ws.server.weblogic.OIMProvisioningImpl.processRequest(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:???)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:27)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:575)
weblogic.webservice.component.javaclass.JavaClassInvocationHandler.invoke(JavaClassInvocationHandler.java:127)
weblogic.webservice.core.handler.InvokeHandler.handleRequest(InvokeHandler.java:75)
weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:141)
weblogic.webservice.core.DefaultOperation.process(DefaultOperation.java:542)
weblogic.webservice.server.Dispatcher.process(Dispatcher.java:200)
weblogic.webservice.server.Dispatcher.doDispatch(Dispatcher.java:140)
weblogic.webservice.server.Dispatcher.dispatch(Dispatcher.java:53)
weblogic.webservice.server.WebServiceManager.dispatch(WebServiceManager.java:100)
weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(WebServiceServlet.java:299)
weblogic.webservice.server.servlet.ServletBase.doPost(ServletBase.java:417)
weblogic.webservice.server.servlet.WebServiceServlet.doPost(WebServiceServlet.java:286)
javax.servlet.http.HttpServlet.service(HttpServlet.java:700)
javax.servlet.http.HttpServlet.service(HttpServlet.java:815)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:224)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:198)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3468)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
weblogic.security.service.SecurityManager.runAs(Unknown Source)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2116)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2038)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1372)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
>
<[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
####<Nov 6, 2009 10:11:48 PM CST> <Info> <ServletContext-/xlWebApp> <abc.abc.com> <OIM_SERVER1> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1257567108507> <BEA-000000> <action: LogonAction: User 'XELSYSADM' logged on in session jJ2bK0zdx4LPTScXWRMG3jznSQgQsJKqC4YSpMlJ3Q4KCRrGYM9l!-1225252524!NONE!1257567101565>
####<Nov 6, 2009 10:11:01 PM CST> <Info> <ServletContext-/xlWebApp> <abc.abc.com> <OIM_SERVER1> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1257567061835> <BEA-000000> <action: LogonAction: User 'XELSYSADM' logged on in session T23kK0ncSs60YfLnZRhpdZDvmL8sq1QQlc7vMLQJSpVQFyvSMvD6!-1225252524!NONE!1257565852875>
####<Nov 6, 2009 10:11:14 PM CST> <Info> <ServletContext-/xlWebApp> <abc.abc.com> <OIM_SERVER1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1257567074087> <BEA-000000> <action: LogonAction: User 'XELSYSADM' logged on in session T23kK0ncSs60YfLnZRhpdZDvmL8sq1QQlc7vMLQJSpVQFyvSMvD6!-1225252524!NONE!1257565852875>
####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167000> <BEA-000339> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167003> <BEA-000339> <[STUCK] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167009> <BEA-000339> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167019> <BEA-000339> <[STUCK] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167022> <BEA-000339> <[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
####<Nov 6, 2009 10:12:47 PM CST> <Info> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257567167033> <BEA-000339> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)' has become "unstuck".>
####<Nov 6, 2009 10:12:47 PM CST> <Notice> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <Thread-1> <<WLS Kernel>> <> <> <1257567167043> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
####<Nov 6, 2009 10:12:47 PM CST> <Alert> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <Thread-1> <<WLS Kernel>> <> <> <1257567167048> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
####<Nov 6, 2009 10:12:47 PM CST> <Notice> <WebLogicServer> <abc.abc.com> <OIM_SERVER1> <Thread-1> <<WLS Kernel>> <> <> <1257567167058> <BEA-000365> <Server state changed to FORCE_SUSPENDING>

Remote start doesn't work in Managed Servers (Weblogic Portal 10.3)

Hi,
I've got problems with starting the managed server from the admin console.
The message in the managed server output log file is :
****CLIP****
<19.10.2008 14:05:33> <Info> <NodeManager> <Starting WebLogic server with command line: D:\beaportal103\jrockit_160_05\bin\java -Dweblogic.Name=server1 -Dbea.home=D:\beaportal103\ -Djava.security.policy=D:\beaportal103\wlserver_10.3\server\lib\weblogic.security -Dweblogic.management.server=http://xxx.xx.xxx.xxx:7001 -Djava.library.path=D:\BEAPOR~1\WLSERV~1.3\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\BEAPOR~1\WLSERV~1.3\server\native\win\32;D:\BEAPOR~1\WLSERV~1.3\server\bin;d:\BEAPOR~1\JROCKI~1\jre\bin;d:\BEAPOR~1\JROCKI~1\bin;D:\BEAPOR~1\WLSERV~1.3\server\native\win\32\oci920_8;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\ -Djava.class.path=d:\BEAPOR~1\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\patch_wlp1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\patch_cie670\profiles\default\sys_manifes_classpath\weblogic_patch.jar;d:\BEAPOR~1\JROCKI~1\lib\tools.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\weblogic.jar;d:\BEAPOR~1\modules\features\weblogic.server.modules_10.3.0.0.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\webservices.jar;d:\BEAPOR~1\modules\ORGAPA~1.5/lib/ant-all.jar;d:\BEAPOR~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;D:\BEAPOR~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\xqrl.jar -Dweblogic.system.BootIdentityFile=D:\beaportal103\user_projects\domains\test\servers\server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xms512m -Xmx512m weblogic.Server >
<19.10.2008 14:05:33> <Info> <NodeManager> <Working directory is "D:\beaportal103\user_projects\domains\test">
<19.10.2008 14:05:33> <Info> <NodeManager> <Server output log file is "D:\beaportal103\user_projects\domains\test\servers\server1\logs\server1.out">
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)
where options include:
-jrockit     to select the "jrockit" VM
-client     to select the "client" VM
-server     to select the "server" VM [synonym for the "jrockit" VM]
The default VM is jrockit.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
-splash:<imagepath>
show splash screen with specified image
<19.10.2008 14:05:33> <Debug> <NodeManager> <Waiting for the process to die: 3464>
<19.10.2008 14:05:33> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<19.10.2008 14:05:33> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
****CLIP****
The message in the nodemanager log file is :
****CLIP****
<19.10.2008 14:05:33> <Info> <test> <server1> <Boot identity properties saved to "D:\beaportal103\user_projects\domains\test\servers\server1\data\nodemanager\boot.properties">
<19.10.2008 14:05:33> <Info> <test> <server1> <Startup configuration properties saved to "D:\beaportal103\user_projects\domains\test\servers\server1\data\nodemanager\startup.properties">
<19.10.2008 14:05:33> <Info> <test> <server1> <Rotated server output log to "D:\beaportal103\user_projects\domains\test\servers\server1\logs\server1.out00004">
<19.10.2008 14:05:33> <Info> <test> <server1> <Server error log also redirected to server log>
<19.10.2008 14:05:33> <Info> <test> <server1> <Starting WebLogic server with command line: D:\beaportal103\jrockit_160_05\bin\java -Dweblogic.Name=server1 -Dbea.home=D:\beaportal103\ -Djava.security.policy=D:\beaportal103\wlserver_10.3\server\lib\weblogic.security -Dweblogic.management.server=http://xxx.xx.xxx.xxx:7001 -Djava.library.path=D:\BEAPOR~1\WLSERV~1.3\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\BEAPOR~1\WLSERV~1.3\server\native\win\32;D:\BEAPOR~1\WLSERV~1.3\server\bin;d:\BEAPOR~1\JROCKI~1\jre\bin;d:\BEAPOR~1\JROCKI~1\bin;D:\BEAPOR~1\WLSERV~1.3\server\native\win\32\oci920_8;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\ -Djava.class.path=d:\BEAPOR~1\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\patch_wlp1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\patch_cie670\profiles\default\sys_manifes_classpath\weblogic_patch.jar;d:\BEAPOR~1\JROCKI~1\lib\tools.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\weblogic.jar;d:\BEAPOR~1\modules\features\weblogic.server.modules_10.3.0.0.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\webservices.jar;d:\BEAPOR~1\modules\ORGAPA~1.5/lib/ant-all.jar;d:\BEAPOR~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;D:\BEAPOR~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\xqrl.jar -Dweblogic.system.BootIdentityFile=D:\beaportal103\user_projects\domains\test\servers\server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xms512m -Xmx512m weblogic.Server >
<19.10.2008 14:05:33> <Info> <test> <server1> <Working directory is "D:\beaportal103\user_projects\domains\test">
<19.10.2008 14:05:33> <Info> <test> <server1> <Server output log file is "D:\beaportal103\user_projects\domains\test\servers\server1\logs\server1.out">
<19.10.2008 14:05:33> <Info> <test> <server1> <Server failed during startup so will not be restarted>
<19.10.2008 14:05:33> <Warning> <Exception while starting server 'server1': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
     at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
     at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run(Thread.java:619)
****CLIP****
I just read this thread: Re: Problem starting maneged server FAILED_NOT_RESTARTABLE , but I didn't find any solution to my problem. I really hope that someone can help me, because right now I'm really desperate and hopeless.
This is my first Oracle Weblogic Portal/Server 10.3 installation.
I haven't seen this kinds of problems with Bea Weblogic Portal 8.1.6 and my remotestart configurations are very similar between the 8.1 and 10.3 installations.
br
Stefan from Finland

What you mean about that? Do you mean these rows:
****CLIP****
C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\
****CLIP****
If i start managed server with the script there is same spaces and server starts without any problems.
****CLIP****
D:\beaportal103\user_projects\domains\test\bin>startManagedWebLogic.cmd server1 >start.log
****CLIP****
The "message" in the start.log file is:
****CLIP****
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Development
CLASSPATH=;d:\BEAPOR~1\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\patch_wlp1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\patch_cie670\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\BEAPOR~1\JROCKI~1\lib\tools.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\weblogic.jar;d:\BEAPOR~1\modules\features\weblogic.server.modules_10.3.0.0.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\webservices.jar;d:\BEAPOR~1\modules\ORGAPA~1.5/lib/ant-all.jar;d:\BEAPOR~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;D:\BEAPOR~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;D:\BEAPOR~1\WLSERV~1.3\server\lib\xqrl.jar;;
PATH=d:\BEAPOR~1\patch_wlw1030\profiles\default\native;d:\BEAPOR~1\patch_wls1030\profiles\default\native;d:\BEAPOR~1\patch_wlp1030\profiles\default\native;d:\BEAPOR~1\patch_cie670\profiles\default\native;D:\BEAPOR~1\WLSERV~1.3\server\native\win\32;D:\BEAPOR~1\WLSERV~1.3\server\bin;d:\BEAPOR~1\modules\ORGAPA~1.5\bin;d:\BEAPOR~1\JROCKI~1\jre\bin;d:\BEAPOR~1\JROCKI~1\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;C:\Program Files\System Center Operations Manager 2007\;D:\BEAPOR~1\WLSERV~1.3\server\native\win\32\oci920_8
* 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 *
starting weblogic with Java version:
Starting WLS with line:
d:\BEAPOR~1\JROCKI~1\bin\java -jrockit -Xms256m -Xmx512m -Dweblogic.security.SSL.trustedCAKeyStore="D:\beaportal103\wlserver_10.3\server\lib\cacerts" -Xverify:none -da -Dplatform.home=D:\BEAPOR~1\WLSERV~1.3 -Dwls.home=D:\BEAPOR~1\WLSERV~1.3\server -Dweblogic.home=D:\BEAPOR~1\WLSERV~1.3\server -Dweblogic.management.discover=false -Dweblogic.management.server=http://XXX.XX.XXX.XXX:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=d:\BEAPOR~1\patch_wlw1030\profiles\default\sysext_manifest_classpath;d:\BEAPOR~1\patch_wls1030\profiles\default\sysext_manifest_classpath;d:\BEAPOR~1\patch_wlp1030\profiles\default\sysext_manifest_classpath;d:\BEAPOR~1\patch_cie670\profiles\default\sysext_manifest_classpath -Dweblogic.Name=server1 -Djava.security.policy=D:\BEAPOR~1\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
<20.10.2008 8.29.17 EEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2105-windows-ia32 from BEA Systems, Inc.>
<20.10.2008 8.29.18 EEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR376251 Wed Aug 06 09:19:34 PDT 2008
WebLogic Server Temporary Patch for CR371247 Sat Aug 09 20:10:38 PDT 2008
WebLogic Server Temporary Patch for CR377673 Tue Aug 12 20:39:50 EDT 2008
WebLogic Server Temporary Patch for CR377673 Tue Aug 12 20:39:50 EDT 2008
WebLogic Server Temporary Patch for CR376759 Thu Aug 14 14:53:02 PDT 2008
WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
<20.10.2008 8.29.19 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<20.10.2008 8.29.19 EEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<20.10.2008 8.29.20 EEST> <Notice> <Log Management> <BEA-170019> <The server log file D:\beaportal103\user_projects\domains\test\servers\server1\logs\server1.log is opened. All server side log events will be written to this file.>
<20.10.2008 8.29.22 EEST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<20.10.2008 8.29.24 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<20.10.2008 8.29.24 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<20.10.2008 8.29.24 EEST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<20.10.2008 8.29.25 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<20.10.2008 8.29.25 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<20.10.2008 8.29.25 EEST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on XXX.XX.XXX.XXX:7603 for protocols iiop, t3, ldap, snmp, http.>
<20.10.2008 8.29.25 EEST> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "server1" for domain "test" running in Development Mode>
<20.10.2008 8.29.26 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<20.10.2008 8.29.26 EEST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
****CLIP****
br
Stefan

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

Error while navigating across the pages in Weblogic portal 10.3

I'm using the content managemnt in Weblogic Portal 10.3 to display the tabs in the portal application. I have multiple pages in a book and am trying to display these pages as tabs in the application instead as a different level of menu.
I have achieved in displaying the tabs using the content management. I'm using a separate portlet for displaying the tabs alone. But while navigating across the tabs, I'm getting the following error in the console.
Can someone please help me in eliminating this.
<Error> <netuix> <BEA-423329> <More than 1,000 events were processed in the request -- not handling any more events for this request.>

See the release note for issue 13371575 at
http://docs.oracle.com/cd/E26806_01/wlp.1034/e14247/relnotes.htm#i1131976
Brad

Session Handling in Weblogic Portal 9.2

Similar Messages

Maybe you are looking for