Mircea Markus <mmarkus> updated the status of jira ISPN-3288 to Resolved

Mircea Markus <mmarkus> made a comment on jira ISPN-3288

duplicate of ISPN-3346

Martin Gencur <mgencur> made a comment on jira ISPN-3346

This happens not only in stress tests but also in functional tests.

Galder Zamarreño <galder.zamarreno> updated the status of jira ISPN-3346 to Coding In Progress

Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-3346

MimeMetadata is marshalled using Externalizers (as demonstrated [here|https://github.com/infinispan/infinispan/blob/master/server/rest/src/test/scala/org/infinispan/rest/TwoServerTest.java]), so the issue is different. Most likely it's a problem related to the externalizer not being registered in this test case.

Which functional test is failing here? Such test should be added to Infinispan Server repo btw.

Michal Linhard <mlinhard> made a comment on jira ISPN-3346

Almost all from here:
https://code.engineering.redhat.com/gerrit/gitweb?p=jdg-functional-tests.git;a=blob;f=remote/core-tests/src/test/java/com/jboss/datagrid/test/rest/RESTClientTestCase.java;h=06bbd1ad4fe2b6c1ad6a66c3b0dc7dddc4790fcb;hb=refs/heads/master
Test results:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/verify-edg-60-functional-tests-rhel6_x86-udp/jdk=java17_default,label=RHEL6_x86_SW/lastCompletedBuild/testReport/
E.g. testGet method:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/verify-edg-60-functional-tests-rhel6_x86-udp/jdk=java17_default,label=RHEL6_x86_SW/lastCompletedBuild/testReport/com.jboss.datagrid.test.rest/RESTClientTestCase%28distmode%29/testGet/

Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-3346

Hmmmmmm, I wonder if this is something similar to what we saw in ISPN-3311...

Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-3346

Assigning this to Tristan since it appears to be some kind of setup/build issue which is stopping from REST server's module lifecycle configuration not being processed correctly. 

[~mlinhard], I think it's great to have jdg-functional-tests.git repository with JDG tests, but I don't see why those tests could not be moved to Infinispan Server repository. This is where these tests belong really. I suspect these issues appear when REST server is tested in clustered mode, which probably is not covered by the tests in Infinispan Server. Instead of duplicating tests, we should move them outright.

Chris Riley <criley> made a comment on jira ISPN-3346

Hi guys, 

We have run into the same exact issue with Infinispan 5.3.0 Final Server (JBoss). In our example we are using the cross site replication configuration file provided with the distribution, I have copied the configuration below. In our case we have found if we comment out the remote site portion of the distributed cache, PUTs and POSTs via REST work fine. With that portion enabled, we get the same exact error as posted in this issue. 

 <subsystem xmlns="urn:infinispan:server:core:5.3" default-cache-container="clustered">
            <cache-container name="clustered" default-cache="default">

                <transport executor="infinispan-transport" lock-timeout="60000" cluster="local" stack="tcp-local"/>
                <distributed-cache mode="ASYNC" name="importantCache">
                    <transaction mode="NONE"/>
                    <compatibility enabled="true"/>
<!--
                    <backups>
                        <backup site="BOS" />
                    </backups>
-->
                </distributed-cache>
            </cache-container>
            <cache-container name="security"/>
        </subsystem>

Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-3346

I've now replicated this in the Infinispan Server testsuite.

Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-3346

Fix coming right up...

Chris Riley <criley> made a comment on jira ISPN-3346

The fix for this is listed as being part of 6.0.0.Beta1 and according to JIRA this was release yesterday. Will this fix still be in 6.0.0.Beta1?

Still present in 6.2.0.DR4

I'm rechecking, I probably confused two bugzillas here.

Verified for 6.2.0.DR4