From galder at redhat.com Tue Feb 4 03:21:13 2014 From: galder at redhat.com (=?windows-1252?Q?Galder_Zamarre=F1o?=) Date: Tue, 4 Feb 2014 09:21:13 +0100 Subject: [jboss-as7-dev] Module jars dissapearing leaving empty classes/ folders and errors Message-ID: <69786B4D-C6DC-49AD-B3ED-2BDED1E7AE28@redhat.com> Hi all, We?re having issues with our Infinispan Server integration tests, which run within Wildfly 8.0.0.Beta1 (as I?m typing I?m wondering if we should just upgrade it to see if this goes away...?). Quite often some of the runs fail with error message [1]. Having looked at the build environment when a run fails, you see this: -- $ ls modules/system/layers/base/org/infinispan/server/rest/main drwxrwxr-x 2 g staff 68B Feb 3 18:41 classes ( ... ... This is completely different to what happens with a successful run: -- $ ls modules/system/layers/base/org/infinispan/server/rest/main -rw-r--r-- 1 g staff 103K Feb 3 19:40 infinispan-classes.jar ( ... > ... > > ... > > This is completely different to what happens with a successful run: > > -- > $ ls modules/system/layers/base/org/infinispan/server/rest/main > -rw-r--r-- 1 g staff 103K Feb 3 19:40 infinispan-classes.jar (<-- a > jar file!) > -rw-r--r-- 1 g staff 278B Feb 3 19:40 infinispan-classes.jar.index > -rw-r--r-- 1 g staff 2.1K Feb 3 19:40 module.xml > > $ jar tf > modules/system/layers/base/org/infinispan/server/rest/main/infinispan-classes.jar > | grep ExtendedHeaders > org/infinispan/rest/configuration/ExtendedHeaders.class > > $ more > modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > ... > > -- > > Anyone can explain what is going on here? Does it ring a bell to anyone? > Is this a known Wildfly issue by any chance? > > [1] https://gist.github.com/galderz/bd74cebfc840ef3ae284 > > Cheers, > -- > Galder Zamarre?o > galder at redhat.com > twitter.com/galderz > > Project Lead, Escalante > http://escalante.io > > Engineer, Infinispan > http://infinispan.org > > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20140204/603d17ac/attachment.html From galder at redhat.com Tue Feb 4 03:56:52 2014 From: galder at redhat.com (=?windows-1252?Q?Galder_Zamarre=F1o?=) Date: Tue, 4 Feb 2014 09:56:52 +0100 Subject: [jboss-as7-dev] Module jars dissapearing leaving empty classes/ folders and errors In-Reply-To: References: <69786B4D-C6DC-49AD-B3ED-2BDED1E7AE28@redhat.com> Message-ID: On 04 Feb 2014, at 09:37, Stuart Douglas wrote: > This looks like an issue with your environment. The modules directory is static. Wildfly does not contain any code that messes with it. I would say the culprit is probably something in either your build process or your test suite. Correction, this is happening with AS 7.2.0.Final (Wildfly 8 used somewhere else). I guess your answer still applies? Cheers, > > Stuart > > > On Tue, Feb 4, 2014 at 10:21 AM, Galder Zamarre?o wrote: > Hi all, > > We?re having issues with our Infinispan Server integration tests, which run within Wildfly 8.0.0.Beta1 (as I?m typing I?m wondering if we should just upgrade it to see if this goes away...?). > > Quite often some of the runs fail with error message [1]. > > Having looked at the build environment when a run fails, you see this: > > -- > $ ls modules/system/layers/base/org/infinispan/server/rest/main > drwxrwxr-x 2 g staff 68B Feb 3 18:41 classes ( -rw-r--r-- 1 g staff 1B Feb 3 18:41 classes.index > -rw-r--r-- 1 g staff 2.1K Feb 3 18:41 module.xml > > $ ls modules/system/layers/base/org/infinispan/server/rest/main/classes > drwxrwxr-x 2 g staff 68B Feb 3 18:41 . > drwxrwxr-x 5 g staff 170B Feb 3 18:41 .. > > $ more modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > ... > > This is completely different to what happens with a successful run: > > -- > $ ls modules/system/layers/base/org/infinispan/server/rest/main > -rw-r--r-- 1 g staff 103K Feb 3 19:40 infinispan-classes.jar ( -rw-r--r-- 1 g staff 278B Feb 3 19:40 infinispan-classes.jar.index > -rw-r--r-- 1 g staff 2.1K Feb 3 19:40 module.xml > > $ jar tf modules/system/layers/base/org/infinispan/server/rest/main/infinispan-classes.jar | grep ExtendedHeaders > org/infinispan/rest/configuration/ExtendedHeaders.class > > $ more modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > ? > > Anyone can explain what is going on here? Does it ring a bell to anyone? Is this a known Wildfly issue by any chance? > > [1] https://gist.github.com/galderz/bd74cebfc840ef3ae284 > > Cheers, > -- > Galder Zamarre?o > galder at redhat.com > twitter.com/galderz > > Project Lead, Escalante > http://escalante.io > > Engineer, Infinispan > http://infinispan.org > > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > -- Galder Zamarre?o galder at redhat.com twitter.com/galderz Project Lead, Escalante http://escalante.io Engineer, Infinispan http://infinispan.org From stuart.w.douglas at gmail.com Tue Feb 4 04:00:10 2014 From: stuart.w.douglas at gmail.com (Stuart Douglas) Date: Tue, 4 Feb 2014 11:00:10 +0200 Subject: [jboss-as7-dev] Module jars dissapearing leaving empty classes/ folders and errors In-Reply-To: References: <69786B4D-C6DC-49AD-B3ED-2BDED1E7AE28@redhat.com> Message-ID: Yes, there is nothing in the server code that modified the modules directory. Stuart On Tue, Feb 4, 2014 at 10:56 AM, Galder Zamarre?o wrote: > > On 04 Feb 2014, at 09:37, Stuart Douglas > wrote: > > > This looks like an issue with your environment. The modules directory is > static. Wildfly does not contain any code that messes with it. I would say > the culprit is probably something in either your build process or your test > suite. > > Correction, this is happening with AS 7.2.0.Final (Wildfly 8 used > somewhere else). I guess your answer still applies? > > Cheers, > > > > > Stuart > > > > > > On Tue, Feb 4, 2014 at 10:21 AM, Galder Zamarre?o > wrote: > > Hi all, > > > > We're having issues with our Infinispan Server integration tests, which > run within Wildfly 8.0.0.Beta1 (as I'm typing I'm wondering if we should > just upgrade it to see if this goes away...?). > > > > Quite often some of the runs fail with error message [1]. > > > > Having looked at the build environment when a run fails, you see this: > > > > -- > > $ ls modules/system/layers/base/org/infinispan/server/rest/main > > drwxrwxr-x 2 g staff 68B Feb 3 18:41 classes (<-- a directory??) > > -rw-r--r-- 1 g staff 1B Feb 3 18:41 classes.index > > -rw-r--r-- 1 g staff 2.1K Feb 3 18:41 module.xml > > > > $ ls modules/system/layers/base/org/infinispan/server/rest/main/classes > > drwxrwxr-x 2 g staff 68B Feb 3 18:41 . > > drwxrwxr-x 5 g staff 170B Feb 3 18:41 .. > > > > $ more > modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > > > ... > > > > ... > > > > This is completely different to what happens with a successful run: > > > > -- > > $ ls modules/system/layers/base/org/infinispan/server/rest/main > > -rw-r--r-- 1 g staff 103K Feb 3 19:40 infinispan-classes.jar (<-- a > jar file!) > > -rw-r--r-- 1 g staff 278B Feb 3 19:40 infinispan-classes.jar.index > > -rw-r--r-- 1 g staff 2.1K Feb 3 19:40 module.xml > > > > $ jar tf > modules/system/layers/base/org/infinispan/server/rest/main/infinispan-classes.jar > | grep ExtendedHeaders > > org/infinispan/rest/configuration/ExtendedHeaders.class > > > > $ more > modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > > > ... > > > > -- > > > > Anyone can explain what is going on here? Does it ring a bell to anyone? > Is this a known Wildfly issue by any chance? > > > > [1] https://gist.github.com/galderz/bd74cebfc840ef3ae284 > > > > Cheers, > > -- > > Galder Zamarre?o > > galder at redhat.com > > twitter.com/galderz > > > > Project Lead, Escalante > > http://escalante.io > > > > Engineer, Infinispan > > http://infinispan.org > > > > > > _______________________________________________ > > jboss-as7-dev mailing list > > jboss-as7-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > > > > -- > Galder Zamarre?o > galder at redhat.com > twitter.com/galderz > > Project Lead, Escalante > http://escalante.io > > Engineer, Infinispan > http://infinispan.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20140204/a7418e8c/attachment-0001.html From stuart.w.douglas at gmail.com Tue Feb 4 04:01:19 2014 From: stuart.w.douglas at gmail.com (Stuart Douglas) Date: Tue, 4 Feb 2014 11:01:19 +0200 Subject: [jboss-as7-dev] Module jars dissapearing leaving empty classes/ folders and errors In-Reply-To: References: <69786B4D-C6DC-49AD-B3ED-2BDED1E7AE28@redhat.com> Message-ID: On Tue, Feb 4, 2014 at 11:00 AM, Stuart Douglas wrote: > Yes, there is nothing in the server code that modified the modules > directory. > Well, except for the new patching stuff, but that is not really relevant here. Stuart > > Stuart > > > On Tue, Feb 4, 2014 at 10:56 AM, Galder Zamarre?o wrote: > >> >> On 04 Feb 2014, at 09:37, Stuart Douglas >> wrote: >> >> > This looks like an issue with your environment. The modules directory >> is static. Wildfly does not contain any code that messes with it. I would >> say the culprit is probably something in either your build process or your >> test suite. >> >> Correction, this is happening with AS 7.2.0.Final (Wildfly 8 used >> somewhere else). I guess your answer still applies? >> >> Cheers, >> >> > >> > Stuart >> > >> > >> > On Tue, Feb 4, 2014 at 10:21 AM, Galder Zamarre?o >> wrote: >> > Hi all, >> > >> > We're having issues with our Infinispan Server integration tests, which >> run within Wildfly 8.0.0.Beta1 (as I'm typing I'm wondering if we should >> just upgrade it to see if this goes away...?). >> > >> > Quite often some of the runs fail with error message [1]. >> > >> > Having looked at the build environment when a run fails, you see this: >> > >> > -- >> > $ ls modules/system/layers/base/org/infinispan/server/rest/main >> > drwxrwxr-x 2 g staff 68B Feb 3 18:41 classes (<-- a directory??) >> > -rw-r--r-- 1 g staff 1B Feb 3 18:41 classes.index >> > -rw-r--r-- 1 g staff 2.1K Feb 3 18:41 module.xml >> > >> > $ ls modules/system/layers/base/org/infinispan/server/rest/main/classes >> > drwxrwxr-x 2 g staff 68B Feb 3 18:41 . >> > drwxrwxr-x 5 g staff 170B Feb 3 18:41 .. >> > >> > $ more >> modules/system/layers/base/org/infinispan/server/rest/main/module.xml >> > >> > ... >> > >> > ... >> > >> > This is completely different to what happens with a successful run: >> > >> > -- >> > $ ls modules/system/layers/base/org/infinispan/server/rest/main >> > -rw-r--r-- 1 g staff 103K Feb 3 19:40 infinispan-classes.jar (<-- a >> jar file!) >> > -rw-r--r-- 1 g staff 278B Feb 3 19:40 infinispan-classes.jar.index >> > -rw-r--r-- 1 g staff 2.1K Feb 3 19:40 module.xml >> > >> > $ jar tf >> modules/system/layers/base/org/infinispan/server/rest/main/infinispan-classes.jar >> | grep ExtendedHeaders >> > org/infinispan/rest/configuration/ExtendedHeaders.class >> > >> > $ more >> modules/system/layers/base/org/infinispan/server/rest/main/module.xml >> > >> > ... >> > >> > -- >> > >> > Anyone can explain what is going on here? Does it ring a bell to >> anyone? Is this a known Wildfly issue by any chance? >> > >> > [1] https://gist.github.com/galderz/bd74cebfc840ef3ae284 >> > >> > Cheers, >> > -- >> > Galder Zamarre?o >> > galder at redhat.com >> > twitter.com/galderz >> > >> > Project Lead, Escalante >> > http://escalante.io >> > >> > Engineer, Infinispan >> > http://infinispan.org >> > >> > >> > _______________________________________________ >> > jboss-as7-dev mailing list >> > jboss-as7-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> > >> >> >> -- >> Galder Zamarre?o >> galder at redhat.com >> twitter.com/galderz >> >> Project Lead, Escalante >> http://escalante.io >> >> Engineer, Infinispan >> http://infinispan.org >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20140204/b6aab9ca/attachment.html From galder at redhat.com Tue Feb 4 04:14:34 2014 From: galder at redhat.com (=?windows-1252?Q?Galder_Zamarre=F1o?=) Date: Tue, 4 Feb 2014 10:14:34 +0100 Subject: [jboss-as7-dev] Module jars dissapearing leaving empty classes/ folders and errors In-Reply-To: References: <69786B4D-C6DC-49AD-B3ED-2BDED1E7AE28@redhat.com> Message-ID: On 04 Feb 2014, at 10:01, Stuart Douglas wrote: > > > > On Tue, Feb 4, 2014 at 11:00 AM, Stuart Douglas wrote: > Yes, there is nothing in the server code that modified the modules directory. > > Well, except for the new patching stuff, but that is not really relevant here. The testsuite AS/WF builds are built out of the distribution build, which shows the same problem. The distribution we build uses the scripts we got from AS [1]. Do you see anything in there that could be causing this? We are using maven-antrun-plugin version 1.3, and take into account the lib.xml in [2]. Finally, do you have any suggestions on changes we could make to these files to further debug the issue? Thanks a lot for your help! [1] https://github.com/infinispan/infinispan/blob/master/server/integration/build/build.xml [2] https://github.com/infinispan/infinispan/blob/master/server/integration/build/lib.xml > > Stuart > > > Stuart > > > On Tue, Feb 4, 2014 at 10:56 AM, Galder Zamarre?o wrote: > > On 04 Feb 2014, at 09:37, Stuart Douglas wrote: > > > This looks like an issue with your environment. The modules directory is static. Wildfly does not contain any code that messes with it. I would say the culprit is probably something in either your build process or your test suite. > > Correction, this is happening with AS 7.2.0.Final (Wildfly 8 used somewhere else). I guess your answer still applies? > > Cheers, > > > > > Stuart > > > > > > On Tue, Feb 4, 2014 at 10:21 AM, Galder Zamarre?o wrote: > > Hi all, > > > > We?re having issues with our Infinispan Server integration tests, which run within Wildfly 8.0.0.Beta1 (as I?m typing I?m wondering if we should just upgrade it to see if this goes away...?). > > > > Quite often some of the runs fail with error message [1]. > > > > Having looked at the build environment when a run fails, you see this: > > > > -- > > $ ls modules/system/layers/base/org/infinispan/server/rest/main > > drwxrwxr-x 2 g staff 68B Feb 3 18:41 classes ( > -rw-r--r-- 1 g staff 1B Feb 3 18:41 classes.index > > -rw-r--r-- 1 g staff 2.1K Feb 3 18:41 module.xml > > > > $ ls modules/system/layers/base/org/infinispan/server/rest/main/classes > > drwxrwxr-x 2 g staff 68B Feb 3 18:41 . > > drwxrwxr-x 5 g staff 170B Feb 3 18:41 .. > > > > $ more modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > > > ... > > > > This is completely different to what happens with a successful run: > > > > -- > > $ ls modules/system/layers/base/org/infinispan/server/rest/main > > -rw-r--r-- 1 g staff 103K Feb 3 19:40 infinispan-classes.jar ( > -rw-r--r-- 1 g staff 278B Feb 3 19:40 infinispan-classes.jar.index > > -rw-r--r-- 1 g staff 2.1K Feb 3 19:40 module.xml > > > > $ jar tf modules/system/layers/base/org/infinispan/server/rest/main/infinispan-classes.jar | grep ExtendedHeaders > > org/infinispan/rest/configuration/ExtendedHeaders.class > > > > $ more modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > > > ? > > > > Anyone can explain what is going on here? Does it ring a bell to anyone? Is this a known Wildfly issue by any chance? > > > > [1] https://gist.github.com/galderz/bd74cebfc840ef3ae284 > > > > Cheers, > > -- > > Galder Zamarre?o > > galder at redhat.com > > twitter.com/galderz > > > > Project Lead, Escalante > > http://escalante.io > > > > Engineer, Infinispan > > http://infinispan.org > > > > > > _______________________________________________ > > jboss-as7-dev mailing list > > jboss-as7-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > > > > -- > Galder Zamarre?o > galder at redhat.com > twitter.com/galderz > > Project Lead, Escalante > http://escalante.io > > Engineer, Infinispan > http://infinispan.org > > > -- Galder Zamarre?o galder at redhat.com twitter.com/galderz Project Lead, Escalante http://escalante.io Engineer, Infinispan http://infinispan.org From stuart.w.douglas at gmail.com Tue Feb 4 04:38:22 2014 From: stuart.w.douglas at gmail.com (Stuart Douglas) Date: Tue, 4 Feb 2014 11:38:22 +0200 Subject: [jboss-as7-dev] Module jars dissapearing leaving empty classes/ folders and errors In-Reply-To: References: <69786B4D-C6DC-49AD-B3ED-2BDED1E7AE28@redhat.com> Message-ID: It is almost certainly something to do with this: I guess sometimes the classes artefact is being attached as a reference to the classes directory, rather than a reference to a jar, which causes the issue. Stuart On Tue, Feb 4, 2014 at 11:14 AM, Galder Zamarre?o wrote: > > On 04 Feb 2014, at 10:01, Stuart Douglas > wrote: > > > > > > > > > On Tue, Feb 4, 2014 at 11:00 AM, Stuart Douglas < > stuart.w.douglas at gmail.com> wrote: > > Yes, there is nothing in the server code that modified the modules > directory. > > > > Well, except for the new patching stuff, but that is not really relevant > here. > > The testsuite AS/WF builds are built out of the distribution build, which > shows the same problem. The distribution we build uses the scripts we got > from AS [1]. > > Do you see anything in there that could be causing this? We are using > maven-antrun-plugin version 1.3, and take into account the lib.xml in [2]. > > Finally, do you have any suggestions on changes we could make to these > files to further debug the issue? > > Thanks a lot for your help! > > [1] > https://github.com/infinispan/infinispan/blob/master/server/integration/build/build.xml > [2] > https://github.com/infinispan/infinispan/blob/master/server/integration/build/lib.xml > > > > > Stuart > > > > > > Stuart > > > > > > On Tue, Feb 4, 2014 at 10:56 AM, Galder Zamarre?o > wrote: > > > > On 04 Feb 2014, at 09:37, Stuart Douglas > wrote: > > > > > This looks like an issue with your environment. The modules directory > is static. Wildfly does not contain any code that messes with it. I would > say the culprit is probably something in either your build process or your > test suite. > > > > Correction, this is happening with AS 7.2.0.Final (Wildfly 8 used > somewhere else). I guess your answer still applies? > > > > Cheers, > > > > > > > > Stuart > > > > > > > > > On Tue, Feb 4, 2014 at 10:21 AM, Galder Zamarre?o > wrote: > > > Hi all, > > > > > > We're having issues with our Infinispan Server integration tests, > which run within Wildfly 8.0.0.Beta1 (as I'm typing I'm wondering if we > should just upgrade it to see if this goes away...?). > > > > > > Quite often some of the runs fail with error message [1]. > > > > > > Having looked at the build environment when a run fails, you see this: > > > > > > -- > > > $ ls modules/system/layers/base/org/infinispan/server/rest/main > > > drwxrwxr-x 2 g staff 68B Feb 3 18:41 classes (<-- a directory??) > > > -rw-r--r-- 1 g staff 1B Feb 3 18:41 classes.index > > > -rw-r--r-- 1 g staff 2.1K Feb 3 18:41 module.xml > > > > > > $ ls modules/system/layers/base/org/infinispan/server/rest/main/classes > > > drwxrwxr-x 2 g staff 68B Feb 3 18:41 . > > > drwxrwxr-x 5 g staff 170B Feb 3 18:41 .. > > > > > > $ more > modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > > > > > ... > > > > > > ... > > > > > > This is completely different to what happens with a successful run: > > > > > > -- > > > $ ls modules/system/layers/base/org/infinispan/server/rest/main > > > -rw-r--r-- 1 g staff 103K Feb 3 19:40 infinispan-classes.jar (<-- > a jar file!) > > > -rw-r--r-- 1 g staff 278B Feb 3 19:40 infinispan-classes.jar.index > > > -rw-r--r-- 1 g staff 2.1K Feb 3 19:40 module.xml > > > > > > $ jar tf > modules/system/layers/base/org/infinispan/server/rest/main/infinispan-classes.jar > | grep ExtendedHeaders > > > org/infinispan/rest/configuration/ExtendedHeaders.class > > > > > > $ more > modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > > > > > ... > > > > > > -- > > > > > > Anyone can explain what is going on here? Does it ring a bell to > anyone? Is this a known Wildfly issue by any chance? > > > > > > [1] https://gist.github.com/galderz/bd74cebfc840ef3ae284 > > > > > > Cheers, > > > -- > > > Galder Zamarre?o > > > galder at redhat.com > > > twitter.com/galderz > > > > > > Project Lead, Escalante > > > http://escalante.io > > > > > > Engineer, Infinispan > > > http://infinispan.org > > > > > > > > > _______________________________________________ > > > jboss-as7-dev mailing list > > > jboss-as7-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > > > > > > > > -- > > Galder Zamarre?o > > galder at redhat.com > > twitter.com/galderz > > > > Project Lead, Escalante > > http://escalante.io > > > > Engineer, Infinispan > > http://infinispan.org > > > > > > > > > -- > Galder Zamarre?o > galder at redhat.com > twitter.com/galderz > > Project Lead, Escalante > http://escalante.io > > Engineer, Infinispan > http://infinispan.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20140204/07fbb9e4/attachment-0001.html From galder at redhat.com Tue Feb 4 07:30:35 2014 From: galder at redhat.com (=?windows-1252?Q?Galder_Zamarre=F1o?=) Date: Tue, 4 Feb 2014 13:30:35 +0100 Subject: [jboss-as7-dev] Module jars dissapearing leaving empty classes/ folders and errors In-Reply-To: References: <69786B4D-C6DC-49AD-B3ED-2BDED1E7AE28@redhat.com> Message-ID: <05187A01-9E89-41D7-9E85-0FE4AC9DACCA@redhat.com> On 04 Feb 2014, at 10:38, Stuart Douglas wrote: > It is almost certainly something to do with this: > > > > > > > > I guess sometimes the classes artefact is being attached as a reference to the classes directory, rather than a reference to a jar, which causes the issue. Here?s a gist with a subset of the build log [1]. When it works fine, it?s copying a jar, when it?s not, it?s copying an empty folder. However, this is not only happening for the org.infinispan.server.rest module, others show the same issue [2]. What seems to be a pattern is that it only happens with modules that are built by us, it?s not happening for modules coming with the base AS/WF instance. I?ve traced back and this might be due to build failures that are not producing the right jars [3]. @Stuart, this is really our problem. Sorry for the inconvenience! [1] https://gist.github.com/galderz/b9286f385aad1316df51 [2] https://gist.github.com/galderz/9e6a9bd9b18b805db323 [3] https://gist.github.com/galderz/6ab662a1027cd96cbd8c > > Stuart > > > On Tue, Feb 4, 2014 at 11:14 AM, Galder Zamarre?o wrote: > > On 04 Feb 2014, at 10:01, Stuart Douglas wrote: > > > > > > > > > On Tue, Feb 4, 2014 at 11:00 AM, Stuart Douglas wrote: > > Yes, there is nothing in the server code that modified the modules directory. > > > > Well, except for the new patching stuff, but that is not really relevant here. > > The testsuite AS/WF builds are built out of the distribution build, which shows the same problem. The distribution we build uses the scripts we got from AS [1]. > > Do you see anything in there that could be causing this? We are using maven-antrun-plugin version 1.3, and take into account the lib.xml in [2]. > > Finally, do you have any suggestions on changes we could make to these files to further debug the issue? > > Thanks a lot for your help! > > [1] https://github.com/infinispan/infinispan/blob/master/server/integration/build/build.xml > [2] https://github.com/infinispan/infinispan/blob/master/server/integration/build/lib.xml > > > > > Stuart > > > > > > Stuart > > > > > > On Tue, Feb 4, 2014 at 10:56 AM, Galder Zamarre?o wrote: > > > > On 04 Feb 2014, at 09:37, Stuart Douglas wrote: > > > > > This looks like an issue with your environment. The modules directory is static. Wildfly does not contain any code that messes with it. I would say the culprit is probably something in either your build process or your test suite. > > > > Correction, this is happening with AS 7.2.0.Final (Wildfly 8 used somewhere else). I guess your answer still applies? > > > > Cheers, > > > > > > > > Stuart > > > > > > > > > On Tue, Feb 4, 2014 at 10:21 AM, Galder Zamarre?o wrote: > > > Hi all, > > > > > > We?re having issues with our Infinispan Server integration tests, which run within Wildfly 8.0.0.Beta1 (as I?m typing I?m wondering if we should just upgrade it to see if this goes away...?). > > > > > > Quite often some of the runs fail with error message [1]. > > > > > > Having looked at the build environment when a run fails, you see this: > > > > > > -- > > > $ ls modules/system/layers/base/org/infinispan/server/rest/main > > > drwxrwxr-x 2 g staff 68B Feb 3 18:41 classes ( > > -rw-r--r-- 1 g staff 1B Feb 3 18:41 classes.index > > > -rw-r--r-- 1 g staff 2.1K Feb 3 18:41 module.xml > > > > > > $ ls modules/system/layers/base/org/infinispan/server/rest/main/classes > > > drwxrwxr-x 2 g staff 68B Feb 3 18:41 . > > > drwxrwxr-x 5 g staff 170B Feb 3 18:41 .. > > > > > > $ more modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > > > > > ... > > > > > > This is completely different to what happens with a successful run: > > > > > > -- > > > $ ls modules/system/layers/base/org/infinispan/server/rest/main > > > -rw-r--r-- 1 g staff 103K Feb 3 19:40 infinispan-classes.jar ( > > -rw-r--r-- 1 g staff 278B Feb 3 19:40 infinispan-classes.jar.index > > > -rw-r--r-- 1 g staff 2.1K Feb 3 19:40 module.xml > > > > > > $ jar tf modules/system/layers/base/org/infinispan/server/rest/main/infinispan-classes.jar | grep ExtendedHeaders > > > org/infinispan/rest/configuration/ExtendedHeaders.class > > > > > > $ more modules/system/layers/base/org/infinispan/server/rest/main/module.xml > > > > > > ? > > > > > > Anyone can explain what is going on here? Does it ring a bell to anyone? Is this a known Wildfly issue by any chance? > > > > > > [1] https://gist.github.com/galderz/bd74cebfc840ef3ae284 > > > > > > Cheers, > > > -- > > > Galder Zamarre?o > > > galder at redhat.com > > > twitter.com/galderz > > > > > > Project Lead, Escalante > > > http://escalante.io > > > > > > Engineer, Infinispan > > > http://infinispan.org > > > > > > > > > _______________________________________________ > > > jboss-as7-dev mailing list > > > jboss-as7-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > > > > > > > > -- > > Galder Zamarre?o > > galder at redhat.com > > twitter.com/galderz > > > > Project Lead, Escalante > > http://escalante.io > > > > Engineer, Infinispan > > http://infinispan.org > > > > > > > > > -- > Galder Zamarre?o > galder at redhat.com > twitter.com/galderz > > Project Lead, Escalante > http://escalante.io > > Engineer, Infinispan > http://infinispan.org > > -- Galder Zamarre?o galder at redhat.com twitter.com/galderz Project Lead, Escalante http://escalante.io Engineer, Infinispan http://infinispan.org From galder at redhat.com Fri Feb 7 09:27:11 2014 From: galder at redhat.com (=?windows-1252?Q?Galder_Zamarre=F1o?=) Date: Fri, 7 Feb 2014 15:27:11 +0100 Subject: [jboss-as7-dev] Wildfly's build/lib.xml behaves unexpectedly with JDK8 Message-ID: Hi, In JDK8, [1] causes issues, since the replace only happens the first time the character is found. We use this lib.xml in Infinispan as well [2]. I?ve workaround it by doing this instead: name = name.split(".").join("/"); This seems to work fine, but have not fully tested it. Cheers, [1] https://github.com/wildfly/wildfly/blob/master/build/lib.xml#L75 [2] https://issues.jboss.org/browse/ISPN-3974?focusedCommentId=12942643&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12942643 -- Galder Zamarre?o galder at redhat.com twitter.com/galderz Project Lead, Escalante http://escalante.io Engineer, Infinispan http://infinispan.org