ConfigurationException

Question

Hi,
I am getting the following error when I try to login into the portal. I
am able to see the first page on the portal. As I try to login, it throws
the following exception.
<Feb 21, 2002 5:17:36 PM IST> <Error> <Webflow> <Error while parsing uri
/powerp
athportal/application, path null, query string null - Webflow XML does not
exist
, is not loaded properly, or you do not have a configuration-error-page
defined.
Exception[com.bea.p13n.appflow.exception.ConfigurationException: The
configurati
on-error-page node was not found in the webflow xml file. for webapp [null],
nam
espace [portal]. While trying to display CONFIGURATION ERROR:
[Exception[com.bea
.p13n.appflow.exception.ConfigurationException: Bad Namespace - namespace
[porta
l] is not available for webflow execution. Make sure the [portal.wf] file is
dep
loyed in webapp [null].]],]
at
com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processConf
igurationError(WebflowExecutorImpl.java:772)
at
com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebf
lowRequest(WebflowExecutorImpl.java:474)
at
com.bea.portal.appflow.PortalAppflowHelper.invokeWebflow(PortalAppflo
wHelper.java:139)
at
com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(P
ortalWebflowServlet.java:124)
at
com.bea.p13n.appflow.webflow.servlets.internal.WebflowServlet.doPost(
WebflowServlet.java:213)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispat
cherImpl.java:215)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112
at jsp_servlet.__index._jspService(__index.java:116)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispat
cherImpl.java:215)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112
at jsp_servlet.__login._jspService(__login.java:227)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2459)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Answer 1

Hello Rahul,
Did you use the EBCC to sync the portal.wf XML file to the server and the
database? If that is not the problem then, if you are using Portal 4.0 sp1 with
Oracle, then maybe you have encountered a bug involving the writing of CLOBs.
It was fixed and support has a patch, patch_CR067935.zip, that addresses it.
Here is the README from the patch:
patch_CR067935
This patch addresses an issue for the UPDATE of CLOBs when
using Oracle.
Oracle has unusual behavior for the UPDATE of CLOBs.
If you use UPDATE to put a small CLOB into a field that contains
a larger CLOB, then the CLOB size remains unchanged. In other
words, the new small CLOB data overlaps the large CLOB data and
the end of the CLOB consists of the old data from the end of the
large CLOB.
This patch modifies the OracleJdbcHelperDelegate to trim a CLOB
after updating it. The OracleJDriverJdbcHelperDelegate and
OracleThinJdbcHelperDelegate, which extend this abstract base
class, were updated to use the new trimClob() method.
Installation and Setup Procedures:
It is important that all of these steps be followed for the
service pack to be applied correctly. Failure to follow these
steps may result in unexpected behavior.
Throughout this document, <wlportal-install> refers to the
directory where wlportal 4.0 sp1 is installed on the system.
1. To apply the Service Pack on UNIX, you must have READ, WRITE,
and EXECUTE permission in the <wlportal-install> directory (and
associated subdirectories).
2. Stop the server.
3. Extract the file patch_CR067935.zip in a temp directory or
save time by extracting it directly into the <portal-install>
directory.
4. If you extracted the .zip file into a temp directory then copy
patch_CR067935.jar into <wlportal-install>/lib/
5. The replaced classes are used in your system classpath. You can
see this if you note that they originally appeared in
<wlportal-install>/lib/p13n_system.jar. This jar file is placed
in the system class path in your set-environment script.
Therefore, you can use this patch by placing it first in your system
classpath. All applications deployed on your server will load the
new classes:
Modify your set-environment script to place
<wlportal-install>/lib/patch_CR067935.jar before p13n_system.jar in
your system classpath.
For example (for Win32)...
CHANGE
REM ----------- WebLogic CLASSPATH -----------
SET
CLASSPATH=%P13N_DIR%\lib\patches.jar;%JAVA_CLASSPATH%;%EXT_CLASSPATH%;%DB_CLASSPATH%
TO
REM ----------- WebLogic CLASSPATH -----------
SET
CLASSPATH=%P13N_DIR%\lib\patch_CR067935.jar;%P13N_DIR%\lib\patches.jar;%JAVA_CLASSPATH%;%EXT_CLASSPATH%;%DB_CLASSPATH%
6. Restart your server.
7. If you have CLOBs in your DATA_SYNC_ITEM table that were corrupted by
this
bug, then you will get several DocumentProcessingException stack traces
upon
server startup. To fix this:
* note the exceptions because you can fix them by replacing the
corrupted
rows from the DATA_SYNC_ITEM table using the data sync mechanism.
The DocumentProcessingException identifies the URI of the bad XML
file.
You and can replace it in the database like this:
* Touch the file in your application-sync directory for your project to
update
the timestamp.
* Perform a data sync for this file (or files), using the EBCC.
Rahul Kapoor wrote:
Hi,
I am getting the following error when I try to login into the portal. I
am able to see the first page on the portal. As I try to login, it throws
the following exception.
<Feb 21, 2002 5:17:36 PM IST> <Error> <Webflow> <Error while parsing uri
/powerp
athportal/application, path null, query string null - Webflow XML does not
exist
, is not loaded properly, or you do not have a configuration-error-page
defined.
Exception[com.bea.p13n.appflow.exception.ConfigurationException: The
configurati
on-error-page node was not found in the webflow xml file. for webapp [null],
nam
espace [portal]. While trying to display CONFIGURATION ERROR:
[Exception[com.bea
.p13n.appflow.exception.ConfigurationException: Bad Namespace - namespace
[porta
l] is not available for webflow execution. Make sure the [portal.wf] file is
dep
loyed in webapp [null].]],]
at
com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processConf
igurationError(WebflowExecutorImpl.java:772)
at
com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebf
lowRequest(WebflowExecutorImpl.java:474)
at
com.bea.portal.appflow.PortalAppflowHelper.invokeWebflow(PortalAppflo
wHelper.java:139)
at
com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(P
ortalWebflowServlet.java:124)
at
com.bea.p13n.appflow.webflow.servlets.internal.WebflowServlet.doPost(
WebflowServlet.java:213)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispat
cherImpl.java:215)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112
at jsp_servlet.__index._jspService(__index.java:116)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispat
cherImpl.java:215)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112
at jsp_servlet.__login._jspService(__login.java:227)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2459)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)--
Ture Hoefner
BEA Systems, Inc.
2590 Pearl St.
Suite 110
Boulder, CO 80302
www.bea.com