Theme Builder

Hello -

We have are trying to use the Builder Plugin v3.3.3 on a recently upgraded copy of:

• Confluence 2.9.2 on
• CentOS 4.7
• MySQL 5.0.67
• jdk1.5.0_17

We are testing out the builder plugin to see if it will work for us, but we're seeing stack traces sometimes.  What's really awful is that we can disable the plugin and re-enable it and the stack traces go away (for a while?).  The stack traces show up in the logs as:

2009-02-26 11:07:19,430 ERROR [http-8080-Processor4] [opensymphony.webwork.dispatcher.ServletDispatcher] serviceAction Could not execute action

- url: /display/somespace/Home | userName: validuser

org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only
        at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:626)
        at com.atlassian.xwork.interceptors.XWorkTransactionInterceptor.intercept(XWorkTransactionInterceptor.java:131)
        at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
        at com.atlassian.confluence.xwork.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:56)
        at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
        at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:35)
        at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:165)
        at com.opensymphony.xwork.DefaultActionProxy.execute(DefaultActionProxy.java:115)
        at com.opensymphony.webwork.dispatcher.ServletDispatcher.serviceAction(ServletDispatcher.java:229)
        at com.opensymphony.webwork.dispatcher.ServletDispatcher.service(ServletDispatcher.java:199)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

...

Does anyone have any insight into why this might be happening?  The stack traces go away if the plugin is disabled altogether or is disabled and then re-enabled

We don't want to use/buy the plugin if this is the kind of behavior we can expect from it.  Hopefully there is something minor wrong with the install and we just missed something.

Please help and thanks -

Webguy