The infinispan-spring module is quite late in the sequence of modules to
be compiled so it could be that there is a bug in your version of
OpenJDK's compiler (incidentally which one is it ?). Maybe just adding
"fork" to the maven-compiler-plugin would work around it. Can you try
with the Oracle JDK for 1.6.x ?
Tristan
On 01/20/2012 09:11 AM, Dan Berindei wrote:
Never seen it before Sanne.
Are you using -XX:CompileThreshold with a really low threshold? That
could explain it, as the JIT would compile a lot more code (that would
otherwise be interpreted).
It could also be because Maven uses a separate classloader when
compiling each module and it keeps loading the same classes over and
over again...
Anyway, using -XX:ReservedCodeCacheSize=64m probably wouldn't hurt.
Cheers
Dan
On Fri, Jan 20, 2012 at 9:14 AM, Sanne Grinovero<sanne(a)infinispan.org> wrote:
> No, the build is reported as successful.I'm wondering if it's true.
>
> On Jan 20, 2012 6:52 AM, "Manik Surtani"<manik(a)jboss.org> wrote:
>> I have no idea, I've never seen this before. Does it stop the build?
>>
>> On 20 Jan 2012, at 04:55, Sanne Grinovero wrote:
>>
>>> Hi,
>>> I just noticed this warning in my build logs; I don't read them often
>>> so it might have been there for a while:
>>>
>>> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
>>> infinispan-spring ---
>>> [INFO] Compiling 22 source files to
>>> /home/sanne/workspaces/infinispan/infinispan/spring/target/classes
>>> OpenJDK 64-Bit Server VM warning: CodeCache is full. Compiler has been
>>> disabled.
>>> OpenJDK 64-Bit Server VM warning: Try increasing the code cache size
>>> using -XX:ReservedCodeCacheSize=
>>> Code Cache [0x00007fb8da000000, 0x00007fb8dff90000, 0x00007fb8e0000000)
>>> total_blobs=34047 nmethods=33597 adapters=367 free_code_cache=1036Kb
>>> largest_free_block=511552
>>> [INFO]
>>> [INFO]>>> exec-maven-plugin:1.2.1:java
(serialize_component_metadata)
>>> @ infinispan-spring>>>
>>>
>>> I've never seen such a warning before, anything to be concerned about?
>>>