[JBoss JIRA] (WFLY-5351) querying TimerService information from CLI fails for canceled timer
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5351?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-5351:
--------------------------------------
Fix Version/s: 12.0.0.Alpha1
Assignee: Matthieu Brouillard
Resolution: Done
> querying TimerService information from CLI fails for canceled timer
> -------------------------------------------------------------------
>
> Key: WFLY-5351
> URL: https://issues.jboss.org/browse/WFLY-5351
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.2.1.Final, 10.0.0.CR2, 10.0.0.CR4, 10.0.0.CR5
> Environment: probably not relevant but here is my environment
> {{Java Version : 1.8.0_60
> Java Vendor : Oracle Corporation
> OS Hostname : PAMWX125
> OS Architecture : amd64
> OS Name : Windows 7
> }}
> Reporter: Matthieu Brouillard
> Assignee: Matthieu Brouillard
> Fix For: 12.0.0.Alpha1
>
> Attachments: WFLY-5351diff, patch1.diff, timer-cli-failure.zip
>
>
> When (at least) a persistent calendar timer is created then cancelled, querying TimerService information via CLI (script or library) fails when retrieving also runtime information.
> We discovered the issue because our arquillian tests are failing due to some code in arquillian that fires the equivalent of the provided CLI command below when remotes tests are executed.
> Attached is a proposed patch and a demo project to reproduce in a simple way.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-3801) Wrong Transaction behaviour for EJBs if JTS is enabled
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin.... ]
David Lloyd reassigned WFLY-3801:
---------------------------------
Assignee: Stuart Douglas (was: David Lloyd)
> Wrong Transaction behaviour for EJBs if JTS is enabled
> ------------------------------------------------------
>
> Key: WFLY-3801
> URL: https://issues.jboss.org/browse/WFLY-3801
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Environment: standalone-full profile with JTS enabled
> Reporter: Wolf-Dieter Fink
> Assignee: Stuart Douglas
> Attachments: 456a624-withDestroy.log, 8d49872-error.log, enableJTS.cli, reproducer.zip, server.log
>
>
> If JTS is enabled the invocation of EJB's might show a arjuna warning for each method invocation:
> WARN [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
> This is only the case if other resources are involved, i.e. a DB via JPA.
> If a simple bean is used (like ejb-remote quickstart) this warning is not shown.
> It looks like the transaction is local commited but in case of a SFSB @Remove method the result is a " WFLYEE0006: Failed to destroy component instance Instance of SFTestBean" and the lifecycle method @PreDestroy is not invoked.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month