Joseph Fialli wrote:
> glassfish_at_javadesktop.org wrote:
>> Thaks for you reply.
>>
>
>> The scene just like this:
>> deploy the app to instance in a cluster, set availablity = true.
>>
> The app should be deployed to all instances in the cluster.
> I will assume that step was done correctly.
>> In a page, i display the sessionid from server. when refresh the page
>> quickly by IE's or Firefox's toolbar or menu, you'll find that
>> sometimes the sessionid value is changed, sometimes it is unchanged.
>>
> Your scenario does not describe stopping or killing the instance, so
> am I to assume that you are not attempting to verify failover of
> http-session data from a failed instance to replicated version of the
> sesssion data in the cluster.
>
> If you truely are not testing failover finding replicated data, it
> would be interesting to repeat your test w/o availability enabled
>
>> And you may find glassfish's log like:
>> the sessionid's Expired is set true, and then the sessionid's Expired
>> is set false.
>>
> It would assist this effort to submit an issue to glassfish issues
> with a server.log recording the issue you are observing
> and step by step description of the observed failure. (Be careful to
> mention browser and version of browser involved in issue.)
Here is link to location to report the issue (you must be logged into
glassfish.dev.java.net to be able to report issues at this link)
https://glassfish.dev.java.net/issues/enter_bug.cgi?issue_type=DEFECT.
Subcomponent "failover"
After you have reported the issue, you can attach files to the report.
Please attach server.log for
server instance(s) involved in this scenario. Server logs can be
found under
<glassfish-install>/node-agents/<node-agent-name>/<instanceName>/logs/server*.log.
Additionally, since you think the issue has to do with premature expiration.
If multiple machines are involved, be sure to verify that the time for
the machines are synchronized.
Time skew exceeding the expiration range could explain premature
expiration of session information.
-Joe
>
> Could you enable FINE debugging for availability following these steps.
>
> Add property com.sun.enterprise.ee.web.sessmgmt to "FINE" Module Log
> Level for cluster configuration.
> Here are precise steps for clusterjsp example.
> Steps to enable:
> Setup: In AppServer Admin Console running under a web browser:
> (Only have the DAS running, do not start cluster yet.)
> 1. Select "Clusters" under "Common Tasks" in left pane.
> 2. For the appropriate cluster listed in right pane of Admin Console,
> click on appropriate "Configuration".
> 3. Right pane for my case has "Configurations > cluster1-config" at
> this point.
> Select "Logger Settings" from this pane.
> 4. Select tab named "Log Levels" under "Configurations >
> cluster1-config > Logger Settings".
> 5. Under "Additional Properties" at bottom of tab labeled "Module Log
> Levels" (on my browser, I
> have to scroll to bottom.),
> click [Add Property] button.
> - Under "Name" field add:
> com.sun.enterprise.ee.web.sessmgmt
> - Under "Value" field add:
> FINE
> 6. At top of "Module Log Levels" tab, select [SAVE].
> 7. When cluster is restarted, the ha in-memory logging level property
> will be propagated to each
> instance.
>
>
> -Joe Fialli, Sun Microsystems
>
>> http://forums.java.net/jive/thread.jspa?threadID=32742&tstart=15
>> [Message sent by forum member 'hanjingdi' (hanjingdi)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=243996
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>