voyent
FacesMessage(s) have been enqueued, but may not have been displayed.  XML
Forum Index -> General Help Go to Page: 1, 2 Next 
Author Message
edykory


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


Hi there!
We have moved this morning our platform from IBM JDK 1.4.2 + JBoss 4.0.5 to IBM 1.5.0 + JBoss 4.2.1 (with JSF 1.2 instead of MyFaces 1.1).
In the logs I notice quite frequent an info line which reads:
INFO [javax.enterprise.resource.webcontainer.jsf.lifecycle] WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(FATAL 3), summary=(null), detail=(Autentificare esuata. Utilizator si / sau parola incorecta.)] 

When I enqueue a message into the FacesContext.
The application functions normally, but I was wondering if it's something we are doing wrong according to the JBoss 4.2.1/JSF 1.2 paradigm.
Thanx.
judy.guglielmin

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


An annoyance, for sure, but I have found it doesn't affect functionality. A jira exists:- ICE-1900


ansel1


Joined: 07/Nov/2006 00:00:00
Messages: 85
Offline


It seems to be more than an annoyance for us, as our faces messages are actually not being displayed.
ansel1


Joined: 07/Nov/2006 00:00:00
Messages: 85
Offline


Ok, scratch that. They are sometimes displayed.
judy.guglielmin

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


Can you find any consistency to when they are/are not being displayed? So far all of mine have been displayed. We can update the jira if we can get some more information on this. Are you using ICEfaces1.6.1 or 1.6.0?

ansel1


Joined: 07/Nov/2006 00:00:00
Messages: 85
Offline


I'm using 1.6.1. I haven't been able to reproduce that again. I had been debugging in that session earlier, maybe that triggered it. I'll update the ticket if I can reproduce it.
sendewelt

Joined: 04/Sep/2007 00:00:00
Messages: 47
Offline


hello there,

i have the same problem. messages dont get displayed, despite being queued.
im using 1.6.1 icefaces and tomcat 6.0.14....
any help would be apriciated......

br,

andi
sendewelt

Joined: 04/Sep/2007 00:00:00
Messages: 47
Offline


hey,

by the way the log:
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=j_id101:j_id102:fromDate[severity=(INFO 0), summary=(Ungültiges Datum. Geben Sie ein Datum im Format tt.mm.yyyy ein.), detail=(Ungültiges Datum. Geben Sie ein Datum im Format tt.mm.yyyy ein.)]
sourceId=j_id101:j_id102:fromDate[severity=(ERROR 2), summary=(j_id101:j_id102:fromDate: Validierungs-Fehler: Wert ist nicht vom richtigen Datentyp.), detail=(j_id101:j_id102:fromDate: Validierungs-Fehler: Wert ist nicht vom richtigen Datentyp.)]
sourceId=j_id101:j_id102:j_id139[severity=(INFO 0), summary=(Ungültiges Datum. Geben Sie ein Datum im Format tt.mm.yyyy ein.), detail=(Ungültiges Datum. Geben Sie ein Datum im Format tt.mm.yyyy ein.)]



the message

15:40:03,946 WARN [Parameters] Parameters: Invalid chunk ignored.

mentionend in jira 1900 is not appaering though.

br,

andi
ansel1


Joined: 07/Nov/2006 00:00:00
Messages: 85
Offline


I'm not sure if this is the same case, but we did find one scenario which consistently does not display the faces messages:

If you queue faces messages during the render phase, after the <ice:message/ice:messages/> has already been rendered, your messages will not be displayed. We run into this frequently in our architecture. We lazily initialize stuff during the JSF render phase, and our <ice:messages> is at the top of our screen, so it gets rendered before our other backing beans are accessed.
sendewelt

Joined: 04/Sep/2007 00:00:00
Messages: 47
Offline


well this might be the case:

INFO: BEFORE RENDER_RESPONSE 6
22.10.2007 16:58:37 org.exadel.jsf.PhaseTracker beforePhase
INFO: BEFORE RENDER_RESPONSE 6
22.10.2007 16:58:37 com.sun.faces.lifecycle.RenderResponsePhase execute
INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=j_id101:j_id102:fromDate[severity=(FATAL 3), summary=(Ungültiges Datum. Geben Sie ein Datum im Format tt.mm.yyyy ein.), detail=(Ungültiges Datum. Geben Sie ein Datum im Format tt.mm.yyyy ein.)]
sourceId=j_id101:j_id102:fromDate[severity=(ERROR 2), summary=(j_id101:j_id102:fromDate: Validierungs-Fehler: Wert ist nicht vom richtigen Datentyp.), detail=(j_id101:j_id102:fromDate: Validierungs-Fehler: Wert ist nicht vom richtigen Datentyp.)]
sourceId=j_id101:j_id102:j_id139[severity=(FATAL 3), summary=(Ungültiges Datum. Geben Sie ein Datum im Format tt.mm.yyyy ein.), detail=(Ungültiges Datum. Geben Sie ein Datum im Format tt.mm.yyyy ein.)]
22.10.2007 16:58:37 org.exadel.jsf.PhaseTracker afterPhase
INFO: AFTER RENDER_RESPONSE 6
22.10.2007 16:58:37 org.exadel.jsf.PhaseTracker afterPhase
INFO: AFTER RENDER_RESPONSE 6

cause the warning appears between "before" and "after render response".
is there any fix workaround etc?

br,

andi
ansel1


Joined: 07/Nov/2006 00:00:00
Messages: 85
Offline


We haven't come up with one yet. Here are the possibilities we came up with in brainstorming:

1. Move the <ice:messages> component to the end of the page. This will cause it to be rendered almost last, and it will render all the messages queued during the render phase before it gets rendered.
2. Use a lifecycle listener to capture all queued messages before and after the render phase. Compare the two sets. If the two sets differ, then messages were queued during the render. Cache all the messages, trigger a second render (via icefaces server-side render push), and queue up the cached messages at the beginning of the next render phase.

This second approach almost works, but I ran into problems with Icefaces, and didn't have time to resolve them. I still think a variation of this might work, but haven't had time to finish it.
mark.collette


Joined: 07/Feb/2005 00:00:00
Messages: 1692
Offline


Perhaps you could use CSS to position the messages component at the top of the screen, while it exists below the other components in the component tree?
[Email]
sendewelt

Joined: 04/Sep/2007 00:00:00
Messages: 47
Offline


thx for your quick reply.......
i think i will get around this in a different way.
will the issue be fixed in an upcoming release?

@ansel1: when your fix should be working, i would appreciate you posting it here......



br,
andi
ansel1


Joined: 07/Nov/2006 00:00:00
Messages: 85
Offline


Will do.
ansel1


Joined: 07/Nov/2006 00:00:00
Messages: 85
Offline


Finally got around to writing a phase listener which I think works around this problem, and a couple others. I posted the solution in this thread:

http://www.icefaces.org/JForum/posts/list/0/5377.page#29183
 
Forum Index -> General Help Go to Page: 1, 2 Next 
Go to:   
Powered by JForum 2.1.7ice © JForum Team