[
https://issues.apache.org/jira/browse/WOOKIE-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778804#action_12778804
]
Scott Wilson commented on WOOKIE-63:
------------------------------------
Hi Anton, this problem is caused by the Tomcat Security Manager. If you run
tomcat using:
catalina.sh start -security
Then it starts up applying its default policies.
If you start up Tomcat without Security Manager running (e.g. for development)
then you won't get this error.
To run Wookie on Tomcat with Security Manager active you need to edit
catalina.policy and grant permissions for everything Wookie wants to do (use
JDBC, connect to MySQL, run JSPs etc.)
I'll add this to the FAQ
> HibernateException: flush is not valid without active transaction
> -----------------------------------------------------------------
>
> Key: WOOKIE-63
> URL: https://issues.apache.org/jira/browse/WOOKIE-63
> Project: Wookie
> Issue Type: Bug
> Components: Server
> Environment: Ubuntu 9.10 x86, Apache Tomcat 6.0.20, MySQL 5.1
> Reporter: Anton Zolotarjov
> Priority: Blocker
>
> Build for use with MySQL and Tomcat went fine with no errors, and the Wookie
> Widget Server is shown in the Tomcat Web Application Manager. However, on
> trying to access http://localhost/wookie or
> http://localhost:8080/wookie/admin this exception is thrown:
> org.hibernate.HibernateException: flush is not valid without active
> transaction
> org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:338)
> $Proxy0.flush(Unknown Source)
>
> org.apache.wookie.util.hibernate.impl.DBManagerImpl.closeSession(DBManagerImpl.java:72)
> org.apache.wookie.server.MainFilter.doFilter(MainFilter.java:60)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:597)
> org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:269)
> java.security.AccessController.doPrivileged(Native Method)
> javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
> org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:301)
>
> org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:243)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
