Re: [aspectwerkz-user] JVM crash with prepared bootclasspath weaving (Modified by Kenji Nakamura)

Alex,

I also turned on details flag in the server log, but since there is no 
aspect definition in aop.xml,
nothing displayed in the log. I removed the entry to narrow down the 
cause of the problem.
Once I get rid of bootclasspath entries for enhanced jar and AW jars, 
the problem disappears so that
I think either enhanced jar or AW jar causes the issue.

If it is not known issue, that's fine, and I can simply note our system 
requires Sun JDK1.4.2_05 or above.
However, this brings another concern regarding the fact that I also 
need to support IBM JDK 1.4.2 for WebSphere.
So far I haven't had time to test on it, but has anyone tried enhance 
jar weaving with IBM JDK?

Thanks,

-Kenji


On May 20, 2005, at 9:47 AM, Alexandre Vasseur wrote:

> Hi
>
> You may check how the memory is going perhaps
> The thing is that it is obvious that the server starts up to a point
> where it crash, which means that the enhanced.jar is not at all in
> cause. The jar you provided thru this link is fine.
> But there might be some other reasons
> Actually turning on the -Daspectwerkz.transform.details=true would
> help to see where the aspects are applied exactly.
>
> Alex
>
> On 5/20/05, Kenji Nakamura <[email protected]> wrote:
>> Alex,
>> I uploaded the screenshot, enhanced jar, server log with AW verbose
>> option, and the text file that is supposed to be sent out to Microsoft
>> with the crash report. You should be able to download them from
>> http://www.clazzsoft.com/aw/
>>
>> Error report contains the list of DLLs loaded into JVM process, and
>> memory dump. That information is not selectable so I can't copy and
>> paste.
>>
>> Please note that JBoss boot up process continued even after the error
>> panel popped up. I also attach the server log with AW verbose option
>> on.
>>
>> Thanks,
>>
>> -Kenji
>>
>> On May 20, 2005, at 8:49 AM, Alexandre Vasseur wrote:
>>
>>> could you send me the enhanced.jar you obtain when running those vm
>>> crash information (screenshot of the panel ?) would help a lot as 
>>> well
>>> You can send those to me directly.
>>> Alex
>>>
>>> On 5/20/05, Kenji Nakamura <[email protected]> wrote:
>>>> Forgot to mention about AW version.
>>>> I use AW-2.0 with the patch to get rid of JDK dependency from Plug
>>>> (MAIN:avasseur:20050513073502)
>>>>
>>>> Thanks,
>>>>
>>>> -kenji
>>>>
>>>> On May 20, 2005, at 8:28 AM, Kenji Nakamura wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> My colleagues reported JVM crash on application startup with old
>>>>> revisions of Sun JDK1.4.2 on Windows XP pro.
>>>>> I use prepared bootclasspath weaving, and confirmed enhanced jar is
>>>>> generated with the same JDK.
>>>>> Our application uses Jboss3.2.6 as the platform. It crashes even 
>>>>> when
>>>>> aop.xml doesn't have any aspect definition.
>>>>>
>>>>> I confirmed it crashes on Sun JDK1.4.2_01, 03 and 04 on Windows. 
>>>>> 05,
>>>>> 07, and 08 are fine.
>>>>> Unfortunately, I cannot copy and paste the JVM crash details 
>>>>> appeared
>>>>> in the crash panel.
>>>>>
>>>>> Is this a known issue?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -Kenji
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>