Forums for ICEfaces and ICEpdf

I forgot ... on ICEfaces 1.6.0 DR4, on the Javascript consolse of Mozilla, the next error appears:

Code:

 Error: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: http://localhost:8080/JSF%20-%20ICEFaces/xmlhttp/1179173110078/icefaces-d2d.js :: anonymous :: line 1106"  data: no]
 Source File: http://localhost:8080/JSF%20-%20ICEFaces/xmlhttp/1179173110078/icefaces-d2d.js
 Line: 1106

That line is this one:
Code:

if(this.isComplete()){
 this.logger.debug("["+this.identifier+"] : receive ["+this.request.status+"] "+this.request.statusText);
 }

Hope that helps for something.

just to confirm ....you are using DR4 and creating the component-showcase application (there are 2 versions for regular component-showcase that come in the samples directory of our DR4 release) Problems with this are normally reported on the General questions part of the forum.

The seam-component-showcase is bundled separately and are dealt with on this forum. It also requires JDK1.5 and an ejb3 container(since seam uses annotations and session beans). If you can give us some more details as to which product you are having problems with, that would be great. (which browser are you using and what version perhaps?)

I am so sorry, I am not using JBoss, I am using Tomcat 5.025. I arrived here using the search tool and I just saw the "User Session Expired" thread title, didn't notice this was a JBoss section :(

I was a bit unclear on my first message, I will try to explain it better:

- I tried to create my own paginator example (and some others too) with DR4. They didn't work.
- I installed the component-showcase and the address demo that come with DR4 zip file. Those worked fine.
- I changed my own paginator to 1.5.3 release. Didn't work either.

I am using Mozilla Firefox 2, but also tested with Internet Explorer 6 and the same thing happens.

The component-showcase has an example of the paginator with an ice:dataTable which you stated worked fine. Perhaps you could attach your source for your facelet or jsp as well as the backing bean? We could make assumptions that your configuration files are setup as per the component-showcase (for DR4) for all required components or you could attach them as well. You may want to start with the source code from component-showcase as a base and then modify to want you are trying to do.

The exception is thrown in a section of code that is trying to find a dispatch handler to handle a request. Dispatch handlers are created for a user when a new session is created, and the appropriate HttpSessionListener is notified. In the past we've had problems with this when:

a) the correct listener is not specified in web.xml. I believe the correct format is now:
Code:

 <listener>
 <listener-class>com.icesoft.faces.util.event.servlet.ContextEventRepeater</listener-class>
 </listener>

b) the hashtable containing the dispatchers was keyed by the Session object, which worked for JBoss, but not for Websphere. It currently is keyed by Session id. I can't say for sure if this works in Tomcat, it should, but I will try to duplicate this.

c) If you are running the web application, and you redeploy with the browser still pointed at the server, it may be making heartbeat requests and blocking requests (depending on the application) to a session that no longer is valid, in which case the exception is valid.

I had the same problem with a very simple page (label + button). The problem disappeared as soon as i enabled cookies for localhost. ;->

I had the same problem with jboss 4.2.1(without seam) someone have a solution?

Hi Marcos,
If you're still seeing these errors after including the ContextEventListener, as Greg mentioned, and you're not seeing any functional impact on your application, the javascript errors are probably harmless. Usually you can get rid of them by restarting Firefox/Mozilla.

Philip

Looks like this problem dates back to January '07. Is there a workaround to turn this stupid thing off?

I am running Liferay 4.3.1 on Tomcat 5.5 with Liferay deployed in webapps/ROOT and the 'sample-icefaces-sun-portlet' keeps displaying the "User Session Expired" dialog. The portlet is unusable. I'm using Firefox 2.0.0.7 on OS X 10.4.

I tried the things mentioned on this forum thread (allowing cookies for localhost, restarting the browser, making sure the <listener> entry in web.xml is correct). Still does it.

It seems to be related to class reloading somehow. I added reloadable="true" to the META-INF/context.xml file so Tomcat would reload classes if they change.

If I restart Tomcat, I can use the job app form several times with no problem. I then modified JobApplication.java to change the message that gets displayed (I was doing this just to confirm the class was getting reloaded). About 30 seconds after the recompile, the "User Session Expired" dialog popups up without me doing anything.

Is there some kind of option to disable this thing?

Hope this helps,
Phil

Hi sbergonzi,

Please re-post your message in the General Help forum and then we can look into it. This forum is only for Seam-related inquiries.

Thanks.
Philip

I am also experiencing this issue (Weblogic 10, Icefaces 1.6, MyFaces 1.2). Listener info is in the web.xml. I'm getting this error, the class is defined in the icefaces.jar file which is in the WEB-INF/lib directory.

2007-10-03 15:06:15,374 WARN : com.icesoft.faces.webapp.http.servlet.SessionDispatcher - java.lang.ExceptionInInitializerError
2007-10-03 15:06:15,384 WARN : com.icesoft.faces.webapp.http.servlet.SessionDispatcher - java.lang.NoClassDefFoundError
<Oct 3, 2007 3:06:15 PM EDT> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@1d849ae - appName: '_appsdir_SimpleTest_dir', name: 'SimpleTest', context-path: '/SimpleTest'] Root cause of ServletException.
javax.servlet.ServletException: Session expired

Hello all...

Not sure if this helps anyone, but I had the same problem without Seam on JBoss 4.0.2/Tomcat 5.5 and fixed it by opening the content.xml file located in the root of the jbossweb-tomcat55.sar, and changing the cookies attribute from false to true. After making the change, I cleared my browser cache and bounced my JBoss instance. I also bumped my timeout to a ridiculous number just to make sure that wasn't the issue. The xml from my content.xml is below.

A lot of people have been posting the same issue so I figured I put this out there on how I solved my particular instance of this very, very annoying problem. I hope it helps you all.

For the record I am using Icefaces v1.70/MyEcliplse 6.0/JBoss 4.0.2-Tomcat 5.5/MyFaces 1.1.5/J2EE 1.4

<Context cookies="true" crossContext="true">
<Manager className="org.apache.catalina.session.StandardManager"
pathname="" />
</Context>

Take it easy...

Check this:

http://jira.icefaces.org//browse/ICE-2152

Mike Lawrence [08/Oct/07 01:21 PM]
Adding emptySessionPath="true" attribute to the connector element in the tomcat conf/server.xml file seems to fix this problem

Saludos, greetings

Try with
<ice:outputConnectionStatus activeLabel="false"/>

And add to web.xml

<session-config>
<session-timeout>90000</session-timeout>
</session-config>

bye