[
https://issues.jboss.org/browse/WFLY-1172?page=com.atlassian.jira.plugin....
]
Frank Langelage commented on WFLY-1172:
---------------------------------------
This implementation created a big performance drop when deploying my ear.
Before it took about 1 min 15s to deploy, now the 5 minutes are not enough and deployment
gets a timeout and is stopped.
My ear is of 22 MB size, contains 23 ejb and web modules.
If I revert changes in UndertowSubsystemAdd.java everything is fine again.
I added some debug statements to ExternalTldParsingDeploymentProcessor.java and found out,
that line 83 is causing the problem.
The first call of next for a deploymentunit takes a lot of time, subsequent calls for the
same DU are no problem then.
Getting the first element takes about 1m - 1m 30s and lot of memory is used, as I see many
lines of the garbage collector in this period.
mechanism to load tag libraries from module
-------------------------------------------
Key: WFLY-1172
URL:
https://issues.jboss.org/browse/WFLY-1172
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Undertow)
Reporter: Ivica Loncar
Assignee: Stuart Douglas
Priority: Critical
Labels: modules, tag, taglib, tld
Fix For: 9.0.0.Beta1
Original Estimate: 1 day
Remaining Estimate: 1 day
tag libraries are scanned only if they appear in jar inside WEB-INF/lib or are defined in
tld under WEB-INF.
The simplest scenario to explain why this is a problem: portlet 2 defines standard
portlet taglib, but the classes in this file come from concrete implementations. Currently
I see no way to use 2 different portals in a portable way.
Please provide a way to notify a relevant subsystem for web applications that specific
module contains a .tld.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)