Migration issue on EJB timer from wildfly 26.1.3.Final to 34.0.1.Final

[Pramod Singh]

Hi 

I am new into wildfly and currently working on migration from wildfly 26.1.3.Final to widlfly 34.0.1.Final  and also migrating our existing EJB timer with 34.0.1.Final as suggested in wildlfy 27. but somehow this latest EJB timer not working and unable to add as susbsystem in wildfly. 

Existing Timer implementation in wildfly 26.1.3.Final as below:

/subsystem=ejb3/service=timer-service/database-data-store=abc-timer-data-store:add(datasource-jndi-name=java:/jdbc/abc_TIMER, database=postgresql, partition=vis, allow-execution=true)

/subsystem=ejb3/service=timer-service:write-attribute(name=default-data-store, value=abc-timer-data-store)

Note: java:/jdbc/abc_TIMER datasource is already defined.

Implemented New Ejb timer in wildfly 34.0.1.Final as per wildfly 27 suggestion as below .

/subsystem=infinispan/cache-container=ejb/distributed-cache=abc_timer:add()
/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/store=file:add(purge=false)

/subsystem=infinispan/cache-container=ejb/distributed-cache=persistent/store=jdbc:add(datasource-jndi-name=java:/jdbc/abc_TIMER, passivation=false, preload=true, purge=false)

/subsystem=distributable-ejb/infinispan-timer-management=persistent:add(cache-container=ejb, cache=persistent)

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

Could you please suggest , what is wrong here in the implementation.

Thanks In Advance.

[Pramod Singh]

Your suggestion would be appreciated. Please suggest me what i am missing here.

[Paul Ferraro]

What exactly do you mean by "not working and unable to add as susbsystem in wildfly"?

I suspect you mean that one or more of the commands below fails to execute?  If so, can you paste those exceptions?

[Pramod Singh]

Getting below error while deploying the war...

ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "abc-service.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.clustering.infinispan.cache.ejb.\"abc-service-.war.StatsDeleteSchedule.PERSISTENT\"" => "org.infinispan.commons.CacheConfigurationException: ISPN000659: Component ComponentWrapper{name=org.infinispan.persistence.manager.PersistenceManager, instance=org.infinispan.persistence.manager.PersistenceManagerImpl@e053bb2, status=FAILED} failed to start
    Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000659: Component ComponentWrapper{name=org.infinispan.persistence.manager.PersistenceManager, instance=org.infinispan.persistence.manager.PersistenceManagerImpl@e053bb2, status=FAILED} failed to start
    Caused by: java.util.concurrent.CompletionException: org.infinispan.persistence.spi.PersistenceException: ERROR: type \"binary\" does not exist
  Position: 97
    Caused by: org.infinispan.persistence.spi.PersistenceException: ERROR: type \"binary\" does not exist
  Position: 97
    Caused by: org.postgresql.util.PSQLException: ERROR: type \"binary\" does not exist

[Claudio Weiler]

"org.postgresql.util.PSQLException: ERROR: type \"binary\" does not exist"

This indicates an persistence mapping error. Are you connecting to a postgres server?

[Pramod Singh]

yes, using postgres server

[Pramod Singh]

while deploying the wildfly server with EJB timer,  its throwing above error while connecting postgres server.

[Bartosz Baranowski]

Either wrong user perms or dialect?

https://groups.google.com/g/wildfly/c/YNM5w0919iY

[Paul Ferraro]

> /subsystem=infinispan/cache-container=ejb/distributed-cache=persistent/store=jdbc:add(datasource-jndi-name=java:/jdbc/abc_TIMER, passivation=false, preload=true, purge=false)

datasource-jndi-name is not a valid parameter for this operation.

See: https://docs.wildfly.org/34/wildscribe/subsystem/infinispan/cache-container/distributed-cache/store/jdbc/index.html

Additionally, you need to specify dialect=POSTGRES

[Pramod Singh]

HI Paul, Still i am getting same error.   

/subsystem=infinispan/cache-container=ejb/distributed-cache=persistent/store=jdbc:add(data-source=ABC, dialect=POSTGRES, shared=true, passivation=false, preload=true, purge=false).

could you please check and update me .

Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000659: Component ComponentWrapper{name=org.infinispan.persistence.manager.PersistenceManager, instance=org.infinispan.persistence.manager.PersistenceManagerImpl@234c90d4, status=FAILED} failed to start

Caused by: java.util.concurrent.CompletionException: org.infinispan.persistence.spi.PersistenceException: ERROR: type \"binary\" does not exist

Position: 97

Caused by: org.infinispan.persistence.spi.PersistenceException: ERROR: type \"binary\" does not exist

Position: 97

Caused by: org.postgresql.util.PSQLException: ERROR: type \"binary\" does not exist

 Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000659: Component ComponentWrapper{name=org.infinispan.persistence.manager.PersistenceManager, instance=org.infinispan.persistence.manager.PersistenceManagerImpl@234c90d4, status=FAILED} failed to start

    Caused by: java.util.concurrent.CompletionException: org.infinispan.persistence.spi.PersistenceException: ERROR: type \"binary\" does not exist
  Position: 97
    Caused by: org.infinispan.persistence.spi.PersistenceException: ERROR: type \"binary\" does not exist
  Position: 97
    Caused by: org.postgresql.util.PSQLException: ERROR: type \"binary\" does not exist

----------------------------------------------------------------------------------------------------------------------------------------

[Pramod Singh]

Using wildlfy 36.0.1.Final and Using code as below

/subsystem=infinispan/cache-container=ejb/distributed-cache=dist/store=jdbc:add(data-source= ABC_TIMER  , dialect=POSTGRES, shared=true, passivation=false, purge=false)
/subsystem=infinispan/cache-container=ejb/distributed-cache=dist/store=jdbc/table=string:add(prefix="JBOSS_TIMER")
/subsystem=infinispan/cache-container=ejb/distributed-cache=dist/store=jdbc/table=string:write-attribute(name=data-column.type, value=BYTEA)

Getting error as below : 

Operation: /subsystem=infinispan/cache-container=ejb/distributed-cache=dist/store=jdbc/table=string:add(prefix="ABC_TIMER") 17:00:31.604 #16 17.05 Failure: WFLYCTL0216: Management resource '[ 17:00:31.604 #16 17.05 ("subsystem" => "infinispan"), 17:00:31.604 #16 17.05 ("cache-container" => "ejb"), 17:00:31.604 #16 17.05 ("distributed-cache" => "dist"), 17:00:31.604 #16 17.05 ("store" => "jdbc") 

17:00:31.604 #16 17.05 ]' not found 

[Pramod Singh]

Hi i

I identified the issue and fixed it. But its creating separate table for each timer. Is it expected behaviour or we can make some changes to address this

[Paul Ferraro]

There will be a separate table per EJB component.  That is expected.