You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by Marc Logemann <li...@logemann.org> on 2009/05/16 15:09:02 UTC
strange JPA Enhance stack
Hi,
today we installed our Continous build system (TeamCity) and we tried
to run our first automated build on Linux with OpenJDK 6. Even though
our build works on all client computers it fails with the same (ivy
resolved) build path on OpenJDK 6 wih the following stack. Perhaps
someone can comment on this:
[15:06:10]: [jpaenhance] openjpac
[15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
[15:06:11]: [openjpac] at serp.bytecode.Code.getInstruction(Code.java:
2131)
[15:06:11]: [openjpac] at serp.bytecode.Local.getEnd(Local.java:113)
[15:06:11]: [openjpac] at serp.bytecode.Local.updateTargets(Local.java:
155)
[15:06:11]: [openjpac] at
serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
[15:06:11]: [openjpac] at serp.bytecode.Code.read(Code.java:2031)
[15:06:11]: [openjpac] at
serp.bytecode.Attributes.readAttributes(Attributes.java:152)
[15:06:11]: [openjpac] at serp.bytecode.BCMember.read(BCMember.java:365)
[15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:123)
[15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:144)
[15:06:11]: [openjpac] at serp.bytecode.Project.loadClass(Project.java:
139)
[15:06:11]: [openjpac] at
org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
[15:06:11]: [openjpac] at
org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:89)
[15:06:11]: [openjpac] at
org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
[15:06:11]: [openjpac] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[15:06:11]: [openjpac] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[15:06:11]: [openjpac] at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57)
[15:06:11]: [openjpac] at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
43)
[15:06:11]: [openjpac] at java.lang.reflect.Method.invoke(Method.java:
616)
[15:06:11]: [openjpac] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
106)
[15:06:11]: [openjpac] at org.apache.tools.ant.Task.perform(Task.java:
348)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Target.execute(Target.java:357)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Target.performTasks(Target.java:385)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[15:06:11]: [openjpac] at
org
.apache
.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:
41)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Project.executeTargets(Project.java:1189)
[15:06:11]: [openjpac] at org.apache.tools.ant.Main.runBuild(Main.java:
758)
[15:06:11]: [openjpac] at org.apache.tools.ant.Main.startAnt(Main.java:
217)
[15:06:11]: [openjpac] at
org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
[15:06:11]: [openjpac] at
org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
[15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
[15:06:16]: Ant output:
at serp.bytecode.Local.updateTargets(Local.java:155)
at serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
at serp.bytecode.Code.read(Code.java:2031)
at serp.bytecode.Attributes.readAttributes(Attributes.java:152)
at serp.bytecode.BCMember.read(BCMember.java:365)
at serp.bytecode.BCClass.read(BCClass.java:123)
at serp.bytecode.BCClass.read(BCClass.java:144)
at serp.bytecode.Project.loadClass(Project.java:139)
at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
at org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:
89)
at org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:
172)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57)
at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at
org
.apache
.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:
41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Re: strange JPA Enhance stack
Posted by Donald Woods <dw...@apache.org>.
Which Linux platform and level of OpenJDK 6 are you using? Are you
using Fedora 10 and the OpenJDK it provides...? Are you running x86 or
x86_64 Linux?
-Donald
Marc Logemann wrote:
> Hi,
>
> today we installed our Continous build system (TeamCity) and we tried to
> run our first automated build on Linux with OpenJDK 6. Even though our
> build works on all client computers it fails with the same (ivy
> resolved) build path on OpenJDK 6 wih the following stack. Perhaps
> someone can comment on this:
>
> [15:06:10]: [jpaenhance] openjpac
> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
> [15:06:11]: [openjpac] at serp.bytecode.Code.getInstruction(Code.java:2131)
> [15:06:11]: [openjpac] at serp.bytecode.Local.getEnd(Local.java:113)
> [15:06:11]: [openjpac] at serp.bytecode.Local.updateTargets(Local.java:155)
> [15:06:11]: [openjpac] at
> serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
> [15:06:11]: [openjpac] at serp.bytecode.Code.read(Code.java:2031)
> [15:06:11]: [openjpac] at
> serp.bytecode.Attributes.readAttributes(Attributes.java:152)
> [15:06:11]: [openjpac] at serp.bytecode.BCMember.read(BCMember.java:365)
> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:123)
> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:144)
> [15:06:11]: [openjpac] at serp.bytecode.Project.loadClass(Project.java:139)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:89)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> [15:06:11]: [openjpac] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [15:06:11]: [openjpac] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> [15:06:11]: [openjpac] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> [15:06:11]: [openjpac] at java.lang.reflect.Method.invoke(Method.java:616)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [15:06:11]: [openjpac] at org.apache.tools.ant.Task.perform(Task.java:348)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Target.execute(Target.java:357)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Target.performTasks(Target.java:385)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> [15:06:11]: [openjpac] at org.apache.tools.ant.Main.runBuild(Main.java:758)
> [15:06:11]: [openjpac] at org.apache.tools.ant.Main.startAnt(Main.java:217)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
> [15:06:16]: Ant output:
> at serp.bytecode.Local.updateTargets(Local.java:155)
> at serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
> at serp.bytecode.Code.read(Code.java:2031)
> at serp.bytecode.Attributes.readAttributes(Attributes.java:152)
> at serp.bytecode.BCMember.read(BCMember.java:365)
> at serp.bytecode.BCClass.read(BCClass.java:123)
> at serp.bytecode.BCClass.read(BCClass.java:144)
> at serp.bytecode.Project.loadClass(Project.java:139)
> at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
> at org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:89)
> at org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> at org.apache.tools.ant.Main.runBuild(Main.java:758)
> at org.apache.tools.ant.Main.startAnt(Main.java:217)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>
>
>
> ---
> regards
> Marc Logemann
> http://www.logemann.org
> http://www.logentis.de
>
>
>
>
>
Re: strange JPA Enhance stack
Posted by Marc Logemann <li...@logemann.org>.
Craig,
my intention was not to rant against SERP :-)
I already filed a JIRA. I will report things there if i see something
new during my tests...
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 19.05.2009 um 21:57 schrieb Craig L Russell:
> Hi Marc,
>
> As Mike says, we could be a bit more friendly. By the way, SERP has
> been very reliable so this hasn't been much of an issue to date.
>
> Could you please file a JIRA so we don't forget about it?
>
> Thanks,
>
> Craig
>
> On May 19, 2009, at 5:53 AM, Michael Dick wrote:
>
>> Hi Marc,
>>
>> Sounds like an unchecked exception thrown by Serp and we could be a
>> bit
>> friendlier about how we handle it. At least dumping the classname
>> that we're
>> trying to load would help. Adding a try / catch might be helpful.
>> Which
>> version of OpenJPA are you using?
>>
>> My guess is that it is OpenJDK related and the compiled class is not
>> matching Serp's expectation. I haven't seen this exception before
>> though and
>> I can't tell you why you're getting it.
>>
>> -mike
>>
>> On Tue, May 19, 2009 at 3:46 AM, Marc Logemann <li...@logemann.org>
>> wrote:
>>
>>> David,
>>>
>>> no, have not done this. Its quite a hughe effort to create a
>>> project from
>>> scratch and deploy it to SCM and configure TeamCity to "compile/
>>> test" it. I
>>> still think its not a library issue because i use ivy within ANT
>>> and the
>>> build system resolves libs the same way as its done on each
>>> developer
>>> machine. The stack doesnt look like a missing lib to me. And its
>>> definitely
>>> also not an ANT issue because i am using the same ANT Target on
>>> the dev
>>> machines.
>>>
>>> I hoped somebody who developed the enhancer can tell something
>>> about the
>>> stack. I mean something like "this problem can only occur under
>>> this or that
>>> condition".
>>>
>>> In any way... do we agree that an IllegalArgumentException in SERP
>>> shouldnt
>>> be the first Exception on the stack ? I definitely would expect an
>>> Enhancer
>>> Exception saying whats wrong on an upper level. Something like
>>> "Enhancement
>>> failed on Class X" or something. The root cause would be of course
>>> the SERP
>>> exception.
>>>
>>> ---
>>> regards
>>> Marc Logemann
>>> http://www.logemann.org
>>> http://www.logentis.de
>>>
>>>
>>>
>>>
>>> Am 18.05.2009 um 16:29 schrieb Rick Curtis:
>>>
>>>
>>>
>>>> -Marc
>>>>
>>>> Any luck with the suggestion that David made?
>>>>
>>>>
>>>> David Beer-2 wrote:
>>>>
>>>>>
>>>>> On Sat, 16 May 2009 15:32:36 +0200
>>>>> Marc Logemann <li...@logemann.org> wrote:
>>>>>
>>>>> Hi Marc
>>>>>
>>>>> Can't seem that it is OpenJDK 6 related as I use it here for
>>>>> both my
>>>>> development and continous build system (hudson under tomcat).
>>>>>
>>>>> Are you using Ant or Maven with the build process. I have seen
>>>>> on lists
>>>>> that this can sometimes be a problem. Can you create a small
>>>>> project
>>>>> which has say just one class to enhance and see if that works
>>>>> through
>>>>> you build system. I am thinking that it may be a classpath or
>>>>> library
>>>>> problem.
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>> --
>>>> View this message in context:
>>>> http://n2.nabble.com/strange-JPA-Enhance-stack-tp2912505p2933425.html
>>>> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
Re: strange JPA Enhance stack
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Marc,
As Mike says, we could be a bit more friendly. By the way, SERP has
been very reliable so this hasn't been much of an issue to date.
Could you please file a JIRA so we don't forget about it?
Thanks,
Craig
On May 19, 2009, at 5:53 AM, Michael Dick wrote:
> Hi Marc,
>
> Sounds like an unchecked exception thrown by Serp and we could be a
> bit
> friendlier about how we handle it. At least dumping the classname
> that we're
> trying to load would help. Adding a try / catch might be helpful.
> Which
> version of OpenJPA are you using?
>
> My guess is that it is OpenJDK related and the compiled class is not
> matching Serp's expectation. I haven't seen this exception before
> though and
> I can't tell you why you're getting it.
>
> -mike
>
> On Tue, May 19, 2009 at 3:46 AM, Marc Logemann <li...@logemann.org>
> wrote:
>
>> David,
>>
>> no, have not done this. Its quite a hughe effort to create a
>> project from
>> scratch and deploy it to SCM and configure TeamCity to "compile/
>> test" it. I
>> still think its not a library issue because i use ivy within ANT
>> and the
>> build system resolves libs the same way as its done on each developer
>> machine. The stack doesnt look like a missing lib to me. And its
>> definitely
>> also not an ANT issue because i am using the same ANT Target on the
>> dev
>> machines.
>>
>> I hoped somebody who developed the enhancer can tell something
>> about the
>> stack. I mean something like "this problem can only occur under
>> this or that
>> condition".
>>
>> In any way... do we agree that an IllegalArgumentException in SERP
>> shouldnt
>> be the first Exception on the stack ? I definitely would expect an
>> Enhancer
>> Exception saying whats wrong on an upper level. Something like
>> "Enhancement
>> failed on Class X" or something. The root cause would be of course
>> the SERP
>> exception.
>>
>> ---
>> regards
>> Marc Logemann
>> http://www.logemann.org
>> http://www.logentis.de
>>
>>
>>
>>
>> Am 18.05.2009 um 16:29 schrieb Rick Curtis:
>>
>>
>>
>>> -Marc
>>>
>>> Any luck with the suggestion that David made?
>>>
>>>
>>> David Beer-2 wrote:
>>>
>>>>
>>>> On Sat, 16 May 2009 15:32:36 +0200
>>>> Marc Logemann <li...@logemann.org> wrote:
>>>>
>>>> Hi Marc
>>>>
>>>> Can't seem that it is OpenJDK 6 related as I use it here for both
>>>> my
>>>> development and continous build system (hudson under tomcat).
>>>>
>>>> Are you using Ant or Maven with the build process. I have seen on
>>>> lists
>>>> that this can sometimes be a problem. Can you create a small
>>>> project
>>>> which has say just one class to enhance and see if that works
>>>> through
>>>> you build system. I am thinking that it may be a classpath or
>>>> library
>>>> problem.
>>>>
>>>> David
>>>>
>>>>
>>>>
>>> --
>>> View this message in context:
>>> http://n2.nabble.com/strange-JPA-Enhance-stack-
>>> tp2912505p2933425.html
>>> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>>>
>>>
>>
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: strange JPA Enhance stack
Posted by Marc Logemann <li...@logemann.org>.
Mike,
i am using:
<dependency org="org.apache.openjpa" name="apache-openjpa" rev="1.2.0"
conf="default->default,sources,javadoc"/>
I am 80% sure its OpenJDK related because the rest of the story is
absolutely the same compared what our people do on their dev machines
but nobody uses OpenJDK 6 on the dev machines. So thats why we never
had problems with that before.
Now the big question is... how to solve :-) I could start patching the
Enhancer classes to get a little bit more info out of it. And i can
increase the Enhancer logging level and hope for more infos there.
Another opportunity would be to use the latest version of Serp and see
what goes on then. Unfortunately SERP seems to be a library which only
JPA folks use so i have not much hope that a newer version will fix it.
Will report back if i have some more infos.... Perhaps its worth a
JIRA, then we can log things. Its hard to track infos on maillists
over time.....
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 19.05.2009 um 14:53 schrieb Michael Dick:
> Hi Marc,
>
> Sounds like an unchecked exception thrown by Serp and we could be a
> bit
> friendlier about how we handle it. At least dumping the classname
> that we're
> trying to load would help. Adding a try / catch might be helpful.
> Which
> version of OpenJPA are you using?
>
> My guess is that it is OpenJDK related and the compiled class is not
> matching Serp's expectation. I haven't seen this exception before
> though and
> I can't tell you why you're getting it.
>
> -mike
>
> On Tue, May 19, 2009 at 3:46 AM, Marc Logemann <li...@logemann.org>
> wrote:
>
>> David,
>>
>> no, have not done this. Its quite a hughe effort to create a
>> project from
>> scratch and deploy it to SCM and configure TeamCity to "compile/
>> test" it. I
>> still think its not a library issue because i use ivy within ANT
>> and the
>> build system resolves libs the same way as its done on each developer
>> machine. The stack doesnt look like a missing lib to me. And its
>> definitely
>> also not an ANT issue because i am using the same ANT Target on the
>> dev
>> machines.
>>
>> I hoped somebody who developed the enhancer can tell something
>> about the
>> stack. I mean something like "this problem can only occur under
>> this or that
>> condition".
>>
>> In any way... do we agree that an IllegalArgumentException in SERP
>> shouldnt
>> be the first Exception on the stack ? I definitely would expect an
>> Enhancer
>> Exception saying whats wrong on an upper level. Something like
>> "Enhancement
>> failed on Class X" or something. The root cause would be of course
>> the SERP
>> exception.
>>
>> ---
>> regards
>> Marc Logemann
>> http://www.logemann.org
>> http://www.logentis.de
>>
>>
>>
>>
>> Am 18.05.2009 um 16:29 schrieb Rick Curtis:
>>
>>
>>
>>> -Marc
>>>
>>> Any luck with the suggestion that David made?
>>>
>>>
>>> David Beer-2 wrote:
>>>
>>>>
>>>> On Sat, 16 May 2009 15:32:36 +0200
>>>> Marc Logemann <li...@logemann.org> wrote:
>>>>
>>>> Hi Marc
>>>>
>>>> Can't seem that it is OpenJDK 6 related as I use it here for both
>>>> my
>>>> development and continous build system (hudson under tomcat).
>>>>
>>>> Are you using Ant or Maven with the build process. I have seen on
>>>> lists
>>>> that this can sometimes be a problem. Can you create a small
>>>> project
>>>> which has say just one class to enhance and see if that works
>>>> through
>>>> you build system. I am thinking that it may be a classpath or
>>>> library
>>>> problem.
>>>>
>>>> David
>>>>
>>>>
>>>>
>>> --
>>> View this message in context:
>>> http://n2.nabble.com/strange-JPA-Enhance-stack-
>>> tp2912505p2933425.html
>>> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>>>
>>>
>>
Re: strange JPA Enhance stack
Posted by Michael Dick <mi...@gmail.com>.
Hi Marc,
Sounds like an unchecked exception thrown by Serp and we could be a bit
friendlier about how we handle it. At least dumping the classname that we're
trying to load would help. Adding a try / catch might be helpful. Which
version of OpenJPA are you using?
My guess is that it is OpenJDK related and the compiled class is not
matching Serp's expectation. I haven't seen this exception before though and
I can't tell you why you're getting it.
-mike
On Tue, May 19, 2009 at 3:46 AM, Marc Logemann <li...@logemann.org> wrote:
> David,
>
> no, have not done this. Its quite a hughe effort to create a project from
> scratch and deploy it to SCM and configure TeamCity to "compile/test" it. I
> still think its not a library issue because i use ivy within ANT and the
> build system resolves libs the same way as its done on each developer
> machine. The stack doesnt look like a missing lib to me. And its definitely
> also not an ANT issue because i am using the same ANT Target on the dev
> machines.
>
> I hoped somebody who developed the enhancer can tell something about the
> stack. I mean something like "this problem can only occur under this or that
> condition".
>
> In any way... do we agree that an IllegalArgumentException in SERP shouldnt
> be the first Exception on the stack ? I definitely would expect an Enhancer
> Exception saying whats wrong on an upper level. Something like "Enhancement
> failed on Class X" or something. The root cause would be of course the SERP
> exception.
>
> ---
> regards
> Marc Logemann
> http://www.logemann.org
> http://www.logentis.de
>
>
>
>
> Am 18.05.2009 um 16:29 schrieb Rick Curtis:
>
>
>
>> -Marc
>>
>> Any luck with the suggestion that David made?
>>
>>
>> David Beer-2 wrote:
>>
>>>
>>> On Sat, 16 May 2009 15:32:36 +0200
>>> Marc Logemann <li...@logemann.org> wrote:
>>>
>>> Hi Marc
>>>
>>> Can't seem that it is OpenJDK 6 related as I use it here for both my
>>> development and continous build system (hudson under tomcat).
>>>
>>> Are you using Ant or Maven with the build process. I have seen on lists
>>> that this can sometimes be a problem. Can you create a small project
>>> which has say just one class to enhance and see if that works through
>>> you build system. I am thinking that it may be a classpath or library
>>> problem.
>>>
>>> David
>>>
>>>
>>>
>> --
>> View this message in context:
>> http://n2.nabble.com/strange-JPA-Enhance-stack-tp2912505p2933425.html
>> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>>
>>
>
Re: strange JPA Enhance stack
Posted by Marc Logemann <li...@logemann.org>.
David,
no, have not done this. Its quite a hughe effort to create a project
from scratch and deploy it to SCM and configure TeamCity to "compile/
test" it. I still think its not a library issue because i use ivy
within ANT and the build system resolves libs the same way as its done
on each developer machine. The stack doesnt look like a missing lib to
me. And its definitely also not an ANT issue because i am using the
same ANT Target on the dev machines.
I hoped somebody who developed the enhancer can tell something about
the stack. I mean something like "this problem can only occur under
this or that condition".
In any way... do we agree that an IllegalArgumentException in SERP
shouldnt be the first Exception on the stack ? I definitely would
expect an Enhancer Exception saying whats wrong on an upper level.
Something like "Enhancement failed on Class X" or something. The root
cause would be of course the SERP exception.
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 18.05.2009 um 16:29 schrieb Rick Curtis:
>
> -Marc
>
> Any luck with the suggestion that David made?
>
>
> David Beer-2 wrote:
>>
>> On Sat, 16 May 2009 15:32:36 +0200
>> Marc Logemann <li...@logemann.org> wrote:
>>
>> Hi Marc
>>
>> Can't seem that it is OpenJDK 6 related as I use it here for both my
>> development and continous build system (hudson under tomcat).
>>
>> Are you using Ant or Maven with the build process. I have seen on
>> lists
>> that this can sometimes be a problem. Can you create a small project
>> which has say just one class to enhance and see if that works through
>> you build system. I am thinking that it may be a classpath or library
>> problem.
>>
>> David
>>
>>
>
> --
> View this message in context: http://n2.nabble.com/strange-JPA-Enhance-stack-tp2912505p2933425.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
Re: strange JPA Enhance stack
Posted by Rick Curtis <cu...@gmail.com>.
-Marc
Any luck with the suggestion that David made?
David Beer-2 wrote:
>
> On Sat, 16 May 2009 15:32:36 +0200
> Marc Logemann <li...@logemann.org> wrote:
>
> Hi Marc
>
> Can't seem that it is OpenJDK 6 related as I use it here for both my
> development and continous build system (hudson under tomcat).
>
> Are you using Ant or Maven with the build process. I have seen on lists
> that this can sometimes be a problem. Can you create a small project
> which has say just one class to enhance and see if that works through
> you build system. I am thinking that it may be a classpath or library
> problem.
>
> David
>
>
--
View this message in context: http://n2.nabble.com/strange-JPA-Enhance-stack-tp2912505p2933425.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
Fwd: strange JPA Enhance stack
Posted by Marc Logemann <li...@logemann.org>.
Hi,
really noone who can explain the stack? I double checked that this is
not a SERP version problem but OpenJPA is the only library using SERP.
Looking at the SERP sourcecode reveals that it is more related to some
dynamic bytecode introspecition and not a version issue.
Why cant the PCEnhancer enhance the entitiy. I dont even know what
entity it is..... After all a very unlucky stack without much infos
for non-JPA developers.
[15:06:10]: [jpaenhance] openjpac
[15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
[15:06:11]: [openjpac] at serp.bytecode.Code.getInstruction(Code.java:
2131)
[15:06:11]: [openjpac] at serp.bytecode.Local.getEnd(Local.java:113)
[15:06:11]: [openjpac] at serp.bytecode.Local.updateTargets(Local.java:
155)
[15:06:11]: [openjpac] at
serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
[15:06:11]: [openjpac] at serp.bytecode.Code.read(Code.java:2031)
[15:06:11]: [openjpac] at
serp.bytecode.Attributes.readAttributes(Attributes.java:152)
[15:06:11]: [openjpac] at serp.bytecode.BCMember.read(BCMember.java:365)
[15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:123)
[15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:144)
[15:06:11]: [openjpac] at serp.bytecode.Project.loadClass(Project.java:
139)
[15:06:11]: [openjpac] at
org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
[15:06:11]: [openjpac] at
org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:89)
[15:06:11]: [openjpac] at
org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
[15:06:11]: [openjpac] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[15:06:11]: [openjpac] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[15:06:11]: [openjpac] at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57)
[15:06:11]: [openjpac] at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
43)
[15:06:11]: [openjpac] at java.lang.reflect.Method.invoke(Method.java:
616)
[15:06:11]: [openjpac] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
106)
[15:06:11]: [openjpac] at org.apache.tools.ant.Task.perform(Task.java:
348)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Target.execute(Target.java:357)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Target.performTasks(Target.java:385)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[15:06:11]: [openjpac] at
org
.apache
.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:
41)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Project.executeTargets(Project.java:1189)
[15:06:11]: [openjpac] at org.apache.tools.ant.Main.runBuild(Main.java:
758)
[15:06:11]: [openjpac] at org.apache.tools.ant.Main.startAnt(Main.java:
217)
[15:06:11]: [openjpac] at
org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
[15:06:11]: [openjpac] at
org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
[15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
[15:06:16]: Ant output:
at serp.bytecode.Local.updateTargets(Local.java:155)
at serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
at serp.bytecode.Code.read(Code.java:2031)
at serp.bytecode.Attributes.readAttributes(Attributes.java:152)
at serp.bytecode.BCMember.read(BCMember.java:365)
at serp.bytecode.BCClass.read(BCClass.java:123)
at serp.bytecode.BCClass.read(BCClass.java:144)
at serp.bytecode.Project.loadClass(Project.java:139)
at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
at org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:
89)
at org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:
172)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57)
at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at
org
.apache
.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:
41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
>
>
> Anfang der weitergeleiteten E-Mail:
>
>> Von: Marc Logemann <li...@logemann.org>
>> Datum: 17. Mai 2009 11:03:04 MESZ
>> An: users@openjpa.apache.org
>> Betreff: Re: strange JPA Enhance stack
>>
>> Just to clarify. I am using exactly same build file (ANT) with the
>> same task on the Ingegration server as on our development machines.
>> In fact the server checkouts the original source and does what
>> every developer does. Thats the idea of continous build server isnt
>> it? :-)
>>
>> The only difference i see is the JDK but it can be also something
>> else though.... The classpath (at least user classpath) should be
>> 100% the same because i am using ivy and again the server uses the
>> same ivy file than every developer.
>>
>> ---
>> regards
>> Marc Logemann
>> http://www.logemann.org
>> http://www.logentis.de
>>
>>
>>
>>
>> Am 16.05.2009 um 17:38 schrieb David Beer:
>>
>>> On Sat, 16 May 2009 15:32:36 +0200
>>> Marc Logemann <li...@logemann.org> wrote:
>>>
>>>> Upppps. Sorry. Wrong assumption: its not EMMA related. It must be
>>>> something else.... perhaps OpenJDK 6 related?
>>>
>>> Hi Marc
>>>
>>> Can't seem that it is OpenJDK 6 related as I use it here for both my
>>> development and continous build system (hudson under tomcat).
>>>
>>> Are you using Ant or Maven with the build process. I have seen on
>>> lists
>>> that this can sometimes be a problem. Can you create a small project
>>> which has say just one class to enhance and see if that works
>>> through
>>> you build system. I am thinking that it may be a classpath or
>>> library
>>> problem.
>>>
>>> David
>>
>
Re: Fwd: strange JPA Enhance stack
Posted by Dave Newton <ne...@yahoo.com>.
You may have posted this to the wrong mailing list.
Dave
Marc Logemann wrote:
> really noone who can explain the stack? I double checked that this is
> not a SERP version problem but OpenJPA is the only library using SERP.
> Looking at the SERP sourcecode reveals that it is more related to some
> dynamic bytecode introspecition and not a version issue.
>
> Why cant the PCEnhancer enhance the entitiy. I dont even know what
> entity it is..... After all a very unlucky stack without much infos for
> non-JPA developers.
>
>
>
>
> [15:06:10]: [jpaenhance] openjpac
> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
> [15:06:11]: [openjpac] at serp.bytecode.Code.getInstruction(Code.java:2131)
> [15:06:11]: [openjpac] at serp.bytecode.Local.getEnd(Local.java:113)
> [15:06:11]: [openjpac] at serp.bytecode.Local.updateTargets(Local.java:155)
> [15:06:11]: [openjpac] at
> serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
> [15:06:11]: [openjpac] at serp.bytecode.Code.read(Code.java:2031)
> [15:06:11]: [openjpac] at
> serp.bytecode.Attributes.readAttributes(Attributes.java:152)
> [15:06:11]: [openjpac] at serp.bytecode.BCMember.read(BCMember.java:365)
> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:123)
> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:144)
> [15:06:11]: [openjpac] at serp.bytecode.Project.loadClass(Project.java:139)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:89)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> [15:06:11]: [openjpac] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [15:06:11]: [openjpac] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> [15:06:11]: [openjpac] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> [15:06:11]: [openjpac] at java.lang.reflect.Method.invoke(Method.java:616)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [15:06:11]: [openjpac] at org.apache.tools.ant.Task.perform(Task.java:348)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Target.execute(Target.java:357)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Target.performTasks(Target.java:385)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> [15:06:11]: [openjpac] at org.apache.tools.ant.Main.runBuild(Main.java:758)
> [15:06:11]: [openjpac] at org.apache.tools.ant.Main.startAnt(Main.java:217)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
> [15:06:16]: Ant output:
> at serp.bytecode.Local.updateTargets(Local.java:155)
> at serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
> at serp.bytecode.Code.read(Code.java:2031)
> at serp.bytecode.Attributes.readAttributes(Attributes.java:152)
> at serp.bytecode.BCMember.read(BCMember.java:365)
> at serp.bytecode.BCClass.read(BCClass.java:123)
> at serp.bytecode.BCClass.read(BCClass.java:144)
> at serp.bytecode.Project.loadClass(Project.java:139)
> at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
> at org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:89)
> at org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>
> at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> at org.apache.tools.ant.Main.runBuild(Main.java:758)
> at org.apache.tools.ant.Main.startAnt(Main.java:217)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>
> ---
> regards
> Marc Logemann
> http://www.logemann.org
> http://www.logentis.de
>
>
>
>
> Anfang der weitergeleiteten E-Mail:
>
>> Von: Marc Logemann <li...@logemann.org>
>> Datum: 17. Mai 2009 11:03:04 MESZ
>> An: users@openjpa.apache.org
>> Betreff: Re: strange JPA Enhance stack
>>
>> Just to clarify. I am using exactly same build file (ANT) with the
>> same task on the Ingegration server as on our development machines. In
>> fact the server checkouts the original source and does what every
>> developer does. Thats the idea of continous build server isnt it? :-)
>>
>> The only difference i see is the JDK but it can be also something else
>> though.... The classpath (at least user classpath) should be 100% the
>> same because i am using ivy and again the server uses the same ivy
>> file than every developer.
>>
>> ---
>> regards
>> Marc Logemann
>> http://www.logemann.org
>> http://www.logentis.de
>>
>>
>>
>>
>> Am 16.05.2009 um 17:38 schrieb David Beer:
>>
>>> On Sat, 16 May 2009 15:32:36 +0200
>>> Marc Logemann <li...@logemann.org> wrote:
>>>
>>>> Upppps. Sorry. Wrong assumption: its not EMMA related. It must be
>>>> something else.... perhaps OpenJDK 6 related?
>>>
>>> Hi Marc
>>>
>>> Can't seem that it is OpenJDK 6 related as I use it here for both my
>>> development and continous build system (hudson under tomcat).
>>>
>>> Are you using Ant or Maven with the build process. I have seen on lists
>>> that this can sometimes be a problem. Can you create a small project
>>> which has say just one class to enhance and see if that works through
>>> you build system. I am thinking that it may be a classpath or library
>>> problem.
>>>
>>> David
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: strange JPA Enhance stack
Posted by Marc Logemann <li...@logemann.org>.
Sorry, wrong Maillist.
PLEASE IGNORE.
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 18.05.2009 um 16:20 schrieb Marc Logemann:
> really noone who can explain the stack? I double checked that this
> is not a SERP version problem but OpenJPA is the only library using
> SERP. Looking at the SERP sourcecode reveals that it is more related
> to some dynamic bytecode introspecition and not a version issue.
>
> Why cant the PCEnhancer enhance the entitiy. I dont even know what
> entity it is..... After all a very unlucky stack without much infos
> for non-JPA developers.
>
>
>
>
> [15:06:10]: [jpaenhance] openjpac
> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
> [15:06:11]: [openjpac] at
> serp.bytecode.Code.getInstruction(Code.java:2131)
> [15:06:11]: [openjpac] at serp.bytecode.Local.getEnd(Local.java:113)
> [15:06:11]: [openjpac] at
> serp.bytecode.Local.updateTargets(Local.java:155)
> [15:06:11]: [openjpac] at
> serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
> [15:06:11]: [openjpac] at serp.bytecode.Code.read(Code.java:2031)
> [15:06:11]: [openjpac] at
> serp.bytecode.Attributes.readAttributes(Attributes.java:152)
> [15:06:11]: [openjpac] at serp.bytecode.BCMember.read(BCMember.java:
> 365)
> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:123)
> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:144)
> [15:06:11]: [openjpac] at
> serp.bytecode.Project.loadClass(Project.java:139)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:
> 89)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> [15:06:11]: [openjpac] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [15:06:11]: [openjpac] at
> sun
> .reflect
> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [15:06:11]: [openjpac] at
> sun
> .reflect
> .DelegatingMethodAccessorImpl
> .invoke(DelegatingMethodAccessorImpl.java:43)
> [15:06:11]: [openjpac] at
> java.lang.reflect.Method.invoke(Method.java:616)
> [15:06:11]: [openjpac] at
> org
> .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
> 106)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Task.perform(Task.java:348)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Target.execute(Target.java:357)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Target.performTasks(Target.java:385)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [15:06:11]: [openjpac] at
> org
> .apache
> .tools
> .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Main.runBuild(Main.java:758)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Main.startAnt(Main.java:217)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
> [15:06:16]: Ant output:
> at serp.bytecode.Local.updateTargets(Local.java:155)
> at serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
> at serp.bytecode.Code.read(Code.java:2031)
> at serp.bytecode.Attributes.readAttributes(Attributes.java:152)
> at serp.bytecode.BCMember.read(BCMember.java:365)
> at serp.bytecode.BCClass.read(BCClass.java:123)
> at serp.bytecode.BCClass.read(BCClass.java:144)
> at serp.bytecode.Project.loadClass(Project.java:139)
> at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
> at
> org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:
> 89)
> at org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:
> 172)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:
> 288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun
> .reflect
> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun
> .reflect
> .DelegatingMethodAccessorImpl
> .invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org
> .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
> 106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:
> 1337)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> at
> org
> .apache
> .tools
> .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> at org.apache.tools.ant.Main.runBuild(Main.java:758)
> at org.apache.tools.ant.Main.startAnt(Main.java:217)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>
> ---
> regards
> Marc Logemann
> http://www.logemann.org
> http://www.logentis.de
>
>
>
>
> Anfang der weitergeleiteten E-Mail:
>
>> Von: Marc Logemann <li...@logemann.org>
>> Datum: 17. Mai 2009 11:03:04 MESZ
>> An: users@openjpa.apache.org
>> Betreff: Re: strange JPA Enhance stack
>>
>> Just to clarify. I am using exactly same build file (ANT) with the
>> same task on the Ingegration server as on our development machines.
>> In fact the server checkouts the original source and does what
>> every developer does. Thats the idea of continous build server isnt
>> it? :-)
>>
>> The only difference i see is the JDK but it can be also something
>> else though.... The classpath (at least user classpath) should be
>> 100% the same because i am using ivy and again the server uses the
>> same ivy file than every developer.
>>
>> ---
>> regards
>> Marc Logemann
>> http://www.logemann.org
>> http://www.logentis.de
>>
>>
>>
>>
>> Am 16.05.2009 um 17:38 schrieb David Beer:
>>
>>> On Sat, 16 May 2009 15:32:36 +0200
>>> Marc Logemann <li...@logemann.org> wrote:
>>>
>>>> Upppps. Sorry. Wrong assumption: its not EMMA related. It must be
>>>> something else.... perhaps OpenJDK 6 related?
>>>
>>> Hi Marc
>>>
>>> Can't seem that it is OpenJDK 6 related as I use it here for both my
>>> development and continous build system (hudson under tomcat).
>>>
>>> Are you using Ant or Maven with the build process. I have seen on
>>> lists
>>> that this can sometimes be a problem. Can you create a small project
>>> which has say just one class to enhance and see if that works
>>> through
>>> you build system. I am thinking that it may be a classpath or
>>> library
>>> problem.
>>>
>>> David
>>
>
Fwd: strange JPA Enhance stack
Posted by Marc Logemann <li...@logemann.org>.
really noone who can explain the stack? I double checked that this is
not a SERP version problem but OpenJPA is the only library using SERP.
Looking at the SERP sourcecode reveals that it is more related to some
dynamic bytecode introspecition and not a version issue.
Why cant the PCEnhancer enhance the entitiy. I dont even know what
entity it is..... After all a very unlucky stack without much infos
for non-JPA developers.
[15:06:10]: [jpaenhance] openjpac
[15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
[15:06:11]: [openjpac] at serp.bytecode.Code.getInstruction(Code.java:
2131)
[15:06:11]: [openjpac] at serp.bytecode.Local.getEnd(Local.java:113)
[15:06:11]: [openjpac] at serp.bytecode.Local.updateTargets(Local.java:
155)
[15:06:11]: [openjpac] at
serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
[15:06:11]: [openjpac] at serp.bytecode.Code.read(Code.java:2031)
[15:06:11]: [openjpac] at
serp.bytecode.Attributes.readAttributes(Attributes.java:152)
[15:06:11]: [openjpac] at serp.bytecode.BCMember.read(BCMember.java:365)
[15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:123)
[15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:144)
[15:06:11]: [openjpac] at serp.bytecode.Project.loadClass(Project.java:
139)
[15:06:11]: [openjpac] at
org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
[15:06:11]: [openjpac] at
org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:89)
[15:06:11]: [openjpac] at
org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
[15:06:11]: [openjpac] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[15:06:11]: [openjpac] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[15:06:11]: [openjpac] at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57)
[15:06:11]: [openjpac] at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
43)
[15:06:11]: [openjpac] at java.lang.reflect.Method.invoke(Method.java:
616)
[15:06:11]: [openjpac] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
106)
[15:06:11]: [openjpac] at org.apache.tools.ant.Task.perform(Task.java:
348)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Target.execute(Target.java:357)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Target.performTasks(Target.java:385)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[15:06:11]: [openjpac] at
org
.apache
.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:
41)
[15:06:11]: [openjpac] at
org.apache.tools.ant.Project.executeTargets(Project.java:1189)
[15:06:11]: [openjpac] at org.apache.tools.ant.Main.runBuild(Main.java:
758)
[15:06:11]: [openjpac] at org.apache.tools.ant.Main.startAnt(Main.java:
217)
[15:06:11]: [openjpac] at
org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
[15:06:11]: [openjpac] at
org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
[15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
[15:06:16]: Ant output:
at serp.bytecode.Local.updateTargets(Local.java:155)
at serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
at serp.bytecode.Code.read(Code.java:2031)
at serp.bytecode.Attributes.readAttributes(Attributes.java:152)
at serp.bytecode.BCMember.read(BCMember.java:365)
at serp.bytecode.BCClass.read(BCClass.java:123)
at serp.bytecode.BCClass.read(BCClass.java:144)
at serp.bytecode.Project.loadClass(Project.java:139)
at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
at org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:
89)
at org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:
172)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
57)
at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at
org
.apache
.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:
41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Anfang der weitergeleiteten E-Mail:
> Von: Marc Logemann <li...@logemann.org>
> Datum: 17. Mai 2009 11:03:04 MESZ
> An: users@openjpa.apache.org
> Betreff: Re: strange JPA Enhance stack
>
> Just to clarify. I am using exactly same build file (ANT) with the
> same task on the Ingegration server as on our development machines.
> In fact the server checkouts the original source and does what every
> developer does. Thats the idea of continous build server isnt it? :-)
>
> The only difference i see is the JDK but it can be also something
> else though.... The classpath (at least user classpath) should be
> 100% the same because i am using ivy and again the server uses the
> same ivy file than every developer.
>
> ---
> regards
> Marc Logemann
> http://www.logemann.org
> http://www.logentis.de
>
>
>
>
> Am 16.05.2009 um 17:38 schrieb David Beer:
>
>> On Sat, 16 May 2009 15:32:36 +0200
>> Marc Logemann <li...@logemann.org> wrote:
>>
>>> Upppps. Sorry. Wrong assumption: its not EMMA related. It must be
>>> something else.... perhaps OpenJDK 6 related?
>>
>> Hi Marc
>>
>> Can't seem that it is OpenJDK 6 related as I use it here for both my
>> development and continous build system (hudson under tomcat).
>>
>> Are you using Ant or Maven with the build process. I have seen on
>> lists
>> that this can sometimes be a problem. Can you create a small project
>> which has say just one class to enhance and see if that works through
>> you build system. I am thinking that it may be a classpath or library
>> problem.
>>
>> David
>
Re: strange JPA Enhance stack
Posted by Marc Logemann <li...@logemann.org>.
Just to clarify. I am using exactly same build file (ANT) with the
same task on the Ingegration server as on our development machines. In
fact the server checkouts the original source and does what every
developer does. Thats the idea of continous build server isnt it? :-)
The only difference i see is the JDK but it can be also something else
though.... The classpath (at least user classpath) should be 100% the
same because i am using ivy and again the server uses the same ivy
file than every developer.
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 16.05.2009 um 17:38 schrieb David Beer:
> On Sat, 16 May 2009 15:32:36 +0200
> Marc Logemann <li...@logemann.org> wrote:
>
>> Upppps. Sorry. Wrong assumption: its not EMMA related. It must be
>> something else.... perhaps OpenJDK 6 related?
>
> Hi Marc
>
> Can't seem that it is OpenJDK 6 related as I use it here for both my
> development and continous build system (hudson under tomcat).
>
> Are you using Ant or Maven with the build process. I have seen on
> lists
> that this can sometimes be a problem. Can you create a small project
> which has say just one class to enhance and see if that works through
> you build system. I am thinking that it may be a classpath or library
> problem.
>
> David
Re: strange JPA Enhance stack
Posted by David Beer <da...@googlemail.com>.
On Sat, 16 May 2009 15:32:36 +0200
Marc Logemann <li...@logemann.org> wrote:
> Upppps. Sorry. Wrong assumption: its not EMMA related. It must be
> something else.... perhaps OpenJDK 6 related?
Hi Marc
Can't seem that it is OpenJDK 6 related as I use it here for both my
development and continous build system (hudson under tomcat).
Are you using Ant or Maven with the build process. I have seen on lists
that this can sometimes be a problem. Can you create a small project
which has say just one class to enhance and see if that works through
you build system. I am thinking that it may be a classpath or library
problem.
David
Re: strange JPA Enhance stack
Posted by Marc Logemann <li...@logemann.org>.
Upppps. Sorry. Wrong assumption: its not EMMA related. It must be
something else.... perhaps OpenJDK 6 related?
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 16.05.2009 um 15:17 schrieb Marc Logemann:
> Ok guys, i give you a hint: It does work when i disable EMMA
> instrumentation. Why is it a problem when i let the EMMA instrument
> the classes? I wanted to use it because of code coverage statistics
> and its supported out of the box by TeamCity.
>
> ---
> regards
> Marc Logemann
> http://www.logemann.org
> http://www.logentis.de
>
>
>
>
> Am 16.05.2009 um 15:09 schrieb Marc Logemann:
>
>> Hi,
>>
>> today we installed our Continous build system (TeamCity) and we
>> tried to run our first automated build on Linux with OpenJDK 6.
>> Even though our build works on all client computers it fails with
>> the same (ivy resolved) build path on OpenJDK 6 wih the following
>> stack. Perhaps someone can comment on this:
>>
>> [15:06:10]: [jpaenhance] openjpac
>> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
>> [15:06:11]: [openjpac] at
>> serp.bytecode.Code.getInstruction(Code.java:2131)
>> [15:06:11]: [openjpac] at serp.bytecode.Local.getEnd(Local.java:113)
>> [15:06:11]: [openjpac] at
>> serp.bytecode.Local.updateTargets(Local.java:155)
>> [15:06:11]: [openjpac] at
>> serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
>> [15:06:11]: [openjpac] at serp.bytecode.Code.read(Code.java:2031)
>> [15:06:11]: [openjpac] at
>> serp.bytecode.Attributes.readAttributes(Attributes.java:152)
>> [15:06:11]: [openjpac] at serp.bytecode.BCMember.read(BCMember.java:
>> 365)
>> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:
>> 123)
>> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:
>> 144)
>> [15:06:11]: [openjpac] at
>> serp.bytecode.Project.loadClass(Project.java:139)
>> [15:06:11]: [openjpac] at
>> org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
>> [15:06:11]: [openjpac] at
>> org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:
>> 89)
>> [15:06:11]: [openjpac] at
>> org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:
>> 172)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
>> [15:06:11]: [openjpac] at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> [15:06:11]: [openjpac] at
>> sun
>> .reflect
>> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> [15:06:11]: [openjpac] at
>> sun
>> .reflect
>> .DelegatingMethodAccessorImpl
>> .invoke(DelegatingMethodAccessorImpl.java:43)
>> [15:06:11]: [openjpac] at
>> java.lang.reflect.Method.invoke(Method.java:616)
>> [15:06:11]: [openjpac] at
>> org
>> .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
>> 106)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.Task.perform(Task.java:348)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.Target.execute(Target.java:357)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.Target.performTasks(Target.java:385)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
>> [15:06:11]: [openjpac] at
>> org
>> .apache
>> .tools
>> .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.Project.executeTargets(Project.java:1189)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.Main.runBuild(Main.java:758)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.Main.startAnt(Main.java:217)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
>> [15:06:11]: [openjpac] at
>> org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
>> [15:06:16]: Ant output:
>> at serp.bytecode.Local.updateTargets(Local.java:155)
>> at serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
>> at serp.bytecode.Code.read(Code.java:2031)
>> at serp.bytecode.Attributes.readAttributes(Attributes.java:152)
>> at serp.bytecode.BCMember.read(BCMember.java:365)
>> at serp.bytecode.BCClass.read(BCClass.java:123)
>> at serp.bytecode.BCClass.read(BCClass.java:144)
>> at serp.bytecode.Project.loadClass(Project.java:139)
>> at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
>> at
>> org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:
>> 89)
>> at
>> org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:
>> 172)
>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:
>> 288)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun
>> .reflect
>> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun
>> .reflect
>> .DelegatingMethodAccessorImpl
>> .invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:616)
>> at
>> org
>> .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
>> 106)
>> at org.apache.tools.ant.Task.perform(Task.java:348)
>> at org.apache.tools.ant.Target.execute(Target.java:357)
>> at org.apache.tools.ant.Target.performTasks(Target.java:385)
>> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:
>> 1337)
>> at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
>> at
>> org
>> .apache
>> .tools
>> .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
>> at org.apache.tools.ant.Main.runBuild(Main.java:758)
>> at org.apache.tools.ant.Main.startAnt(Main.java:217)
>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>>
>>
>>
>> ---
>> regards
>> Marc Logemann
>> http://www.logemann.org
>> http://www.logentis.de
>>
>>
>>
>>
>
Re: strange JPA Enhance stack
Posted by Marc Logemann <li...@logemann.org>.
Ok guys, i give you a hint: It does work when i disable EMMA
instrumentation. Why is it a problem when i let the EMMA instrument
the classes? I wanted to use it because of code coverage statistics
and its supported out of the box by TeamCity.
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 16.05.2009 um 15:09 schrieb Marc Logemann:
> Hi,
>
> today we installed our Continous build system (TeamCity) and we
> tried to run our first automated build on Linux with OpenJDK 6. Even
> though our build works on all client computers it fails with the
> same (ivy resolved) build path on OpenJDK 6 wih the following stack.
> Perhaps someone can comment on this:
>
> [15:06:10]: [jpaenhance] openjpac
> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
> [15:06:11]: [openjpac] at
> serp.bytecode.Code.getInstruction(Code.java:2131)
> [15:06:11]: [openjpac] at serp.bytecode.Local.getEnd(Local.java:113)
> [15:06:11]: [openjpac] at
> serp.bytecode.Local.updateTargets(Local.java:155)
> [15:06:11]: [openjpac] at
> serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
> [15:06:11]: [openjpac] at serp.bytecode.Code.read(Code.java:2031)
> [15:06:11]: [openjpac] at
> serp.bytecode.Attributes.readAttributes(Attributes.java:152)
> [15:06:11]: [openjpac] at serp.bytecode.BCMember.read(BCMember.java:
> 365)
> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:123)
> [15:06:11]: [openjpac] at serp.bytecode.BCClass.read(BCClass.java:144)
> [15:06:11]: [openjpac] at
> serp.bytecode.Project.loadClass(Project.java:139)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:
> 89)
> [15:06:11]: [openjpac] at
> org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
> [15:06:11]: [openjpac] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [15:06:11]: [openjpac] at
> sun
> .reflect
> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [15:06:11]: [openjpac] at
> sun
> .reflect
> .DelegatingMethodAccessorImpl
> .invoke(DelegatingMethodAccessorImpl.java:43)
> [15:06:11]: [openjpac] at
> java.lang.reflect.Method.invoke(Method.java:616)
> [15:06:11]: [openjpac] at
> org
> .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
> 106)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Task.perform(Task.java:348)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Target.execute(Target.java:357)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Target.performTasks(Target.java:385)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> [15:06:11]: [openjpac] at
> org
> .apache
> .tools
> .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Main.runBuild(Main.java:758)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.Main.startAnt(Main.java:217)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> [15:06:11]: [openjpac] at
> org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
> [15:06:11]: [openjpac] java.lang.IllegalArgumentException: 5
> [15:06:16]: Ant output:
> at serp.bytecode.Local.updateTargets(Local.java:155)
> at serp.bytecode.LocalTable.updateTargets(LocalTable.java:163)
> at serp.bytecode.Code.read(Code.java:2031)
> at serp.bytecode.Attributes.readAttributes(Attributes.java:152)
> at serp.bytecode.BCMember.read(BCMember.java:365)
> at serp.bytecode.BCClass.read(BCClass.java:123)
> at serp.bytecode.BCClass.read(BCClass.java:144)
> at serp.bytecode.Project.loadClass(Project.java:139)
> at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4491)
> at
> org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:
> 89)
> at org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:
> 172)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:
> 288)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun
> .reflect
> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun
> .reflect
> .DelegatingMethodAccessorImpl
> .invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org
> .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:
> 106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:357)
> at org.apache.tools.ant.Target.performTasks(Target.java:385)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:
> 1337)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
> at
> org
> .apache
> .tools
> .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
> at org.apache.tools.ant.Main.runBuild(Main.java:758)
> at org.apache.tools.ant.Main.startAnt(Main.java:217)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
>
>
>
> ---
> regards
> Marc Logemann
> http://www.logemann.org
> http://www.logentis.de
>
>
>
>