-
Bug
-
Resolution: Won't Fix
-
High
-
None
-
1.0 Alpha2
After your latest commits, although it seems to work fine but I still get the following exception on server log, while upgrading from Alpha1 to Alpha2 for the first time. Then if I down the server and have it up again, no exception will be on server console.
Other than this problem, everything seems to be fine (here locally on HSQL database).
[java] 2003-10-23 18:46:36,842 ERROR [sf.hibernate.util.XMLHelper] Error parsing XML: hibernate.cfg.xml(27)
[java] org.xml.sax.SAXParseException: The content of element type "session-factory" must match "(property*,mapping+, (class-cache|collection-cache|jcs-class-cache|jcs-collection-cache)*)".
[java] at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unkno
wn Source)
[java] at
org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
[java] at
org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
[java] at
org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
[java] at
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown
Source)
[java] at
org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
[java] at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
[java] at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis
patcher.dispatch(Unknown Sour
ce)
[java] at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno
wn Source)
[java] at
org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
[java] at
org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
[java] at org.apache.xerces.parsers.XMLParser.parse(Unknown
Source)
[java] at
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
[java] at org.dom4j.io.SAXReader.read(SAXReader.java:339)
[java] at
net.sf.hibernate.cfg.Configuration.configure(Configuration.java:818)
[java] at
net.sf.hibernate.cfg.Configuration.configure(Configuration.java:765)
[java] at
com.atlassian.confluence.setup.ConfluenceHibernateSetup.getConfluenceHib
ernateConfiguration(Confluenc
eHibernateSetup.java:68)
[java] at
com.atlassian.confluence.upgrade.impl.Build28UpgradeTask.dropUniquenessC
onstraintFromAttachmentFileNa
me(Build28UpgradeTask.java:163)
[java] at
com.atlassian.confluence.upgrade.impl.Build28UpgradeTask.doUpgrade(Build
28UpgradeTask.java:52)
[java] at
com.atlassian.confluence.upgrade.UpgradeLauncher.doUpgrade(UpgradeLaunch
er.java:48)
[java] at
com.atlassian.confluence.upgrade.UpgradeLauncher.doUpgrade(UpgradeLaunch
er.java:27)
[java] at
com.atlassian.confluence.upgrade.UpgradeLauncherServletContextListener.c
ontextInitialized(UpgradeLaun
cherServletContextListener.java:27)
[java] at
com.caucho.server.http.Application.init(Application.java:1843)
[java] at
com.caucho.server.http.VirtualHost.init(VirtualHost.java:728)
[java] at
com.caucho.server.http.ServletServer.initHosts(ServletServer.java:874)
[java] at
com.caucho.server.http.ServletServer.initInternal(ServletServer.java:719
)
[java] at
com.caucho.server.http.ServletServer.init(ServletServer.java:530)
[java] at
com.caucho.server.http.ResinServer.init(ResinServer.java:393)
[java] at
com.caucho.server.http.ResinServer.main(ResinServer.java:1154)
[java] at
com.caucho.server.http.HttpServer.main(HttpServer.java:103)
[java] 2003-10-23 18:46:39,217 WARN [sf.hibernate.impl.SessionFactoryObjectFactory] InitialContext did not implement EventContext
[java] http listening to *:8080
[java] MailQueueFlushJob.MailQueueFlushJob
[CONFSERVER-260] Upgrading from A1 to A2 throws exception...
Ara Abrahamian
added a comment - VerifyError, hmm, looks like a configuration problem to me, possibly older version of hibernate or something like that in classpath. It might be caused by class reloading bugs in app server too. Try restarting the server and make sure all of Confluence's dependencies are correctly resolved.
Btw alpha2 supports automatic upgrade. So you just drop a2 in the server and restart it. Upon starting the web app it should upgrade everything, just like Jira.
Ara.
Ara Abrahamian
added a comment - VerifyError, hmm, looks like a configuration problem to me, possibly older version of hibernate or something like that in classpath. It might be caused by class reloading bugs in app server too. Try restarting the server and make sure all of Confluence's dependencies are correctly resolved.
Btw alpha2 supports automatic upgrade. So you just drop a2 in the server and restart it. Upon starting the web app it should upgrade everything, just like Jira.
Ara. I get a different error, strange enought it's a verifier error...
10.11.2003 11:33:36 net.sf.hibernate.cfg.Configuration configure
INFO: Configured SessionFactory: /jndi/ConfluenceSessionFactory
2003-11-10 11:33:36,557 ERROR [atlassian.confluence.upgrade.UpgradeLauncher] Exc
eption thrown during upgrade: (class: com/atlassian/confluence/persistence/hiber
nate/HibernateSessionFactory, method: reset signature: ()V) Incompatible object
argument for function call
java.lang.VerifyError: (class: com/atlassian/confluence/persistence/hibernate/Hi
bernateSessionFactory, method: reset signature: ()V) Incompatible object argumen
t for function call
at com.atlassian.confluence.persistence.hibernate.HibernateThreadLocal.g
etSession(HibernateThreadLocal.java:29)
at com.atlassian.confluence.persistence.hibernate.AbstractHibernatePersi
stence.getSession(AbstractHibernatePersistence.java:42)
at com.atlassian.confluence.upgrade.impl.AbstractConfluenceUpgradeTask.g
etSession(AbstractConfluenceUpgradeTask.java:40)
at com.atlassian.confluence.upgrade.impl.Build28UpgradeTask.dropUniquene
ssConstraintFromAttachmentFileName(Build28UpgradeTask.java:165)
at com.atlassian.confluence.upgrade.impl.Build28UpgradeTask.doUpgrade(Bu
ild28UpgradeTask.java:52)
at com.atlassian.confluence.upgrade.UpgradeLauncher.doUpgrade(UpgradeLau
ncher.java:48)
at com.atlassian.confluence.upgrade.UpgradeLauncher.doUpgrade(UpgradeLau
ncher.java:27)
at com.atlassian.confluence.upgrade.UpgradeLauncherServletContextListene
r.contextInitialized(UpgradeLauncherServletContextListener.java:27)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContex
t.java:3270)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3
599)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347
)
at org.apache.catalina.core.StandardService.start(StandardService.java:4
97)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:219
0)
at org.apache.catalina.startup.Catalina.start(Catalina.java:512)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
[Filter: profiling] Using parameter [profile]
[Filter: profiling] defaulting to on [autostart=true]
[Filter: profiling] Turning filter on [profile=on]
10.11.2003 11:33:36 com.opensymphony.webwork.views.velocity.VelocityManager load
Configuration
INFO: Initializing velocity using 'velocity.properties'
So how is upgradeing done?
There was nothin in the release notes... Or did I just missed it?
– Ingomar
Ara Abrahamian
added a comment - It's been fixed.
Ara. 
I'll give it a shot...