Re: Session replication will never happen after disabling session persistence across Tomcat restarts

[Keiichi Fujino]

2016-04-23 15:29 GMT+09:00 sanigo :

> Hi!
>I have tested quite a few times to confirm that session replication
> will not happen after uncommenting  in
> conf/context.xml.
>If the line is commented out, the session replication will work
> happily.
>

Is there a warning message to your log files?
such as [Manager [xxx] does not implement ClusterManager, addition to
cluster has been aborted.]

if you have uncommented  in conf/context.xml,
All of the Web applications on your Tomcat use the StandardManager as a
session manager.
The StandardManager cannot replicate session.
If you want to replicate session, you have to use
ClusteManager(DeltaManager/BackupManager) as a session manager.
Usually defines a cluster manager template in the  / ,
and then it is cloned by distributable web application.




>The versions I have tested are 7.0.68 and 7.0.69.
>Any ideas?
> san...@gmail.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
> --
> Keiichi.Fujino
> 

Re: Tomcat 9.0.0-M4 seems not to start digest algorithm on JDBC Realm as did tomcat 8.0.25

[Fabio Ricci]

appreciate the sunday answer (thank you).

To say the truth: I did read the documentation and the migration guide.
But since there are no examples in 
http://tomcat.apache.org/tomcat-8.0-doc/config/credentialhandler.html, I did 
not manage to create my own implementation concreteness. That’s why I deared to 
ask the community.

Thanks
F.


> On 24 Apr 2016, at 17:31, Mark Thomas  wrote:
> 
> On 22/04/2016 23:35, Fabio Ricci wrote:
>> Dear tomcat Community
>> 
>> I am using cross context (which seems to be easy to configure but in in
>> tomcat 8 hard to run) … so today I downloaded tomcat 9 and I migrated my
>> apps to it.
>> In tomcat 9 cross context is running smoothly (thank you!)
>> 
>> To authenticate my config is using JDBCRealm with a mysql database. The
>> config below ran very well with tomcat 8 but on tomcat 9 accepted only
>> the password digests (which are stored in the table tomcat_users)
>> directly instead of the usual passwords. It seems that the digest
>> algorithm MD5 be here not executed.
> 
> Given that the digest attribute doesn't exist on the Realm in 9.0.x,
> that behaviour is as expected.
> 
> You should read the migration guide:
> 
> http://tomcat.apache.org/migration-9.html#Migrating_from_8.0.x_to_9.0.x/Internal_APIs
> 
> If you had read the 8.0.x docs, you wouldn't have been using a
> deprecated configuration option...
> 
> http://tomcat.apache.org/tomcat-8.0-doc/config/realm.html#Common_Attributes
> 
> ... you would have been using the replacement configuration option.
> 
> http://tomcat.apache.org/tomcat-8.0-doc/config/credentialhandler.html
> 
> 
> Mark
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Tomcat 9.0.0-M4 seems not to start digest algorithm on JDBC Realm as did tomcat 8.0.25

[Mark Thomas]

On 22/04/2016 23:35, Fabio Ricci wrote:
> Dear tomcat Community
> 
> I am using cross context (which seems to be easy to configure but in in
> tomcat 8 hard to run) … so today I downloaded tomcat 9 and I migrated my
> apps to it.
> In tomcat 9 cross context is running smoothly (thank you!)
> 
> To authenticate my config is using JDBCRealm with a mysql database. The
> config below ran very well with tomcat 8 but on tomcat 9 accepted only
> the password digests (which are stored in the table tomcat_users)
> directly instead of the usual passwords. It seems that the digest
> algorithm MD5 be here not executed.

Given that the digest attribute doesn't exist on the Realm in 9.0.x,
that behaviour is as expected.

You should read the migration guide:

http://tomcat.apache.org/migration-9.html#Migrating_from_8.0.x_to_9.0.x/Internal_APIs

If you had read the 8.0.x docs, you wouldn't have been using a
deprecated configuration option...

http://tomcat.apache.org/tomcat-8.0-doc/config/realm.html#Common_Attributes

... you would have been using the replacement configuration option.

http://tomcat.apache.org/tomcat-8.0-doc/config/credentialhandler.html


Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org