title: No timers to be deleted for id: xxx
body: <p>Using EJB timers in a singleton session bean in GlassFish 4.1/Java EE 7 as follows.</p>
  
  <pre><code>@Singleton
  @LocalBean
  @Startup
  public class BackgroundJobManager {
  
      @PersistenceContext
      private EntityManager entityManager;
  
      @PostConstruct
      private void init() {
          // Do something.
      }
  
      @Schedule(hour = "*/1", minute = "0", second = "0", persistent = false)
      public void doHourlyJob() {
          // Do something hourly.
      }
  
      @Schedule(hour = "*", minute = "*/1", second = "0", persistent = false)
      private void doOnEveryMinute() {
          // Do something on every minute.
      }
  }
  </code></pre>
  
  <p>Although the log level is <code>INFO</code>, the following somewhat wonky caveats appear on the server terminal upon (re)deploying the application.</p>
  
  <pre><code>Info:   No timers to be deleted for id: 94427432094072832
  Info:   No timers to be deleted for id: 94427432094072832
  </code></pre>
  
  <p>What does it mean? Is it avoidable or the container attempts to warn against something seriously (is there any fix in this case)?</p>
  
  <hr>
  
  <p>The server also logs the following lines on startup.</p>
  
  <pre><code>Info:   Portable JNDI names for EJB TimerBean: [java:global/ejb-timer-service-app/TimerBean, java:global/ejb-timer-service-app/TimerBean!org.glassfish.ejb.persistent.timer.TimerLocal]
  Info:   Loading application [ejb-timer-service-app] at [/ejb-timer-service-app]
  Info:   ejb.timer_service_started
  Info:   ==&gt; Restoring Timers ... 
  Info:   EclipseLink, version: Eclipse Persistence Services - 2.6.0.v20150309-bf26070
  Info:   /file:/C:/Program Files/glassfish-4.1/glassfish/domains/domain1/applications/ejb-timer-service-app/WEB-INF/classes/___EJB__Timer__App login successful
  Info:   There are no EJB Timers owned by this server
  Info:   &lt;== ... Timers Restored.
  </code></pre>