[JBoss JIRA] (ISPN-5507) Transactions committed immediately before cache stop can block shutdown
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5507?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-5507:
--------------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.Alpha2)
> Transactions committed immediately before cache stop can block shutdown
> -----------------------------------------------------------------------
>
> Key: ISPN-5507
> URL: https://issues.jboss.org/browse/ISPN-5507
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 7.2.1.Final, 8.0.0.Alpha1
> Reporter: Dan Berindei
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 8.0.0.Beta1
>
>
> This is causing random failures in {{DistributedEntryRetrieverTxTest.verifyNodeLeavesBeforeGettingData}}.
> The test inserts some values into the cache, starts an iteration, and then kills one of the nodes. In rare instances, the killed cache only receives the TxCompletionCommand for one of the writes after it started the shutdown, and ignores it. That leaves the remote tx on-going, and {{TransactionTable.shutDownGracefully()}} blocks for 30 seconds - causing a {{TimeoutException}} elsewhere in the test.
> {noformat}
> 10:52:18,129 TRACE (remote-thread-NodeAM-p12133-t6:) [CommandAwareRpcDispatcher] About to send back response SuccessfulResponse{responseValue=null} for command CommitCommand {gtx=GlobalTransaction:<NodeAL-45757>:22325:remote, cacheName='org.infinispan.iteration.DistributedEntryRetrieverTxTest', topologyId=4}
> 10:52:18,129 TRACE (testng-DistributedEntryRetrieverTxTest:) [JGroupsTransport] dests=[NodeAM-45518, NodeAL-45757], command=TxCompletionNotificationCommand{ xid=null, internalId=0, topologyId=4, gtx=GlobalTransaction:<NodeAL-45757>:22325:local, cacheName=org.infinispan.iteration.DistributedEntryRetrieverTxTest} , mode=ASYNCHRONOUS, timeout=15000
> 10:52:18,133 DEBUG (testng-DistributedEntryRetrieverTxTest:) [CacheImpl] Stopping cache org.infinispan.iteration.DistributedEntryRetrieverTxTest on NodeAM-45518
> 10:52:18,133 TRACE (OOB-2,NodeAM-45518:) [GlobalInboundInvocationHandler] Attempting to execute CacheRpcCommand: TxCompletionNotificationCommand{ xid=null, internalId=0, topologyId=4, gtx=GlobalTransaction:<NodeAL-45757>:22325:local, cacheName=org.infinispan.iteration.DistributedEntryRetrieverTxTest} [sender=NodeAL-45757]
> 10:52:18,133 TRACE (OOB-2,NodeAM-45518:) [GlobalInboundInvocationHandler] Silently ignoring that org.infinispan.iteration.DistributedEntryRetrieverTxTest cache is not defined
> 10:52:18,133 DEBUG (testng-DistributedEntryRetrieverTxTest:) [TransactionTable] Wait for on-going transactions to finish for 30 seconds.
> 10:52:48,139 WARN (testng-DistributedEntryRetrieverTxTest:) [TransactionTable] ISPN000100: Stopping, but there are 0 local transactions and 1 remote transactions that did not finish in time.
> 10:52:48,386 ERROR (testng-DistributedEntryRetrieverTxTest:) [UnitTestTestNGListener] Test verifyNodeLeavesBeforeGettingData(org.infinispan.iteration.DistributedEntryRetrieverTxTest) failed.
> java.lang.IllegalStateException: Thread already timed out waiting for event pre_send_response_released
> at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:131)
> at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:116)
> at org.infinispan.iteration.DistributedEntryRetrieverTest.verifyNodeLeavesBeforeGettingData(DistributedEntryRetrieverTest.java:105)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5551) Infinispan AS modules artifact should include JBoss Marshalling
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5551?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-5551:
--------------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.Alpha2)
> Infinispan AS modules artifact should include JBoss Marshalling
> ---------------------------------------------------------------
>
> Key: ISPN-5551
> URL: https://issues.jboss.org/browse/ISPN-5551
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 7.2.2.Final
> Reporter: Horia Chiorean
> Assignee: Tristan Tarrant
> Fix For: 8.0.0.Beta1, 7.2.3.Final, 8.0.0.Final
>
>
> Infinispan 7 provides the following Maven artifact:
> {code:xml}
> <dependency>
> <groupId>org.infinispan</groupId>
> <artifactId>infinispan-as-embedded-modules</artifactId>
> <type>zip</type>
> </dependency>
> {code}
> which can be used (and is used by ModeShape) when running in a JBoss AS instance.
> However, this artifact does not contain the version of JBoss Marshalling that a particular version of Infinspan requires but rather picks up the {{main}} version which is available in the container:
> {code:xml}
> <module name="org.jboss.marshalling"/>
> <module name="org.jboss.marshalling.river" services="import"/>
> {code}
> Because of this, when deploying Infinispan 7.2.x in Wildfly 8.2.0, Infinispan will pick up the version of marshalling delivered by Wildfly (1.4.9.Final instead of 1.4.10.Final) causing class cast exceptions like:
> {code:java}
> Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to org.jboss.marshalling.Externalizer
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1012)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1256)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:276)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.objectFromObjectStream(AbstractJBossMarshaller.java:135) [infinispan-commons.jar:7.2.0.Final]
> at org.infinispan.marshall.core.VersionAwareMarshaller.objectFromByteBuffer(VersionAwareMarshaller.java:101) [infinispan-core.jar:7.2.0.Final]
> at org.infinispan.commons.marshall.AbstractDelegatingMarshaller.objectFromByteBuffer(AbstractDelegatingMarshaller.java:80) [infinispan-commons.jar:7.2.0.Final]
> at org.infinispan.marshall.core.MarshalledEntryImpl.unmarshall(MarshalledEntryImpl.java:114) [infinispan-core.jar:7.2.0.Final]
> ... 162 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5544) Deprecate eager near caching
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5544?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-5544:
--------------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.Alpha2)
> Deprecate eager near caching
> ----------------------------
>
> Key: ISPN-5544
> URL: https://issues.jboss.org/browse/ISPN-5544
> Project: Infinispan
> Issue Type: Task
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 8.0.0.Beta1, 8.0.0.Final
>
>
> In it's current form, eager near caching can lead the server to run out of direct memory, see ISPN-5523. The reason that's happening is because we're having to send events containing keys + values for each put() operation, indiscriminately to clients. So, regardless of what the client stores in the near cache, the client receives key+value information for all keys, as each key is created/modified, and this is having a big toll on the capabilities of the server to push those events to clients.
> So, we have decided to deprecate eager near caching in Infinispan 8.0, and we'll remove it completely for Infinispan 9.0.
> Lazy near caching still remains and works well because events are smaller since no value is sent to clients. Lazy near caching is still indiscriminate but we have plans to make it more selective, so that for example, only modified/removed events are sent for those keys that are stored in the client near cache, which would reduce traffic considerably (new jira to be created).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5555) Custom externalizer for Cache Store (jdbc)
by Veli Cris (JIRA)
[ https://issues.jboss.org/browse/ISPN-5555?page=com.atlassian.jira.plugin.... ]
Veli Cris updated ISPN-5555:
----------------------------
Description:
For a POJO object I created a class that implements Externalizer interface. I used @SerializeWith annotation for POJO class and I printed out debugging information in writeObject() method defined in Externalizer interface and I can see the log it's ok.
The problem is that in my database table (defined as Datasource), in data column I see some hexa code and not what I overrided in writeObject() method.
Thank you,
was:
For a POJO object I created a class that implements Externalizer interface. I used @SerializeWith annotation for POJO class and I printed out debugging information in writeObject() method defined in Externalizer interface and I can see the log it's ok.
The problem is that in my database table (defined as Datasource), in data column I see some hexa code and not what I overrided in writeObject() method.
Thank you,
Cris
> Custom externalizer for Cache Store (jdbc)
> ------------------------------------------
>
> Key: ISPN-5555
> URL: https://issues.jboss.org/browse/ISPN-5555
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.2.Final
> Environment: WildFly 8.2.0 / Linux
> Reporter: Veli Cris
>
> For a POJO object I created a class that implements Externalizer interface. I used @SerializeWith annotation for POJO class and I printed out debugging information in writeObject() method defined in Externalizer interface and I can see the log it's ok.
> The problem is that in my database table (defined as Datasource), in data column I see some hexa code and not what I overrided in writeObject() method.
> Thank you,
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5555) Custom externalizer for Cache Store (jdbc)
by Veli Cris (JIRA)
[ https://issues.jboss.org/browse/ISPN-5555?page=com.atlassian.jira.plugin.... ]
Veli Cris commented on ISPN-5555:
---------------------------------
Data column in database:
0301FE030200013E01310369036A060301FE3E0131036AD1070301FE043800000033636F6D2E617465736E6574776F726B732E707573682E70726F746F636F6C2E6265616E2E5075736853657373696F6E4265616E220A1CA061D1D07F00000028000000065F69734E6577200000000002696416000000000F69644973496E697469616C697A656420000000000C696449734D6F64696669656420000000000469646C6516000000001169646C654973496E697469616C697A656420000000000E69646C6549734D6F646966696564200000000008696E7465726E4964160000000015696E7465726E49644973496E697469616C697A6564200000000012696E7465726E496449734D6F64696669656420000000000870726F746F636F6C16000000001570726F746F636F6C4973496E697469616C697A656420000000001270726F746F636F6C49734D6F6469666965642000000000087075626C696349641600000000157075626C696349644973496E697469616C697A65642000000000127075626C6963496449734D6F64696669656420000000000D72656D6F74654164647265737316000000001A72656D6F7465416464726573734973496E697469616C697A656420000000001772656D6F7465416464726573734973
> Custom externalizer for Cache Store (jdbc)
> ------------------------------------------
>
> Key: ISPN-5555
> URL: https://issues.jboss.org/browse/ISPN-5555
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.2.Final
> Environment: WildFly 8.2.0 / Linux
> Reporter: Veli Cris
>
> Hi,
> For a POJO object I created a class that implements Externalizer interface. I used @SerializeWith annotation for POJO class and I printed out debugging information in writeObject() method defined in Externalizer interface and I can see the log it's ok.
> The problem is that in my database table (defined as Datasource), in data column I see some hexa code and not what I overrided in writeObject() method.
> Thank you,
> Cris
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5555) Custom externalizer for Cache Store (jdbc)
by Veli Cris (JIRA)
[ https://issues.jboss.org/browse/ISPN-5555?page=com.atlassian.jira.plugin.... ]
Veli Cris edited comment on ISPN-5555 at 6/16/15 12:46 PM:
-----------------------------------------------------------
Data column in database (BLOB):
0301FE030200013E01310369036A060301FE3E0131036AD1070301FE043800000033636F6D2E617465736E6574776F726B732E707573682E70726F746F636F6C2E6265616E2E5075736853657373696F6E4265616E220A1CA061D1D07F00000028000000065F69734E6577200000000002696416000000000F69644973496E697469616C697A656420000000000C696449734D6F64696669656420000000000469646C6516000000001169646C654973496E697469616C697A656420000000000E69646C6549734D6F646966696564200000000008696E7465726E4964160000000015696E7465726E49644973496E697469616C697A6564200000000012696E7465726E496449734D6F64696669656420000000000870726F746F636F6C16000000001570726F746F636F6C4973496E697469616C697A656420000000001270726F746F636F6C49734D6F6469666965642000000000087075626C696349641600000000157075626C696349644973496E697469616C697A65642000000000127075626C6963496449734D6F64696669656420000000000D72656D6F74654164647265737316000000001A72656D6F7465416464726573734973496E697469616C697A656420000000001772656D6F7465416464726573734973
was (Author: vlcvlc):
Data column in database:
0301FE030200013E01310369036A060301FE3E0131036AD1070301FE043800000033636F6D2E617465736E6574776F726B732E707573682E70726F746F636F6C2E6265616E2E5075736853657373696F6E4265616E220A1CA061D1D07F00000028000000065F69734E6577200000000002696416000000000F69644973496E697469616C697A656420000000000C696449734D6F64696669656420000000000469646C6516000000001169646C654973496E697469616C697A656420000000000E69646C6549734D6F646966696564200000000008696E7465726E4964160000000015696E7465726E49644973496E697469616C697A6564200000000012696E7465726E496449734D6F64696669656420000000000870726F746F636F6C16000000001570726F746F636F6C4973496E697469616C697A656420000000001270726F746F636F6C49734D6F6469666965642000000000087075626C696349641600000000157075626C696349644973496E697469616C697A65642000000000127075626C6963496449734D6F64696669656420000000000D72656D6F74654164647265737316000000001A72656D6F7465416464726573734973496E697469616C697A656420000000001772656D6F7465416464726573734973
> Custom externalizer for Cache Store (jdbc)
> ------------------------------------------
>
> Key: ISPN-5555
> URL: https://issues.jboss.org/browse/ISPN-5555
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.2.Final
> Environment: WildFly 8.2.0 / Linux
> Reporter: Veli Cris
>
> Hi,
> For a POJO object I created a class that implements Externalizer interface. I used @SerializeWith annotation for POJO class and I printed out debugging information in writeObject() method defined in Externalizer interface and I can see the log it's ok.
> The problem is that in my database table (defined as Datasource), in data column I see some hexa code and not what I overrided in writeObject() method.
> Thank you,
> Cris
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5555) Custom externalizer for Cache Store (jdbc)
by Veli Cris (JIRA)
[ https://issues.jboss.org/browse/ISPN-5555?page=com.atlassian.jira.plugin.... ]
Veli Cris updated ISPN-5555:
----------------------------
Description:
For a POJO object I created a class that implements Externalizer interface. I used @SerializeWith annotation for POJO class and I printed out debugging information in writeObject() method defined in Externalizer interface and I can see the log it's ok.
The problem is that in my database table (defined as Datasource), in data column I see some hexa code and not what I overrided in writeObject() method.
Thank you,
Cris
was:
Hi,
For a POJO object I created a class that implements Externalizer interface. I used @SerializeWith annotation for POJO class and I printed out debugging information in writeObject() method defined in Externalizer interface and I can see the log it's ok.
The problem is that in my database table (defined as Datasource), in data column I see some hexa code and not what I overrided in writeObject() method.
Thank you,
Cris
> Custom externalizer for Cache Store (jdbc)
> ------------------------------------------
>
> Key: ISPN-5555
> URL: https://issues.jboss.org/browse/ISPN-5555
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.2.Final
> Environment: WildFly 8.2.0 / Linux
> Reporter: Veli Cris
>
> For a POJO object I created a class that implements Externalizer interface. I used @SerializeWith annotation for POJO class and I printed out debugging information in writeObject() method defined in Externalizer interface and I can see the log it's ok.
> The problem is that in my database table (defined as Datasource), in data column I see some hexa code and not what I overrided in writeObject() method.
> Thank you,
> Cris
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5555) Custom externalizer for Cache Store (jdbc)
by Veli Cris (JIRA)
Veli Cris created ISPN-5555:
-------------------------------
Summary: Custom externalizer for Cache Store (jdbc)
Key: ISPN-5555
URL: https://issues.jboss.org/browse/ISPN-5555
Project: Infinispan
Issue Type: Bug
Affects Versions: 6.0.2.Final
Environment: WildFly 8.2.0 / Linux
Reporter: Veli Cris
Hi,
For a POJO object I created a class that implements Externalizer interface. I used @SerializeWith annotation for POJO class and I printed out debugging information in writeObject() method defined in Externalizer interface and I can see the log it's ok.
The problem is that in my database table (defined as Datasource), in data column I see some hexa code and not what I overrided in writeObject() method.
Thank you,
Cris
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years