[JBoss JIRA] (ISPN-4072) JPA Cache Store fails to clear entity which conatins ElementCollection
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-4072?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-4072:
--------------------------------
Labels: 630 (was: )
> JPA Cache Store fails to clear entity which conatins ElementCollection
> ----------------------------------------------------------------------
>
> Key: ISPN-4072
> URL: https://issues.jboss.org/browse/ISPN-4072
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
> Labels: 630
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> When entity stored by JPA Cache Store contains [ElementCollection|http://docs.oracle.com/javaee/6/api/javax/persistence/E...], {{clear()}} operation fails with foreign key constraint violation.
> Stack trace in case of MySQL:
> {noformat}
> org.infinispan.persistence.jpa.JpaStoreException: Exception caught in clear()
> at org.infinispan.persistence.jpa.JpaStore.clear(JpaStore.java:143)
> at org.infinispan.persistence.jpa.BaseJpaStoreTest.setUp(BaseJpaStoreTest.java:85)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not execute statement
> at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1387)
> at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1310)
> at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:1397)
> at org.hibernate.ejb.AbstractQueryImpl.executeUpdate(AbstractQueryImpl.java:108)
> at org.infinispan.persistence.jpa.JpaStore.clear(JpaStore.java:128)
> ... 23 more
> Caused by: org.hibernate.exception.ConstraintViolationException: could not execute statement
> at org.hibernate.exception.internal.SQLExceptionTypeDelegate.convert(SQLExceptionTypeDelegate.java:74)
> at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:49)
> at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:125)
> at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:110)
> at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:136)
> at org.hibernate.hql.internal.ast.exec.BasicExecutor.execute(BasicExecutor.java:103)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.executeUpdate(QueryTranslatorImpl.java:413)
> at org.hibernate.engine.query.spi.HQLQueryPlan.performExecuteUpdate(HQLQueryPlan.java:282)
> at org.hibernate.internal.SessionImpl.executeUpdate(SessionImpl.java:1290)
> at org.hibernate.internal.QueryImpl.executeUpdate(QueryImpl.java:116)
> at org.hibernate.ejb.QueryImpl.internalExecuteUpdate(QueryImpl.java:194)
> at org.hibernate.ejb.AbstractQueryImpl.executeUpdate(AbstractQueryImpl.java:99)
> ... 24 more
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`ispn_jpa_test`.`Person_nickNames`, CONSTRAINT `FK_ne1r4l90nve6426b7c7ws198i` FOREIGN KEY (`Person_id`) REFERENCES `Person` (`id`))
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> at com.mysql.jdbc.Util.getInstance(Util.java:386)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1039)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4098)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4030)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2677)
> at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2134)
> at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2434)
> at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2352)
> at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2337)
> at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:133)
> ... 31 more
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (ISPN-4076) RHQ server plugin: bytesRead and bytesWritten stats are broken
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-4076?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-4076:
--------------------------------
Labels: 630 (was: )
> RHQ server plugin: bytesRead and bytesWritten stats are broken
> --------------------------------------------------------------
>
> Key: ISPN-4076
> URL: https://issues.jboss.org/browse/ISPN-4076
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 7.0.0.Alpha1
> Reporter: Tomas Sykora
> Assignee: Tomas Sykora
> Labels: 630
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> resource path: subsystem=endpoint
> and underlined connectors provides statistics: bytesRead, bytesWritten.
> However plugin asks for bytes-read and bytes-written which is wrong. Small change in map in MetricsRemappingComponent is needed.
> + We will remove monitoring of those statistics for REST endpoint, as this endpoint does not provide those statistics at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (ISPN-4085) Random failures in StateProviderTest due to race condition
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-4085?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-4085:
--------------------------------
Labels: 630 (was: )
> Random failures in StateProviderTest due to race condition
> ----------------------------------------------------------
>
> Key: ISPN-4085
> URL: https://issues.jboss.org/browse/ISPN-4085
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 7.0.0.Alpha1
> Environment: jgroups.bind_addr = 127.0.0.1
> java.runtime.version = 1.7.0_51-b13
> java.runtime.name =Java(TM) SE Runtime Environment
> java.vm.version = 24.51-b03
> java.vm.vendor = Oracle Corporation
> os.name = Mac OS X
> os.version = 10.9.2
> sun.arch.data.model = 64
> sun.cpu.endian = little
> protocol.stack = null
> infinispan.test.jgroups.protocol = tcp
> infinispan.unsafe.allow_jdk8_chm = true
> java.net.preferIPv4Stack = true
> java.net.preferIPv6Stack = null
> log4.configuration = null
> MAVEN_OPTS = null
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Labels: 630
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> In my environment the StateProviderTest .test2() fails sometimes (about 10% of the time) with the following error(s):
> {code}
> Tests run: 4233, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 428.06 sec <<< FAILURE!
> test2(org.infinispan.statetransfer.StateProviderTest) Time elapsed: 0.042 sec <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:92)
> at org.junit.Assert.assertTrue(Assert.java:43)
> at org.junit.Assert.assertTrue(Assert.java:54)
> at org.infinispan.statetransfer.StateProviderTest.test2(StateProviderTest.java:316)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> {code}
> The reason why is that test2() feeds the StateProvider a ThreadPoolExecutorService to execute a OutboundTransfer task asynchronously and right after forcing a state transfer
> asserts that there is a StateTransfer in progress. Sometimes the executor service manages to execute the task and as a result it clear the ‘transfersByDestination’ map, and thus the test cannot assert that the state transfer is happening
> OTOH, the method test1() never fails because it users a mock executor service which never executes the task, so the state transfer map will always contain the outbound task after initiating the state transfer and thus always visible from outside
> The quick fix is to also use a mock executor test for the test2()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (ISPN-4053) WriteSkew not throwing an exception for AtomicMap in REPL and DIST mode
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-4053?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-4053:
--------------------------------
Labels: 621 630 (was: 621)
> WriteSkew not throwing an exception for AtomicMap in REPL and DIST mode
> -----------------------------------------------------------------------
>
> Key: ISPN-4053
> URL: https://issues.jboss.org/browse/ISPN-4053
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.1.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Labels: 621, 630
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> The writeSkewCheck flag does not work correctly for AtomicMap. When Infinispan runs in REPEATABLE_READ isolation mode for transactions, the writeSkewCheck flag is enabled, and two concurrent transactions read/write data from the same AtomicMap. The WriteSkewException exception is never thrown when committing either of the transactions.
> Consequently, the data stored in the AtomicMap might be changed by another transaction, and current transaction will not register this change during commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3942?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3942:
--------------------------------
Labels: 630 clustered hotrod hotrod-java-client (was: clustered hotrod hotrod-java-client)
> HotRod client keep trying recover a connection to a cluster member after shutdown
> ---------------------------------------------------------------------------------
>
> Key: ISPN-3942
> URL: https://issues.jboss.org/browse/ISPN-3942
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Environment: Infinispan server with HotRod client in server-client mode and replicated caches.
> Reporter: Wolf-Dieter Fink
> Assignee: Pedro Ruivo
> Priority: Critical
> Labels: 630, clustered, hotrod, hotrod-java-client
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
> Attachments: hotrod-client.log
>
>
> If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed.
> There is only a replicated cache configured.
> From the server-logfile the new cluster view is established
> 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered]
> There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server.
> This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months
[JBoss JIRA] (ISPN-3338) DistributionManager operations Locate key & Is key local are not working properly
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3338?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3338:
--------------------------------
Assignee: Martin Gencur (was: Mircea Markus)
> DistributionManager operations Locate key & Is key local are not working properly
> ---------------------------------------------------------------------------------
>
> Key: ISPN-3338
> URL: https://issues.jboss.org/browse/ISPN-3338
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Environment: Tested localy Fedora16
> Reporter: Tomas Sykora
> Assignee: Martin Gencur
> Labels: 630
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> Testing infinispan-rhq-plugin (for InVM).
> DistributionManager operations Locate key & Is key local seem not to working properly. For a nonsense key Locate key operation is returning success with result of a label for cache "home node".
> Is key local operation for nonsense key is returning TRUE which is obviously wrong. This happens even on totally clear, entry-free, cache.
> Operation Could key be affected by a rehash is returning operation success with result false. This is questionable whether it should return failure or not. Again, for nonsense key.
> Please can anyone look at it?
> I don't think this is directly jon/plugin related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months