[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1707) pageflow parsing is slow
Ronald van Kuijk (JIRA)
jira-events at lists.jboss.org
Wed Jan 27 15:50:19 EST 2010
[ https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12508819#action_12508819 ]
Ronald van Kuijk commented on JBPM-1707:
----------------------------------------
@Tihomir
Yes
> pageflow parsing is slow
> ------------------------
>
> Key: JBPM-1707
> URL: https://jira.jboss.org/jira/browse/JBPM-1707
> Project: jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Runtime Engine
> Affects Versions: jBPM 3.2.3
> Environment: Red Hat Enterprise Linux AS release 4 (Nahant Update 7)
> enterprise-installer-4.3.0.GA-1.ep1.8.jar
> jdk-1.5.0_16-fcs
> Reporter: Alejandro Guizar
> Assignee: Alejandro Guizar
> Fix For: jBPM 3.3.0 GA, jBPM 3.2.4 GA
>
>
> On a RHEL machine, while deploying a seam based ear, which contains 13 pageflow definitions, the parsing of these 13 pageflow files takes more than 34 minutes (!).
> The culprit seems to be the usage of the original systemId (http://jboss.com/products/seam/pageflow-2.0.xsd) in the org.jbpm.jdpl.xml.JpdlParser$JpdlEntityResolver class, as this
> apparently results in slow internet lookups:
> log.debug("original systemId as input source");
> inputSource = new InputSource(systemId);
> Using a null InputSource:
> inputSource = new InputSource((InputStream)null);
> brings the parsing time down to less than 1 second.
> Of course it would be better to actually pass in a reference to the local pageflow-2.0.xsd file, which is inside the jboss-seam.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbpm-issues
mailing list