[JBoss JIRA] (GTNPORTAL-2710) ChromatticLifeCycle doesn't remove context from currenctContext when closed
8:42 a.m.
Stian Thorgersen created GTNPORTAL-2710:
-------------------------------------------
Summary: ChromatticLifeCycle doesn't remove context from currenctContext
when closed
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Stian Thorgersen
Assignee: Stian Thorgersen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if save fails
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Stian Thorgersen updated GTNPORTAL-2710:
----------------------------------------
Summary: Context not removed from ChromatticLifeCycle#currenctContext if save fails
(was: ChromatticLifeCycle doesn't remove context from currenctContext when closed)
Context not removed from ChromatticLifeCycle#currenctContext if save
fails
--------------------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Stian Thorgersen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if save fails
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Stian Thorgersen updated GTNPORTAL-2710:
----------------------------------------
Description: If ChromatticLifeCycle#closeContext is called with save=true and a
failure occurs the context is not removed from ChromatticLifeCycle#currenctContext. This
is caused by AbstractContext#close only calling lifeCycle.currentContext.set(null); if no
exception is thrown. (was: If ChromatticLifeCycle#closeContext is called with save=true
and a failure occurs the context is not removed from )
Context not removed from ChromatticLifeCycle#currenctContext if save
fails
--------------------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Stian Thorgersen
If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the
context is not removed from ChromatticLifeCycle#currenctContext. This is caused by
AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is
thrown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if save fails
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Stian Thorgersen updated GTNPORTAL-2710:
----------------------------------------
Description: If ChromatticLifeCycle#closeContext is called with save=true and a
failure occurs the context is not removed from (was: When calling closeContext)
Context not removed from ChromatticLifeCycle#currenctContext if save
fails
--------------------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Stian Thorgersen
If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the
context is not removed from
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if save fails
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Stian Thorgersen updated GTNPORTAL-2710:
----------------------------------------
Description: When calling closeContext
Context not removed from ChromatticLifeCycle#currenctContext if save
fails
--------------------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Stian Thorgersen
When calling closeContext
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Stian Thorgersen updated GTNPORTAL-2710:
----------------------------------------
Summary: Context not removed from ChromatticLifeCycle#currenctContext if (was:
Context not removed from ChromatticLifeCycle#currenctContext if save fails)
Context not removed from ChromatticLifeCycle#currenctContext if
----------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Stian Thorgersen
If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the
context is not removed from ChromatticLifeCycle#currenctContext. This is caused by
AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is
thrown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Stian Thorgersen updated GTNPORTAL-2710:
----------------------------------------
Summary: Context not removed from ChromatticLifeCycle#currenctContext if an exception
is thrown in AbstractContext#close (was: Context not removed from
ChromatticLifeCycle#currenctContext if )
Context not removed from ChromatticLifeCycle#currenctContext if an
exception is thrown in AbstractContext#close
---------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Stian Thorgersen
If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the
context is not removed from ChromatticLifeCycle#currenctContext. This is caused by
AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is
thrown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Stian Thorgersen updated GTNPORTAL-2710:
----------------------------------------
Description:
If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the
context is not removed from ChromatticLifeCycle#currenctContext. This is caused by
AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is
thrown.
This can be reproduced by running test specified in GTNPORTAL-2711. When this test is run
the first test fails with the failure specified in that JIRA issue. However, the rest of
the tests fails with the failure in this issue.
Stack trace:
{code}
org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: This kind
of operation is forbidden after a session.logout().
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:199)
at
org.chromattic.core.api.ChromatticSessionImpl.findByPath(ChromatticSessionImpl.java:228)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.getGadgetTokenContainer(GadgetTokenInfoService.java:149)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:55)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:1)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.execute(GadgetTokenInfoService.java:165)
at org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:54)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:59)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testSize(TestGadgetTokenInfoService.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.jcr.RepositoryException: This kind of operation is forbidden after a
session.logout().
at org.exoplatform.services.jcr.impl.core.SessionImpl.checkLive(SessionImpl.java:917)
at org.exoplatform.services.jcr.impl.core.SessionImpl.getRootNode(SessionImpl.java:760)
at org.chromattic.core.DomainSessionImpl._getRoot(DomainSessionImpl.java:809)
at org.chromattic.core.DomainSessionImpl._findByPath(DomainSessionImpl.java:115)
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:196)
... 29 more
{code}
was:If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs
the context is not removed from ChromatticLifeCycle#currenctContext. This is caused by
AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is
thrown.
Context not removed from ChromatticLifeCycle#currenctContext if an
exception is thrown in AbstractContext#close
---------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Stian Thorgersen
If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the
context is not removed from ChromatticLifeCycle#currenctContext. This is caused by
AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is
thrown.
This can be reproduced by running test specified in GTNPORTAL-2711. When this test is run
the first test fails with the failure specified in that JIRA issue. However, the rest of
the tests fails with the failure in this issue.
Stack trace:
{code}
org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: This
kind of operation is forbidden after a session.logout().
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:199)
at
org.chromattic.core.api.ChromatticSessionImpl.findByPath(ChromatticSessionImpl.java:228)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.getGadgetTokenContainer(GadgetTokenInfoService.java:149)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:55)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:1)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.execute(GadgetTokenInfoService.java:165)
at
org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:54)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:59)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testSize(TestGadgetTokenInfoService.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at
org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.jcr.RepositoryException: This kind of operation is forbidden after a
session.logout().
at org.exoplatform.services.jcr.impl.core.SessionImpl.checkLive(SessionImpl.java:917)
at org.exoplatform.services.jcr.impl.core.SessionImpl.getRootNode(SessionImpl.java:760)
at org.chromattic.core.DomainSessionImpl._getRoot(DomainSessionImpl.java:809)
at org.chromattic.core.DomainSessionImpl._findByPath(DomainSessionImpl.java:115)
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:196)
... 29 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:30 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Stian Thorgersen updated GTNPORTAL-2710:
----------------------------------------
Fix Version/s: 3.5.0.Final
Context not removed from ChromatticLifeCycle#currenctContext if an
exception is thrown in AbstractContext#close
---------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Stian Thorgersen
Fix For: 3.5.0.Final
If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the
context is not removed from ChromatticLifeCycle#currenctContext. This is caused by
AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is
thrown.
This can be reproduced by running test specified in GTNPORTAL-2711. When this test is run
the first test fails with the failure specified in that JIRA issue. However, the rest of
the tests fails with the failure in this issue.
Stack trace:
{code}
org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: This
kind of operation is forbidden after a session.logout().
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:199)
at
org.chromattic.core.api.ChromatticSessionImpl.findByPath(ChromatticSessionImpl.java:228)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.getGadgetTokenContainer(GadgetTokenInfoService.java:149)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:55)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:1)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.execute(GadgetTokenInfoService.java:165)
at
org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:54)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:59)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testSize(TestGadgetTokenInfoService.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at
org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.jcr.RepositoryException: This kind of operation is forbidden after a
session.logout().
at org.exoplatform.services.jcr.impl.core.SessionImpl.checkLive(SessionImpl.java:917)
at org.exoplatform.services.jcr.impl.core.SessionImpl.getRootNode(SessionImpl.java:760)
at org.chromattic.core.DomainSessionImpl._getRoot(DomainSessionImpl.java:809)
at org.chromattic.core.DomainSessionImpl._findByPath(DomainSessionImpl.java:115)
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:196)
... 29 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:30 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Stian Thorgersen updated GTNPORTAL-2710:
----------------------------------------
Assignee: Julien Viet (was: Stian Thorgersen)
Context not removed from ChromatticLifeCycle#currenctContext if an
exception is thrown in AbstractContext#close
---------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Julien Viet
Fix For: 3.5.0.Final
If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the
context is not removed from ChromatticLifeCycle#currenctContext. This is caused by
AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is
thrown.
This can be reproduced by running test specified in GTNPORTAL-2711. When this test is run
the first test fails with the failure specified in that JIRA issue. However, the rest of
the tests fails with the failure in this issue.
Stack trace:
{code}
org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: This
kind of operation is forbidden after a session.logout().
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:199)
at
org.chromattic.core.api.ChromatticSessionImpl.findByPath(ChromatticSessionImpl.java:228)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.getGadgetTokenContainer(GadgetTokenInfoService.java:149)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:55)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:1)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.execute(GadgetTokenInfoService.java:165)
at
org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:54)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:59)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testSize(TestGadgetTokenInfoService.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at
org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.jcr.RepositoryException: This kind of operation is forbidden after a
session.logout().
at org.exoplatform.services.jcr.impl.core.SessionImpl.checkLive(SessionImpl.java:917)
at org.exoplatform.services.jcr.impl.core.SessionImpl.getRootNode(SessionImpl.java:760)
at org.chromattic.core.DomainSessionImpl._getRoot(DomainSessionImpl.java:809)
at org.chromattic.core.DomainSessionImpl._findByPath(DomainSessionImpl.java:115)
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:196)
... 29 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:24 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
[
https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl...
]
Boleslaw Dawidowicz updated GTNPORTAL-2710:
-------------------------------------------
Fix Version/s: 3.6.0.Final
(was: 3.5.0.Final)
Context not removed from ChromatticLifeCycle#currenctContext if an
exception is thrown in AbstractContext#close
---------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-2710
URL: https://issues.jboss.org/browse/GTNPORTAL-2710
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stian Thorgersen
Assignee: Julien Viet
Fix For: 3.6.0.Final
If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the
context is not removed from ChromatticLifeCycle#currenctContext. This is caused by
AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is
thrown.
This can be reproduced by running test specified in GTNPORTAL-2711. When this test is run
the first test fails with the failure specified in that JIRA issue. However, the rest of
the tests fails with the failure in this issue.
Stack trace:
{code}
org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: This
kind of operation is forbidden after a session.logout().
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:199)
at
org.chromattic.core.api.ChromatticSessionImpl.findByPath(ChromatticSessionImpl.java:228)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.getGadgetTokenContainer(GadgetTokenInfoService.java:149)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:55)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:1)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.execute(GadgetTokenInfoService.java:165)
at
org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:54)
at
org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:59)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
at
org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testSize(TestGadgetTokenInfoService.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at
org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.jcr.RepositoryException: This kind of operation is forbidden after a
session.logout().
at org.exoplatform.services.jcr.impl.core.SessionImpl.checkLive(SessionImpl.java:917)
at org.exoplatform.services.jcr.impl.core.SessionImpl.getRootNode(SessionImpl.java:760)
at org.chromattic.core.DomainSessionImpl._getRoot(DomainSessionImpl.java:809)
at org.chromattic.core.DomainSessionImpl._findByPath(DomainSessionImpl.java:115)
at org.chromattic.core.DomainSession.findByPath(DomainSession.java:196)
... 29 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4188
days inactive
4211
days old
10 comments
2 participants
participants (2)
-
Boleslaw Dawidowicz (JIRA) -
Stian Thorgersen (JIRA)