December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6057) Error message when adding a messaging's grouping-handler

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-6057: -------------------------------- Summary: Error message when adding a messaging's grouping-handler Key: AS7-6057 URL: https://issues.jboss.org/browse/AS7-6057 Project: Application Server 7 Issue Type: Feature Request Reporter: Jeff Mesnil Fix For: 7.2.0.Alpha1 When a grouping-handler is added to the hornetq-server section, the AS7 server starts with an error: 15:18:14,521 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 52) JBAS014613: Operation ("add") failed - address: ([ ("subsystem" => "messaging"), ("hornetq-server" => "default"), ("grouping-handler" => "group-handler-test") ]) - failure description: "JBAS011637: A child resource of type grouping-handler already exists; the messaging subsystem only allows a single resource of type grouping-handler" The error is misleading as there is only 1 grouping-handler and the server runs fine. -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] (JASSIST-182) update ClassFileWriter for Java 7 invokedynamic

by Shigeru Chiba (JIRA)

Shigeru Chiba created JASSIST-182: ------------------------------------- Summary: update ClassFileWriter for Java 7 invokedynamic Key: JASSIST-182 URL: https://issues.jboss.org/browse/JASSIST-182 Project: Javassist Issue Type: Feature Request Affects Versions: 3.17.0-GA Reporter: Shigeru Chiba Assignee: Shigeru Chiba Priority: Minor (Originally reported by Grigori Goronzy) With Javassist 3.17, the ClassFile, ConstPool, etc. classes gained support for the invokedynamic JVM opcode and associated constant pool data. However, ClassFileWriter wasn't updated, and it isn't possible, for instance, to add an InvokeDynamic_info with a ConstPoolWriter. The attached patch fixes this in the most straight-forward manner. I haven't tested it well, but the code is so simple that it is unlikely to have any bugs. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] (JASSIST-180) Javassist fails to load class from jar (com.tivoli.pd.jutil.PDPermResource_cs )

by ami tabak (JIRA)

ami tabak created JASSIST-180: --------------------------------- Summary: Javassist fails to load class from jar (com.tivoli.pd.jutil.PDPermResource_cs ) Key: JASSIST-180 URL: https://issues.jboss.org/browse/JASSIST-180 Project: Javassist Issue Type: Bug Affects Versions: 3.17.0-GA Reporter: ami tabak Assignee: Shigeru Chiba Trying to load class com.tivoli.mts.util.PDPermResource_cs which has only java dependencies. (based on JAD) Getting the following error at instantiation. 1. Not sure if its related to the 3.17.0 or just 3.17.1 code drops. 2. Not sure why its looking to the second class com.tivoli.pd.jutil.PDPermResource_cs rather than to what I'm trying to load. java.lang.InstantiationException: javassist.CtClassType at java.lang.Class.newInstance0(Class.java:357) at java.lang.Class.newInstance(Class.java:325) at com.optier.bug.report.WASTest.wasTestCase(WASTest.java:42) at com.optier.bug.report.WASTest.main(WASTest.java:18) Exception in thread "main" java.lang.RuntimeException: cannot find com.tivoli.mts.util.PDPermResource_cs: com.tivoli.pd.jutil.PDPermResource_cs found in com/tivoli/mts/util/PDPermResource_cs.class at javassist.CtClassType.getClassFile2(CtClassType.java:194) at javassist.CtClassType.makeFieldCache(CtClassType.java:848) at javassist.CtClassType.getMembers(CtClassType.java:839) at javassist.CtClassType.getDeclaredBehaviors(CtClassType.java:987) at com.optier.bug.report.WASTest.wasTestCase(WASTest.java:50) at com.optier.bug.report.WASTest.main(WASTest.java:18) -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] (AS7-6063) Deadlock in Module FallbackClassLoader

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6063?page=com.atlassian.jira.plugin.s... ] Thomas Diesler edited comment on AS7-6063 at 12/3/12 3:50 AM: -------------------------------------------------------------- Does this issue still exist in the latest [jboss-as/master|https://github.com/jbossas/jboss-as] build? was (Author: thomas.diesler): Does this issue still exist in the latest [jboss-as/master](https://github.com/jbossas/jboss-as) build? > Deadlock in Module FallbackClassLoader > -------------------------------------- > > Key: AS7-6063 > URL: https://issues.jboss.org/browse/AS7-6063 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Reporter: Steve Reed > Assignee: Thomas Diesler > Attachments: jboss-dead-lock.txt > > > Actually the version is 2.0.1.final - jbosgi-framework-core-2.0.1.Final.jar > Commit reference for JBOSS AS :- https://github.com/jbossas/jboss-as/commit/ed2bc551a55ec6a8167a8657cbb5d8... > During start up of JBOSS AS7.0 two GeminiBlueprintExtender Threads deadlock, and services in the JBOSS OSGI container are not started. > The deadlock appears to be concerned with a Module FallbackLoader, which acquires a lock during a call to loadClassLocal() and then proceeds to use an alternate Module to load the class, if this results in the alternate Module using it's FallbackLoader to load a class or resource, then it must also acquire a lock first. Obviously if two or more threads are attempting this, then a dead lock is possible. > I will attach the thread dump to this issue as supporting evidence. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6063) Deadlock in Module FallbackClassLoader

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6063?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on AS7-6063: ------------------------------------- Does this issue still exist in the latest [jboss-as/master](https://github.com/jbossas/jboss-as) build? > Deadlock in Module FallbackClassLoader > -------------------------------------- > > Key: AS7-6063 > URL: https://issues.jboss.org/browse/AS7-6063 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Reporter: Steve Reed > Assignee: Thomas Diesler > Attachments: jboss-dead-lock.txt > > > Actually the version is 2.0.1.final - jbosgi-framework-core-2.0.1.Final.jar > Commit reference for JBOSS AS :- https://github.com/jbossas/jboss-as/commit/ed2bc551a55ec6a8167a8657cbb5d8... > During start up of JBOSS AS7.0 two GeminiBlueprintExtender Threads deadlock, and services in the JBOSS OSGI container are not started. > The deadlock appears to be concerned with a Module FallbackLoader, which acquires a lock during a call to loadClassLocal() and then proceeds to use an alternate Module to load the class, if this results in the alternate Module using it's FallbackLoader to load a class or resource, then it must also acquire a lock first. Obviously if two or more threads are attempting this, then a dead lock is possible. > I will attach the thread dump to this issue as supporting evidence. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6063) Deadlock in Module FallbackClassLoader

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6063?page=com.atlassian.jira.plugin.s... ] Thomas Diesler moved JBOSGI-622 to AS7-6063: -------------------------------------------- Project: Application Server 7 (was: JBoss OSGi) Key: AS7-6063 (was: JBOSGI-622) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: JBossOSGi 2.0.0) Component/s: OSGi (was: Blueprint) Security: (was: Public) > Deadlock in Module FallbackClassLoader > -------------------------------------- > > Key: AS7-6063 > URL: https://issues.jboss.org/browse/AS7-6063 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Reporter: Steve Reed > Assignee: Thomas Diesler > Attachments: jboss-dead-lock.txt > > > Actually the version is 2.0.1.final - jbosgi-framework-core-2.0.1.Final.jar > Commit reference for JBOSS AS :- https://github.com/jbossas/jboss-as/commit/ed2bc551a55ec6a8167a8657cbb5d8... > During start up of JBOSS AS7.0 two GeminiBlueprintExtender Threads deadlock, and services in the JBOSS OSGI container are not started. > The deadlock appears to be concerned with a Module FallbackLoader, which acquires a lock during a call to loadClassLocal() and then proceeds to use an alternate Module to load the class, if this results in the alternate Module using it's FallbackLoader to load a class or resource, then it must also acquire a lock first. Obviously if two or more threads are attempting this, then a dead lock is possible. > I will attach the thread dump to this issue as supporting evidence. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6055) Support multiple <entry> elements for <pooled-connection-factory>

by Justin Bertram (JIRA)

Justin Bertram created AS7-6055: ----------------------------------- Summary: Support multiple <entry> elements for <pooled-connection-factory> Key: AS7-6055 URL: https://issues.jboss.org/browse/AS7-6055 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.1.Final Reporter: Justin Bertram Assignee: Jeff Mesnil Currently a <pooled-connection-factory> can only be bound to a single JNDI location because it only supports one <entry> despite the fact that the schema allows multiple <entry> elements. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7882) Wrong provider code base for security provider included in packed ear

by Petr H (JIRA)

Wrong provider code base for security provider included in packed ear --------------------------------------------------------------------- Key: JBAS-7882 URL: https://jira.jboss.org/jira/browse/JBAS-7882 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: VFS Affects Versions: JBossAS-6.0.0.M2, JBossAS-5.1.0.GA Environment: Any OS, JDK 5 and 6, JBoss AS 5.1.0 and 6.0.0.M2 Reporter: Petr H We've got applications which uses the IAIK JCE provider (http://jce.iaik.tugraz.at/sic/Products/Core-Crypto-Toolkits/JCA-JCE) whose library is included directly in our application. On JBoss AS 5 and later, we can't use this provider as usually. The new VFS mechanism seems to break the path determination to the IAIK provider library (needed to determine provider code base) - it still points into the ear/war structure inside the server deploy directory but as all this is packed into one ear file, the provider verification.fails because of unsigned ear/war and thus the following exception is thrown: 2010-04-01 15:04:20,890 ERROR [STDERR] (http-0.0.0.0-8180-1) java.lang.SecurityException: JCE cannot authenticate the provider IAIK 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.Cipher.getInstance(DashoA13*..) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.Cipher.getInstance(DashoA13*..) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at iaik.test.ControllerServlet.service(ControllerServlet.java:123) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 2010-04-01 15:04:20,893 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:905) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:592) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2036) 2010-04-01 15:04:20,894 ERROR [STDERR] (http-0.0.0.0-8180-1) at java.lang.Thread.run(Thread.java:619) 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) Caused by: java.util.jar.JarException: Cannot parse jar:file:/opt/jboss-5.1.0.GA/server/test1/deploy/IAIKTest.ear!/IAIKTestWeb.war 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.SunJCE_c.a(DashoA13*..) 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.SunJCE_b.b(DashoA13*..) 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) at javax.crypto.SunJCE_b.a(DashoA13*..) 2010-04-01 15:04:20,895 ERROR [STDERR] (http-0.0.0.0-8180-1) ... 24 more This works when one of tho three mentioned workarounds is used. The most interesting of course is the third workaround for which the code base corectly points to the temporary IAIK library instance in the java.io.tmpdir: 2010-04-01 15:09:51,291 INFO [STDOUT] (http-0.0.0.0-8180-1) Provider code base: file:/tmp/nestedjar2481829661547119990.tmp I'll attach a simple testcase ear (IAIKTest.ear) which contains an evaluation version of IAIK provider library (thanks for permission to the IAIK authors) and a simple servlet (including source) which demonstrates the problem. All you need to do is to have the unrestricted JCE policy files installed in your JRE and then just put the IAIKTest.ear into the deploy directory, start the JBoss instance and access the test servlet URL in browser, for example: http://localhost:8080/IAIKTestWeb/ControllerServlet On init (which happens on start) it will register the IAIK provider On service (after you access it in browser) it will attempt to get some cipher instance and here it fails. I'll also attach two log files covering the problem: - server-default.log with default server setup where the issue occurs - server-forceVfsJar.log with jboss.vfs.forceVfsJar=true where the issue doesn't occur Also I think this is more generic problem because we had similar issues, where some jar or resource location was pointing to the packed ear/war structure inside the deploy directory instead of those VFS temporary locations, with our own code (when attemting to obtain full path) and had to perform some modifications in order to make it working. The same set of workarounds could resolve these issues as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

17
51
0 / 0

[JBoss JIRA] (AS7-5293) Align domain.sh and standalone.sh logic about adding -server

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5293: ------------------------------------- Summary: Align domain.sh and standalone.sh logic about adding -server Key: AS7-5293 URL: https://issues.jboss.org/browse/AS7-5293 Project: Application Server 7 Issue Type: Sub-task Components: Scripts Reporter: Brian Stansberry Fix For: 7.2.0.CR1, Open To Community The domain.sh script has a number of JVM vendor checks it uses to decide whether to add -server to the jvm launch command. In standalone.sh it's simpler; it simply checks for OSX. I can't see any reason this logic should be significantly different between the two cases, either the JVM vendor checks are needed in both or they aren't needed in either. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] (JASSIST-181) java.lang.RuntimeException: multiple descriptors? with javac 1.7

by Oleh Faizulin (JIRA)

Oleh Faizulin created JASSIST-181: ------------------------------------- Summary: java.lang.RuntimeException: multiple descriptors? with javac 1.7 Key: JASSIST-181 URL: https://issues.jboss.org/browse/JASSIST-181 Project: Javassist Issue Type: Bug Affects Versions: 3.17.0-GA Environment: Windows 7 x64, java version "1.7.0_05" Java(TM) SE Runtime Environment (build 1.7.0_05-b06) Java HotSpot(TM) Client VM (build 23.1-b03, mixed mode, sharing) Eclipse Juno Service Release 1 Reporter: Oleh Faizulin Assignee: Shigeru Chiba Attachments: javassist_test.zip Hi, When I try to run attached code compiled with javac I recive the following error: {noformat} Exception in thread "main" java.lang.RuntimeException: multiple descriptors?: Ljavassist_test/A<TT;>.B; at javassist.bytecode.Descriptor.toClassName(Descriptor.java:108) at javassist.bytecode.annotation.ClassMemberValue.getValue(ClassMemberValue.java:100) at javassist.bytecode.annotation.ClassMemberValue.toString(ClassMemberValue.java:117) at java.lang.String.valueOf(String.java:2902) at java.lang.StringBuffer.append(StringBuffer.java:232) at javassist.bytecode.annotation.Annotation.toString(Annotation.java:223) at javassist.bytecode.annotation.AnnotationImpl.invoke(AnnotationImpl.java:137) at $Proxy0.toString(Unknown Source) at java.lang.String.valueOf(String.java:2902) at java.io.PrintStream.println(PrintStream.java:821) at javassist_test.Test.main(Test.java:21) 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:601) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) {noformat} -- 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, 5 months

1
6
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 December 2012