voyent
Query does not contain parameter named: icefacesID  XML
Forum Index -> General Help Go to Page: 1, 2, 3 Next 
Author Message
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


Hi there !
After some troubles trying to run IceFaces with IBM's jdk 1.4.2 on a JBoss 4.0.5 - Suse Enterprise 9 (there are different NPE in logs from IceFaces, apache commons, http, etc) we decided to give it a try with IBM's jdk 5.
Now all those errors disappeared, and there's only one exception in our logs, which says:
Query does not contain parameter named: icefacesID 

(it's the only exception, but it appears quite a few times).
I've never seen this error in 1.5.3 or 1.6 DR#4 so I have no clue why does it appear.

anybody found the same problem?
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


2007-07-10 13:40:21,617 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/OTPProject].[Persistent Faces Servlet]] Servlet.service() for servlet Persistent Faces Servlet threw exception
java.lang.RuntimeException: Query does not contain parameter named: icefacesID
at com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.checkExistenceOf(ServletRequestResponse.java:176)
at com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.getParameter(ServletRequestResponse.java:75)
at com.icesoft.faces.webapp.http.core.IDVerifier.service(IDVerifier.java:23)
at com.icesoft.faces.webapp.http.servlet.ThreadBlockingAdaptingServlet.service(ThreadBlockingAdaptingServlet.java:19)
at com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet.service(EnvironmentAdaptingServlet.java:103)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
at com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:97)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:359)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:54)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:801)
 

This is the full stack trace, in case it helps
ted.goddard

Joined: 26/Oct/2004 00:00:00
Messages: 874
Offline


Does the page contain a form?

[Email]
JeffLee

Joined: 07/Sep/2006 00:00:00
Messages: 42
Offline


Ted, I have seen this same error and my page does contain an ice:form with ice:panelCollapsible's in it. I received the error when I clicked on the collapsible control.
[Email]
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


Hi there!
We in particular as I said in the first post are using now IBM's JDK 5.0 on a JBoss 4.0.5 (no SEAM) on a Suse Enterprise 9.
All the pages are inside forms ... and in our case, the error message is very random and quite seldom, so I can't say why does it happen. It usually happens after login, but we are not using any fancy features. It's one of those cases where ... it should simply work ...
Anyway, in the past 6 hours we haven't got anymore of those ... and I can't say why ....
Cheers
judy.guglielmin

Joined: 20/Feb/2007 00:00:00
Messages: 1396
Offline


are you using the expanded property on the panelCollapsible? If you are using jsf1.2 you can sometimes get this error if you have this property set to "#{true}" or something other than "true" or "false" or a proper el expression that involves some kind of bean.

Let us know if you are using the jsf1.2 implementation jars, whether you are using Seam, any other external jars?

Thanks.
JeffLee

Joined: 07/Sep/2006 00:00:00
Messages: 42
Offline


I do not believe I am using the 1.2 libraries. I was using the expanded property but I removed it and I cannot remember if it was on the page when I received the error.
[Email]
judy.guglielmin

Joined: 20/Feb/2007 00:00:00
Messages: 1396
Offline


What server are you using and are you using the myfaces jars then?
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


We are using JBoss 4.0.5 and Myfaces. At a first look, they seemed to me a little bit better written than Sun's RI, but if you think this changed by now ... please let me know.
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


We have been using the 1.6 DR#4 from the very first day it appeared and I've never seen this message before. But I'll do a double check, just to make sure. The problem is that we are using facelets, and the forms are declared in the 4-5 templates that all the other pages are using, so it's quite impossible to have any fields running crazy arround.
See you!
judy.guglielmin

Joined: 20/Feb/2007 00:00:00
Messages: 1396
Offline


...and you are certain that you don't have a button or a link outside of a form? That is typically the cause of this error with the platform you are using. I(personally) think you are correct in that myfaces/jboss-4.0.5.GA is more stable and typically the exceptions that are thrown mean what they say (which is why I would really check over your facelets pages for this one and looking at their structure). This message is a new one since DR#3 which is why you probably didn't see it before. I'll check with the others to see if there is any notable difference when using IBM's jdk though.
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


Actually we do have some <h:outputLink>, a few <h:outputText> and one <h:panelGroup> outside the form. Do you think this could be the problem?
And if so, why didn't it reproduce anymore for more than 8 hours now?
It's h:outputLink, not commandLink, so in html they are just simple <a href .... >
JeffLee

Joined: 07/Sep/2006 00:00:00
Messages: 42
Offline


JBoss 4.0.3 and I was using jsf-api.jar/jsf-impl.jar. I just changed those out to the 1.2 versions.
[Email]
judy.guglielmin

Joined: 20/Feb/2007 00:00:00
Messages: 1396
Offline


So the error is intermittent? Are you using concurrentDomViews?
ted.goddard

Joined: 26/Oct/2004 00:00:00
Messages: 874
Offline


Do you have a connection status component in the page? Perhaps the connection and the session are timing out, and for some reason this is not being reported accurately.

[Email]
 
Forum Index -> General Help Go to Page: 1, 2, 3 Next 
Go to:   
Powered by JForum 2.1.7ice © JForum Team