[
https://issues.apache.org/jira/browse/WICKET-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885201#comment-13885201
]
Arjan Zwaan commented on WICKET-5492:
-------------------------------------
Understood, I already kind of expected 1.4.x would no longer get these kind of
changes.
Thanks for the feedback and responses, hopefully we will be able to switch to
1.5.x or higher in the near future.
> WebApplication ignores a SecurityException
> ------------------------------------------
>
> Key: WICKET-5492
> URL: https://issues.apache.org/jira/browse/WICKET-5492
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.18
> Environment: WebSphere 6.1 with shared classloading enabled. Linux
> system.
> Reporter: Arjan Zwaan
> Labels: exception-handling, security
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The WebApplication class has a piece of code in the method
> getConfigurationType(), that ignores a SecurityException.
> Code snippet:
> try
> {
> result = System.getProperty("wicket." +
> Application.CONFIGURATION);
> }
> catch (SecurityException e)
> {
> // Ignore - we're not allowed to read system
> properties.
> }
> This apparently causes a performance problem at one of our customers, where
> they had shared classloading enabled.
> Permissions were set differently on shared classloader level, which caused
> the retrieval of the property to fail silently, while taking about 10ms
> longer. This code is called everytime Component.getMarkupId is called, which
> means with 300+ components on a page, you get a delay of 3 seconds or more.
> Ofcourse the problem can be (and has been) solved with a correct
> configuration. My request however is that the exception is atleast logged at
> some level (warning for example), so spotting the problem will become a lot
> easier (it took us 2 weeks to narrow it down).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
