[JBoss JIRA] (DROOLS-1093) Database Outage causes Session Persistence to break
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-1093?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-1093:
--------------------------------
Sprint: 2019 Week 50-52 (from Dec 9)
> Database Outage causes Session Persistence to break
> ----------------------------------------------------
>
> Key: DROOLS-1093
> URL: https://issues.redhat.com/browse/DROOLS-1093
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Environment: Mac OS 10.10.5, Eclipse Mars Release, Java 1.8, Drools 6.3.0.Final
> Docs QE Status: NEW
> Reporter: Artur Kronenberg
> Assignee: Mario Fusco
> Priority: Major
> Attachments: test-standalone.zip, test-standalone.zip
>
>
> Hi,
> I have ran into this a number of times and I am still working on the reproducer. I decided to raise this issue in case someone has seen something similar and/or I am on the wrong track and I'd rather know now before spending even more days on chasing this down.
> We had a DB outage 2 nights ago, and I have a timer task inserting 1 object into my rules every minute. The first time this happened with the DB outage, the result was:
> {code:java}
> java.lang.RuntimeException: Unable to commit transaction
> at org.drools.persistence.jta.JtaTransactionManager.commit(JtaTransactionManager.java:239) ~[drools-persistence-jpa-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.persistence.SingleSessionCommandService$TransactionInterceptor.execute(SingleSessionCommandService.java:587) ~[drools-persistence-jpa-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.persistence.SingleSessionCommandService.execute(SingleSessionCommandService.java:377) ~[drools-persistence-jpa-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.core.command.impl.CommandBasedStatefulKnowledgeSession.insert(CommandBasedStatefulKnowledgeSession.java:410) ~[drools-core-6.3.0.Final.jar:6.3.0.Final]
> at io.shureview.drools.model.impl.SessionHolder.insert(SessionHolder.java:62) ~[shureview-drools-engine-1.0.jar:na]
> at io.shureview.drools.tasks.ExpiryTimerTask.lambda$run$18(ExpiryTimerTask.java:60) ~[shureview-drools-engine-1.0.jar:na]
> at java.util.concurrent.ConcurrentHashMap$ValuesView.forEach(ConcurrentHashMap.java:4707) ~[na:1.8.0_72]
> at io.shureview.drools.tasks.ExpiryTimerTask.run(ExpiryTimerTask.java:55) ~[shureview-drools-engine-1.0.jar:na]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_72]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_72]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_72]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_72]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_72]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_72]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_72]
> Caused by: bitronix.tm.internal.BitronixRollbackException: RuntimeException thrown during beforeCompletion cycle caused transaction rollback
> at bitronix.tm.BitronixTransaction.commit(BitronixTransaction.java:241) ~[btm-2.1.4.jar:2.1.4]
> at bitronix.tm.BitronixTransactionManager.commit(BitronixTransactionManager.java:143) ~[btm-2.1.4.jar:2.1.4]
> at org.drools.persistence.jta.JtaTransactionManager.commit(JtaTransactionManager.java:236) ~[drools-persistence-jpa-6.3.0.Final.jar:6.3.0.Final]
> ... 14 common frames omitted
> Caused by: javax.persistence.PersistenceException: org.hibernate.exception.JDBCConnectionException: could not execute statement
> at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1387) ~[hibernate-entitymanager-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1310) ~[hibernate-entitymanager-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1316) ~[hibernate-entitymanager-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.ejb.AbstractEntityManagerImpl$CallbackExceptionMapperImpl.mapManagedFlushFailure(AbstractEntityManagerImpl.java:1510) ~[hibernate-entitymanager-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorNonTrackingImpl.beforeCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:114) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization.beforeCompletion(RegisteredSynchronization.java:53) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at bitronix.tm.BitronixTransaction.fireBeforeCompletionEvent(BitronixTransaction.java:532) ~[btm-2.1.4.jar:2.1.4]
> at bitronix.tm.BitronixTransaction.commit(BitronixTransaction.java:235) ~[btm-2.1.4.jar:2.1.4]
> ... 16 common frames omitted
> Caused by: org.hibernate.exception.JDBCConnectionException: could not execute statement
> at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:132) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:49) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:124) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:109) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:189) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:3240) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:3138) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:3468) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.action.internal.EntityUpdateAction.execute(EntityUpdateAction.java:140) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.engine.spi.ActionQueue.execute(ActionQueue.java:395) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:387) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:304) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:349) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:56) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1195) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:404) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> at org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorNonTrackingImpl.beforeCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:109) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> ... 19 common frames omitted
> Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1884) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1868) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1855) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:4215) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:4116) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3122) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:7127) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:444) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:383) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:6703) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1929) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:184) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:159) ~[sqljdbc4-4.2.jar:na]
> at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:326) ~[sqljdbc4-4.2.jar:na]
> at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:186) ~[hibernate-core-4.2.21.Final.jar:4.2.21.Final]
> ... 31 common frames omitted
> {code}
> This is then followed by:
> {code:java}
> java.lang.RuntimeException: Unable to load session snapshot
> at org.drools.persistence.SessionMarshallingHelper.loadSnapshot(SessionMarshallingHelper.java:103) ~[drools-persistence-jpa-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.persistence.SingleSessionCommandService.initExistingKnowledgeSession(SingleSessionCommandService.java:242) ~[drools-persistence-jpa-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.persistence.SingleSessionCommandService$TransactionInterceptor.execute(SingleSessionCommandService.java:557) ~[drools-persistence-jpa-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.persistence.SingleSessionCommandService.execute(SingleSessionCommandService.java:377) ~[drools-persistence-jpa-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.core.command.impl.CommandBasedStatefulKnowledgeSession.insert(CommandBasedStatefulKnowledgeSession.java:410) ~[drools-core-6.3.0.Final.jar:6.3.0.Final]
> at io.shureview.drools.model.impl.SessionHolder.insert(SessionHolder.java:62) ~[shureview-drools-engine-1.0.jar:na]
> at io.shureview.drools.tasks.ExpiryTimerTask.lambda$run$18(ExpiryTimerTask.java:60) ~[shureview-drools-engine-1.0.jar:na]
> at java.util.concurrent.ConcurrentHashMap$ValuesView.forEach(ConcurrentHashMap.java:4707) ~[na:1.8.0_72]
> at io.shureview.drools.tasks.ExpiryTimerTask.run(ExpiryTimerTask.java:55) ~[shureview-drools-engine-1.0.jar:na]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_72]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_72]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_72]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_72]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_72]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_72]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_72]
> Caused by: java.lang.NullPointerException: null
> at org.drools.core.marshalling.impl.ProtobufInputMarshaller.readTruthMaintenanceSystem(ProtobufInputMarshaller.java:586) ~[drools-core-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.core.marshalling.impl.ProtobufInputMarshaller.readSession(ProtobufInputMarshaller.java:247) ~[drools-core-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.core.marshalling.impl.ProtobufInputMarshaller.readSession(ProtobufInputMarshaller.java:118) ~[drools-core-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.core.marshalling.impl.ProtobufMarshaller.unmarshall(ProtobufMarshaller.java:131) ~[drools-core-6.3.0.Final.jar:6.3.0.Final]
> at org.drools.persistence.SessionMarshallingHelper.loadSnapshot(SessionMarshallingHelper.java:95) ~[drools-persistence-jpa-6.3.0.Final.jar:6.3.0.Final]
> ... 15 common frames omitted
> {code}
> My rules update and retract facts each time the rules are run.
> I wonder if somehow an object is removed from the working memory, then the persistence fails to update the table, the rollback does not rollback the working memory, and the persistence is broken.
> I have NOT found a solution for this so far. I was wondering though, is there a way for me to run a replace-all flush operation to simply serialise the working state of my session and throw away all other data. This could be a temporary workaround.
> Thanks and let me know if there is something else you need. I will try and add a reproducer as soon as I can.
> P.S.: Not sure if this may be Bitronix at fault here. I am running without a container, so I provided this standalone implementation for JTA.
> Thanks,
> Artur
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-299) Support rule configuration in a web archive
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-299?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-299.
--------------------------------
Resolution: Out of Date
> Support rule configuration in a web archive
> -------------------------------------------
>
> Key: DROOLS-299
> URL: https://issues.redhat.com/browse/DROOLS-299
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 6.0.0.CR4
> Reporter: Shane Bryzak
> Assignee: Mario Fusco
> Priority: Major
>
> I'm currently working on integration between PicketLink and Drools to provide rule-based security permissions which control access to protected application resources, similar to a feature that we had in Seam 2:
> https://github.com/seam2/jboss-seam/blob/Seam_2_3/jboss-seam/src/main/jav...
> The following quickstart (work in progress) is intended to demonstrate this integration:
> https://github.com/picketlink/picketlink-quickstarts/tree/master/picketli...
> Building this quickstart first requires building the latest trunk of PicketLink locally:
> https://github.com/picketlink/picketlink
> What we would like is to allow the developer to define their security rules in the war project itself. Currently the quickstart defines the following kmodule.xml file in the src/main/resources/META-INF directory:
> <?xml version="1.0" encoding="UTF-8"?>
> <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
> <kbase name="security" default="true">
> <ksession name="ksession1" default="true"/>
> </kbase>
> </kmodule>
> There is also a security-rules.drl file in the src/main/resources/security directory which defines the security rules.
> Deployment of the quickstart yields the following errors and partial stacktrace:
> 18:52:56,036 INFO [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-7) Found kmodule: vfs:/content/picketlink-authorization-drools.war/WEB-INF/classes/META-INF/kmodule.xml
> 18:52:56,036 INFO [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-7) Virtual file physical path = /home/shane/apps/jboss/standalone/tmp/vfs/tempa9983c4071e1249/picketlink-authorization-drools.war-1c243fd87ed695cf/WEB-INF/classes
> 18:52:56,060 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-7) Unable to load pom.properties tried recursing down from/home/shane/apps/jboss/standalone/tmp/vfs/tempa9983c4071e1249/picketlink-authorization-drools.war-1c243fd87ed695cf/WEB-INF/classes
> null
> 18:52:56,061 ERROR [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-7) Unable to build index of kmodule.xml url=vfs:/content/picketlink-authorization-drools.war/WEB-INF/classes/META-INF/kmodule.xml
> null
> 18:52:56,140 ERROR [org.drools.compiler.cdi.KieCDIExtension] (MSC service thread 1-7) Annotation @KSession(ksession1) found, but no KieSessioneModel exist.
> Either the required kproject.xml does not exist, was corrupted, or mising the KieBase entry
> 18:52:56,160 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."picketlink-authorization-drools.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."picketlink-authorization-drools.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [KieSession] with qualifiers [@KSession] at injection point [[field] @Inject @KSession org.jboss.as.quickstarts.picketlink.authorization.drools.PermissionAuthorizer.kSession]
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
> Mario indicated (during a discussion on IRC) that the rules are currently expected to be deployed within a separate jar file (which is then packaged as a library in the war), however our users are likely to view this as an extraneous requirement. It would be far more convenient to allow them to create their rule definitions within the war project itself, and also be easier to promote this integration via tutorials and quickstarts.
> Thanks for looking into this!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12887) Clustering: com.ibm.db2.jcc.am.SqlSyntaxErrorException when DB2 is used as invalidation-cache
by Tommasso Borgato (Jira)
Tommasso Borgato created WFLY-12887:
---------------------------------------
Summary: Clustering: com.ibm.db2.jcc.am.SqlSyntaxErrorException when DB2 is used as invalidation-cache
Key: WFLY-12887
URL: https://issues.redhat.com/browse/WFLY-12887
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 19.0.0.Beta1
Reporter: Tommasso Borgato
Assignee: Paul Ferraro
The error happens in clustering tests where the cache is backed by a DB2 relational database;
The cache is configured as follows:
{noformat}
embed-server --server-config=standalone-ha.xml
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload:add()
/subsystem=infinispan/cache-container=web/invalidation-cache==offload/component=transaction:write-attribute(name=mode, value=BATCH)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
data-source add --name=testDS --jndi-name=java:jboss/datasources/testDS --driver-name=db2-connector.jar --connection-url=jdbc:db2://db2-111.hosts.mwqe.eng.bos.redhat.com:50000/dballo --enabled=true --jta=true --use-java-context=true --transaction-isolation=TRANSACTION_READ_COMMITTED --min-pool-size=1 --max-pool-size=5 --pool-prefill=true --user-name=dballo00 --password=dballo00 --prepared-statements-cache-size=32 --share-prepared-statements=true
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc:add(data-source=testDS,fetch-state=false,passivation=false,purge=false,shared=true,dialect=DB2){allow-resource-service-restart=true}
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=prefix,value=s)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.name,value=id)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.type,value=VARCHAR(255))
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.name,value=datum)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.type,value=BLOB)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.name,value=version)
/subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.type,value=BIGINT)
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=offload)
/subsystem=transactions:write-attribute(name=node-identifier,value=wildfly1)
/subsystem=datasources/data-source=testDS:write-attribute(name=spy,value=true)
/subsystem=logging/logger=jboss.jdbc.spy:add(level=TRACE)
{noformat}
The error is the following:
{noformat}
2019-12-16 16:49:31,961 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [DataSource] getConnection()
2019-12-16 16:49:31,961 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [Connection] setAutoCommit(false)
2019-12-16 16:49:31,962 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [Connection] prepareStatement(SELECT datum, id FROM "s_cbnc_ear_a_war" WHERE version < ? AND version > 0 FOR UPDATE)
2019-12-16 16:49:31,971 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [PreparedStatement] setLong(1, 1576514971971)
2019-12-16 16:49:31,971 DEBUG [jboss.jdbc.spy] (expiration-thread--p24-t1) java:jboss/datasources/testDS [PreparedStatement] executeQuery()
2019-12-16 16:49:31,987 DEBUG [jboss.jdbc.spy] (persistence-thread--p25-t4) java:jboss/datasources/testDS [Connection] close()
2019-12-16 16:49:31,991 DEBUG [jboss.jdbc.spy] (persistence-thread--p25-t2) java:jboss/datasources/testDS [DataSource] getConnection()
2019-12-16 16:49:31,992 DEBUG [jboss.jdbc.spy] (persistence-thread--p25-t2) java:jboss/datasources/testDS [Connection] isValid(10)
2019-12-16 16:49:31,998 ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (expiration-thread--p24-t1) ISPN008001: Failed clearing cache store: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DBALLO00.s_cbnc_ear_a_war, DRIVER=4.25.1301
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.b6.a(b6.java:810)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.b6.a(b6.java:66)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.b6.a(b6.java:140)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k3.c(k3.java:2824)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k3.d(k3.java:2808)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k3.a(k3.java:2234)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.a(k4.java:8242)
at deployment.db2-connector.jar//com.ibm.db2.jcc.t4.ab.i(ab.java:206)
at deployment.db2-connector.jar//com.ibm.db2.jcc.t4.ab.b(ab.java:96)
at deployment.db2-connector.jar//com.ibm.db2.jcc.t4.p.a(p.java:32)
at deployment.db2-connector.jar//com.ibm.db2.jcc.t4.av.i(av.java:150)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k3.al(k3.java:2203)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.bq(k4.java:3730)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.a(k4.java:4609)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.b(k4.java:4182)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.bd(k4.java:780)
at deployment.db2-connector.jar//com.ibm.db2.jcc.am.k4.executeQuery(k4.java:745)
at org.jboss.ironjacamar.jdbcadapters@1.4.19.Final//org.jboss.jca.adapters.jdbc.CachedPreparedStatement.executeQuery(CachedPreparedStatement.java:113)
at org.jboss.ironjacamar.jdbcadapters@1.4.19.Final//org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:504)
at org.infinispan.persistence.jdbc@9.4.16.Final//org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.purge(JdbcStringBasedStore.java:456)
at org.infinispan@9.4.16.Final//org.infinispan.persistence.manager.PersistenceManagerImpl.lambda$purgeExpired$6(PersistenceManagerImpl.java:470)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1540)
at org.infinispan@9.4.16.Final//org.infinispan.persistence.manager.PersistenceManagerImpl.purgeExpired(PersistenceManagerImpl.java:473)
at org.infinispan@9.4.16.Final//org.infinispan.expiration.impl.ExpirationManagerImpl.processExpiration(ExpirationManagerImpl.java:111)
at org.infinispan@9.4.16.Final//org.infinispan.expiration.impl.ExpirationManagerImpl$ScheduledTask.run(ExpirationManagerImpl.java:245)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at org.jboss.as.clustering.common@19.0.0.Beta1-SNAPSHOT//org.jboss.as.clustering.context.ContextReferenceExecutor.execute(ContextReferenceExecutor.java:49)
at org.jboss.as.clustering.common@19.0.0.Beta1-SNAPSHOT//org.jboss.as.clustering.context.ContextualExecutor$1.run(ContextualExecutor.java:70)
at java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
The issue is set as "Blocker" because DB2 is one of the supported databases and we don't have a workaround at present
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4775) Some .CLI commands that has been working since WF9 fails on WF18
by Peter Jonsson (Jira)
[ https://issues.redhat.com/browse/WFCORE-4775?page=com.atlassian.jira.plug... ]
Peter Jonsson commented on WFCORE-4775:
---------------------------------------
Did a 18.0.1 installation via Galleon just now... did not help.
WFLYSRV0025: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final)
Precondition is a 100% clean standalone-full.xml
Just run this .CLI
/subsystem=transactions:write-attribute(name=node-identifier,value=ismobile)
echo KaBoom
/subsystem=undertow:write-attribute(name=statistics-enabled,value=true)
The output
{
"outcome" => "success",
"response-headers" => {
"operation-requires-restart" => true,
"process-state" => "restart-required"
}
}
KaBoom
{
"outcome" => "failed",
"failure-description" => "java.lang.StackOverflowError:null"
}
The server.log
at org.jboss.as.controller.CapabilityRegistry.getCapabilityStatus(CapabilityRegistry.java:392)
at org.jboss.as.controller.CapabilityRegistry.getDependentCapabilityStatus(CapabilityRegistry.java:426)
at org.jboss.as.controller.CapabilityRegistry.getCapabilityStatus(CapabilityRegistry.java:392)
> Some .CLI commands that has been working since WF9 fails on WF18
> ----------------------------------------------------------------
>
> Key: WFCORE-4775
> URL: https://issues.redhat.com/browse/WFCORE-4775
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 11.0.0.Beta4
> Reporter: Peter Jonsson
> Assignee: Yeray Borges
> Priority: Major
>
> Error message is
> ERROR [org.jboss.as.cli.CommandContext] (CLI command) {
> "outcome" => "failed",
> "failure-description" => "java.lang.StackOverflowError:null"
> }
> And in the log
> 2019-10-21 19:14:44,377 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0403: Unexpected failure during execution of the following operation(s): [{
> "address" => [("subsystem" => "undertow")],
> "operation" => "write-attribute",
> "name" => "statistics-enabled",
> "value" => true,
> "operation-headers" => {
> "caller-type" => "user",
> "access-mechanism" => "NATIVE"
> }
> }]: java.lang.StackOverflowError
> at org.jboss.as.controller.CapabilityRegistry.getDependentCapabilityStatus(CapabilityRegistry.java:418)
> at org.jboss.as.controller.CapabilityRegistry.getCapabilityStatus(CapabilityRegistry.java:392)
> at org.jboss.as.controller.CapabilityRegistry.getDependentCapabilityStatus(CapabilityRegistry.java:426)
> at org.jboss.as.controller.CapabilityRegistry.getCapabilityStatus(CapabilityRegistry.java:392)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4874) Unsaved changes dialog appears even if it just have been saved
by Anna Dupliak (Jira)
Anna Dupliak created DROOLS-4874:
------------------------------------
Summary: Unsaved changes dialog appears even if it just have been saved
Key: DROOLS-4874
URL: https://issues.redhat.com/browse/DROOLS-4874
Project: Drools
Issue Type: Bug
Components: Guided Rule Editor
Affects Versions: 7.32.0.Final
Reporter: Anna Dupliak
Assignee: Michael Anstis
Attachments: bpms_guvnor.zip, image-2019-12-16-15-44-57-488.png
When user closes the *Guided rules editor*
Right after pushing *save* button
The *Unsaved changes dialog * appears instead of closing window
!image-2019-12-16-15-44-57-488.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4870) Materialize consequences using Drools
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4870?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-4870:
--------------------------------------
Story Points: 9
> Materialize consequences using Drools
> -------------------------------------
>
> Key: DROOLS-4870
> URL: https://issues.redhat.com/browse/DROOLS-4870
> Project: Drools
> Issue Type: Bug
> Reporter: Luca Molteni
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Currently consequences using Drools are not materialized (extracted in a different lambda) because they are capturing, as they use the relative bitmask instance.
> We should find a way to pass the bitmask instance to the consequence so that we can materialize them.
> This means we should probably not change only the compiler, but also the interpreter of the DSL
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months