RE: Persist object fails
Thank you all for your answers. After querying for the jsessionid value it is found that we have a new value per request. And that seems to break the persist mechanism at the tomcat level. We will go for a solution to change this behavior. And check afterwards. Thank you all!
VS: Persist object fails
I can also report 4 production systems running on Server Java 7 (The new option, server jdk) and tomcats. Ville -Alkuperäinen viesti- Lähettäjä: Bob Harner [mailto:bobhar...@gmail.com] Lähetetty: 7. maaliskuuta 2014 15:34 Vastaanottaja: Tapestry users Aihe: Re: Persist object fails I know of many cases of Tapestry 5.3.x web apps running on Java 1.7 and Tomcat in production. No problems, as long as the version of Tomcat chosen is Java 1.7-compatible. On Mar 6, 2014 5:28 PM, "Cezary Biernacki" wrote: > Tapestry uses Servlet API to persist data, so if they are not > persisted, something wrong is with your Tomcat configuration. I would > first check if JSESSIONID cookies are generated properly and they stay > unchanged in a single session (or alternatively ';jsessionid=' is > added to URLs). Then I would check Tomcat configuration and Tomcat > logs. See how your Tomcat is configured to store sessions. If you use > load balancing or put the Tomcat instance behind a reverse proxy, I > would recommend checking how they are configured. > > If you would still could not solve your problem, I recommend writing a > very simple servlet without Tapestry or any other framework, with > simple session related test, and see if it works correctly on your new > installation. If it would not work too, try to get help on some Tomcat related forum. > > I migrated a Tapestry 5.3 application from Java 6 to Java 7 without > any changes, though I have not used Tomcat. > > Best regards, > Cezary > > > > > On Wed, Mar 5, 2014 at 5:05 PM, Trimech, Fethi > >wrote: > > > Hi Tapestry users, > > > > > > > > We are currently migrating our tapestry application to a new server > > using java 1.7. the application was running smoothly until this > > migration where most the features in the application broke down. > > After analysis we found out that all objects annotated with @Persist > > and @SessionState are no longer persisted. > > > > > > > > btw: > > > > same Tomcat version > > > > same OS > > > > using tapetsry 5.3.6 and related jars. > > > > (gave a try to 5.3.7 but also failed) > > > > > > > > does it have todo with the java version or something else? any hint > > would be of great help! > > > > > > > > Thanks! > > > > > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Persist object fails
I know of many cases of Tapestry 5.3.x web apps running on Java 1.7 and Tomcat in production. No problems, as long as the version of Tomcat chosen is Java 1.7-compatible. On Mar 6, 2014 5:28 PM, "Cezary Biernacki" wrote: > Tapestry uses Servlet API to persist data, so if they are not persisted, > something wrong is with your Tomcat configuration. I would first check if > JSESSIONID cookies are generated properly and they stay unchanged in a > single session (or alternatively ';jsessionid=' is added to URLs). Then I > would check Tomcat configuration and Tomcat logs. See how your Tomcat is > configured to store sessions. If you use load balancing or put the Tomcat > instance behind a reverse proxy, I would recommend checking how they are > configured. > > If you would still could not solve your problem, I recommend writing a very > simple servlet without Tapestry or any other framework, with simple session > related test, and see if it works correctly on your new installation. If it > would not work too, try to get help on some Tomcat related forum. > > I migrated a Tapestry 5.3 application from Java 6 to Java 7 without any > changes, though I have not used Tomcat. > > Best regards, > Cezary > > > > > On Wed, Mar 5, 2014 at 5:05 PM, Trimech, Fethi >wrote: > > > Hi Tapestry users, > > > > > > > > We are currently migrating our tapestry application to a new server using > > java 1.7. the application was running smoothly until this migration where > > most the features in the application broke down. After analysis we found > > out that all objects annotated with @Persist and @SessionState are no > > longer persisted. > > > > > > > > btw: > > > > same Tomcat version > > > > same OS > > > > using tapetsry 5.3.6 and related jars. > > > > (gave a try to 5.3.7 but also failed) > > > > > > > > does it have todo with the java version or something else? any hint would > > be of great help! > > > > > > > > Thanks! > > > > >
Re: Persist object fails
Tapestry uses Servlet API to persist data, so if they are not persisted, something wrong is with your Tomcat configuration. I would first check if JSESSIONID cookies are generated properly and they stay unchanged in a single session (or alternatively ';jsessionid=' is added to URLs). Then I would check Tomcat configuration and Tomcat logs. See how your Tomcat is configured to store sessions. If you use load balancing or put the Tomcat instance behind a reverse proxy, I would recommend checking how they are configured. If you would still could not solve your problem, I recommend writing a very simple servlet without Tapestry or any other framework, with simple session related test, and see if it works correctly on your new installation. If it would not work too, try to get help on some Tomcat related forum. I migrated a Tapestry 5.3 application from Java 6 to Java 7 without any changes, though I have not used Tomcat. Best regards, Cezary On Wed, Mar 5, 2014 at 5:05 PM, Trimech, Fethi wrote: > Hi Tapestry users, > > > > We are currently migrating our tapestry application to a new server using > java 1.7. the application was running smoothly until this migration where > most the features in the application broke down. After analysis we found > out that all objects annotated with @Persist and @SessionState are no > longer persisted. > > > > btw: > > same Tomcat version > > same OS > > using tapetsry 5.3.6 and related jars. > > (gave a try to 5.3.7 but also failed) > > > > does it have todo with the java version or something else? any hint would > be of great help! > > > > Thanks! > >
Persist object fails
Hi Tapestry users, We are currently migrating our tapestry application to a new server using java 1.7. the application was running smoothly until this migration where most the features in the application broke down. After analysis we found out that all objects annotated with @Persist and @SessionState are no longer persisted. btw: same Tomcat version same OS using tapetsry 5.3.6 and related jars. (gave a try to 5.3.7 but also failed) does it have todo with the java version or something else? any hint would be of great help! Thanks!
