[JBoss JIRA] (WFLY-13051) provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService
by nimo stephan (Jira)
[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ]
nimo stephan commented on WFLY-13051:
-------------------------------------
Ok thanks for the information.
>If you really need to remove tasks when canceled (instead of when these expire)
The problem is that even if the task is expired it will be within the scheduled queue for the next time and then will be fired again when I use
{code:java}
// no possibility to cancel tasks after it was submitted
executor.scheduleWithFixedDelay(..)
{code}
Hence there is a need to cancel the task..the spec lacks for such cases..
However, thanks for that info..maybe you can keep this in mind when discussing to improve the spec..
> provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService
> ------------------------------------------------------------------
>
> Key: WFLY-13051
> URL: https://issues.redhat.com/browse/WFLY-13051
> Project: WildFly
> Issue Type: Enhancement
> Components: Concurrency Utilities
> Affects Versions: 19.0.0.Beta1
> Reporter: nimo stephan
> Assignee: Eduardo Martins
> Priority: Major
>
> Using
> {code:java}
> @Resource
> private ManagedScheduledExecutorService executor;
> {code}
> provides no possiblity to setRemoveOnCancelPolicy to true.
> A casting within a method:
> {code:java}
> ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true);
> {code}
> throws the error:
> {code:java}
> Caused by: javax.ejb.EJBException: java.lang.ClassCastException: class org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter cannot be cast to class java.util.concurrent.ScheduledThreadPoolExecutor (org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter is in unnamed module of loader 'org.glassfish.javax.enterprise.concurrent' @a93b7af; java.util.concurrent.ScheduledThreadPoolExecutor is in module java.base of loader 'bootstrap')
> at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246)
> at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388)
> at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68)
> {code}
> Please provide option to cast or if not possible to add the property
> {code:java}
> setRemoveOnCancelPolicy()
> {code}
> within the object ManagedScheduledExecutorService. Because without it, we cannot remove a task from the queue with "future.cancel(false)".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13514) Huge memory leak in WildFly
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13514?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-13514:
-----------------------------------------
Thanks so much [~konbk] for the report, [~manovotn] for the analysis and [~flavia.rainone] for the fix!
> Huge memory leak in WildFly
> ---------------------------
>
> Key: WFLY-13514
> URL: https://issues.redhat.com/browse/WFLY-13514
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF, Web (Undertow)
> Affects Versions: 18.0.1.Final, 19.1.0.Final, 20.0.0.Beta1
> Reporter: Konrad Bak
> Assignee: Flavia Rainone
> Priority: Blocker
> Fix For: 20.0.0.Final
>
>
> https://github.com/konbk/bug-report-wildfly-oome
> The project shows a huge memory leak introduced in recent WildFly versions that can crash a real-world Java EE application in a matter of hours.
> When a JSF page contains any component bound to page variable, all CDI beans (regardless of scope) used on that page stay in memory.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5400) Executable model build fails with SerialVersionUID and key annotations
by Matteo Casalino (Jira)
[ https://issues.redhat.com/browse/DROOLS-5400?page=com.atlassian.jira.plug... ]
Matteo Casalino commented on DROOLS-5400:
-----------------------------------------
Note: this is similar to DROOLS-5340, but occurs when the declared type has all its fields annotated with _@key_
> Executable model build fails with SerialVersionUID and key annotations
> ----------------------------------------------------------------------
>
> Key: DROOLS-5400
> URL: https://issues.redhat.com/browse/DROOLS-5400
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.38.0.Final
> Reporter: Matteo Casalino
> Assignee: Mario Fusco
> Priority: Minor
> Attachments: serial-version-uid-exec-model.zip
>
>
> Executable model compilation fails on declared types with both _@SerialVersionUID_ and _@key_ annotations.
> Example of DRL that fails to compile:
> {noformat}
> declare ServiceInformation
> @serialVersionUID( 0 )
> code: String @key
> end
> rule "create new ServiceInformation"
> when
> then
> insert( new ServiceInformation("123456") );
> end
> {noformat}
> Error:
> {noformat}
> Error Messages:
> Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=null, line=56, column=0
> text=Duplicate method ServiceInformation(String) in type ServiceInformation]
> Message [id=2, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=null, line=61, column=0
> text=Duplicate method ServiceInformation(String) in type ServiceInformation]
> {noformat}
> The example works fine when compiling without executable model.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-10173?page=com.atlassian.jira.plugi... ]
Paul Ferraro reopened WFLY-10173:
---------------------------------
[~cfang] We are still seeing this test intermittently fail in the CI.
e.g.
https://ci.wildfly.org/buildConfiguration/WF_PullRequest_LinuxJdk11/207534
https://ci.wildfly.org/buildConfiguration/WF_PullRequest_LinuxSm/207535
> EjbInvocationStatisticsTestCase fails on Windows: wait-time=0
> -------------------------------------------------------------
>
> Key: WFLY-10173
> URL: https://issues.redhat.com/browse/WFLY-10173
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 12.0.0.Final
> Reporter: Jan Kalina
> Assignee: Cheng Fang
> Priority: Major
> Fix For: 20.0.0.Final
>
>
> Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0 (verified it is 0 by adding debug message).
> For me it fails allTests in most of cases, but when running test standalone, it fails only in 1 of 4 cases.
> I suppose it is because of too short sleep in AbstractManagedBean. (in test is called 4 times, each invocation include 50ms sleep, so I consider probable the wait-time is 0 - need to use longer sleeps to fulfill the test)
> {code}
> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.078 s <<< FAILURE! - in org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase
> [ERROR] testSingletonWaitTime(org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase) Time elapsed: 0.438 s <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.validateWaitTimeStatistic(EjbInvocationStatisticsTestCase.java:179)
> at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.testSingletonWaitTime(EjbInvocationStatisticsTestCase.java:148)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379)
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5400) Executable model build fails with SerialVersionUID and key annotations
by Matteo Casalino (Jira)
Matteo Casalino created DROOLS-5400:
---------------------------------------
Summary: Executable model build fails with SerialVersionUID and key annotations
Key: DROOLS-5400
URL: https://issues.redhat.com/browse/DROOLS-5400
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.38.0.Final
Reporter: Matteo Casalino
Assignee: Mario Fusco
Attachments: serial-version-uid-exec-model.zip
Executable model compilation fails on declared types with both _@SerialVersionUID_ and _@key_ annotations.
Example of DRL that fails to compile:
{noformat}
declare ServiceInformation
@serialVersionUID( 0 )
code: String @key
end
rule "create new ServiceInformation"
when
then
insert( new ServiceInformation("123456") );
end
{noformat}
Error:
{noformat}
Error Messages:
Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=null, line=56, column=0
text=Duplicate method ServiceInformation(String) in type ServiceInformation]
Message [id=2, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=null, line=61, column=0
text=Duplicate method ServiceInformation(String) in type ServiceInformation]
{noformat}
The example works fine when compiling without executable model.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month