[jboss-jira] [JBoss JIRA] (WFCORE-3210) Wildfly module isolation not working consistently

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455712#comment-13455712 ] 

jaikiran pai commented on WFCORE-3210:
--------------------------------------

[~nuno.godinhomatos], To some extent I understand what you are trying to achieve. However, the way you have presented it, makes it very difficult to understand or narrow this down to the actual issue. For example, that module.xml that you have in one of the comments in this JIRA, to me, looks too complicated. And I can't imagine (even with the comments in that file) why it's defined in that manner.

As David noted, tell us what you are trying to achieve, not what WildFly is doing (I really don't mean it as some kind of insult). Provide exact details like the entire exception stacktrace. You have been trying to explain to us what WildFly internally does and what it shouldn't do. It's fine to explain that, but there needs to be a separate precise explanation which shows us what your configs are, what exception stacktraces you run into so that we too can either come to the same conclusion about what WildFly is doing or figure out if there's something else going on.

P.S: It's also better to use formatting while posting logs, code or xml configurations so that it's easier to read.

> Wildfly module isolation not working consistently
> -------------------------------------------------
>
>                 Key: WFCORE-3210
>                 URL: https://issues.jboss.org/browse/WFCORE-3210
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging, Modules
>    Affects Versions: 2.2.0.Final
>            Reporter: Nuno Godinho de Matos
>
> There is an underministic bug on the module layer of wildfly, whereby the boot logic of the application server is not ensured to give the appropriate module isolation - which can lead to unexpected boot classpath problems.
> An example of this phenomena is given on the wildfly forum thread:
> https://developer.jboss.org/thread/275839
> In this example, we have the logging subsystem setup to use a custome handler.
> The custom handler wishes to have acces to the JUL extension classes on the org.jboss.logmanger module, but wishes to do have no relationship with the org.apache.log4j packages associated to the wildfly org.jboss.log4j module.
> What we see in this example is that an application gets from wildfly mixed behavior.
> Most of the time, during boot, the processes works without problem, where the custom handler runs isolated from the undersired log4j libraries within wildfly.
> But other times the application boot procedure will not go smoothly with the custom handler having processes routing JUL LogRecords events into the bundled log4j because the application server has loaded some of the classes that exist the org.jboss.log4j module.
> And as we know when the same class is loaded by different class loaders, then that class that orinates from class loader A cannot be assigned to the corresponding class of class loader B, even if the classes are exactly the same.
> This is not an isolated issue.
> There are also open issues on the wildfly forum reporting on startup problems on the logging subsystme where sometimes the LogManager class had not yet been loaded, and sometimes this issue goes away.
> This is an indication of some deep issue engrained into the module loading, where the module isolation behavior is not ensured to work all the time and that the boot procedure is not deterministically reliable. 
> It should not be that the application server some time starts successfully and others not.
> Booting wildfly should always result in the same outcode.
> Problems of this nature with class loading problems should either always happen if the configuration is not done properly or never happen if the configuration is proper.
> In the case of thread:
> https://developer.jboss.org/thread/275839
> Our belief is that the configuration is doing all it possible can to request the necessary module isolation from base packages and the outcome where log4j class load problems take place should never be allowed to happen.
> Many thanks.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)