9:15 a.m.
jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion
"Re: SLSB pool size is always one in jboss 6.0 CR1 using ejb 3.1"
To view the discussion, visit: http://community.jboss.org/message/572797#572797
--------------------------------------------------------------
aravind kopparthi wrote:
because of the fact that SingletonBean's timeout did not choose/pick the new instance
of SLSB what it is referencing instead @timout method was blocked until the
previous(timout expiration event) slsbs method completed.
Did you try changing the
Lock attribute which I explained in some of my previous posts?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/572797#572797]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
9:18 a.m.
aravind kopparthi [http://community.jboss.org/people/aravindsk] created the discussion
"Re: SLSB pool size is always one in jboss 6.0 CR1 using ejb 3.1"
To view the discussion, visit: http://community.jboss.org/message/572798#572798
--------------------------------------------------------------
yes, i did.
@Startup
@Singleton
@Lock(LockType.READ)
public class SingletonScheduleBean {
String item = "MySchedule";
...
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/572798#572798]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
9:18 a.m.
jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion
"Re: SLSB pool size is always one in jboss 6.0 CR1 using ejb 3.1"
To view the discussion, visit: http://community.jboss.org/message/572799#572799
--------------------------------------------------------------
And you are still seeing the same blocking behaviour? Can you post the new logs with this
change?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/572799#572799]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:48 p.m.
aravind kopparthi [http://community.jboss.org/people/aravindsk] created the discussion
"Re: SLSB pool size is always one in jboss 6.0 CR1 using ejb 3.1"
To view the discussion, visit: http://community.jboss.org/message/572860#572860
--------------------------------------------------------------
yes, i am still seeing that blocking:
http://community.jboss.org/message/572522#572522
http://community.jboss.org/message/572522#572522
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/572860#572860]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4 p.m.
aravind kopparthi [http://community.jboss.org/people/aravindsk] created the discussion
"Re: SLSB pool size is always one in jboss 6.0 CR1 using ejb 3.1"
To view the discussion, visit: http://community.jboss.org/message/572890#572890
--------------------------------------------------------------
i changed the implementation little bit so that i have completely removed the
SingtonScheduleBean and moved the timer to SLSBean. from functionlaity wise it is doing
exactly what i was expected in terms of firing timeout by container (timerservice) and
calling aviable SLSB instances from the pool as i limited to 7. in the
ejb-interseptors-aop.xml using StrictMaxPool=7
but server throws below exception( this make sense because i ristricted slsbs to be 7) and
if the TimerService expires it has to wait for the SLSBs from completing their current
process to get the 8th one.
how to stop these ERRORS to be thrown in logs.
16:54:46,343 ERROR [org.jboss.ejb3.timerservice.mk2.task.TimerTask] Error during retyring
timeout for timer: [id=960cd66d-3726-481b-a617-5e298ce86b73
timedObjectId=jboss.j2ee:jar=javaee6-app.war,name=SLSBProcessBean,service=EJB3
auto-timer?:true persistent?:false
timerService=org.jboss.ejb3.timerservice.mk2.TimerServiceImpl@2cfbd8 initialExpiration=Wed
Nov 24 00:00:00 EST 2010 intervalDuration(in milli sec)=0 nextExpiration=Wed Nov 24
16:53:22 EST 2010 timerState=IN_TIMEOUT: javax.ejb.EJBException: Failed to acquire the
pool semaphore, strictTimeout=10000
at org.jboss.ejb3.pool.StrictMaxPool.acquire(StrictMaxPool.java:86) [:1.6.3]
at org.jboss.ejb3.pool.StrictMaxPool.get(StrictMaxPool.java:145) [:1.6.3]
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at
org.jboss.ejb3.core.context.SessionInvocationContextAdapter.proceed(SessionInvocationContextAdapter.java:91)
[:1.6.3]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:247)
[:0.0.1]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.required(CMTTxInterceptor.java:349) [:0.0.1]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invoke(CMTTxInterceptor.java:209) [:0.0.1]
at org.jboss.ejb3.tx2.aop.CMTTxInterceptorWrapper.invoke(CMTTxInterceptorWrapper.java:52)
[:0.0.1]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
[:1.0.0.GA]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at
org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at
org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at
org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
[:1.0.1]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at org.jboss.ejb3.stateless.StatelessContainer.callTimeout(StatelessContainer.java:692)
[:1.6.3]
at
org.jboss.ejb3.timerservice.mk2.task.CalendarTimerTask.callTimeout(CalendarTimerTask.java:80)
[:1.0.0-alpha-10]
at org.jboss.ejb3.timerservice.mk2.task.TimerTask.run(TimerTask.java:127)
[:1.0.0-alpha-10]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_13]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_13]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_13]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
[:1.6.0_13]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
[:1.6.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_13]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_13]
16:54:46,343 ERROR [org.jboss.ejb3.timerservice.mk2.task.TimerTask] Error during retyring
timeout for timer: [id=960cd66d-3726-481b-a617-5e298ce86b73
timedObjectId=jboss.j2ee:jar=javaee6-app.war,name=SLSBProcessBean,service=EJB3
auto-timer?:true persistent?:false
timerService=org.jboss.ejb3.timerservice.mk2.TimerServiceImpl@2cfbd8 initialExpiration=Wed
Nov 24 00:00:00 EST 2010 intervalDuration(in milli sec)=0 nextExpiration=Wed Nov 24
16:53:22 EST 2010 timerState=IN_TIMEOUT: javax.ejb.EJBException: Failed to acquire the
pool semaphore, strictTimeout=10000
at org.jboss.ejb3.pool.StrictMaxPool.acquire(StrictMaxPool.java:86) [:1.6.3]
at org.jboss.ejb3.pool.StrictMaxPool.get(StrictMaxPool.java:145) [:1.6.3]
at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at
org.jboss.ejb3.core.context.SessionInvocationContextAdapter.proceed(SessionInvocationContextAdapter.java:91)
[:1.6.3]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:247)
[:0.0.1]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.required(CMTTxInterceptor.java:349) [:0.0.1]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invoke(CMTTxInterceptor.java:209) [:0.0.1]
at org.jboss.ejb3.tx2.aop.CMTTxInterceptorWrapper.invoke(CMTTxInterceptorWrapper.java:52)
[:0.0.1]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
[:1.0.0.GA]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at
org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at
org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at
org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
[:1.0.1]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86)
[:1.6.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
[jboss-aop.jar:2.2.1.Alpha3]
at org.jboss.ejb3.stateless.StatelessContainer.callTimeout(StatelessContainer.java:692)
[:1.6.3]
at
org.jboss.ejb3.timerservice.mk2.task.CalendarTimerTask.callTimeout(CalendarTimerTask.java:80)
[:1.0.0-alpha-10]
at org.jboss.ejb3.timerservice.mk2.task.TimerTask.run(TimerTask.java:127)
[:1.0.0-alpha-10]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_13]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_13]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_13]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
[:1.6.0_13]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
[:1.6.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_13]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_13]
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/572890#572890]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:08 p.m.
jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion
"Re: SLSB pool size is always one in jboss 6.0 CR1 using ejb 3.1"
To view the discussion, visit: http://community.jboss.org/message/572916#572916
--------------------------------------------------------------
aravind kopparthi wrote:
yes, i am still seeing that blocking:
http://community.jboss.org/message/572522#572522
http://community.jboss.org/message/572522#572522
I asked for the new logs, please.
Pointing to some old logs which were generated out a different code is of no use.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/572916#572916]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5172
days inactive
5173
days old
5 comments
2 participants
participants (2)
-
aravind kopparthi -
jaikiran pai