Hi Daniel,
what you do is deploy the MDB as HASingleton and the timer will only have one
server with this special MDB. But the timeout will happen for each node,
because the TIMER-table is the same for all.
What I need is a real cluster aware timer where a SLSB|MDB can create a timer
and it is
I know that the ejb2 timer with JBoss 3.x/4.x is not really cluster aware.
How the new ejb3-timer-service manage the timers in a clustered environment.
Are the timer-events syncronized via database that a single execution of a
timeout is ensured ?
Anybody who know this?
View the original post :
I try to use the EJB3 timer service with Oracle DS.
First of all I have to use a non XA connection, is the XA protocol not needed?
If I use a local-tx-datasource the table can not created because of an illegal
data type.
The Statement:
anonymous wrote : CREATE TABLE QRTZ_JOB_DETAILS(JOB_NAME VAR
IMHO not.
The only way to ensure that one process (JBoss) consume all resources is to use
a resource partitioning of the system.
In this case it's ensured that one system-partition can not consume more than
the configured resources (CPU/Memory etc.)
View the original post :
http://www.jboss.com
we do this, but without JMS..
just for CMP and EJB-Timers.
For CMP it is not a risk if you aren't use CMP-caching.
The timer tables must different (if you use timer), this can be configured in
version 4.2. Otherwise ejbtimer services are started twice.
JMS depends on what you using:
JBossMQ -> de
Thanks jaikiran,
this looks like the right configuration.
Here I found the deploy path list and the scanner.
Do you know how to deactivate scanning? scanPeriod=0 ???
And how to deactivate farming?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171962#4171962
Hi,
with JBoss4 the jboss-service.xml contains the scanner configuration, include
lib/deploy directory and the configuration of the period to scan for new files.
I found the 'lib' configuraration, but I miss the 'deploy' and the period
settings.
Where can I set this parameter?
View the original
Do you have used the 'all' configuration?
Is the Multicast and UDP Port/Address the same at all nodes?
Is the partition name always the same?
Are you sure that a multicast works?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015670#4015670
Reply to the post
Hello klejs,
the ejbTimer service is NOT clustered and supports no failover.
You have to configure the timer on each node with a different database!!!
Then the timer is started (configured) at one node and will be started at this
node (even if it is alive).
Also it is possible to caonfigure the
Ok found,
was a mistake of my JBoss installation.
Using installer and running default installation works.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002782#4002782
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002
playing around with EJB3 (first itme)
I create a SimpleBean:
| @Stateless
| public class SimpleBean {
| public void aMethod() {
| // log something ...
| }
| }
|
| @Remote
| public interface Simple {
| public void aMethod();
| }
|
If I deploy this, JBoss will
Hello,
in your case you prevent a lock if using the method getUuid.
Any other method include findBy... will set a lock if declared.
You can set the transaction of getter, finder to "Supports" and setter/create
to Mandatory/Required.
If you use a Session without a transaction reads to the bean wil
Hi Brian,
I meant that the answer from JBoss in your telnet is correct.
JBoss will give a Remotestub, but telnet dont work with it.
Your connection should work without the URL_PKG_PREFIXES this only restricts
the packages.
regards
Wolf
View the original post :
http://www.jboss.com/index.html?m
This looks OK.
Your JBoss is up and running and will give a RMI connection.
But telnet does not understand.
IMO that is not the problem ;-(
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967847#3967847
Reply to the post :
http://www.jboss.com/index.html?modu
in your EJB createTimerHandle() you should ask the timerService for existing
timers with getTimers().
If you only one (looks like, theres no info) you skip the creation if the
Collection is not empty.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967845#3967
Timers are an EJB 2.1 feature so the application has to manage.
MBeans are helpful to do something server/system specific for the EJB's.
A point to start for MBeans are JBoss admin guide
(http://docs.jboss.org/jbossas/jboss4guide/r5/html/) chapter '2.4.3. Writing
JBoss MBean Services'
View the
often we have two cases:
- do something for the depends on a timestamp from data
(e.g. warning of a meeting in calendar)
- start some checks for administrativ issues
(cleaning or statistics ...)
In the first case the entity manage the timer (it's easy)
In the second case an administrator
Yes,
you should use a Timer.
implement TimerObject in you StatelessSessionBean, EntityBean or MessageBean.
In your application set a Timer for this Bean.
After that the timout method of your bean is called when the timeout has come
The Timer is persistent (since 4.0.4 also if you shutdown t
18 matches
Mail list logo
