users@glassfish.java.net

Re: In memory session management Problem

From: Naveen Kumar G N <Naveen.Kumar_at_Sun.COM>
Date: Tue, 09 Jun 2009 09:43:49 +0530

Hi Larry,

  Version = Sun GlassFish Enterprise Server v2.1

  Added <|distributable|/> Tag in web.xml

  Added following in sun-web.xml
    <session-manager persistence-type="replicated">
  <manager-properties>
  <property name="persistenceFrequency" value="web-method"/>
  </manager-properties>
  <store-properties>
  <property name="persistenceScope" value="session"/>
  </store-properties>
  </session-manager>
  <session-properties/>
  <cookie-properties/>
  </session-config>

Enabled availability during deployment

Are all the instances of your cluster on the same subnet? Yes.

Regards
Naveen


 
Larry White wrote:
> Hi Naveen:
>
> Could you please provide more information about your problem.
>
> What version of the Application server are you using?
> What steps have you followed in setting up your environment
> and deploying the app - you said:
> "I have done all the changes requried for inmemory session management"
> so if you want you can provide the list of steps you were working from.
> Have you tried the first step of using the sample clusterjsp app to
> see if that
> works in your environment?
> Are all the instances of your cluster on the same subnet?
>
> These are some of the questions that are important in resolving your
> problems.
>
> hope this helps
>
>
> Naveen Kumar G N wrote:
>> Hi,
>>
>> I have deployed the Application in cluster environment and I have
>> done all the changes requried for inmemory session management.
>>
>> But Session failure is not happening, Attached the log file.
>>
>> [#|2009-06-08T12:23:34.433+0530|INFO|sun-appserver2.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=27;_ThreadName=ReplicationSenderExecutor
>> - 10;|IOException sending message
>> java.io.IOException: Messenger was closed, it cannot be used to send
>> messages.
>> at
>> net.jxta.impl.endpoint.tcp.TcpMessenger.sendMessageDirect(TcpMessenger.java:535)
>>
>> at net.jxta.util.JxtaBiDiPipe.sendMessage(JxtaBiDiPipe.java:1036)
>> at
>> com.sun.enterprise.ee.web.sessmgmt.JxtaReplicationSender.sendOverPipe(JxtaReplicationSender.java:754)
>>
>> at
>> com.sun.enterprise.ee.web.sessmgmt.JxtaReplicationSender.sendState(JxtaReplicationSender.java:2078)
>>
>> at
>> com.sun.enterprise.ee.web.sessmgmt.JxtaReplicationSender.sendState(JxtaReplicationSender.java:2058)
>>
>> at
>> com.sun.enterprise.ee.web.sessmgmt.JxtaReplicationSender.sendBulkMessage(JxtaReplicationSender.java:2128)
>>
>> at
>> com.sun.enterprise.ee.web.sessmgmt.JxtaReplicationSender.createMessageAndSend(JxtaReplicationSender.java:2050)
>>
>> at
>> com.sun.enterprise.ee.web.sessmgmt.JxtaReplicationSender.access$1300(JxtaReplicationSender.java:97)
>>
>> at
>> com.sun.enterprise.ee.web.sessmgmt.JxtaReplicationSender$BulkMessageSender.run(JxtaReplicationSender.java:2335)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>>
>> at java.lang.Thread.run(Thread.java:595)
>> |#]
>>
>> Thanks in advance
>>
>> Regards
>> Naveen
>