3 Replies Latest reply on Nov 1, 2011 1:17 PM by mgainty

    EJB timer service not available

    gholmer
      We're learning to set up clustering, and got the clusterjsp test app working successfully (fronted by Apache mod_jk load balancing). Now it's on to the harder stuff, so we tried to deploy our eCommerce app, which uses timers. All of them are non-persistent, declared with @Schedule(...persistent=false). When we deploy this app to the cluster, we get this: [#|2011-10-24T16:17:07.153-0500|SEVERE|glassfish3.1.1| javax.enterprise.system.tools.deployment.org.glassfish.de ployment.common|_ThreadID=145;_ThreadName=Thread-2;|Exception while invoking class org.glassfish.ejb.startup.EjbApplication start method java.lang.RuntimeException: EJB Timer Service is not available Mr. Google suggested this: http://download.oracle.com/docs/cd/E18930_01/html/821-2434/ggrvi.html#glhnl But I added com.sun.ejb.timer.ReadDBBeforeTimeout=false to the JVM properties of the cluster config and still got the error after re-deploying. Anybody got any suggestions? -- ____________________________________________________________ Glenn Holmer                          gholmer@weycogroup.com Software Engineer                        phone: 414-908-1809 Weyco Group, Inc.                          fax: 414-908-1601
        • 1. Re: EJB timer service not available
          mvatkina
          Try this instead: http://download.oracle.com/docs/cd/E18930_01/html/821-2418/beahw.html#gktqo -marina Glenn Holmer wrote: > We're learning to set up clustering, and got the clusterjsp test app > working successfully (fronted by Apache mod_jk load balancing). > > Now it's on to the harder stuff, so we tried to deploy our eCommerce > app, which uses timers. All of them are non-persistent, declared with > @Schedule(...persistent=false). > > When we deploy this app to the cluster, we get this: > > [#|2011-10-24T16:17:07.153-0500|SEVERE|glassfish3.1.1| > javax.enterprise.system.tools.deployment.org.glassfish.de > ployment.common|_ThreadID=145;_ThreadName=Thread-2;|Exception while > invoking class org.glassfish.ejb.startup.EjbApplication start method > java.lang.RuntimeException: EJB Timer Service is not available > > Mr. Google suggested this: > > http://download.oracle.com/docs/cd/E18930_01/html/821-2434/ggrvi.html#glhnl > > But I added com.sun.ejb.timer.ReadDBBeforeTimeout=false to the JVM > properties of the cluster config and still got the error after > re-deploying. > > Anybody got any suggestions? > >  
          • 2. Re: EJB timer service not available
            gholmer
            On Thu, 2011-10-27 at 12:13 -0700, Marina Vatkina wrote: > Try this instead: > http://download.oracle.com/docs/cd/E18930_01/html/821-2418/beahw.html#gktqo    Thanks, that seems to have gotten us past that point. I dumped the DDL from Derby, created it as a Postgres database, then changed GlassFish's jdbc__TimerPool resource to point to it. Since none of our timers are persistent, it won't get used anyway, and I can't say whether it would work if they were, since I had to change "blob" to "bytea". But at least it got us as far as the next obstacle. -- ____________________________________________________________ Glenn Holmer                          gholmer@weycogroup.com Software Engineer                        phone: 414-908-1809 Weyco Group, Inc.                          fax: 414-908-1601
            • 3. RE: EJB timer service not available
              mgainty
              Glenn dont feel bad..i had the same problem with EJB3TimerServicein in JBOSS. after poring thru Redhats marketing documentation i discovered the database params were incirrect someone had changed the password which fubared the DataSourceBinding and because DataSourceBinding was a dependency of EJB3TimerServicethis prevented EJB3TimerService from starting Frustrated with Redhat Martin Gainty ______________________________________________ Jogi és Bizalmassági kinyilatkoztatás/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Ez az üzenet bizalmas.  Ha nem ön az akinek szánva volt, akkor kérjük, hogy jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése nem megengedett.  Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi alkalmazhatósága sincs.  Mivel az electronikus üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet tartalma miatt. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Subject: Re: EJB timer service not available > From: gholmer@weycogroup.com > To: users@glassfish.java.net > Date: Mon, 31 Oct 2011 16:03:21 -0500 > > On Thu, 2011-10-27 at 12:13 -0700, Marina Vatkina wrote: > > Try this instead: > > http://download.oracle.com/docs/cd/E18930_01/html/821-2418/beahw.html#gktqo >    > Thanks, that seems to have gotten us past that point. I dumped the DDL > from Derby, created it as a Postgres database, then changed GlassFish's > jdbc__TimerPool resource to point to it. Since none of our timers are > persistent, it won't get used anyway, and I can't say whether it would > work if they were, since I had to change "blob" to "bytea". But at least > it got us as far as the next obstacle. > > -- > ____________________________________________________________ > Glenn Holmer                          gholmer@weycogroup.com > Software Engineer                        phone: 414-908-1809 > Weyco Group, Inc.                          fax: 414-908-1601 >