[EJB3] - How to manage TimerService/scheduled task on mutiple application servers
by Guillermo Fernández
Guillermo Fernández [http://community.jboss.org/people/perfilgeminis] created the discussion
"How to manage TimerService/scheduled task on mutiple application servers"
To view the discussion, visit: http://community.jboss.org/message/578196#578196
--------------------------------------------------------------
Hi,
I have this scenario:
- multiple +JBoss Application Severs+ (5.1 at this moment) whitout clustering.
- an application within a ejb3 module (+EAR+)
- one database
- every server (so the application) are connected to this same database.
- and the application deployed on each server (same application and configuration for every server)
What I want to do is define, at server runtime, scheduled task to periodically run some heavy process.
But I want that the application be capable of start, modify the time task and/or cancel it.
I probe an evaluate to use +TimerService+ (EJB3) and I had success on one server.
I mean, I could control any timer i create, reference, cancel, get info of it, through its timer id (cause I use +Stateless+ bean, I managed it persisting/retrieving the id from a database, to know wich timer is wich).
But on the scenario I descript, this is not a solution. In part for things like every timer is "associated" (can be retrieved) by the bean who create it.
So I came to request your advice.
May be some of you came through this problem, or could give me a tip to resolve this scenario.
I know that the +JBoss AS+ persist the timer that we create into the default +HSQL DB+. Maybe one solution could be changing the database that use the timer service to the external database (common for every jboss), like it explained in the chapter " http://docs.jboss.org/jbossas/docs/Administration_And_Configuration_Guide... Change Other JBoss AS Services to Use External Database", but I'm very lost yet .. I think.
Thanks, Regards and apolgize for my english.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578196#578196]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 3 months
[JBoss Remoting] - Jboss5.1 - JMS and Linux Heartbeat - server return the real IP and not the VIP
by Kobi Ianko
Kobi Ianko [http://community.jboss.org/people/kobiianko] created the discussion
"Jboss5.1 - JMS and Linux Heartbeat - server return the real IP and not the VIP"
To view the discussion, visit: http://community.jboss.org/message/578352#578352
--------------------------------------------------------------
Hi,
I've got an HA system, using linux HA (heartbeat).
2 machines:
node1 = 10.90.90.33
node2 = 10.90.90.34
and the Virtual IP (VIP) is 10.90.90.35
because JBOSS5 uses hostname and not IP (like Jboss 4.0.5) I've add "-Djava.rmi.server.hostname=10.90.90.35 -Dremoting.bind_by_host=false" to the VM Params, for it to work with IPs
when I access the server from the client I use my VIP, but the server returns to the client the real ip for remoting.
using a sniffer I can see a packet from the server to the client:
+org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy...........xpw.......socket://10.90.90.33:4446/+
let me just point out the EJB call works fine, the problem is with JMS only+.+
+any of you know how to let Jboss 5.1 bind the+ +UnifiedInvokerProxy to my VIP?+
+is there any VM Params that I can add to my "run.sh ..." command ?+
+10x, Kobi
+
+
+
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578352#578352]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 3 months
[IronJacamar] - Re: The replacement of system properties in *-ds.xml is done only for elements of string value type
by Radim Hanus
Radim Hanus [http://community.jboss.org/people/rhanus] created the discussion
"Re: The replacement of system properties in *-ds.xml is done only for elements of string value type"
To view the discussion, visit: http://community.jboss.org/message/578350#578350
--------------------------------------------------------------
Hi Ales
Thanks for answer!
>> How exactly are you seeing the "but no success"?
I've rewritten properties-service.xml to properties-jboss-bean.xml to be able to define supply:
<bean name="SystemProperties" class="org.jboss.varia.property.SystemPropertiesService"> <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:type=Properties,name=MyAppSystemProperties",exposedInterface=org.jboss.varia.property.SystemPropertiesServiceMBean.class</annotation> <property name="properties" replace="false">
istep.db.maxPoolSize=150
istep.db.idleTimeout=60
</property>
<supply>SystemProperties</supply>
</bean>
and I placed demand into ear CL deployer:
<bean name="EARClassLoaderDeployer" class="org.jboss.deployment.EarClassLoaderDeployer">
<!-- A flag indicating if ear deployments should have their own scoped
class loader to isolate their classes from other deployments.
-->
<property name="isolated">false</property>
<demand>SystemProperties</demand>
</bean>
but JAXB started to unmarshal ds descriptor before "configured" of system properties
may be I'm completely wrong but as I had some time during christmas to dive into source codes I'm really curious about solution :-)
>> Placing your property service into deployers/ should work.
and it really works !!!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578350#578350]
Start a new discussion in IronJacamar at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 3 months