Migration issue from EJB timer to infinispan-timer-management

[Pramod Singh]

Hi,

I am migrating EJB timer to infinispan-timer-management in wildfly36.0.1.Final and using below changes but in the same time multiple nodes are executing the timer service causing ejb timer failure. Please suggest how to restrict timer service to execute by single node at a time in multi node cluster.

/subsystem=ejb3/service=timer-service:undefine-attribute(name=default-persistent-timer-management)
/subsystem=ejb3/service=timer-service:undefine-attribute(name=default-transient-timer-management)
/subsystem=ejb3/service=timer-service:write-attribute(name=thread-pool-name, value=default)
/subsystem=ejb3/service=timer-service:undefine-attribute(name=default-data-store)

/subsystem=distributable-ejb/infinispan-timer-management=infini-timer:add(cache-container=ejb, cache=persistent)
/subsystem=ejb3/service=timer-service:write-attribute(name=default-persistent-timer-management, value=infini-timer)

[Joerg Baesner]

Hi,

Are you only using persistent timers? 

Best regards,

  Joerg

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wildfly/b9b0add4-69a4-442c-9f75-d871168f461cn%40googlegroups.com.

[Pramod Singh]

yes, Using only persistent time.

[Paul Ferraro]

When using infinispan-timer-management, the  behaviour of persistent and/or non-persistent timers will be determined by the referenced cache configuration from the Infinispan subsystem. Can you attach that?

To view this discussion visit https://groups.google.com/d/msgid/wildfly/d589779f-c2a8-4f48-ba25-db559e211288n%40googlegroups.com.

[Pramod Singh]

Hi Paul Ferraro,

Using the default cache configuration provided by the infinispan subsystem. 

ex: /subsystem=infinispan/cache-container=ejb/distributed-cache=persistent:add()

[Paul Ferraro]

Assuming you are using one of the stock configuration profiles, the default cache configuration provided by the infinispan subsystem will be different depending on which profile you are using.

Please attach.

[Pramod Singh]

sorry, i didnot get you. please explain what do you mean by profile? i don't have any other changes apart from above mentioned cli command.

Please let me know, if i missing something.

[Pramod Singh]

FYI , using full-ha profile

[Pramod Singh]

Paul Ferraro,

Could you please share any documentation to implement Infinispan timer management with Full-ha profile using JDBC store.

It would be very helful to implement the new timer management in wildlfy 36

[Paul Ferraro]

First, we need to figure out your issue with cluster formation.  Can you attach all INFO+ logs from org.jgroups and org.infinispan ?

Whether Infinispan is configured with a persistent store or not still requires that your cluster members are able to establish a consistent cluster view.

[Pramod Singh]

There is no changes in default configuration of Jgroups and Infinispan. Default cache EJB is using with below changes.

Using full-ha profile.

/subsystem=infinispan/cache-container=ejb/distributed-cache=persistent:write-attribute(name=owners, value=2)
#/subsystem=infinispan/cache-container=ejb/distributed-cache=persistent/component=persistence/file-store=*:remove
/subsystem=infinispan/cache-container=ejb/distributed-cache=persistent/component=locking:add(isolation=REPEATABLE_READ)
/subsystem=infinispan/cache-container=ejb/distributed-cache=persistent/component=transaction:add(mode=BATCH)
/subsystem=infinispan/cache-container=ejb/distributed-cache=persistent/component=persistence:add(passivation=false, attributes={string-keyed-jdbc-store={data-source="java:/jdbc/abc_ds", dialect=POSTGRES, table-name="jboss_ejb_infini_timer", shared=true, id-column={name="id", type="VARCHAR"}, data-column={name="payload", type="BLOB"}, timestamp-column={name="created", type="BIGINT"}}}) --force