JSESSIONIDcookie used to track sessions differently:
JSESSIONIDper web application, with the cookie path set to the context of the application. When an application invalidates the session, Tomcat sends a new
JSESSIONIDto the browser.
JSESSIONIDwith cookie path
/for all the applications. This cookie doesn't change when a session is invalidated, and hence there is no one-to-one mapping between a
JSESSIONIDcookie and a session in WebLogic.
/myappwith Tomcat. Tomcat sets a
/myappwith WebLogic. Tomcat sets a
JSESSIONIDas it is more specific (for
/myappinstead of just
/), but WebLogic doesn't recognize it, hence the error you're getting.
JSESSIONIDcookies for the host you are trying to access.
utf8_unicode_cicollation instead of the default
utf8_bin, and fixes this issue (#1607). Note that no data was lost; data was always safe in the database, and this only impacted how it was shown on the summary page. The [MySQL DDL for Orbeon Forms 4.5][mysql-45-ddl] has been updated after the 4.5 release, so if you're today installing Orbeon Forms 4.5, you can safely use that DDL and don't need to run the above commands.