[JBoss JIRA] (ISPN-6210) "* lacks 'READ' permission" while executing scripts over TaskManager with authentication enabled
by Anna Manukyan (JIRA)
[ https://issues.jboss.org/browse/ISPN-6210?page=com.atlassian.jira.plugin.... ]
Anna Manukyan reassigned ISPN-6210:
-----------------------------------
Assignee: Anna Manukyan
> "* lacks 'READ' permission" while executing scripts over TaskManager with authentication enabled
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-6210
> URL: https://issues.jboss.org/browse/ISPN-6210
> Project: Infinispan
> Issue Type: Bug
> Components: Tasks
> Reporter: Anna Manukyan
> Assignee: Anna Manukyan
>
> When creating an authentication enabled cacheManager/cache and trying to execute a script on it (no matter whether the "role" meta-tag is specified or no), the test throws the following exception:
> {code}
> java.security.PrivilegedActionException: java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [TestPrincipal [name=pheidippides]]' lacks 'READ' permission
> at org.infinispan.security.Security.doAs(Security.java:145)
> at org.infinispan.scripting.SecureScriptingTaskManagerTest.testTask(SecureScriptingTaskManagerTest.java:111)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:348)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305)
> at org.testng.SuiteRunner.run(SuiteRunner.java:254)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
> at org.testng.TestNG.run(TestNG.java:1057)
> at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72)
> at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [TestPrincipal [name=pheidippides]]' lacks 'READ' permission
> at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:86)
> at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:37)
> at org.infinispan.security.impl.SecureCacheImpl.containsKey(SecureCacheImpl.java:364)
> at org.infinispan.scripting.impl.ScriptingManagerImpl.containsScript(ScriptingManagerImpl.java:137)
> at org.infinispan.scripting.impl.ScriptingTaskEngine.handles(ScriptingTaskEngine.java:48)
> at org.infinispan.tasks.impl.TaskManagerImpl.runTask(TaskManagerImpl.java:74)
> at org.infinispan.scripting.SecureScriptingTaskManagerTest$4.run(SecureScriptingTaskManagerTest.java:115)
> at org.infinispan.scripting.SecureScriptingTaskManagerTest$4.run(SecureScriptingTaskManagerTest.java:111)
> at org.infinispan.security.Security.doAs(Security.java:143)
> ... 29 more
> {code}
> You can find the test here:
> https://github.com/andyuk1986/infinispan/blob/4755853001f1f2dd52ca8dfb787...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6210) "* lacks 'READ' permission" while executing scripts over TaskManager with authentication enabled
by Anna Manukyan (JIRA)
[ https://issues.jboss.org/browse/ISPN-6210?page=com.atlassian.jira.plugin.... ]
Anna Manukyan reassigned ISPN-6210:
-----------------------------------
Assignee: Tristan Tarrant (was: Anna Manukyan)
> "* lacks 'READ' permission" while executing scripts over TaskManager with authentication enabled
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-6210
> URL: https://issues.jboss.org/browse/ISPN-6210
> Project: Infinispan
> Issue Type: Bug
> Components: Tasks
> Reporter: Anna Manukyan
> Assignee: Tristan Tarrant
>
> When creating an authentication enabled cacheManager/cache and trying to execute a script on it (no matter whether the "role" meta-tag is specified or no), the test throws the following exception:
> {code}
> java.security.PrivilegedActionException: java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [TestPrincipal [name=pheidippides]]' lacks 'READ' permission
> at org.infinispan.security.Security.doAs(Security.java:145)
> at org.infinispan.scripting.SecureScriptingTaskManagerTest.testTask(SecureScriptingTaskManagerTest.java:111)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:348)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305)
> at org.testng.SuiteRunner.run(SuiteRunner.java:254)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
> at org.testng.TestNG.run(TestNG.java:1057)
> at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72)
> at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [TestPrincipal [name=pheidippides]]' lacks 'READ' permission
> at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:86)
> at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:37)
> at org.infinispan.security.impl.SecureCacheImpl.containsKey(SecureCacheImpl.java:364)
> at org.infinispan.scripting.impl.ScriptingManagerImpl.containsScript(ScriptingManagerImpl.java:137)
> at org.infinispan.scripting.impl.ScriptingTaskEngine.handles(ScriptingTaskEngine.java:48)
> at org.infinispan.tasks.impl.TaskManagerImpl.runTask(TaskManagerImpl.java:74)
> at org.infinispan.scripting.SecureScriptingTaskManagerTest$4.run(SecureScriptingTaskManagerTest.java:115)
> at org.infinispan.scripting.SecureScriptingTaskManagerTest$4.run(SecureScriptingTaskManagerTest.java:111)
> at org.infinispan.security.Security.doAs(Security.java:143)
> ... 29 more
> {code}
> You can find the test here:
> https://github.com/andyuk1986/infinispan/blob/4755853001f1f2dd52ca8dfb787...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6210) "* lacks 'READ' permission" while executing scripts over TaskManager with authentication enabled
by Anna Manukyan (JIRA)
Anna Manukyan created ISPN-6210:
-----------------------------------
Summary: "* lacks 'READ' permission" while executing scripts over TaskManager with authentication enabled
Key: ISPN-6210
URL: https://issues.jboss.org/browse/ISPN-6210
Project: Infinispan
Issue Type: Bug
Components: Tasks
Reporter: Anna Manukyan
When creating an authentication enabled cacheManager/cache and trying to execute a script on it (no matter whether the "role" meta-tag is specified or no), the test throws the following exception:
{code}
java.security.PrivilegedActionException: java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [TestPrincipal [name=pheidippides]]' lacks 'READ' permission
at org.infinispan.security.Security.doAs(Security.java:145)
at org.infinispan.scripting.SecureScriptingTaskManagerTest.testTask(SecureScriptingTaskManagerTest.java:111)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:348)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305)
at org.testng.SuiteRunner.run(SuiteRunner.java:254)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
at org.testng.TestNG.run(TestNG.java:1057)
at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72)
at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [TestPrincipal [name=pheidippides]]' lacks 'READ' permission
at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:86)
at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:37)
at org.infinispan.security.impl.SecureCacheImpl.containsKey(SecureCacheImpl.java:364)
at org.infinispan.scripting.impl.ScriptingManagerImpl.containsScript(ScriptingManagerImpl.java:137)
at org.infinispan.scripting.impl.ScriptingTaskEngine.handles(ScriptingTaskEngine.java:48)
at org.infinispan.tasks.impl.TaskManagerImpl.runTask(TaskManagerImpl.java:74)
at org.infinispan.scripting.SecureScriptingTaskManagerTest$4.run(SecureScriptingTaskManagerTest.java:115)
at org.infinispan.scripting.SecureScriptingTaskManagerTest$4.run(SecureScriptingTaskManagerTest.java:111)
at org.infinispan.security.Security.doAs(Security.java:143)
... 29 more
{code}
You can find the test here:
https://github.com/andyuk1986/infinispan/blob/4755853001f1f2dd52ca8dfb787...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6074) DistExec API should not require a distributed cache
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6074?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-6074:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4008
> DistExec API should not require a distributed cache
> ---------------------------------------------------
>
> Key: ISPN-6074
> URL: https://issues.jboss.org/browse/ISPN-6074
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Distributed Execution and Map/Reduce
> Reporter: Tristan Tarrant
> Assignee: William Burns
> Fix For: 8.2.0.Beta2, 8.2.0.Final
>
>
> The current DistExec API has the limitation that it requires a distributed cache to choose the nodes on which it runs the code.
> The distexec API should instead be based off the DefaultCacheManager.
> Additionally, the API could be redesigned and possibly take inspiration from the streams API (i.e. lambdas, etc)
> cacheManager.cluster().execute(<lambda>)
> Add fluent methods to filter nodes by address, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6074) DistExec API should not require a distributed cache
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6074?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-6074:
--------------------------------
Fix Version/s: 8.2.0.Beta2
> DistExec API should not require a distributed cache
> ---------------------------------------------------
>
> Key: ISPN-6074
> URL: https://issues.jboss.org/browse/ISPN-6074
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Distributed Execution and Map/Reduce
> Reporter: Tristan Tarrant
> Assignee: William Burns
> Fix For: 8.2.0.Beta2, 8.2.0.Final
>
>
> The current DistExec API has the limitation that it requires a distributed cache to choose the nodes on which it runs the code.
> The distexec API should instead be based off the DefaultCacheManager.
> Additionally, the API could be redesigned and possibly take inspiration from the streams API (i.e. lambdas, etc)
> cacheManager.cluster().execute(<lambda>)
> Add fluent methods to filter nodes by address, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6209) 2-node cluster with pessimistic lock: Exceptions reported on remote node even if FAIL_SILENTLY flag is used
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/ISPN-6209?page=com.atlassian.jira.plugin.... ]
Marek Posolda updated ISPN-6209:
--------------------------------
Description:
When I look at the Javadoc of FAIL_SILENTLY flag, it can be seen:
{code}
This Flag will not be replicated to remote nodes, but it will still protect the invoker from remote exceptions.
{code}
I expect that exception is not reported on any cluster node when this flag is used. However in some situation with Pessimistic locking and with flags ZERO_LOCK_ACQUISITION_TIMEOUT + FAIL_SILENTLY, the exception can be seen in remote node log if the remote node owns the lock.
I am attaching reproducer, which can be used to simulate issue (It's Java class with main method, so can be used in any project with dependency on infinispan 8.1)
All the functionality works as expected, only the exception in the log is annoying.
was:
When I look at the Javadoc of FAIL_SILENTLY flag, it can be seen:
{code}
This Flag will not be replicated to remote nodes, but it will still protect the invoker from remote exceptions.
{code}
I expect that exception is not reported on any cluster node when this flag is used. However in some situation with Pessimistic locking and with flags ZERO_LOCK_ACQUISITION_TIMEOUT + FAIL_SILENTLY, the exception can be seen in remote node log if the remote node owns the lock.
I am attaching reproducer, which can be used to simulate issue (It's Java class with main method, so can be used in any project with dependency on infinispan 8.1)
> 2-node cluster with pessimistic lock: Exceptions reported on remote node even if FAIL_SILENTLY flag is used
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6209
> URL: https://issues.jboss.org/browse/ISPN-6209
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Final
> Reporter: Marek Posolda
> Attachments: PessimisticLockClusterReproducer.java
>
>
> When I look at the Javadoc of FAIL_SILENTLY flag, it can be seen:
> {code}
> This Flag will not be replicated to remote nodes, but it will still protect the invoker from remote exceptions.
> {code}
> I expect that exception is not reported on any cluster node when this flag is used. However in some situation with Pessimistic locking and with flags ZERO_LOCK_ACQUISITION_TIMEOUT + FAIL_SILENTLY, the exception can be seen in remote node log if the remote node owns the lock.
> I am attaching reproducer, which can be used to simulate issue (It's Java class with main method, so can be used in any project with dependency on infinispan 8.1)
> All the functionality works as expected, only the exception in the log is annoying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6209) 2-node cluster with pessimistic lock: Exceptions reported on remote node even if FAIL_SILENTLY flag is used
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/ISPN-6209?page=com.atlassian.jira.plugin.... ]
Marek Posolda updated ISPN-6209:
--------------------------------
Attachment: PessimisticLockClusterReproducer.java
> 2-node cluster with pessimistic lock: Exceptions reported on remote node even if FAIL_SILENTLY flag is used
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6209
> URL: https://issues.jboss.org/browse/ISPN-6209
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Final
> Reporter: Marek Posolda
> Attachments: PessimisticLockClusterReproducer.java
>
>
> When I look at the Javadoc of FAIL_SILENTLY flag, it can be seen:
> {code}
> This Flag will not be replicated to remote nodes, but it will still protect the invoker from remote exceptions.
> {code}
> I expect that exception is not reported on any cluster node when this flag is used. However in some situation with Pessimistic locking and with flags ZERO_LOCK_ACQUISITION_TIMEOUT + FAIL_SILENTLY, the exception can be seen in remote node log if the remote node owns the lock.
> I am attaching reproducer, which can be used to simulate issue (It's Java class with main method, so can be used in any project with dependency on infinispan 8.1)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6209) 2-node cluster with pessimistic lock: Exceptions reported on remote node even if FAIL_SILENTLY flag is used
by Marek Posolda (JIRA)
Marek Posolda created ISPN-6209:
-----------------------------------
Summary: 2-node cluster with pessimistic lock: Exceptions reported on remote node even if FAIL_SILENTLY flag is used
Key: ISPN-6209
URL: https://issues.jboss.org/browse/ISPN-6209
Project: Infinispan
Issue Type: Bug
Affects Versions: 8.1.0.Final
Reporter: Marek Posolda
When I look at the Javadoc of FAIL_SILENTLY flag, it can be seen:
{code}
This Flag will not be replicated to remote nodes, but it will still protect the invoker from remote exceptions.
{code}
I expect that exception is not reported on any cluster node when this flag is used. However in some situation with Pessimistic locking and with flags ZERO_LOCK_ACQUISITION_TIMEOUT + FAIL_SILENTLY, the exception can be seen in remote node log if the remote node owns the lock.
I am attaching reproducer, which can be used to simulate issue (It's Java class with main method, so can be used in any project with dependency on infinispan 8.1)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ISPN-6146) XA transactions already committed in prepare as XA_RDONLY fail on commit with "ISPN000112: exception while committing: javax.transaction.xa.XAException"
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/ISPN-6146?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated ISPN-6146:
---------------------------------
Priority: Critical (was: Major)
> XA transactions already committed in prepare as XA_RDONLY fail on commit with "ISPN000112: exception while committing: javax.transaction.xa.XAException"
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6146
> URL: https://issues.jboss.org/browse/ISPN-6146
> Project: Infinispan
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.2.0.Beta1, 8.1.1.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
>
> {noformat}
> 15:34:39,087 WARN [org.infinispan.transaction.tm.DummyTransaction] (default task-1) ISPN000112: exception while committing: javax.transaction.xa.XAException
> at org.infinispan.transaction.xa.TransactionXaAdapter.getLocalTransactionAndValidateImpl(TransactionXaAdapter.java:242)
> at org.infinispan.transaction.xa.TransactionXaAdapter.getLocalTransactionAndValidate(TransactionXaAdapter.java:235)
> at org.infinispan.transaction.xa.TransactionXaAdapter.commit(TransactionXaAdapter.java:103)
> at org.infinispan.transaction.tm.DummyTransaction.finishResource(DummyTransaction.java:389)
> at org.infinispan.transaction.tm.DummyTransaction.commitResources(DummyTransaction.java:435)
> at org.infinispan.transaction.tm.DummyTransaction.runCommit(DummyTransaction.java:314)
> at org.infinispan.transaction.tm.DummyTransaction.commit(DummyTransaction.java:105)
> at org.infinispan.transaction.tm.DummyBaseTransactionManager.commit(DummyBaseTransactionManager.java:73)
> at org.wildfly.clustering.ee.infinispan.ActiveTransactionBatch.close(ActiveTransactionBatch.java:48)
> at org.wildfly.clustering.web.undertow.session.DistributableSession.requestDone(DistributableSession.java:77)
> at io.undertow.servlet.spec.ServletContextImpl.updateSessionAccessTime(ServletContextImpl.java:768)
> at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(HttpServletResponseImpl.java:557)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:331)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month