You say your schedule works, but nowhere are you specifically stating you are
interacting with an @Entity that would cause the XA transaction issue. The post
a few back specifically showed the actions occurring in the same transaction.
The following would not work without XA support.
anonymous w
This way here it worked:
|
| class Parameters{
| void getInterval();
|
| }
|
|
| class Scheduler{
|
| @IgnoreDependency
| @EJB
| Executor executor;
|
|
| void schedule(){
| executor.schedule();
| }
|
|
| }
|
|
| class Executor{
|
|
in my case, i want keep the Timer at the Hypersonic because:
1. The production database is very busy, and sometimes the database is off (I
mean, its avaliable "only" 98% of the time, but I cant trust on 98%, and the
hypersonic is 99,99% avaliable, because it is used only for the timers, in
fact
Did you check:
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources
?
Also, take a look at docs/examples/jca in your distribution.
I don't know if Hypersonic supports XA or has an XA-aware Driver. I've used XA
with MySQL 5.x before, but MyISAM doesn't support commit/rollback, so that
d
Ooopss... Then we are in trouble...
Is it possible to configure MySQL and Hypersonic with a XA data sources. What
we want to do is to use the default data source as the timer data source and
then use JPA with an underlying MySQL (with MyISAM tables) and get this to
work. A config example would
"oskar.carlstedt" wrote : Do I still have to use the JBoss specific annotation
@IgnoreDependency or is it possible to do this in a pure standard java ee way?
Because handling of cyclic dependencies is not defined by EJB3 Core
Specification, it's up to implementation to provide its own mechanism
I'm using JBoss 4.2.2.GA. Do I still have to use the JBoss specific annotation
@IgnoreDependency or is it possible to do this in a pure standard java ee way?
Kind regards
/Oskar
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139503#4139503
Reply to the pos
"rruppel" wrote : oscar, I thought using this solution, but I know that
circular reference is a problem with jboss (at least ive never found a solution)
Use @IgnoreDependency on one of the @EJB instances to avoid the dependency
cycle.
S,
ALR
View the original post :
http://www.jboss.com/index
First of all, thanks very much for starting helping me...
let me say what I am trying to do:
get an interval from database and use this interval to schedule my timer
but, I make this twice in the code
1. when the appplication is deployed
2. at the end of each execution I schedule it again (
ops... i opened a second quote instead of closing it
someone can edit please
thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139496#4139496
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139496
_
Hmm... and now you're back where you started, aren't you?
This is a pretty annoying problem. Is there a working example of doing this
within an EJB? Is the following solution possible?
| @Stateless
| @Local
| public class A {
|
|@EJB
|B b;
|
|/**
|* this meth
You are calling the schedule() method using a raw Java method call. Design a
way to invoke the functionality through a @Local interface object.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139471#4139471
Reply to the post :
http://www.jboss.com/index.html
hi all,
i know this thread is old, but I have an doubt about this subject
I have the same problem, and both suggestions worked
1. editing the ejb-deployer to use the same datasource for the timer
2. editing the jbossjta-properties.xml to allow the two resources at same
transaction
ok, but I
"jcstaff" wrote : I believe you want to do what I described in my option B of
the Jun 07 post. Just update the configuration file that points JMS to
DefaultDS to use the data source your application is using. It will create the
schema it needs. This integrates the Timer and application DB action
Ooopps... It's all in jcstaff's post above.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079278#4079278
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079278
___
jboss-user
I believe you want to do what I described in my option B of the Jun 07 post.
Just update the configuration file that points JMS to DefaultDS to use the data
source your application is using. It will create the schema it needs. This
integrates the Timer and application DB actions into a single re
Hi everyone!
I had the same issue when moving to JBoss 4.2 and nlmarco's method solved it,
albeit I don't want to go into production like that.
Thing is, my production DB is MySQL 4.1.20, which does not support XA. Since
JBoss can support 1 non-XA resource, I was wondering if the other resource
Hello wolfc,
thanks a lot for your quick and very helpful reply!!! It works!
I know that it's bad to turn on this option, but I need it for a development
system (when we'll go productive, there will be solely xa-resources).
For other readers browsing this thread, here a short summary:
I edited
Note that turning this option one can lead to data corruption, because
effectively you disable the two-phase commit protocol!
It is document here: http://wiki.jboss.org/wiki/Wiki.jsp?page=Multiple1PC.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054427#4054
"wolfc" wrote : [...] It is possible to set a property in the transaction
service to allow multiple one phase resources, but that could lead to
transaction problems. [...]
Hello wolfc,
I upgraded from 4.0.4.GA to 4.2.0.GA and I now have the same problem. After
having read your response, I start
In my case, I wanted a small-scale solution for development. I found that I
could do either of the following to get around the issue and still use HSQL.
Both involved an edit of deploy/ejb-deployer.xml
| a) turn off EJBTimer persistence by uncommenting the NoopPersistencePolicy
and commenting
This is not a bug. You're trying to access multiple one phase resources in a
single transaction. This was allowed with the old transaction manager, but it's
not allowed in the new one. It is possible to set a property in the transaction
service to allow multiple one phase resources, but that cou
"adenzo" wrote : Hi,
| Any further info on this?
| I had similar trouble, and in the end got it working by making a seperate
call, i.e.:
| JSF ManagedBean -> A:doSomething();
| JSF ManagedBean -> B:makeTime();
|
| Then making timers worked, as long as I did not EJB work within B.
|
Hi,
Any further info on this?
I had similar trouble, and in the end got it working by making a seperate call,
i.e.:
JSF ManagedBean -> A:doSomething();
JSF ManagedBean -> B:makeTime();
Then making timers worked, as long as I did not EJB work within B.
This was on 4.2.0.CR2
Having other issues li
Oh, forgot the actual code... :)
| this.context.getTimerService().createTimer(this.maintainenceIntervalMillis,
| this.maintainenceIntervalMillis,
| null);
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopi
25 matches
Mail list logo
