glassfishrobot

* **Issue Imported From:** https://github.com/javaee/glassfish/issues/22079 * **Original Issue Raised By:**@edburns * **Original Issue Assigned To:** @edburns * **Original Issue Closed By:**@yaminikb

* **Issue Imported From:** https://github.com/javaee/glassfish/issues/21495 * **Original Issue Raised By:**@glassfishrobot * **Original Issue Assigned To:** @naman223 * **Original Issue Closed By:**@amykang2020

@glassfishrobot Commented napu said: I can confirm the same issue.

@glassfishrobot Commented iordannalbantov said: We have it too. The consequent problem is that our timers are expunged afterwards which makes it critical for us. Downgrade is not an option because...

@glassfishrobot Commented douglasjunior said: I also have a method that persists much data. It displays Warn, but the data is successfully persisted. Exception is not thrown. This Warn has caused...

@glassfishrobot Commented fgonzales said: We are running into the same issue. I also verified that Glassfish 4.1 does not have this problem. It looks specific to 4.1.1.

@glassfishrobot Commented lprimak said: I suggest you open a Payara issue for this. It would help also if you have a ready reproducer application available.

@glassfishrobot Commented rgrashel said: Is there any movement on this issue? if can be used to extend the transaction timeout of an EJB timer, can someone please post an example...

@glassfishrobot Commented lprimak said: Both GlassFish and Payara are actually functioning property in this instance. The solution for this is either to extend the tx timeout via cmt-timeout-in-seconds or via...

@glassfishrobot Commented fgonzales said: In EJBContainerTransactionManager, cmtTimeoutInSeconds is hardcoded to 120 seconds. This was a change made in 4.1.1\. This hard-coded value cannot be over-ridden via the domain configuration. It...