Hi Glenn,

I did a search on the forums for "java.lang.IllegalStateException", and it seems like this was reported for several users using Java 1.5 or non-Sun JDKs. Can you post the output of running "java -version" on a command line here?

I'll need to research more as to why the IllegalStateException "Cannot forward after response has been committed" message is generated. If the application is doing something non-standard that causes compatibility issues then this should be made into a bug report.

The index.jsp page acts as a controller for determining the next action when a user first navigates to the page. Since you have just deployed the application it should detect that and forward the request to be handled by the Setup action.

I was just looking at the log you provided, and it reports that the Exception was thrown on line 33. But this line never should have been reached for new installations, it checks a few lines earlier to see if the prefs are configured and should forward the request to run set up without executing any more of the jsp.

The behavior of forwarding may be dependent on the version of Java/Tomcat, but it seems like this could be avoided completely by using "else if" instead of just "if" for deciding where to forward the request.

If you can provide the version of Java I can test to see if modifying index.jsp's if statements fixes the issue.

The java version is 1.5.0_15 and Tomcat is 5.5.26

Glenn Murray wrote:
The java version is 1.5.0_15 and Tomcat is 5.5.26

I have two installations, first one is gone pretty well
on tomcat 5.5.25 and java 1.6+
, but second one on win2003 server and tomcat 5.5.12 and java 1.5.0_15 gives me the same problem.

So Ive tried to deploy war on BEA WL 8.1 with java 1.5.0 and this is what i`ve see at bea logs.

just small ugly cut:

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Throwable exception trying to forward to JSP. MESSAGE: Failed to compile JSP /pr
ojects_resources_projects_users.jsp
projects_resources_projects_users.jsp:177:31: This attribute is not recognized.
<dhv:evaluate if="<%= !"resourceUnavailable".equals(highlightClass) %>">

^-----------------^
projects_resources_projects_users.jsp:177:51: This attribute is not recognized.
<dhv:evaluate if="<%= !"resourceUnavailable".equals(highlightClass) %>">

^-----^
projects_resources_projects_users.jsp:177:59: This attribute is not recognized.
<dhv:evaluate if="<%= !"resourceUnavailable".equals(highlightClass) %>">

^------------^

javax.servlet.ServletException: Failed to compile JSP /projects_resources_projec
ts_users.jsp

....

so if I rewrite part of messed code like :

<dhv:evaluate if="<%= !"resourceUnavailable".equals(highlightClass) %>">

to
<dhv:evaluate if='<%= !"resourceUnavailable".equals(highlightClass) %>'>

OR rewrite with unescape doublequotes like:
<dhv:evaluate if="<%= !\"resourceUnavailable\".equals(highlightClass) %>">

Then everything works well.

Just to be clear... there are several JSPs which have double-quoting which, while it works on Tomcat, is not to spec and fails on Weblogic and Websphere.

If patches could be submitted with these fixes, against the Team Elements trunk, we'll get the code in.

- Matt

Glenn,

are you installing TeamElements in the same server where you have concursive?

I had some problems in the past with this situation.

Regards

Luis Sorriguieta wrote:
Glenn,

are you installing TeamElements in the same server where you have concursive?

I had some problems in the past with this situation.

Regards

I have removed completely Concursive from my server, and the error still exists.

I updated Java Release, which now is:

java -version
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)

Tomcat apache-tomcat-5.5.26

And now, the error when I try to start TeamElements (rel 9.0) is nearly the same:

Estado HTTP 500 -

type Informe de Excepción

mensaje

descripción El servidor encontró un error interno () que hizo que no pudiera rellenar este requerimiento.

excepción

org.apache.jasper.JasperException: Exception in JSP: /index.jsp:33

30: // If the site is setup, then check to see if this is an upgraded version of the app
31: if (ApplicationVersion.isOutOfDate(applicationPrefs))
32: RequestDispatcher upgrade = getServletConfig().getServletContext().getRequestDispatcher("/Upgrade.do?command=Default&style=true");
33: upgrade.forward(request, response);
34: }
35: // If the site supports a portal, go to the portal
36: if ("true".equals(applicationPrefs.get("PORTAL")))

Stacktrace:
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:451)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:367)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

causa raíz

java.lang.IllegalStateException: No puedo reenviar después de que la respuesta se haya llevado a cabo.
org.apache.jsp.index_jsp._jspService(index_jsp.java:71)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

nota La traza completa de la causa de este error se encuentra en los archivos de diario de Apache Tomcat/5.5.26.

In $CATALINA_HOME/logs/catalina.out it appears:
It appears there is no mapping in the config file
every time I try to load teamelements.

Thanks

Hello All,

Is there a resolution for this yet? I had TE .9 running well on another machine, but now see these exact symptoms after restoring to a new machine from backups. The same occurs using Tomcat 6.0.16 or 5.5.26. Output from java -version:

Mini:~ extranet$ java -version
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)

I'd hate to lose a year of work and start over again! Any ideas from Concursive? Thanks.

I had this issue with tomcat 5.5.27 and both Java 1.5.0_01 and 1.6.0_10.

I uninstalled tomcat and installed tomcat 5.5.25 w/ webapps.
TE is now working with Java 1.6.0_10.

Daniel