April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6924) Cannot resolve package requirement on javax.xml.stream.events

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on AS7-6924: ------------------------------------- Yes, thats good enough > Cannot resolve package requirement on javax.xml.stream.events > ------------------------------------------------------------- > > Key: AS7-6924 > URL: https://issues.jboss.org/browse/AS7-6924 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, XML Frameworks > Affects Versions: 8.0.0.Alpha1 > Reporter: Aaron Whiteside > Assignee: Thomas Diesler > > {code} > 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]] > 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6924) Cannot resolve package requirement on javax.xml.stream.events

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened AS7-6924: --------------------------------- > Cannot resolve package requirement on javax.xml.stream.events > ------------------------------------------------------------- > > Key: AS7-6924 > URL: https://issues.jboss.org/browse/AS7-6924 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, XML Frameworks > Affects Versions: 8.0.0.Alpha1 > Reporter: Aaron Whiteside > Assignee: Thomas Diesler > > {code} > 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]] > 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6925) ignore CNFE when scanning for entity classes in deployment

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6925?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6925: ----------------------------------- I looked at my code change and I don't think it will introduce any leaking of classes (since the not found class isn't loaded). Thanks for trying the change out! > ignore CNFE when scanning for entity classes in deployment > ---------------------------------------------------------- > > Key: AS7-6925 > URL: https://issues.jboss.org/browse/AS7-6925 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha1 > > Attachments: cnfe.jar > > > Deployments may contain non-entity classes that can not be loaded (see above forum reference for example). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6924) Cannot resolve package requirement on javax.xml.stream.events

by Aaron Whiteside (JIRA)

[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ] Aaron Whiteside commented on AS7-6924: -------------------------------------- I can reproduce the issue by deploying this single jar... http://ebr.springsource.com/repository/app/bundle/version/download?name=o... I think that is a pretty good test case? > Cannot resolve package requirement on javax.xml.stream.events > ------------------------------------------------------------- > > Key: AS7-6924 > URL: https://issues.jboss.org/browse/AS7-6924 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, XML Frameworks > Affects Versions: 8.0.0.Alpha1 > Reporter: Aaron Whiteside > Assignee: Thomas Diesler > > {code} > 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]] > 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-148) StackOverflowError when using $sig and $class in call to static method

by Shigeru Chiba (JIRA)

[ https://issues.jboss.org/browse/JASSIST-148?page=com.atlassian.jira.plugi... ] Shigeru Chiba closed JASSIST-148. --------------------------------- Resolution: Won't Fix because no response from the reporter. > StackOverflowError when using $sig and $class in call to static method > ---------------------------------------------------------------------- > > Key: JASSIST-148 > URL: https://issues.jboss.org/browse/JASSIST-148 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.15.0-GA > Environment: Runtime Enviroment: > Java SE 6 Update 30 (64 bit) > also reproduced with: > Java SE 7 Update 2 (64 bit) > Compiler: > Eclipse Indigo (Version: 3.7.1, Build id: M20110909-1335). > Operating System > Windows 7 Professional (64 bit) > CPU: > Intel Core i7 860 (2,8 GHz) > Reporter: Wanja Gayk > Assignee: Shigeru Chiba > > Using $sig or $class as method parameter in "insertBefore"-expressions throws a StackOverflowError if the target is a static method. > Calling nonstatic methods works like expected. > Stack/Log-Traces: > When using $sig: > instrumenting class: de/plush/brix/instrumentation/Main (995 bytes) > instrumenting class: javassist/runtime/Desc (3280 bytes) > Exception in thread "main" java.lang.StackOverflowError > at javassist.runtime.Desc.getParams(Desc.java) > at javassist.runtime.Desc.getParams(Desc.java) > at javassist.runtime.Desc.getParams(Desc.java) > [...] > When using $class: > instrumenting class: de/plush/brix/instrumentation/Main (995 bytes) > instrumenting class: javassist/runtime/Desc (3280 bytes) > Exception in thread "main" java.lang.StackOverflowError > at javassist.runtime.Desc.getClazz(Desc.java) > at javassist.runtime.Desc.getClazz(Desc.java) > [...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6924) Cannot resolve package requirement on javax.xml.stream.events

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on AS7-6924: ------------------------------------- The best way to tackle this is to start with working solution (i.e. the testcase from that PR) and modify it such that it fails. Then we can understand better what makes the functionality break. This issue is about the general usage of javax.xml.stream from an osgi bundle. I'd say this is verified to work properly within the scope of that test. > Cannot resolve package requirement on javax.xml.stream.events > ------------------------------------------------------------- > > Key: AS7-6924 > URL: https://issues.jboss.org/browse/AS7-6924 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, XML Frameworks > Affects Versions: 8.0.0.Alpha1 > Reporter: Aaron Whiteside > Assignee: Thomas Diesler > > {code} > 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]] > 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-78) Provide a way to detect that an instrumented method's code length exceed the 64KB limit

by Shigeru Chiba (JIRA)

[ https://issues.jboss.org/browse/JASSIST-78?page=com.atlassian.jira.plugin... ] Shigeru Chiba closed JASSIST-78. -------------------------------- Resolution: Won't Fix > Provide a way to detect that an instrumented method's code length exceed the 64KB limit > --------------------------------------------------------------------------------------- > > Key: JASSIST-78 > URL: https://issues.jboss.org/browse/JASSIST-78 > Project: Javassist > Issue Type: Bug > Environment: latest javassist from cvs head > Reporter: Yanic Inghelbrecht > Assignee: Shigeru Chiba > Priority: Minor > > When using call site instrumentation, for example with ExprEditor#edit(MethodCall), it is possible to produce a class definition with a method whose class definition exceed the allowed code length. When such a class is actually loaded, it results in a java.lang.VerifyError (Illegal target of jump or branch). > I have encountered some (degenerate) parsing methods whose code length is around 7000 before instrumentation and grows to over 64KB+ after instrumentation. It all depends on the amount of instrumented code that gets added of course (which is pretty minimal in my case, a try/catch block and an extra call). But other people have run into the same issue when instrumenting code that was generated for JSP pages, so it isn't all that exotic to encounter this in the wild. > The problem is that there is no way to detect that the resulting code will break the 64KB limit (afaik). > I've tried using > getMethodInfo().getCodeAttribute().length() > for the instrumented CtBehavior, but that number can not be used for this purpose. For example, one method reported a length of 7169 before instrumentation, and 55317 after instrumentation which is < 64KB. Yet it fails with a VerifyError when loaded into the JVM. > I've also tried > getMethodInfo().getCodeAttribute().getCodeLength() > but that method reports even smaller numbers (resp. 4861 and 47769 for the same case as above) and is not suited for this purpose either. > --- > So this RFE asks to add some way to detect that a method will break the 64KB limit after it has been instrumented but before it is loaded into the jvm. Because there is a (clumsy) work-around, I've given this a minor priority. But I do think it would be a useful addition to javassist's feature set and allow users to write more robust and efficient instrumentation code. > Thanks in advance for considering it Chiba. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-193) assignments without explicit cast cause VM errors

by Shigeru Chiba (JIRA)

[ https://issues.jboss.org/browse/JASSIST-193?page=com.atlassian.jira.plugi... ] Shigeru Chiba closed JASSIST-193. --------------------------------- Resolution: Rejected This is a feature. See JASSIST-173. > assignments without explicit cast cause VM errors > ------------------------------------------------- > > Key: JASSIST-193 > URL: https://issues.jboss.org/browse/JASSIST-193 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.17.1-GA > Environment: 1.6 jdk, but not limited to > Reporter: Pawel Veselov > Assignee: Shigeru Chiba > Attachments: JA1.java, JA2.java > > > javassist will compile code when assignment is done without an explicit cast, e.g.: > Object p; > String s = p; > However, assignment receptacle is not checked for type, causing VM errors when byte code is verified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6924) Cannot resolve package requirement on javax.xml.stream.events

by Aaron Whiteside (JIRA)

[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ] Aaron Whiteside commented on AS7-6924: -------------------------------------- Well something obviously isn't working for me, is there any more debug I can provide you? As I mentioned before I could provide the bundles that produce the issues for me..? > Cannot resolve package requirement on javax.xml.stream.events > ------------------------------------------------------------- > > Key: AS7-6924 > URL: https://issues.jboss.org/browse/AS7-6924 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi, XML Frameworks > Affects Versions: 8.0.0.Alpha1 > Reporter: Aaron Whiteside > Assignee: Thomas Diesler > > {code} > 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]] > 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6925) ignore CNFE when scanning for entity classes in deployment

by Daniel Wehrle (JIRA)

[ https://issues.jboss.org/browse/AS7-6925?page=com.atlassian.jira.plugin.s... ] Daniel Wehrle commented on AS7-6925: ------------------------------------ Hi Scott, i took your changes from GitHub and put it in 7.2.0. If the warnings occurs i get also a PermGenSpace-OOM. If I increase the PermGenSpace to 384M (earlier 256M) I get no warnings and no OOM. > ignore CNFE when scanning for entity classes in deployment > ---------------------------------------------------------- > > Key: AS7-6925 > URL: https://issues.jboss.org/browse/AS7-6925 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha1 > > Attachments: cnfe.jar > > > Deployments may contain non-entity classes that can not be loaded (see above forum reference for example). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013