[JBoss JIRA] (WFCORE-3210) Wildfly module isolation not working consistently
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3210?page=com.atlassian.jira.plugi... ]
Nuno Godinho de Matos commented on WFCORE-3210:
-----------------------------------------------
Hi,
Since the issue is not assigned to anyone, I am not sure if this is in Limbo.
Please let me know if I can be of help.
If you consider this a non-issue, then please let me know as well.
I will adapt to the circumstances.
Kindest regards.
> 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)
8 years, 10 months
[JBoss JIRA] (WFCORE-3237) Seam integration jar name mismatch between WildFly Core and WildFly
by Tõnisik Pool (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3237?page=com.atlassian.jira.plugi... ]
Tõnisik Pool updated WFCORE-3237:
---------------------------------
Description:
Trying to deploy a simple JBoss Seam 2.3.x application on WildFly 11.0.0.CR1 will fail with:
{noformat}
09:06:16,492 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "pkg-seamJboss23-notChangedComponentsReinitializedOnce.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:161)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:127)
at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:158)
... 6 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:100)
... 7 more
{noformat}
The issue is that in https://issues.jboss.org/browse/WFLY-8660 the Seam Integration jar was renamed to {{jboss-seam-int-jbossas.jar}}
([commit|https://github.com/wildfly/wildfly/pull/9982/commits/e8e751299ed24...]) but Seam2Processor in WildFly Core still [expects it to be|https://github.com/wildfly/wildfly-core/blob/master/server/src/main/ja...] {{jboss-seam-int.jar}}
was:
Trying to deploy a simple JBoss Seam 2.3.x application on WildFly 11.0.0.CR1 will fail with:
{noformat}
09:06:16,492 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "pkg-seamJboss23-notChangedComponentsReinitializedOnce.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:161)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:127)
at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:158)
... 6 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:100)
... 7 more
{noformat}
The issue is that in https://issues.jboss.org/browse/WFLY-8660 the Seam Integration jar was renamed to {{jboss-seam-int-jbossas.jar}}([commit|https://github.com/wildfly/wildfly/pull/9982/commits/e8e751299ed246e7770fd1b81b56d75c467d4740]) but Seam2Processor in WildFly Core still [expects it to be|https://github.com/wildfly/wildfly-core/blob/master/server/src/main/ja...] {{jboss-seam-int.jar}}
> Seam integration jar name mismatch between WildFly Core and WildFly
> -------------------------------------------------------------------
>
> Key: WFCORE-3237
> URL: https://issues.jboss.org/browse/WFCORE-3237
> Project: WildFly Core
> Issue Type: Feature Request
> Affects Versions: 3.0.1.Final
> Reporter: Tõnisik Pool
>
> Trying to deploy a simple JBoss Seam 2.3.x application on WildFly 11.0.0.CR1 will fail with:
> {noformat}
> 09:06:16,492 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "pkg-seamJboss23-notChangedComponentsReinitializedOnce.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
> at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:161)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
> at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:127)
> at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:158)
> ... 6 more
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
> at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:100)
> ... 7 more
> {noformat}
> The issue is that in https://issues.jboss.org/browse/WFLY-8660 the Seam Integration jar was renamed to {{jboss-seam-int-jbossas.jar}}
> ([commit|https://github.com/wildfly/wildfly/pull/9982/commits/e8e751299ed24...]) but Seam2Processor in WildFly Core still [expects it to be|https://github.com/wildfly/wildfly-core/blob/master/server/src/main/ja...] {{jboss-seam-int.jar}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3237) Seam integration jar name mismatch between WildFly Core and WildFly
by Tõnisik Pool (JIRA)
Tõnisik Pool created WFCORE-3237:
------------------------------------
Summary: Seam integration jar name mismatch between WildFly Core and WildFly
Key: WFCORE-3237
URL: https://issues.jboss.org/browse/WFCORE-3237
Project: WildFly Core
Issue Type: Feature Request
Affects Versions: 3.0.1.Final
Reporter: Tõnisik Pool
Trying to deploy a simple JBoss Seam 2.3.x application on WildFly 11.0.0.CR1 will fail with:
{noformat}
09:06:16,492 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "pkg-seamJboss23-notChangedComponentsReinitializedOnce.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:161)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:127)
at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:158)
... 6 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:100)
... 7 more
{noformat}
The issue is that in https://issues.jboss.org/browse/WFLY-8660 the Seam Integration jar was renamed to {{jboss-seam-int-jbossas.jar}}([commit|https://github.com/wildfly/wildfly/pull/9982/commits/e8e751299ed246e7770fd1b81b56d75c467d4740]) but Seam2Processor in WildFly Core still [expects it to be|https://github.com/wildfly/wildfly-core/blob/master/server/src/main/ja...] {{jboss-seam-int.jar}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9290) Some MDBTestCase tests fail with security manager
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-9290?page=com.atlassian.jira.plugin.... ]
Chao Wang reassigned WFLY-9290:
-------------------------------
Assignee: Chao Wang
> Some MDBTestCase tests fail with security manager
> -------------------------------------------------
>
> Key: WFLY-9290
> URL: https://issues.jboss.org/browse/WFLY-9290
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 11.0.0.Final
> Reporter: Ondrej Kotek
> Assignee: Chao Wang
> Labels: security-manager
>
> Some {{MDBTestCase}} tests fail with security manager because of missing permission {{"("java.io.FilePermission" "/home/okotek/git/wildfly/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local4437638380092046127.challenge" "read")"}}:
> {noformat}
> java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.as.test.integration.ejb.mdb.MDBTestCase.testSuspendResumeWithMDB(MDBTestCase.java:177)
> ...
> Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
> JBOSS-LOCAL-USER: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/okotek/git/wildfly/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local8043361973857375326.challenge" "read")" in code source "(vfs:/content/MDBTestCase.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.MDBTestCase.jar" from Service Module Loader")
> at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:442)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:570)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:532)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:520)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:204)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> ... 157 more
> Suppressed: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/okotek/git/wildfly/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local8043361973857375326.challenge" "read")" in code source "(vfs:/content/MDBTestCase.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.MDBTestCase.jar" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
> at java.lang.SecurityManager.checkRead(SecurityManager.java:888)
> at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:350)
> at java.io.FileInputStream.<init>(FileInputStream.java:127)
> at org.wildfly.security.sasl.localuser.LocalUserClient.evaluateMessage(LocalUserClient.java:93)
> at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:180)
> at org.wildfly.security.sasl.util.AbstractSaslClient.evaluateChallenge(AbstractSaslClient.java:59)
> at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.lambda$handleEvent$0(ClientConnectionOpenListener.java:646)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
> ... 3 more
> {noformat}
> Adding the missing permission helps.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9291) Delete IronjacamarParser
by Flavia Rainone (JIRA)
Flavia Rainone created WFLY-9291:
------------------------------------
Summary: Delete IronjacamarParser
Key: WFLY-9291
URL: https://issues.jboss.org/browse/WFLY-9291
Project: WildFly
Issue Type: Task
Components: JCA
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Fix For: 11.0.0.Final
Delete IronjacamarParser until all related issues are solved.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months