[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups
by Karim AMMOUS (JIRA)
[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ]
Karim AMMOUS commented on JGRP-1876:
------------------------------------
Yes finally all members merge into a new view {A,B,C}.
I'm making a sequence diagram of what happen in that scenario.
> MERGE3 : Strange number and content of subgroups
> ------------------------------------------------
>
> Key: JGRP-1876
> URL: https://issues.jboss.org/browse/JGRP-1876
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.2
> Reporter: Karim AMMOUS
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6, 3.6.2
>
> Attachments: 4Subgroups.zip, ChannelCreator.java, DkeJgrpAddress.java, karim-logs-files.zip, MergeTest4.java, MergeViewWith210Subgroups.log, SplitMergeTest.java, views.txt
>
>
> Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2).
> The final mergeView is correct and contains 210 members.
> Here is an extract of subviews:
> {code}
> INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172]
> 210 subgroups
> [....
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]]
> [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]]
> ....]
> {code}
> II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view.
> Example:
> {code}
> {A, B, C} => {A, B, C} and {C} => {A, B, C}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1876:
--------------------------------
Karim: in your scenario, if you wait a little, does the BC subgroup merge again with A ?
> MERGE3 : Strange number and content of subgroups
> ------------------------------------------------
>
> Key: JGRP-1876
> URL: https://issues.jboss.org/browse/JGRP-1876
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.2
> Reporter: Karim AMMOUS
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6, 3.6.2
>
> Attachments: 4Subgroups.zip, ChannelCreator.java, DkeJgrpAddress.java, karim-logs-files.zip, MergeTest4.java, MergeViewWith210Subgroups.log, SplitMergeTest.java, views.txt
>
>
> Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2).
> The final mergeView is correct and contains 210 members.
> Here is an extract of subviews:
> {code}
> INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172]
> 210 subgroups
> [....
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]]
> [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]]
> ....]
> {code}
> II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view.
> Example:
> {code}
> {A, B, C} => {A, B, C} and {C} => {A, B, C}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4262) Memory of expired session not released
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4262?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4262:
--------------------------------------
Can you use a profiler to see what is hanging on to the sessions? Also can you confirm that the sessions are actually expired after the specified timeout (i.e. the sessions are not actually usable)?
> Memory of expired session not released
> --------------------------------------
>
> Key: WFLY-4262
> URL: https://issues.jboss.org/browse/WFLY-4262
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.2.0.Final
> Environment: Running on Windows 7
> Wildfly 8.2
> Primefaces 5.1
> Reporter: Jose Perez
> Assignee: Stuart Douglas
> Attachments: Expired session still available.png, JVM memory usage.png, screenshot-1.png
>
>
> Expecting Wildfly to remove expired user session data after 20 minutes. But the memory is released later (see the screen shots from VisualVM)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4262) Memory of expired session not released
by Jose Perez (JIRA)
[ https://issues.jboss.org/browse/WFLY-4262?page=com.atlassian.jira.plugin.... ]
Jose Perez commented on WFLY-4262:
----------------------------------
Sessions are removed but not after time specified in the web.xml.
I tried to call System.gc() several times but the sessions were not cleaned. I run JMeter for 0.5h creating new sessions. Then after ~1.5h the memory was released automatically, cleaning old sessions (which expired 40min earlier, and the newest expired ones)
> Memory of expired session not released
> --------------------------------------
>
> Key: WFLY-4262
> URL: https://issues.jboss.org/browse/WFLY-4262
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.2.0.Final
> Environment: Running on Windows 7
> Wildfly 8.2
> Primefaces 5.1
> Reporter: Jose Perez
> Assignee: Stuart Douglas
> Attachments: Expired session still available.png, JVM memory usage.png, screenshot-1.png
>
>
> Expecting Wildfly to remove expired user session data after 20 minutes. But the memory is released later (see the screen shots from VisualVM)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-3714) Presence of <servlet-name> and <url-pattern> is not validated for <servlet-mapping> inside the web.xml
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-3714?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-3714.
----------------------------------
Fix Version/s: 9.0.0.Beta1
Resolution: Done
This metadata change should be upstream now
> Presence of <servlet-name> and <url-pattern> is not validated for <servlet-mapping> inside the web.xml
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3714
> URL: https://issues.jboss.org/browse/WFLY-3714
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.0.Alpha1
> Reporter: Jay Kumar SenSharma
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Beta1
>
>
> - WildFly do not validate if the <servlet-mapping> tag has valid mappings or not. This should have been handled properly.
> *Example:* If following kind of web.xml based application is deployed on WildFly9 then
> {code}
> <?xml version="1.0"?>
> <web-app xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
> version="3.0">
> <servlet>
> <servlet-name>MyServlet</servlet-name>
> <servlet-class>servlets.MyServlet</servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
> <servlet-mapping>
> <servlet-name>MyServlet</servlet-name>
> <!--url-pattern></url-pattern--> <!-- NOTICE url-pattern-tag is missing here -->
> </servlet-mapping>
> </web-app>
> {code}
> - With the above kind of web.xml a NullPointerException is encountered during deployment.
> {code}
> 15:50:20,207 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./ContextParamNullDemo.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./ContextParamNullDemo.UndertowDeploymentInfoService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.handleServletMappings(UndertowDeploymentInfoService.java:910)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:656)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:252)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> ... 3 more
> 15:50:20,348 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ContextParamNullDemo.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./ContextParamNullDemo.UndertowDeploymentInfoService" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./ContextParamNullDemo.UndertowDeploymentInfoService: Failed to start service
> Caused by: java.lang.NullPointerException"}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-3953) @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method"
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-3953?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-3953:
--------------------------------------
Can you reproduce on WF9?
> @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method"
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3953
> URL: https://issues.jboss.org/browse/WFLY-3953
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Reporter: Andrei Tchijov
> Assignee: Stuart Douglas
>
> Please take a look at this gist : https://gist.github.com/leapingbytes/01838d9534638cb04200
> In case of @Schedule second and all consecutive invocations produce this
> {code}
> 13:19:30,635 ERROR U( ) [org.jboss.as.ejb3] (EJB default - 8) JBAS014120: Error invoking timeout for timer: [id=ba9f1c67-5a91-42ff-8276-f715efaa3723 timedObjectId=ChumbaServer-2.0-SNAPSHOT.ChumbaServer-2.0-SNAPSHOT.SettingsManagerImpl auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@5a898863 initialExpiration=Wed Oct 08 13:17:30 EEST 2014 intervalDuration(in milli sec)=60000 nextExpiration=Wed Oct 08 13:20:30 EEST 2014 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method null is not a timeout method
> at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_67]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-3953) @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method"
by Jaap Reitsma (JIRA)
[ https://issues.jboss.org/browse/WFLY-3953?page=com.atlassian.jira.plugin.... ]
Jaap Reitsma edited comment on WFLY-3953 at 1/18/15 5:14 PM:
-------------------------------------------------------------
I have the same issue in Wildfly 8.1.0. I have tried several configurations with the @Schedule annotation. What I noted was that the error always happens once in an hour. I suspect some idle bean removal thread is interfering? I also noted that the error message does not print the info attribute and persistence attribute correctly. My timer is set to be not persistent.
A piece of log:
{noformat} 20:45:00,048 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 9) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 20:45:00 CET 2015)
21:00:00,041 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 10) Cache cleanup all objects before Sat Jan 17 21:00:00 CET 2015
21:00:00,045 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 10) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:00:00 CET 2015)
21:00:00,695 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014120: Error invoking timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cached
ItemBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in
milli sec)=3600000 nextExpiration=Sun Jan 18 22:00:00 CET 2015 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method
null is not a timeout method
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
21:00:00,702 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014121: Timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cachedItemBean auto-timer?:false
persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in milli sec)=3600000 nextExp
iration=Sun Jan 18 22:00:00 CET 2015 timerState=IN_TIMEOUT info=null will be retried
21:00:00,703 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014123: Retrying timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cachedItemBe
an auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in milli
sec)=3600000 nextExpiration=Sun Jan 18 22:00:00 CET 2015 timerState=IN_TIMEOUT info=null
21:00:00,712 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014122: Error during retrying timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB
.cachedItemBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDura
tion(in milli sec)=3600000 nextExpiration=Sun Jan 18 22:00:00 CET 2015 timerState=RETRY_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method beca
use method null is not a timeout method
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.retryTimeout(TimerTask.java:219) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:176) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
21:15:00,003 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 2) Cache cleanup all objects before Sat Jan 17 21:15:00 CET 2015
21:15:00,006 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 2) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:15:00 CET 2015)
21:30:00,068 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 3) Cache cleanup all objects before Sat Jan 17 21:30:00 CET 2015
21:30:00,070 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 3) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:30:00 CET 2015)
21:45:00,096 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 4) Cache cleanup all objects before Sat Jan 17 21:45:00 CET 2015
21:45:00,097 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 4) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:45:00 CET 2015)
22:00:00,042 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 5) Cache cleanup all objects before Sat Jan 17 22:00:00 CET 2015
22:00:00,044 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 5) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 22:00:00 CET 2015)
22:00:00,697 ERROR [org.jboss.as.ejb3] (EJB default - 6) JBAS014120: Error invoking timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cached
ItemBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in
milli sec)=3600000 nextExpiration=Sun Jan 18 23:00:00 CET 2015 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method
null is not a timeout method
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
{noformat}
was (Author: reitsmaj):
I have the same issue in Wildfly 8.1.0. I have tried several configurations with the @Schedule annotation. What I noted was that the error always happens once in an hour. I suspect some idle bean removal thread is interfering? I also noted that the error message does not print the info attribute and persistence attribute correctly. My timer is set to be not persistent.
A piece of log:
{{ 20:45:00,048 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 9) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 20:45:00 CET 2015)
21:00:00,041 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 10) Cache cleanup all objects before Sat Jan 17 21:00:00 CET 2015
21:00:00,045 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 10) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:00:00 CET 2015)
21:00:00,695 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014120: Error invoking timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cached
ItemBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in
milli sec)=3600000 nextExpiration=Sun Jan 18 22:00:00 CET 2015 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method
null is not a timeout method
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
21:00:00,702 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014121: Timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cachedItemBean auto-timer?:false
persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in milli sec)=3600000 nextExp
iration=Sun Jan 18 22:00:00 CET 2015 timerState=IN_TIMEOUT info=null will be retried
21:00:00,703 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014123: Retrying timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cachedItemBe
an auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in milli
sec)=3600000 nextExpiration=Sun Jan 18 22:00:00 CET 2015 timerState=IN_TIMEOUT info=null
21:00:00,712 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014122: Error during retrying timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB
.cachedItemBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDura
tion(in milli sec)=3600000 nextExpiration=Sun Jan 18 22:00:00 CET 2015 timerState=RETRY_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method beca
use method null is not a timeout method
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.retryTimeout(TimerTask.java:219) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:176) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
21:15:00,003 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 2) Cache cleanup all objects before Sat Jan 17 21:15:00 CET 2015
21:15:00,006 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 2) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:15:00 CET 2015)
21:30:00,068 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 3) Cache cleanup all objects before Sat Jan 17 21:30:00 CET 2015
21:30:00,070 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 3) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:30:00 CET 2015)
21:45:00,096 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 4) Cache cleanup all objects before Sat Jan 17 21:45:00 CET 2015
21:45:00,097 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 4) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:45:00 CET 2015)
22:00:00,042 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 5) Cache cleanup all objects before Sat Jan 17 22:00:00 CET 2015
22:00:00,044 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 5) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 22:00:00 CET 2015)
22:00:00,697 ERROR [org.jboss.as.ejb3] (EJB default - 6) JBAS014120: Error invoking timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cached
ItemBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in
milli sec)=3600000 nextExpiration=Sun Jan 18 23:00:00 CET 2015 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method
null is not a timeout method
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] }}
> @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method"
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3953
> URL: https://issues.jboss.org/browse/WFLY-3953
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Reporter: Andrei Tchijov
> Assignee: Stuart Douglas
>
> Please take a look at this gist : https://gist.github.com/leapingbytes/01838d9534638cb04200
> In case of @Schedule second and all consecutive invocations produce this
> {code}
> 13:19:30,635 ERROR U( ) [org.jboss.as.ejb3] (EJB default - 8) JBAS014120: Error invoking timeout for timer: [id=ba9f1c67-5a91-42ff-8276-f715efaa3723 timedObjectId=ChumbaServer-2.0-SNAPSHOT.ChumbaServer-2.0-SNAPSHOT.SettingsManagerImpl auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@5a898863 initialExpiration=Wed Oct 08 13:17:30 EEST 2014 intervalDuration(in milli sec)=60000 nextExpiration=Wed Oct 08 13:20:30 EEST 2014 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method null is not a timeout method
> at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_67]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-3953) @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method"
by Jaap Reitsma (JIRA)
[ https://issues.jboss.org/browse/WFLY-3953?page=com.atlassian.jira.plugin.... ]
Jaap Reitsma commented on WFLY-3953:
------------------------------------
I have the same issue in Wildfly 8.1.0. I have tried several configurations with the @Schedule annotation. What I noted was that the error always happens once in an hour. I suspect some idle bean removal thread is interfering? I also noted that the error message does not print the info attribute and persistence attribute correctly. My timer is set to be not persistent.
A piece of log:
{{ 20:45:00,048 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 9) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 20:45:00 CET 2015)
21:00:00,041 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 10) Cache cleanup all objects before Sat Jan 17 21:00:00 CET 2015
21:00:00,045 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 10) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:00:00 CET 2015)
21:00:00,695 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014120: Error invoking timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cached
ItemBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in
milli sec)=3600000 nextExpiration=Sun Jan 18 22:00:00 CET 2015 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method
null is not a timeout method
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
21:00:00,702 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014121: Timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cachedItemBean auto-timer?:false
persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in milli sec)=3600000 nextExp
iration=Sun Jan 18 22:00:00 CET 2015 timerState=IN_TIMEOUT info=null will be retried
21:00:00,703 INFO [org.jboss.as.ejb3] (EJB default - 1) JBAS014123: Retrying timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cachedItemBe
an auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in milli
sec)=3600000 nextExpiration=Sun Jan 18 22:00:00 CET 2015 timerState=IN_TIMEOUT info=null
21:00:00,712 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014122: Error during retrying timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB
.cachedItemBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDura
tion(in milli sec)=3600000 nextExpiration=Sun Jan 18 22:00:00 CET 2015 timerState=RETRY_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method beca
use method null is not a timeout method
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.retryTimeout(TimerTask.java:219) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:176) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
21:15:00,003 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 2) Cache cleanup all objects before Sat Jan 17 21:15:00 CET 2015
21:15:00,006 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 2) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:15:00 CET 2015)
21:30:00,068 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 3) Cache cleanup all objects before Sat Jan 17 21:30:00 CET 2015
21:30:00,070 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 3) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:30:00 CET 2015)
21:45:00,096 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 4) Cache cleanup all objects before Sat Jan 17 21:45:00 CET 2015
21:45:00,097 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 4) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 21:45:00 CET 2015)
22:00:00,042 DEBUG [nl.novay.buzzcuit.core.bean.impl.CacheManagerBean] (EJB default - 5) Cache cleanup all objects before Sat Jan 17 22:00:00 CET 2015
22:00:00,044 DEBUG [nl.novay.buzzcuit.core.logging.DebugLogger] (EJB default - 5) Call: CachedItemDaoImpl.removeStaleItems(Date Sat Jan 17 22:00:00 CET 2015)
22:00:00,697 ERROR [org.jboss.as.ejb3] (EJB default - 6) JBAS014120: Error invoking timeout for timer: [id=cdec4a35-0b50-4732-9485-9e07528037a7 timedObjectId=CoreEAR.CoreEJB.cached
ItemBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@39c722c6 initialExpiration=Fri Jan 16 02:00:00 CET 2015 intervalDuration(in
milli sec)=3600000 nextExpiration=Sun Jan 18 23:00:00 CET 2015 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method
null is not a timeout method
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] }}
> @Schedule annotation produces "Cannot invoke timeout method because method null is not a timeout method"
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3953
> URL: https://issues.jboss.org/browse/WFLY-3953
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.1.0.Final
> Reporter: Andrei Tchijov
> Assignee: Stuart Douglas
>
> Please take a look at this gist : https://gist.github.com/leapingbytes/01838d9534638cb04200
> In case of @Schedule second and all consecutive invocations produce this
> {code}
> 13:19:30,635 ERROR U( ) [org.jboss.as.ejb3] (EJB default - 8) JBAS014120: Error invoking timeout for timer: [id=ba9f1c67-5a91-42ff-8276-f715efaa3723 timedObjectId=ChumbaServer-2.0-SNAPSHOT.ChumbaServer-2.0-SNAPSHOT.SettingsManagerImpl auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@5a898863 initialExpiration=Wed Oct 08 13:17:30 EEST 2014 intervalDuration(in milli sec)=60000 nextExpiration=Wed Oct 08 13:20:30 EEST 2014 timerState=IN_TIMEOUT info=null: java.lang.RuntimeException: JBAS014481: Cannot invoke timeout method because method null is not a timeout method
> at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:84) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:114) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.ejb3.timerservice.task.TimerTask.callTimeout(TimerTask.java:196) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.ejb3.timerservice.task.TimerTask.run(TimerTask.java:168) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_67]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4262) Memory of expired session not released
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4262?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4262:
--------------------------------------
So the session is removed after garbage collection?
> Memory of expired session not released
> --------------------------------------
>
> Key: WFLY-4262
> URL: https://issues.jboss.org/browse/WFLY-4262
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.2.0.Final
> Environment: Running on Windows 7
> Wildfly 8.2
> Primefaces 5.1
> Reporter: Jose Perez
> Assignee: Stuart Douglas
> Attachments: Expired session still available.png, JVM memory usage.png, screenshot-1.png
>
>
> Expecting Wildfly to remove expired user session data after 20 minutes. But the memory is released later (see the screen shots from VisualVM)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months