[jboss-user] [JBoss Seam] - Re: Can not persist EJB3 Timer since Jboss 4.2.0cr2 + seam
kevinpauli wrote : I'm seeing the same problem here, with the 4.2.0GA release (though we are not using the Seam annotation to create it, we're invoking the TimerService directly). | | It seems a shame to have to go XA just to get timer functionality. I mean, everything is on the same box, in the same database. Shouldn't it work with a local-tx-datasource as long as the same ds is used throughout? Should work fine if the timer service and the app both use the same local-tx datasource. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4060986#4060986 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4060986 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Can not persist EJB3 Timer since Jboss 4.2.0cr2 + seam
I'm seeing the same problem here, with the 4.2.0GA release (though we are not using the Seam annotation to create it, we're invoking the TimerService directly). It seems a shame to have to go XA just to get timer functionality. I mean, everything is on the same box, in the same database. Shouldn't it work with a local-tx-datasource as long as the same ds is used throughout? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4059671#4059671 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059671 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Can not persist EJB3 Timer since Jboss 4.2.0cr2 + seam
i think, it could, but we use now two different ds one for JBoss and one for our application. In the future, we plan to switch the jboss ds to our production one. Do you think, the XA were the performance killer or a source of system instability? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4059752#4059752 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059752 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Can not persist EJB3 Timer since Jboss 4.2.0cr2 + seam
Ok, i've found it! Since the new jboss ts implementation supports only one local-tx-resource per distributed transaction, the timer can not be commited until a bean uses more then one local-tx resource. Timers are hosted by default within the non xa hsqldb. So if we use in our transaction also one another local-tx data source, the exception above occurs! I've switched from local-tx to xa data source and the timers work fine! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4042949#4042949 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042949 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Can not persist EJB3 Timer since Jboss 4.2.0cr2 + seam
Ok, i've found it! Since the new jboss ts implementation supports only one local-tx-resource per distributed transaction, the timer can not be commited until a bean uses more then one local-tx resource. Timers are hosted by default within the non xa hsqldb. So if we use in our transaction also one another local-tx data source, the exception above occurs! I've switched from local-tx to xa data source and the timers work fine! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4042678#4042678 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042678 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Can not persist EJB3 Timer since Jboss 4.2.0cr2 + seam
Are you using EJB3 timers? If so, then the EJB3 implantation version will have been changed from 4.0.5 to 4.2.0.CR2. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039743#4039743 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039743 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Can not persist EJB3 Timer since Jboss 4.2.0cr2 + seam
Hello, i'm using the seam-wrapper for EJB3 timers via @Asynchronous. In a
simple case it works fine:
Timer iface:
@Local
| public interface TimerTester {
| @Asynchronous
| public abstract Timer say(String what, @Expiration
| Date expireTime, @IntervalDuration
| Long intervallDuration, @Duration Long duration);
| }
Timer Bean:
@Name(timerTester)
| @AutoCreate
| @Stateless
| public class TimerTesterImpl implements TimerTester{
| @In
| Timer timer;
| @Resource
| TimerService timerService;
| public Timer say(String what, Date expireTime, Long intervallDuration,
Long duration) {
| System.out.println(what);
| return timer;
| }
| }
controller (stateless bean with local iface):
public void sayHello() {
| Timer timer =timerTester.say(hello, new
Date(System.currentTimeMillis()+1000), 1l,10l);
| log.info(timer, null);
| }
Page
| h:commandLink value=Say Hello! action=#{sampleController.sayHello}/
My case, which doesn't work anymore:
SFSB:
| ...
| @In(create = true)
| OfferLifecycle offerLifecycle;
| ...
| if (persistOffer()) {
| if (schedule) {
|
| timer =
offerLifecycle.scheduleOfferStart(inOffer.getId(), inOffer.getStartTimestamp());
|
| debug(offer start pending with timer );
|
| timer =
offerLifecycle.scheduleOfferEnd(inOffer.getId(), inOffer.getEndTimestamp());
|
| debug(offer end pending with timer);
| }
Timer bean:
@Local
| public interface OfferLifecycle {
| @Asynchronous
| public abstract Timer scheduleOfferStart(Long offerId, @Expiration
| Date startTime);
| @Asynchronous
| public abstract Timer scheduleOfferEnd(Long offerId, @Expiration
| Date expireTime);
| }
@Stateless
| @Name(offerLifecycle)
| public class OfferLifecycleBean implements OfferLifecycle {
|
| @In(create = true)
| OfferDAO offerDAO;
| @In
| Timer timer;
| @Resource
| TimerService timerService;
|
| public Timer scheduleOfferStart(Long offerId, Date startTime) {
| offerStart(loadOffer(offerId));
| return timer;
| }
| public Timer scheduleOfferEnd(Long offerId, Date expireTime) {
|
| offerEnd(loadOffer(offerId));
| return timer;
| }
| private Offer loadOffer(Long offerId) {
| return offerDAO.findById( offerId,
|
LockMode.UPGRADE);
| }
persistOffer() has flushed the session (because of flush mode manual)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4039778#4039778
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039778
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
