You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by "Boyd, David (Corporate)" <Da...@adesa.com> on 2011/09/26 21:09:57 UTC
Issues with MyFaces and Clusters
I am having some issues with clustering an application with session
affinity enabled on Websphere Application Server.
We are using:
MyFace 1.1.7
Tomahawk 1.1.5
JDK 1.5
WebSphere 7 - Fix Pack 13
I am wondering if this is a known issue with this version of My Faces.
What appears to be happening is that in the application, when a session
object is accesses and the data is changed, the change event is not
being triggered and therefore the change is not being pushed out to all
the servers in the cluster.
It looks like this version of my faces is accessing the session object
via the getter but, it is making a change to the reference and therefore
not calling the setter method.
Looking for some confirmation on this issue or possible a configuration
that needs to be done.
Thanks
Re: Issues with MyFaces and Clusters
Posted by Mark Struberg <st...@yahoo.de>.
For me it always worked pretty well to do 'read-only replication'. I've no idea if there is an established term for it, but here is what I do:
1.) we use sticky sessions in our load balancer. Each user defaults back to his node. If the node is not available for 40 seconds, then he gets moved to a different node
2.) after each request we replicate the session over to our memcached instance. But we do not evict the session from the current node! So it usually just gets backed-up but never restored.
3.) If a node fails, we have a listener which tries to restore the session from the memcached.
memcached of course might get it's own network segment and stuff.
This does not worsen the response times for users since all the session backup is done after the page got rendered already. And since we mainly rely on session-affinity the memcachd session retrieval only takes place if a node goes down.
LieGrue,
strub
----- Original Message -----
> From: Rohit Kelapure <ke...@gmail.com>
> To: MyFaces Discussion <us...@myfaces.apache.org>
> Cc:
> Sent: Tuesday, September 27, 2011 6:24 PM
> Subject: Re: Issues with MyFaces and Clusters
>
> David,
>
> It is difficult for me to tell you what is the average session size for a
> JSF application. I am by no means a JSF expert. The folks on this forum will
> have better insight into typical session sizes for a JSF application. Most
> of the time it varies according to your application.
>
> There is some tuning you can do, like reducing the # of logical views etc
> that will reduce the amount cached my myFaces in the session.
>
> I recommend tuning and if that does not help some rearchitecting to reduce
> your session footprint
> I will also point you to
> http://wasdynacache.blogspot.com/2011/08/websphere-session-persistence-best.html
>
> --Thanks,
> Rohit Kelapure,
> Apache Open WebBeans Committer
>
> On Tue, Sep 27, 2011 at 11:54 AM, Boyd, David (Corporate) <
> David.Boyd@adesa.com> wrote:
>
>> Robit,
>>
>> Going down this road it appears that we will be using a database to
>> store the session information. From What I have seen with JSF - at
>> least our implementation we are looking at around 20 MB in the session
>> per user.
>>
>> So, now the question is, is what I am seeing in the session high for a
>> JSF application - for a non JSF application it is very high.
>>
>> -----Original Message-----
>> From: Rohit Kelapure [mailto:kelapure@gmail.com]
>> Sent: Monday, September 26, 2011 9:28 PM
>> To: MyFaces Discussion
>> Cc: Robert E Goff
>> Subject: Re: Issues with MyFaces and Clusters
>>
>> David,
>>
>> Please take a look at
>>
>> Update All Session Attributes option - Horrible for performance, but
>> fixes
>> issues like this.
>> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2
>> Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
>>
>> --Thanks,
>> Rohit
>>
>> On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
>> David.Boyd@adesa.com> wrote:
>>
>> > I am having some issues with clustering an application with session
>> > affinity enabled on Websphere Application Server.
>> >
>> >
>> >
>> > We are using:
>> >
>> >
>> >
>> > MyFace 1.1.7
>> >
>> > Tomahawk 1.1.5
>> >
>> > JDK 1.5
>> >
>> > WebSphere 7 - Fix Pack 13
>> >
>> >
>> >
>> > I am wondering if this is a known issue with this version of My Faces.
>> >
>> >
>> >
>> > What appears to be happening is that in the application, when a
>> session
>> > object is accesses and the data is changed, the change event is not
>> > being triggered and therefore the change is not being pushed out to
>> all
>> > the servers in the cluster.
>> >
>> >
>> >
>> > It looks like this version of my faces is accessing the session object
>> > via the getter but, it is making a change to the reference and
>> therefore
>> > not calling the setter method.
>> >
>> >
>> >
>> > Looking for some confirmation on this issue or possible a
>> configuration
>> > that needs to be done.
>> >
>> >
>> >
>> > Thanks
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>
Re: Issues with MyFaces and Clusters
Posted by Rohit Kelapure <ke...@gmail.com>.
David,
It is difficult for me to tell you what is the average session size for a
JSF application. I am by no means a JSF expert. The folks on this forum will
have better insight into typical session sizes for a JSF application. Most
of the time it varies according to your application.
There is some tuning you can do, like reducing the # of logical views etc
that will reduce the amount cached my myFaces in the session.
I recommend tuning and if that does not help some rearchitecting to reduce
your session footprint
I will also point you to
http://wasdynacache.blogspot.com/2011/08/websphere-session-persistence-best.html
--Thanks,
Rohit Kelapure,
Apache Open WebBeans Committer
On Tue, Sep 27, 2011 at 11:54 AM, Boyd, David (Corporate) <
David.Boyd@adesa.com> wrote:
> Robit,
>
> Going down this road it appears that we will be using a database to
> store the session information. From What I have seen with JSF - at
> least our implementation we are looking at around 20 MB in the session
> per user.
>
> So, now the question is, is what I am seeing in the session high for a
> JSF application - for a non JSF application it is very high.
>
> -----Original Message-----
> From: Rohit Kelapure [mailto:kelapure@gmail.com]
> Sent: Monday, September 26, 2011 9:28 PM
> To: MyFaces Discussion
> Cc: Robert E Goff
> Subject: Re: Issues with MyFaces and Clusters
>
> David,
>
> Please take a look at
>
> Update All Session Attributes option - Horrible for performance, but
> fixes
> issues like this.
> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2
> Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
>
> --Thanks,
> Rohit
>
> On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
> David.Boyd@adesa.com> wrote:
>
> > I am having some issues with clustering an application with session
> > affinity enabled on Websphere Application Server.
> >
> >
> >
> > We are using:
> >
> >
> >
> > MyFace 1.1.7
> >
> > Tomahawk 1.1.5
> >
> > JDK 1.5
> >
> > WebSphere 7 - Fix Pack 13
> >
> >
> >
> > I am wondering if this is a known issue with this version of My Faces.
> >
> >
> >
> > What appears to be happening is that in the application, when a
> session
> > object is accesses and the data is changed, the change event is not
> > being triggered and therefore the change is not being pushed out to
> all
> > the servers in the cluster.
> >
> >
> >
> > It looks like this version of my faces is accessing the session object
> > via the getter but, it is making a change to the reference and
> therefore
> > not calling the setter method.
> >
> >
> >
> > Looking for some confirmation on this issue or possible a
> configuration
> > that needs to be done.
> >
> >
> >
> > Thanks
> >
> >
> >
> >
> >
> >
> >
> >
>
RE: Issues with MyFaces and Clusters
Posted by "Boyd, David (Corporate)" <Da...@adesa.com>.
Robit,
Going down this road it appears that we will be using a database to
store the session information. From What I have seen with JSF - at
least our implementation we are looking at around 20 MB in the session
per user.
So, now the question is, is what I am seeing in the session high for a
JSF application - for a non JSF application it is very high.
-----Original Message-----
From: Rohit Kelapure [mailto:kelapure@gmail.com]
Sent: Monday, September 26, 2011 9:28 PM
To: MyFaces Discussion
Cc: Robert E Goff
Subject: Re: Issues with MyFaces and Clusters
David,
Please take a look at
Update All Session Attributes option - Horrible for performance, but
fixes
issues like this.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2
Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
--Thanks,
Rohit
On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
David.Boyd@adesa.com> wrote:
> I am having some issues with clustering an application with session
> affinity enabled on Websphere Application Server.
>
>
>
> We are using:
>
>
>
> MyFace 1.1.7
>
> Tomahawk 1.1.5
>
> JDK 1.5
>
> WebSphere 7 - Fix Pack 13
>
>
>
> I am wondering if this is a known issue with this version of My Faces.
>
>
>
> What appears to be happening is that in the application, when a
session
> object is accesses and the data is changed, the change event is not
> being triggered and therefore the change is not being pushed out to
all
> the servers in the cluster.
>
>
>
> It looks like this version of my faces is accessing the session object
> via the getter but, it is making a change to the reference and
therefore
> not calling the setter method.
>
>
>
> Looking for some confirmation on this issue or possible a
configuration
> that needs to be done.
>
>
>
> Thanks
>
>
>
>
>
>
>
>
Re: Issues with MyFaces and Clusters
Posted by Rohit Kelapure <ke...@gmail.com>.
Thanks for pointing it out. I will investigate ...
--Thanks,
Rohit
On Tue, Sep 27, 2011 at 12:27 PM, Leonardo Uribe <lu...@gmail.com> wrote:
> Hi
>
> 2011/9/27 Rohit Kelapure <ke...@gmail.com>:
> > Leonardo,
> >
> > Updating this sessionMap object doesn't mean anything to the session.
> > It has to be the sessionMap object updated within the session.
> Something
> > like this -
> >
> > session.put("sessionMap", object);
> >
>
> Look this class:
>
>
> http://svn.apache.org/repos/asf/myfaces/core/branches/1.1.x/impl/src/main/java/org/apache/myfaces/context/servlet/SessionMap.java
>
> In JSF, the "sessionMap" is a wrapper for the session object, so call
> sessionMap.put will effectively call
> _httpRequest.getSession(true).setAttribute(key, value). It is ok.
>
> regards,
>
> Leonardo Uribe
>
> > --Thanks,
> > Rohit
> >
> >
> > On Mon, Sep 26, 2011 at 10:24 PM, Leonardo Uribe <lu...@gmail.com>
> wrote:
> >
> >> Hi
> >>
> >> 2011/9/26 Boyd, David (Corporate) <Da...@adesa.com>
> >>
> >> > So just to be clear
> >> >
> >> > 1. Based on the code snipit it appears that indeed myfaces is doing
> thing
> >> > as expected.
> >> >
> >> >
> >> Yes.
> >>
> >>
> >> > 2. Are stating that the issue I am seeing is a know bug with Websphere
> 7?
> >> > If so can you provide a link. I was searching the IBM site but did
> not
> >> > have any success in locating any issue list.
> >> >
> >> >
> >> I don't know if it is a known bug. All I can say is myfaces with other
> >> servers in a cluster configuration work as expected, so I suppose based
> on
> >> the evidence it is a bug on Websphere.
> >>
> >> regards,
> >>
> >> Leonardo
> >>
> >>
> >> >
> >> >
> >> > Thanks
> >> > -David Boyd
> >> >
> >> > (Sent via BlackBerry)
> >> >
> >> > ----- Original Message -----
> >> > From: Leonardo Uribe [mailto:lu4242@gmail.com]
> >> > Sent: Monday, September 26, 2011 09:47 PM
> >> > To: MyFaces Discussion <us...@myfaces.apache.org>
> >> > Subject: Re: Issues with MyFaces and Clusters
> >> >
> >> > Hi
> >> >
> >> > I have checked the latest code (and 1.1.7 code) and it seems to be
> >> correct.
> >> > See:
> >> >
> >> >
> >> >
> >>
> http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/jsp/JspStateManagerImpl.java
> >> >
> >> > the following lines:
> >> >
> >> > protected void saveSerializedViewInServletSession(FacesContext
> >> context,
> >> > Object
> >> serializedView)
> >> > {
> >> > Map<String, Object> sessionMap =
> >> > context.getExternalContext().getSessionMap();
> >> > SerializedViewCollection viewCollection =
> >> > (SerializedViewCollection) sessionMap
> >> > .get(SERIALIZED_VIEW_SESSION_ATTR);
> >> > if (viewCollection == null)
> >> > {
> >> > viewCollection = new SerializedViewCollection();
> >> > sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR,
> viewCollection);
> >> > }
> >> > viewCollection.add(context, serializeView(context,
> >> serializedView));
> >> > // replace the value to notify the container about the change
> >> > sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
> >> > }
> >> >
> >> > Look the last line that force the collection to be stored again on the
> >> > session, to notify the container about the change. Maybe since the
> same
> >> > instance is stored, by some reason WebSphere is not notifying the
> change
> >> > and
> >> > cause the problem you described. I think a workaround is create a
> custom
> >> > state manager extending from myfaces one and writing something else on
> >> the
> >> > session, but in practice it is a bug in WebSphere, so a fix should be
> >> done
> >> > there.
> >> >
> >> > regards,
> >> >
> >> > Leonardo Uribe
> >> >
> >> > 2011/9/26 Rohit Kelapure <ke...@gmail.com>
> >> >
> >> > > David,
> >> > >
> >> > > Please take a look at
> >> > >
> >> > > Update All Session Attributes option - Horrible for performance,
> but
> >> > fixes
> >> > > issues like this.
> >> > >
> >> > >
> >> >
> >>
> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
> >> > >
> >> > > --Thanks,
> >> > > Rohit
> >> > >
> >> > > On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
> >> > > David.Boyd@adesa.com> wrote:
> >> > >
> >> > > > I am having some issues with clustering an application with
> session
> >> > > > affinity enabled on Websphere Application Server.
> >> > > >
> >> > > >
> >> > > >
> >> > > > We are using:
> >> > > >
> >> > > >
> >> > > >
> >> > > > MyFace 1.1.7
> >> > > >
> >> > > > Tomahawk 1.1.5
> >> > > >
> >> > > > JDK 1.5
> >> > > >
> >> > > > WebSphere 7 - Fix Pack 13
> >> > > >
> >> > > >
> >> > > >
> >> > > > I am wondering if this is a known issue with this version of My
> >> Faces.
> >> > > >
> >> > > >
> >> > > >
> >> > > > What appears to be happening is that in the application, when a
> >> session
> >> > > > object is accesses and the data is changed, the change event is
> not
> >> > > > being triggered and therefore the change is not being pushed out
> to
> >> all
> >> > > > the servers in the cluster.
> >> > > >
> >> > > >
> >> > > >
> >> > > > It looks like this version of my faces is accessing the session
> >> object
> >> > > > via the getter but, it is making a change to the reference and
> >> > therefore
> >> > > > not calling the setter method.
> >> > > >
> >> > > >
> >> > > >
> >> > > > Looking for some confirmation on this issue or possible a
> >> configuration
> >> > > > that needs to be done.
> >> > > >
> >> > > >
> >> > > >
> >> > > > Thanks
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
RE: Issues with MyFaces and Clusters
Posted by "Boyd, David (Corporate)" <Da...@adesa.com>.
Looking at the code that is referenced by the link below I see the following:
private HttpSession getSession()
{
return _httpRequest.getSession(false);
}
Now based on this understanding:
When you say getSession(true), this method will check whether already a session is existing for the user. If a session is existing, it will return that session object, OTHERWISE WILL CREATE A SESSION OBJECT EXPLICITLY AND RETURN TO THE CLIENT. When you say getSession(false), this method will check whether a session is existing. If yes, then it returns the reference of that session object, OTHERWISE IT WILL RETURN 'null'.
So the above code can return a null for the session - I am not sure what the original intent of the method is as I do not see any JavaDocs with it.
Session Manage is handled by JSF, so I assume then that the SessionMap class is part of the Session Manage process of JSF.
It would appear that the JSF library is making a call to set the attribute on a session, therefore it should trigger the session replication correctly.
The issue then could be is that the session size is so large that it does not have the ability to complete the task in the event of a user moving to a different IP address.
-----Original Message-----
From: Leonardo Uribe [mailto:lu4242@gmail.com]
Sent: Tuesday, September 27, 2011 12:28 PM
To: MyFaces Discussion
Subject: Re: Issues with MyFaces and Clusters
Hi
2011/9/27 Rohit Kelapure <ke...@gmail.com>:
> Leonardo,
>
> Updating this sessionMap object doesn't mean anything to the session.
> It has to be the sessionMap object updated within the session. Something
> like this -
>
> session.put("sessionMap", object);
>
Look this class:
http://svn.apache.org/repos/asf/myfaces/core/branches/1.1.x/impl/src/main/java/org/apache/myfaces/context/servlet/SessionMap.java
In JSF, the "sessionMap" is a wrapper for the session object, so call
sessionMap.put will effectively call
_httpRequest.getSession(true).setAttribute(key, value). It is ok.
regards,
Leonardo Uribe
> --Thanks,
> Rohit
>
>
> On Mon, Sep 26, 2011 at 10:24 PM, Leonardo Uribe <lu...@gmail.com> wrote:
>
>> Hi
>>
>> 2011/9/26 Boyd, David (Corporate) <Da...@adesa.com>
>>
>> > So just to be clear
>> >
>> > 1. Based on the code snipit it appears that indeed myfaces is doing thing
>> > as expected.
>> >
>> >
>> Yes.
>>
>>
>> > 2. Are stating that the issue I am seeing is a know bug with Websphere 7?
>> > If so can you provide a link. I was searching the IBM site but did not
>> > have any success in locating any issue list.
>> >
>> >
>> I don't know if it is a known bug. All I can say is myfaces with other
>> servers in a cluster configuration work as expected, so I suppose based on
>> the evidence it is a bug on Websphere.
>>
>> regards,
>>
>> Leonardo
>>
>>
>> >
>> >
>> > Thanks
>> > -David Boyd
>> >
>> > (Sent via BlackBerry)
>> >
>> > ----- Original Message -----
>> > From: Leonardo Uribe [mailto:lu4242@gmail.com]
>> > Sent: Monday, September 26, 2011 09:47 PM
>> > To: MyFaces Discussion <us...@myfaces.apache.org>
>> > Subject: Re: Issues with MyFaces and Clusters
>> >
>> > Hi
>> >
>> > I have checked the latest code (and 1.1.7 code) and it seems to be
>> correct.
>> > See:
>> >
>> >
>> >
>> http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/jsp/JspStateManagerImpl.java
>> >
>> > the following lines:
>> >
>> > protected void saveSerializedViewInServletSession(FacesContext
>> context,
>> > Object
>> serializedView)
>> > {
>> > Map<String, Object> sessionMap =
>> > context.getExternalContext().getSessionMap();
>> > SerializedViewCollection viewCollection =
>> > (SerializedViewCollection) sessionMap
>> > .get(SERIALIZED_VIEW_SESSION_ATTR);
>> > if (viewCollection == null)
>> > {
>> > viewCollection = new SerializedViewCollection();
>> > sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
>> > }
>> > viewCollection.add(context, serializeView(context,
>> serializedView));
>> > // replace the value to notify the container about the change
>> > sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
>> > }
>> >
>> > Look the last line that force the collection to be stored again on the
>> > session, to notify the container about the change. Maybe since the same
>> > instance is stored, by some reason WebSphere is not notifying the change
>> > and
>> > cause the problem you described. I think a workaround is create a custom
>> > state manager extending from myfaces one and writing something else on
>> the
>> > session, but in practice it is a bug in WebSphere, so a fix should be
>> done
>> > there.
>> >
>> > regards,
>> >
>> > Leonardo Uribe
>> >
>> > 2011/9/26 Rohit Kelapure <ke...@gmail.com>
>> >
>> > > David,
>> > >
>> > > Please take a look at
>> > >
>> > > Update All Session Attributes option - Horrible for performance, but
>> > fixes
>> > > issues like this.
>> > >
>> > >
>> >
>> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
>> > >
>> > > --Thanks,
>> > > Rohit
>> > >
>> > > On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
>> > > David.Boyd@adesa.com> wrote:
>> > >
>> > > > I am having some issues with clustering an application with session
>> > > > affinity enabled on Websphere Application Server.
>> > > >
>> > > >
>> > > >
>> > > > We are using:
>> > > >
>> > > >
>> > > >
>> > > > MyFace 1.1.7
>> > > >
>> > > > Tomahawk 1.1.5
>> > > >
>> > > > JDK 1.5
>> > > >
>> > > > WebSphere 7 - Fix Pack 13
>> > > >
>> > > >
>> > > >
>> > > > I am wondering if this is a known issue with this version of My
>> Faces.
>> > > >
>> > > >
>> > > >
>> > > > What appears to be happening is that in the application, when a
>> session
>> > > > object is accesses and the data is changed, the change event is not
>> > > > being triggered and therefore the change is not being pushed out to
>> all
>> > > > the servers in the cluster.
>> > > >
>> > > >
>> > > >
>> > > > It looks like this version of my faces is accessing the session
>> object
>> > > > via the getter but, it is making a change to the reference and
>> > therefore
>> > > > not calling the setter method.
>> > > >
>> > > >
>> > > >
>> > > > Looking for some confirmation on this issue or possible a
>> configuration
>> > > > that needs to be done.
>> > > >
>> > > >
>> > > >
>> > > > Thanks
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> >
>>
>
Re: Issues with MyFaces and Clusters
Posted by Leonardo Uribe <lu...@gmail.com>.
Hi
2011/9/27 Rohit Kelapure <ke...@gmail.com>:
> Leonardo,
>
> Updating this sessionMap object doesn't mean anything to the session.
> It has to be the sessionMap object updated within the session. Something
> like this -
>
> session.put("sessionMap", object);
>
Look this class:
http://svn.apache.org/repos/asf/myfaces/core/branches/1.1.x/impl/src/main/java/org/apache/myfaces/context/servlet/SessionMap.java
In JSF, the "sessionMap" is a wrapper for the session object, so call
sessionMap.put will effectively call
_httpRequest.getSession(true).setAttribute(key, value). It is ok.
regards,
Leonardo Uribe
> --Thanks,
> Rohit
>
>
> On Mon, Sep 26, 2011 at 10:24 PM, Leonardo Uribe <lu...@gmail.com> wrote:
>
>> Hi
>>
>> 2011/9/26 Boyd, David (Corporate) <Da...@adesa.com>
>>
>> > So just to be clear
>> >
>> > 1. Based on the code snipit it appears that indeed myfaces is doing thing
>> > as expected.
>> >
>> >
>> Yes.
>>
>>
>> > 2. Are stating that the issue I am seeing is a know bug with Websphere 7?
>> > If so can you provide a link. I was searching the IBM site but did not
>> > have any success in locating any issue list.
>> >
>> >
>> I don't know if it is a known bug. All I can say is myfaces with other
>> servers in a cluster configuration work as expected, so I suppose based on
>> the evidence it is a bug on Websphere.
>>
>> regards,
>>
>> Leonardo
>>
>>
>> >
>> >
>> > Thanks
>> > -David Boyd
>> >
>> > (Sent via BlackBerry)
>> >
>> > ----- Original Message -----
>> > From: Leonardo Uribe [mailto:lu4242@gmail.com]
>> > Sent: Monday, September 26, 2011 09:47 PM
>> > To: MyFaces Discussion <us...@myfaces.apache.org>
>> > Subject: Re: Issues with MyFaces and Clusters
>> >
>> > Hi
>> >
>> > I have checked the latest code (and 1.1.7 code) and it seems to be
>> correct.
>> > See:
>> >
>> >
>> >
>> http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/jsp/JspStateManagerImpl.java
>> >
>> > the following lines:
>> >
>> > protected void saveSerializedViewInServletSession(FacesContext
>> context,
>> > Object
>> serializedView)
>> > {
>> > Map<String, Object> sessionMap =
>> > context.getExternalContext().getSessionMap();
>> > SerializedViewCollection viewCollection =
>> > (SerializedViewCollection) sessionMap
>> > .get(SERIALIZED_VIEW_SESSION_ATTR);
>> > if (viewCollection == null)
>> > {
>> > viewCollection = new SerializedViewCollection();
>> > sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
>> > }
>> > viewCollection.add(context, serializeView(context,
>> serializedView));
>> > // replace the value to notify the container about the change
>> > sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
>> > }
>> >
>> > Look the last line that force the collection to be stored again on the
>> > session, to notify the container about the change. Maybe since the same
>> > instance is stored, by some reason WebSphere is not notifying the change
>> > and
>> > cause the problem you described. I think a workaround is create a custom
>> > state manager extending from myfaces one and writing something else on
>> the
>> > session, but in practice it is a bug in WebSphere, so a fix should be
>> done
>> > there.
>> >
>> > regards,
>> >
>> > Leonardo Uribe
>> >
>> > 2011/9/26 Rohit Kelapure <ke...@gmail.com>
>> >
>> > > David,
>> > >
>> > > Please take a look at
>> > >
>> > > Update All Session Attributes option - Horrible for performance, but
>> > fixes
>> > > issues like this.
>> > >
>> > >
>> >
>> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
>> > >
>> > > --Thanks,
>> > > Rohit
>> > >
>> > > On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
>> > > David.Boyd@adesa.com> wrote:
>> > >
>> > > > I am having some issues with clustering an application with session
>> > > > affinity enabled on Websphere Application Server.
>> > > >
>> > > >
>> > > >
>> > > > We are using:
>> > > >
>> > > >
>> > > >
>> > > > MyFace 1.1.7
>> > > >
>> > > > Tomahawk 1.1.5
>> > > >
>> > > > JDK 1.5
>> > > >
>> > > > WebSphere 7 - Fix Pack 13
>> > > >
>> > > >
>> > > >
>> > > > I am wondering if this is a known issue with this version of My
>> Faces.
>> > > >
>> > > >
>> > > >
>> > > > What appears to be happening is that in the application, when a
>> session
>> > > > object is accesses and the data is changed, the change event is not
>> > > > being triggered and therefore the change is not being pushed out to
>> all
>> > > > the servers in the cluster.
>> > > >
>> > > >
>> > > >
>> > > > It looks like this version of my faces is accessing the session
>> object
>> > > > via the getter but, it is making a change to the reference and
>> > therefore
>> > > > not calling the setter method.
>> > > >
>> > > >
>> > > >
>> > > > Looking for some confirmation on this issue or possible a
>> configuration
>> > > > that needs to be done.
>> > > >
>> > > >
>> > > >
>> > > > Thanks
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> >
>>
>
Re: Issues with MyFaces and Clusters
Posted by Rohit Kelapure <ke...@gmail.com>.
Leonardo,
Updating this sessionMap object doesn't mean anything to the session.
It has to be the sessionMap object updated within the session. Something
like this -
session.put("sessionMap", object);
--Thanks,
Rohit
On Mon, Sep 26, 2011 at 10:24 PM, Leonardo Uribe <lu...@gmail.com> wrote:
> Hi
>
> 2011/9/26 Boyd, David (Corporate) <Da...@adesa.com>
>
> > So just to be clear
> >
> > 1. Based on the code snipit it appears that indeed myfaces is doing thing
> > as expected.
> >
> >
> Yes.
>
>
> > 2. Are stating that the issue I am seeing is a know bug with Websphere 7?
> > If so can you provide a link. I was searching the IBM site but did not
> > have any success in locating any issue list.
> >
> >
> I don't know if it is a known bug. All I can say is myfaces with other
> servers in a cluster configuration work as expected, so I suppose based on
> the evidence it is a bug on Websphere.
>
> regards,
>
> Leonardo
>
>
> >
> >
> > Thanks
> > -David Boyd
> >
> > (Sent via BlackBerry)
> >
> > ----- Original Message -----
> > From: Leonardo Uribe [mailto:lu4242@gmail.com]
> > Sent: Monday, September 26, 2011 09:47 PM
> > To: MyFaces Discussion <us...@myfaces.apache.org>
> > Subject: Re: Issues with MyFaces and Clusters
> >
> > Hi
> >
> > I have checked the latest code (and 1.1.7 code) and it seems to be
> correct.
> > See:
> >
> >
> >
> http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/jsp/JspStateManagerImpl.java
> >
> > the following lines:
> >
> > protected void saveSerializedViewInServletSession(FacesContext
> context,
> > Object
> serializedView)
> > {
> > Map<String, Object> sessionMap =
> > context.getExternalContext().getSessionMap();
> > SerializedViewCollection viewCollection =
> > (SerializedViewCollection) sessionMap
> > .get(SERIALIZED_VIEW_SESSION_ATTR);
> > if (viewCollection == null)
> > {
> > viewCollection = new SerializedViewCollection();
> > sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
> > }
> > viewCollection.add(context, serializeView(context,
> serializedView));
> > // replace the value to notify the container about the change
> > sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
> > }
> >
> > Look the last line that force the collection to be stored again on the
> > session, to notify the container about the change. Maybe since the same
> > instance is stored, by some reason WebSphere is not notifying the change
> > and
> > cause the problem you described. I think a workaround is create a custom
> > state manager extending from myfaces one and writing something else on
> the
> > session, but in practice it is a bug in WebSphere, so a fix should be
> done
> > there.
> >
> > regards,
> >
> > Leonardo Uribe
> >
> > 2011/9/26 Rohit Kelapure <ke...@gmail.com>
> >
> > > David,
> > >
> > > Please take a look at
> > >
> > > Update All Session Attributes option - Horrible for performance, but
> > fixes
> > > issues like this.
> > >
> > >
> >
> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
> > >
> > > --Thanks,
> > > Rohit
> > >
> > > On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
> > > David.Boyd@adesa.com> wrote:
> > >
> > > > I am having some issues with clustering an application with session
> > > > affinity enabled on Websphere Application Server.
> > > >
> > > >
> > > >
> > > > We are using:
> > > >
> > > >
> > > >
> > > > MyFace 1.1.7
> > > >
> > > > Tomahawk 1.1.5
> > > >
> > > > JDK 1.5
> > > >
> > > > WebSphere 7 - Fix Pack 13
> > > >
> > > >
> > > >
> > > > I am wondering if this is a known issue with this version of My
> Faces.
> > > >
> > > >
> > > >
> > > > What appears to be happening is that in the application, when a
> session
> > > > object is accesses and the data is changed, the change event is not
> > > > being triggered and therefore the change is not being pushed out to
> all
> > > > the servers in the cluster.
> > > >
> > > >
> > > >
> > > > It looks like this version of my faces is accessing the session
> object
> > > > via the getter but, it is making a change to the reference and
> > therefore
> > > > not calling the setter method.
> > > >
> > > >
> > > >
> > > > Looking for some confirmation on this issue or possible a
> configuration
> > > > that needs to be done.
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
Re: Issues with MyFaces and Clusters
Posted by Leonardo Uribe <lu...@gmail.com>.
Hi
2011/9/26 Boyd, David (Corporate) <Da...@adesa.com>
> So just to be clear
>
> 1. Based on the code snipit it appears that indeed myfaces is doing thing
> as expected.
>
>
Yes.
> 2. Are stating that the issue I am seeing is a know bug with Websphere 7?
> If so can you provide a link. I was searching the IBM site but did not
> have any success in locating any issue list.
>
>
I don't know if it is a known bug. All I can say is myfaces with other
servers in a cluster configuration work as expected, so I suppose based on
the evidence it is a bug on Websphere.
regards,
Leonardo
>
>
> Thanks
> -David Boyd
>
> (Sent via BlackBerry)
>
> ----- Original Message -----
> From: Leonardo Uribe [mailto:lu4242@gmail.com]
> Sent: Monday, September 26, 2011 09:47 PM
> To: MyFaces Discussion <us...@myfaces.apache.org>
> Subject: Re: Issues with MyFaces and Clusters
>
> Hi
>
> I have checked the latest code (and 1.1.7 code) and it seems to be correct.
> See:
>
>
> http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/jsp/JspStateManagerImpl.java
>
> the following lines:
>
> protected void saveSerializedViewInServletSession(FacesContext context,
> Object serializedView)
> {
> Map<String, Object> sessionMap =
> context.getExternalContext().getSessionMap();
> SerializedViewCollection viewCollection =
> (SerializedViewCollection) sessionMap
> .get(SERIALIZED_VIEW_SESSION_ATTR);
> if (viewCollection == null)
> {
> viewCollection = new SerializedViewCollection();
> sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
> }
> viewCollection.add(context, serializeView(context, serializedView));
> // replace the value to notify the container about the change
> sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
> }
>
> Look the last line that force the collection to be stored again on the
> session, to notify the container about the change. Maybe since the same
> instance is stored, by some reason WebSphere is not notifying the change
> and
> cause the problem you described. I think a workaround is create a custom
> state manager extending from myfaces one and writing something else on the
> session, but in practice it is a bug in WebSphere, so a fix should be done
> there.
>
> regards,
>
> Leonardo Uribe
>
> 2011/9/26 Rohit Kelapure <ke...@gmail.com>
>
> > David,
> >
> > Please take a look at
> >
> > Update All Session Attributes option - Horrible for performance, but
> fixes
> > issues like this.
> >
> >
> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
> >
> > --Thanks,
> > Rohit
> >
> > On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
> > David.Boyd@adesa.com> wrote:
> >
> > > I am having some issues with clustering an application with session
> > > affinity enabled on Websphere Application Server.
> > >
> > >
> > >
> > > We are using:
> > >
> > >
> > >
> > > MyFace 1.1.7
> > >
> > > Tomahawk 1.1.5
> > >
> > > JDK 1.5
> > >
> > > WebSphere 7 - Fix Pack 13
> > >
> > >
> > >
> > > I am wondering if this is a known issue with this version of My Faces.
> > >
> > >
> > >
> > > What appears to be happening is that in the application, when a session
> > > object is accesses and the data is changed, the change event is not
> > > being triggered and therefore the change is not being pushed out to all
> > > the servers in the cluster.
> > >
> > >
> > >
> > > It looks like this version of my faces is accessing the session object
> > > via the getter but, it is making a change to the reference and
> therefore
> > > not calling the setter method.
> > >
> > >
> > >
> > > Looking for some confirmation on this issue or possible a configuration
> > > that needs to be done.
> > >
> > >
> > >
> > > Thanks
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
Re: Issues with MyFaces and Clusters
Posted by Scott O'Bryan <da...@gmail.com>.
Actually Dave, I would follow Rohit's suggestion.
Leonardo, that's appears to be the state saving code. I think,
essentially, the issue is that when objects are modified, they need to
be set on the session again so that the container knows to
re-serialize them for failover.
AFAIK, there is no known failover issue with websphere provided these
attributes are re-set when the object is modified.
Sent from my iPhone
On Sep 26, 2011, at 7:59 PM, "Boyd, David (Corporate)"
<Da...@adesa.com> wrote:
> So just to be clear
>
> 1. Based on the code snipit it appears that indeed myfaces is doing thing as expected.
>
> 2. Are stating that the issue I am seeing is a know bug with Websphere 7? If so can you provide a link. I was searching the IBM site but did not have any success in locating any issue list.
>
>
>
> Thanks
> -David Boyd
>
> (Sent via BlackBerry)
>
> ----- Original Message -----
> From: Leonardo Uribe [mailto:lu4242@gmail.com]
> Sent: Monday, September 26, 2011 09:47 PM
> To: MyFaces Discussion <us...@myfaces.apache.org>
> Subject: Re: Issues with MyFaces and Clusters
>
> Hi
>
> I have checked the latest code (and 1.1.7 code) and it seems to be correct.
> See:
>
> http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/jsp/JspStateManagerImpl.java
>
> the following lines:
>
> protected void saveSerializedViewInServletSession(FacesContext context,
> Object serializedView)
> {
> Map<String, Object> sessionMap =
> context.getExternalContext().getSessionMap();
> SerializedViewCollection viewCollection =
> (SerializedViewCollection) sessionMap
> .get(SERIALIZED_VIEW_SESSION_ATTR);
> if (viewCollection == null)
> {
> viewCollection = new SerializedViewCollection();
> sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
> }
> viewCollection.add(context, serializeView(context, serializedView));
> // replace the value to notify the container about the change
> sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
> }
>
> Look the last line that force the collection to be stored again on the
> session, to notify the container about the change. Maybe since the same
> instance is stored, by some reason WebSphere is not notifying the change and
> cause the problem you described. I think a workaround is create a custom
> state manager extending from myfaces one and writing something else on the
> session, but in practice it is a bug in WebSphere, so a fix should be done
> there.
>
> regards,
>
> Leonardo Uribe
>
> 2011/9/26 Rohit Kelapure <ke...@gmail.com>
>
>> David,
>>
>> Please take a look at
>>
>> Update All Session Attributes option - Horrible for performance, but fixes
>> issues like this.
>>
>> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
>>
>> --Thanks,
>> Rohit
>>
>> On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
>> David.Boyd@adesa.com> wrote:
>>
>>> I am having some issues with clustering an application with session
>>> affinity enabled on Websphere Application Server.
>>>
>>>
>>>
>>> We are using:
>>>
>>>
>>>
>>> MyFace 1.1.7
>>>
>>> Tomahawk 1.1.5
>>>
>>> JDK 1.5
>>>
>>> WebSphere 7 - Fix Pack 13
>>>
>>>
>>>
>>> I am wondering if this is a known issue with this version of My Faces.
>>>
>>>
>>>
>>> What appears to be happening is that in the application, when a session
>>> object is accesses and the data is changed, the change event is not
>>> being triggered and therefore the change is not being pushed out to all
>>> the servers in the cluster.
>>>
>>>
>>>
>>> It looks like this version of my faces is accessing the session object
>>> via the getter but, it is making a change to the reference and therefore
>>> not calling the setter method.
>>>
>>>
>>>
>>> Looking for some confirmation on this issue or possible a configuration
>>> that needs to be done.
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
Re: Issues with MyFaces and Clusters
Posted by "Boyd, David (Corporate)" <Da...@adesa.com>.
So just to be clear
1. Based on the code snipit it appears that indeed myfaces is doing thing as expected.
2. Are stating that the issue I am seeing is a know bug with Websphere 7? If so can you provide a link. I was searching the IBM site but did not have any success in locating any issue list.
Thanks
-David Boyd
(Sent via BlackBerry)
----- Original Message -----
From: Leonardo Uribe [mailto:lu4242@gmail.com]
Sent: Monday, September 26, 2011 09:47 PM
To: MyFaces Discussion <us...@myfaces.apache.org>
Subject: Re: Issues with MyFaces and Clusters
Hi
I have checked the latest code (and 1.1.7 code) and it seems to be correct.
See:
http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/jsp/JspStateManagerImpl.java
the following lines:
protected void saveSerializedViewInServletSession(FacesContext context,
Object serializedView)
{
Map<String, Object> sessionMap =
context.getExternalContext().getSessionMap();
SerializedViewCollection viewCollection =
(SerializedViewCollection) sessionMap
.get(SERIALIZED_VIEW_SESSION_ATTR);
if (viewCollection == null)
{
viewCollection = new SerializedViewCollection();
sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
}
viewCollection.add(context, serializeView(context, serializedView));
// replace the value to notify the container about the change
sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
}
Look the last line that force the collection to be stored again on the
session, to notify the container about the change. Maybe since the same
instance is stored, by some reason WebSphere is not notifying the change and
cause the problem you described. I think a workaround is create a custom
state manager extending from myfaces one and writing something else on the
session, but in practice it is a bug in WebSphere, so a fix should be done
there.
regards,
Leonardo Uribe
2011/9/26 Rohit Kelapure <ke...@gmail.com>
> David,
>
> Please take a look at
>
> Update All Session Attributes option - Horrible for performance, but fixes
> issues like this.
>
> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
>
> --Thanks,
> Rohit
>
> On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
> David.Boyd@adesa.com> wrote:
>
> > I am having some issues with clustering an application with session
> > affinity enabled on Websphere Application Server.
> >
> >
> >
> > We are using:
> >
> >
> >
> > MyFace 1.1.7
> >
> > Tomahawk 1.1.5
> >
> > JDK 1.5
> >
> > WebSphere 7 - Fix Pack 13
> >
> >
> >
> > I am wondering if this is a known issue with this version of My Faces.
> >
> >
> >
> > What appears to be happening is that in the application, when a session
> > object is accesses and the data is changed, the change event is not
> > being triggered and therefore the change is not being pushed out to all
> > the servers in the cluster.
> >
> >
> >
> > It looks like this version of my faces is accessing the session object
> > via the getter but, it is making a change to the reference and therefore
> > not calling the setter method.
> >
> >
> >
> > Looking for some confirmation on this issue or possible a configuration
> > that needs to be done.
> >
> >
> >
> > Thanks
> >
> >
> >
> >
> >
> >
> >
> >
>
Re: Issues with MyFaces and Clusters
Posted by Leonardo Uribe <lu...@gmail.com>.
Hi
I have checked the latest code (and 1.1.7 code) and it seems to be correct.
See:
http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/jsp/JspStateManagerImpl.java
the following lines:
protected void saveSerializedViewInServletSession(FacesContext context,
Object serializedView)
{
Map<String, Object> sessionMap =
context.getExternalContext().getSessionMap();
SerializedViewCollection viewCollection =
(SerializedViewCollection) sessionMap
.get(SERIALIZED_VIEW_SESSION_ATTR);
if (viewCollection == null)
{
viewCollection = new SerializedViewCollection();
sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
}
viewCollection.add(context, serializeView(context, serializedView));
// replace the value to notify the container about the change
sessionMap.put(SERIALIZED_VIEW_SESSION_ATTR, viewCollection);
}
Look the last line that force the collection to be stored again on the
session, to notify the container about the change. Maybe since the same
instance is stored, by some reason WebSphere is not notifying the change and
cause the problem you described. I think a workaround is create a custom
state manager extending from myfaces one and writing something else on the
session, but in practice it is a bug in WebSphere, so a fix should be done
there.
regards,
Leonardo Uribe
2011/9/26 Rohit Kelapure <ke...@gmail.com>
> David,
>
> Please take a look at
>
> Update All Session Attributes option - Horrible for performance, but fixes
> issues like this.
>
> http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
>
> --Thanks,
> Rohit
>
> On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
> David.Boyd@adesa.com> wrote:
>
> > I am having some issues with clustering an application with session
> > affinity enabled on Websphere Application Server.
> >
> >
> >
> > We are using:
> >
> >
> >
> > MyFace 1.1.7
> >
> > Tomahawk 1.1.5
> >
> > JDK 1.5
> >
> > WebSphere 7 - Fix Pack 13
> >
> >
> >
> > I am wondering if this is a known issue with this version of My Faces.
> >
> >
> >
> > What appears to be happening is that in the application, when a session
> > object is accesses and the data is changed, the change event is not
> > being triggered and therefore the change is not being pushed out to all
> > the servers in the cluster.
> >
> >
> >
> > It looks like this version of my faces is accessing the session object
> > via the getter but, it is making a change to the reference and therefore
> > not calling the setter method.
> >
> >
> >
> > Looking for some confirmation on this issue or possible a configuration
> > that needs to be done.
> >
> >
> >
> > Thanks
> >
> >
> >
> >
> >
> >
> >
> >
>
Re: Issues with MyFaces and Clusters
Posted by Rohit Kelapure <ke...@gmail.com>.
David,
Please take a look at
Update All Session Attributes option - Horrible for performance, but fixes
issues like this.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Fuprs_rtuning_parameters.html
--Thanks,
Rohit
On Mon, Sep 26, 2011 at 3:09 PM, Boyd, David (Corporate) <
David.Boyd@adesa.com> wrote:
> I am having some issues with clustering an application with session
> affinity enabled on Websphere Application Server.
>
>
>
> We are using:
>
>
>
> MyFace 1.1.7
>
> Tomahawk 1.1.5
>
> JDK 1.5
>
> WebSphere 7 - Fix Pack 13
>
>
>
> I am wondering if this is a known issue with this version of My Faces.
>
>
>
> What appears to be happening is that in the application, when a session
> object is accesses and the data is changed, the change event is not
> being triggered and therefore the change is not being pushed out to all
> the servers in the cluster.
>
>
>
> It looks like this version of my faces is accessing the session object
> via the getter but, it is making a change to the reference and therefore
> not calling the setter method.
>
>
>
> Looking for some confirmation on this issue or possible a configuration
> that needs to be done.
>
>
>
> Thanks
>
>
>
>
>
>
>
>