[JBoss JIRA] (WFLY-10385) TransactionInflowTestCase does not function correctly under security manager
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-10385?page=com.atlassian.jira.plugin... ]
Ondra Chaloupka edited comment on WFLY-10385 at 5/17/18 7:10 AM:
-----------------------------------------------------------------
thanks [~dmlloyd]. I've added the permissions needed for the test to pass.
was (Author: ochaloup):
thanks [~dmlloyd]. I've added the permissions needed for the test pass.
> TransactionInflowTestCase does not function correctly under security manager
> ----------------------------------------------------------------------------
>
> Key: WFLY-10385
> URL: https://issues.jboss.org/browse/WFLY-10385
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: David Lloyd
> Assignee: Ondra Chaloupka
>
> Proactively assigning to [~ochaloup] as he is the original test author; feel free to adjust as necessary.
> {{org.jboss.as.test.integration.transaction.inflow.TransactionInflowTestCase}} does not function correctly under a security manager. The stack trace is like this:
> {noformat}
> Breakpoint reached
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:295)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:192)
> at java.lang.SecurityManager.checkConnect(SecurityManager.java:1048)
> at org.wildfly.security.manager.WildFlySecurityManager.checkConnect(WildFlySecurityManager.java:390)
> at java.net.InetAddress.getLocalHost(InetAddress.java:1477)
> at org.jboss.as.test.integration.transaction.inflow.TransactionInflowXid.getXid(TransactionInflowXid.java:128)
> at org.jboss.as.test.integration.transaction.inflow.TransactionInflowXid.getUniqueXid(TransactionInflowXid.java:102)
> at org.jboss.as.test.integration.transaction.inflow.TransactionInflowResourceAdapter.endpointActivation(TransactionInflowResourceAdapter.java:65)
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:194)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:277)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:235)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Perm = ("java.net.SocketPermission" "behemoth.local" "resolve"), CS = (vfs:/content/inflow-txn-ra.rar/inflow-txn-inside.jar <no signer certificates>), CL = ModuleClassLoader for Module "deployment.inflow-txn-ra.rar" from Service Module Loader, ID = 824b419
> {noformat}
> The cause is that {{org.jboss.as.test.integration.transaction.inflow.TransactionInflowXid#getXid}} calls {{java.net.InetAddress#getLocalHost}} which requires a security manager permission. If the permission is denied (which it always is when running under a security manager), then it falls back through a {{catch (Exception ex)}} to a bogus IP address of "1.2.3.4".
> For correct operation, the test archives which use this method should have the {{"*"}} {{"resolve"}} {{SocketPermission}} granted to them.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-8451) org.wildfly.clustering.web.session.IdentifierExternalizerTestCase#toHex fails on JDK9 b162
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8451?page=com.atlassian.jira.plugin.... ]
Radoslav Husar closed WFLY-8451.
--------------------------------
Resolution: Out of Date
> org.wildfly.clustering.web.session.IdentifierExternalizerTestCase#toHex fails on JDK9 b162
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-8451
> URL: https://issues.jboss.org/browse/WFLY-8451
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> testHex(org.wildfly.clustering.web.session.IdentifierExternalizerTestCase) Time elapsed: 0.008 sec <<< ERROR!
> java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:533)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:186)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:476)
> at org.wildfly.clustering.web.IdentifierExternalizer$3.writeObject(IdentifierExternalizer.java:74)
> at org.wildfly.clustering.web.IdentifierExternalizer$3.writeObject(IdentifierExternalizer.java:71)
> at org.wildfly.clustering.web.session.IdentifierExternalizerTestCase.test(IdentifierExternalizerTestCase.java:97)
> at org.wildfly.clustering.web.session.IdentifierExternalizerTestCase.testHex(IdentifierExternalizerTestCase.java:61)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2549?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2549:
-----------------------------------
Sprint: 2018 Week 19-20
> [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase
> -------------------------------------------------------------------
>
> Key: DROOLS-2549
> URL: https://issues.jboss.org/browse/DROOLS-2549
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes.
> At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}).
> Changes required for this JIRA (split into sub-tasks when work starts):-
> * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller
> * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children
> * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/)
> * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2549?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2549:
-----------------------------------
Description:
{{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes.
At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}).
Changes required for this JIRA (split into sub-tasks when work starts):-
* Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller
* Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children
* Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/)
* When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}}.
was:
{{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes.
At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}).
Changes required for this JIRA (split into sub-tasks when work starts):-
* Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller
* Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children
* Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}}
> [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase
> -------------------------------------------------------------------
>
> Key: DROOLS-2549
> URL: https://issues.jboss.org/browse/DROOLS-2549
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes.
> At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}).
> Changes required for this JIRA (split into sub-tasks when work starts):-
> * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller
> * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children
> * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/)
> * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10385) TransactionInflowTestCase does not function correctly under security manager
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-10385?page=com.atlassian.jira.plugin... ]
Ondra Chaloupka updated WFLY-10385:
-----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/11243
> TransactionInflowTestCase does not function correctly under security manager
> ----------------------------------------------------------------------------
>
> Key: WFLY-10385
> URL: https://issues.jboss.org/browse/WFLY-10385
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: David Lloyd
> Assignee: Ondra Chaloupka
>
> Proactively assigning to [~ochaloup] as he is the original test author; feel free to adjust as necessary.
> {{org.jboss.as.test.integration.transaction.inflow.TransactionInflowTestCase}} does not function correctly under a security manager. The stack trace is like this:
> {noformat}
> Breakpoint reached
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:295)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:192)
> at java.lang.SecurityManager.checkConnect(SecurityManager.java:1048)
> at org.wildfly.security.manager.WildFlySecurityManager.checkConnect(WildFlySecurityManager.java:390)
> at java.net.InetAddress.getLocalHost(InetAddress.java:1477)
> at org.jboss.as.test.integration.transaction.inflow.TransactionInflowXid.getXid(TransactionInflowXid.java:128)
> at org.jboss.as.test.integration.transaction.inflow.TransactionInflowXid.getUniqueXid(TransactionInflowXid.java:102)
> at org.jboss.as.test.integration.transaction.inflow.TransactionInflowResourceAdapter.endpointActivation(TransactionInflowResourceAdapter.java:65)
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:194)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:277)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:235)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Perm = ("java.net.SocketPermission" "behemoth.local" "resolve"), CS = (vfs:/content/inflow-txn-ra.rar/inflow-txn-inside.jar <no signer certificates>), CL = ModuleClassLoader for Module "deployment.inflow-txn-ra.rar" from Service Module Loader, ID = 824b419
> {noformat}
> The cause is that {{org.jboss.as.test.integration.transaction.inflow.TransactionInflowXid#getXid}} calls {{java.net.InetAddress#getLocalHost}} which requires a security manager permission. If the permission is denied (which it always is when running under a security manager), then it falls back through a {{catch (Exception ex)}} to a bogus IP address of "1.2.3.4".
> For correct operation, the test archives which use this method should have the {{"*"}} {{"resolve"}} {{SocketPermission}} granted to them.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months