On Wed, Sep 4, 2013 at 9:16 AM, Francesco Chicchiriccò
<ilgro...@apache.org>wrote:

> On 04/09/2013 14:37, Ralph Goers wrote:
>
>> Also, I think Nick made changes to how we are calling getCallerClass in
>> trunk, so if you want to use that version of OpenJDK you might need to use
>> the latest code.
>>
>
> I have downloaded JDK7u40 Early Access from https://jdk7.java.net/**
> download.html <https://jdk7.java.net/download.html> and set log4j
> artifacts version to 2.0-beta9-SNAPSHOT: no hung occurred.
>
> Afterwards, I've switched back to OpenJDK7u25 (still with log4j
> 2.0-beta9-SNAPSHOT) and everything worked as well; finally successfully
> tested even with Oracle JDK 7.
>
> Guess I've solved our problem on Syncope for the moment: we'll stay on
> 2.0-beta9-SNAPSHOT which is expected to be released way before our next
> major release (featuring log4j).


Good news! Ralph mentioned he was going to push beta9 ASAP (within a week I
am guessing). Stay tuned.

Gary


>
>
> Thanks for your support.
> Regards.
>
>  On Sep 4, 2013, at 6:35 AM, Ralph Goers <rgo...@apache.org> wrote:
>>
>>  I see a thread in getCallerClass.  I don't recall what the status of
>>> 7u25 is (Nick would probably know), but OpenJDK has been going back and
>>> forth on that method.  I think there might be a newer OpenJDK release (40?)
>>> that fixes the problem.
>>>
>>> Sent from my iPad
>>>
>>> On Sep 4, 2013, at 6:19 AM, Francesco Chicchiriccò <ilgro...@apache.org>
>>> wrote:
>>>
>>>  On 04/09/2013 14:14, Gary Gregory wrote:
>>>>
>>>>> [...]
>>>>>
>>>>>> Update: on Linux, with OpenJDK 6 / Oracle JDK6 everything works fine.
>>>>>> With Oracle JDK 7 everything is fine as well, but with OpenJDK 7 test
>>>>>> execution hangs:
>>>>>>
>>>>>> java version "1.7.0_25"
>>>>>> OpenJDK Runtime Environment (IcedTea 2.3.12) (7u25-2.3.12-4)
>>>>>> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
>>>>>>
>>>>>> Using vanilla or "colorized" Maven 3.1.0 does not make any difference.
>>>>>>
>>>>>> Any clue?
>>>>>>
>>>>> On Windows/Oracle, you can hit Ctrl-Break on the command line and get
>>>>> a JVM
>>>>> dump of what all threads are doing. I would try that when the JVM
>>>>> appears
>>>>> hung.
>>>>>
>>>> On Linux it's CTRL+ATL+\ - here you go: http://apaste.info/fPVg
>>>>
>>>> Thanks for your support.
>>>> Regards.
>>>>
>>>
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~**ilgrosso/<http://people.apache.org/~ilgrosso/>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: 
> log4j-user-unsubscribe@**logging.apache.org<log4j-user-unsubscr...@logging.apache.org>
> For additional commands, e-mail: 
> log4j-user-help@logging.**apache.org<log4j-user-h...@logging.apache.org>
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Reply via email to