[#JRA-8597] XSLT-based upgrade task fails in OC4J: XSL-1900: (Fatal Error) An internal error condition occurred.

JIRA

XSLT-based upgrade task fails in OC4J: XSL-1900: (Fatal Error) An internal error condition occurred.

Created: 21/Nov/05 06:23 PM Updated: 23/Nov/06 11:35 PM

Component/s:

Documentation

Affects Version/s:

3.3

Fix Version/s:

3.5

Time Tracking:

Original Estimate:

Remaining Estimate:

Time Spent:

Not Specified

Environment:

OC4J 9.0.4 and 10.1.2.0.2

Participants:	Anton Mazkovoi [Atlassian], Dylan Etkin [Atlassian] and Jeff Turner [Atlassian]
Since last comment:	2 years, 31 weeks, 6 days ago
Resolution Date:	10/Jan/06 05:11 PM
Labels:

Description

« Hide

When importing or upgrading old data into JIRA 3.3+, it looks like saved filters are not updated to the new search format:

2005-11-22 11:17:01,924 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 93
2005-11-22 11:17:01,929 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Upgrade search request XML new format which allows dynamically loading of the group parameter every time

XSL-1900: (Fatal Error) An internal error condition occurred.
2005-11-22 11:17:01,968 ERROR [jira.upgrade.util.UsersGroupParamConverter] Error converting searchrequest document org.dom4j.tree.DefaultDocument@1d5e0b3 [Document: name null] returning original search request
2005-11-22 11:17:01,970 INFO [jira.upgrade.tasks.AbstractSearchRequestUpgradeTask] Upgraded search request Component: Advance
XSL-1900: (Fatal Error) An internal error condition occurred.
2005-11-22 11:17:01,976 ERROR [jira.upgrade.util.UsersGroupParamConverter] Error converting searchrequest document org.dom4j.tree.DefaultDocument@1c3f452 [Document: name null] returning original search request
2005-11-22 11:17:01,978 INFO [jira.upgrade.tasks.AbstractSearchRequestUpgradeTask] Upgraded search request Component: Candidature

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Jeff Turner [Atlassian] added a comment - 21/Nov/05 06:54 PM

This problem can be avoided by starting JIRA with an extra parameter, forcing the use of the Saxon XSLT engine bundled with JIRA:

java -Djavax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryImpl -jar oc4j.jar -userThreads

[ Permalink | « Hide ]

Jeff Turner [Atlassian] added a comment - 21/Nov/05 07:15 PM

It appears Oracle are aware of this bug:

http://forums.oracle.com/forums/message.jspa?messageID=332988

[ Permalink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 20/Dec/05 12:25 AM

If the bug is not resolved I guess we nee dto update the docs about this.

[ Permalink | « Hide ]

Dylan Etkin [Atlassian] added a comment - 10/Jan/06 05:11 PM

Jeff fixed this up in the docs.

[ Permalink | « Hide ]

Jeff Turner [Atlassian] added a comment - 23/Nov/06 11:35 PM

FWIW, the same problem affects OC4J 10.1.3.1.0:

XML-22900: (Fatal Error) An internal error condition occurred.
2006-11-24 16:33:44,505 ERROR [jira.upgrade.util.UsersGroupParamConverter] Error converting searchrequest document org.dom4j.tree.DefaultDocument@13f25e3 [Document: name null] returning original search request