6:57 p.m.
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core 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 CR1
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
2:58 a.m.
New subject: [JBoss JIRA] Resolved: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Alejandro Guizar resolved JBPM-1707.
------------------------------------
Resolution: Done
I made the jPDL parser read the pageflow schema from a local resource instead of the
remote URL.
Plus I added several pageflow parsing tests to the existing XmlSchemaTest.
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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 CR1
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
8:22 p.m.
New subject: [JBoss JIRA] Reopened: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Alejandro Guizar reopened JBPM-1707:
------------------------------------
Tests for this issue have been removed, needs attention.
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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 CR1
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
8:24 p.m.
New subject: [JBoss JIRA] Assigned: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Alejandro Guizar reassigned JBPM-1707:
--------------------------------------
Assignee: Tom Baeyens (was: Alejandro Guizar)
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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: Tom Baeyens
Fix For: jBPM 3.3.0 CR1
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
2:14 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Thomas Diesler updated JBPM-1707:
---------------------------------
Fix Version/s: jBPM 3.3.0 GA
(was: jBPM 3.3.0 CR1)
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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: Tom Baeyens
Fix For: jBPM 3.3.0 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
10:53 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-1707:
----------------------------------------
removed as in deleted or as in disabled? what kind of attention is needed?
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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: Tom Baeyens
Fix For: jBPM 3.3.0 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
3:37 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-1707:
----------------------------------------
As in deleted. We need to restore them.
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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: Tom Baeyens
Fix For: jBPM 3.3.0 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
4:15 p.m.
New subject: [JBoss JIRA] Assigned: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Alejandro Guizar reassigned JBPM-1707:
--------------------------------------
Assignee: Alejandro Guizar (was: Tom Baeyens)
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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
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
4:38 p.m.
New subject: [JBoss JIRA] Work started: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Work on JBPM-1707 started by Alejandro Guizar.
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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
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
6:47 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Alejandro Guizar resolved JBPM-1707.
------------------------------------
Resolution: Done
Restored pageflow parsing tests.
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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
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
1:43 a.m.
New subject: [JBoss JIRA] Closed: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Alejandro Guizar closed JBPM-1707.
----------------------------------
Closing issues that I resolved in already released versions.
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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
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
4:20 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
Tihomir Surdilovic commented on JBPM-1707:
------------------------------------------
Is the fix version for this JIRA correct?
pageflow parsing is slow
------------------------
Key: JBPM-1707
URL: https://jira.jboss.org/jira/browse/JBPM-1707
Project: JBoss 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
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
2:50 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1707) pageflow parsing is slow
[
https://jira.jboss.org/jira/browse/JBPM-1707?page=com.atlassian.jira.plug...
]
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
5234
days inactive
5751
days old
12 comments
4 participants
participants (4)
-
Alejandro Guizar (JIRA) -
Ronald van Kuijk (JIRA)
-
Thomas Diesler (JIRA)
-
Tihomir Surdilovic (JIRA)