Re: [enhydra] Re: jvmRoute effect on JSESSIONID

Hi,
  Thanks for your hints. I'm using
'com.lutris.appserver.server.sessionContainerAdapter.JmxContainerAdapterSessionManager'
for now (with Enhydra 6.4-1) and it seems to be working fine.
  Since we're already in the final stages of deployment of our webapp
and we've settled for Enhydra 6.4-1, are there any particular reasons to
switch to
'com.lutris.appserver.server.sessionContainerAdapter.TomcatContainerAdapterSessionManager'
(in particular, any known problems with
'JmxContainerAdapterSessionManager' that don't apply to
'TomcatContainerAdapterSessionManager')?
  If so, and we decide to switch to EAF 6.5-1, what is the best way to
replace the EAF of an existing Enhydra 6.4-1 installation? Is it OK to
just overwrite the contents of multiserver/enhydra/lib/ with the
contents of the lib/ that comes with the EAF 6.5-1 binary distribution?

  Best regards,

    -- Edgar Alves

Slobodan Vujasinovic wrote:

> Hi,
>
> you can try with using
> 'com.lutris.appserver.server.sessionContainerAdapter.ContainerAdapterSessionManager'
> or
> 'com.lutris.appserver.server.sessionContainerAdapter.JmxContainerAdapterSessionManager'
> 'SessionManager' implementations.
>
> The new EAF 6.5-1 release (it is included in new Enhydra 6.5-1 that is
> going to be released in days now) offers additional implementation: 
> 'com.lutris.appserver.server.sessionContainerAdapter.TomcatContainerAdapterSessionManager'
>
> This is also (as 'JmxContainerAdapterSessionManager') extension of
> 'ContainerAdapterSessionManager' implementation but with improved
> Tomcat SessionManager wrapping.
>
> My recommendation is to use new 'TomcatContainerAdapterSessionManager'
> implementation!
>
> You can use 'JmxContainerAdapterSessionManager' or
> 'ContainerAdapterSessionManager' for now and migrate to
> 'TomcatContainerAdapterSessionManager' in few days or to download EAF
> 6.5-1 and include its binaries in existing Enhydra Server installation
> (runtime binaries are placed in
> '<enhydra_root>/multiserver/shared/lib' directory and development in
> '<enhydra_root>/multiserver/enhydra/lib').
>
> Regards,
>  Slobodan Vujasinovic
> Enhydra Development Team
>
>
>
> Edgar Alves wrote:
>
>>  I've found out what was wrong. The configuration for the webapp
>> (WEB-INF/web.xml) was specifiying the Enhydra session manager as session
>> manager. This session manager seems to be ignoring the jvmRoute Engine
>> attribute. Can the Enhydra session manager be configured to use the
>> jvmRoute attribute?
>>  If not, my best bet at this point is using
>> com.lutris.appserver.server.sessionContainerAdapter.JmxContainerAdapterSessionManager
>>
>> as the session manager. Any loss of functionality or/and
>> incompatibilities that I should look for if I do so?
>>
>>    -- Edgar Alves
>>
>> ealves@xxxxxxxxxxxx wrote:
>>
>>  
>>
>>> Hi again,
>>> I've verified correct behaviour using the jsp-examples/sessions/cart
>>> example. Having configured jvmRoute="dummy1" in server.xml, here's
>>> an example JSESSIONID: "3F00C9699C9D22B837B821D2BB4DC941.dummy1".
>>> However, running a complex in-house webapp inside the same Enhydra
>>> instance, I get this JSESSIONID: "ek5wgK-P76S_VblgeQMYnIvJ".
>>> I've checked the configuration for the application and everything
>>> seems to be OK. Any ideas?
>>>
>>>   -- Edgar Alves
>>>




--
You receive this message as a subscriber of the enhydra@xxxxxxxxxxxxx mailing 
list.
To unsubscribe: mailto:enhydra-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws