ifications are scheduled relative to the time of the first expiration. If expiration is delayed (e.g.
 due to the interleaving of other method calls on the bean), two or more expiration notifications may occur in close
 succession to "catch up".</dd>
<dd><code>info</code> - application information to be delivered along with the timer expiration. This can be null.</dd>
<dt>Returns:</dt>
<dd>the newly created Timer.</dd>
<dt>Throws:</dt>
<dd><code><a href="https://docs.oracle.com/en/java/javase/17/docs/api/ja