Theme Builder Plugin

[All Adaptavist Apps]

Page tree

  • Created by Unknown User (webguy), last modified on Feb 26, 2009

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 (tongue)

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

  • No labels

6 Comments

  1. Unknown User (amoran)

    That definfitely sounds like something wrong with your install, what version of confluence have you upgraded from? Which application container are you using? Are you seeing any other exceptions in your logs? Can you attach a backup of your layout data?

    1. Unknown User (webguy)

      We're upgrading from 2.4.4 and using the bundled tomcat that comes with confluence 2.9.2, i.e. "stand-alone confluence" or confluence inside of tomcat from their tar file. Ha.

      1. Unknown User (amoran)

        What steps did you take when upgrading from 2.4? .. did you use any staging points or did you go straight to 2.9.2?

        1. Unknown User (webguy)

          We went straight to 2.9.2. I suppose it's not impossible we could have missed something but we followed the documentation from Atlassian. shrug

          1. Unknown User (hevans)

            Are you seeing any out of memory or heap errors in the logs? Out of interest is the indexing working?

            It may be better if you create a new issue on our customer support portal. https://tracker.adaptavist.com. That way we can ask for things like the logs without exposing them to the public.

            1. Unknown User (webguy)

              No out of memory errors in the logs but I am seeing some potential brokenness related to indexing (shows up in the logs, but not in the UI).

              Stuff like:

              2009-02-26 14:32:49,696 ERROR 3 confluence.plugin.descriptor.ExtractorModuleDescriptor addFields Unable to completely index page: OurContent Release Summary 03-12-08 v.13 (17957187).

              I'll do some more poking around and open a support ticket if we are still having issues after resolving the couple items in the logs.

              Thanks -

              Webguy