Logging from plugin framework does not get sent to log file, instead goes to standard error with unusual format

XMLWordPrintable

      Starting up Confluence 3.3 leads to the following output on standard error, instead of the normal log file:

      Jul 5, 2010 1:09:36 PM org.springframework.osgi.extender.internal.activator.ContextLoaderListener start
      INFO: Starting [org.springframework.osgi.extender] bundle v.[1.2.1]
      Jul 5, 2010 1:09:36 PM org.springframework.osgi.extender.internal.support.ExtenderConfiguration <init>
      INFO: Detected extender custom configurations at {bundle://2.0:0/META-INF/spring/extender/spring-event-bridge.xml}
      Jul 5, 2010 1:09:36 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh
      INFO: Refreshing org.springframework.osgi.context.support.OsgiBundleXmlApplicationContext@210a5750: display name [OsgiBundleXmlApplicationContext(bundle=org.springframework.osgi.extender, config=bundle://2.0:0/META-INF/spring/extender/spring-event-bridge.xml)]; startup date [Mon Jul 05 13:09:36 EST 2010]; root of context hierarchy
      Jul 5, 2010 1:09:36 PM org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext unpublishContextAsOsgiService
      INFO: Application Context service already unpublished
      Jul 5, 2010 1:09:36 PM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory
      INFO: Bean factory for application context [org.springframework.osgi.context.support.OsgiBundleXmlApplicationContext@210a5750]: org.springframework.beans.factory.support.DefaultListableBeanFactory@1201f5bc
      Jul 5, 2010 1:09:36 PM org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext publishContextAsOsgiServiceIfNecessary
      INFO: Publishing application context as OSGi service with properties {org.springframework.context.service.name=org.springframework.osgi.extender, Bundle-SymbolicName=org.springframework.osgi.extender, Bundle-Version=1.2.1}
      Jul 5, 2010 1:09:36 PM org.springframework.scheduling.timer.TimerTaskExecutor afterPropertiesSet
      INFO: Initializing Timer
      

      This is caused by https://studio.atlassian.com/browse/PLUG-616. There is more information on that issue about the cause and possible solutions.

              Assignee:
              Unassigned
              Reporter:
              Matt Ryall
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: