November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JASSIST-179) Diff functionality for java classes and bundles (jars, ears, sars etc)

by Sviatoslav Abramenkov (JIRA)

Sviatoslav Abramenkov created JASSIST-179: --------------------------------------------- Summary: Diff functionality for java classes and bundles (jars, ears, sars etc) Key: JASSIST-179 URL: https://issues.jboss.org/browse/JASSIST-179 Project: Javassist Issue Type: Enhancement Affects Versions: 3.17.1-GA, 3.18.0-GA Reporter: Sviatoslav Abramenkov Assignee: Shigeru Chiba Fix For: 3.18.0-GA -- 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

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-3713) JBoss Web module.xml declares clustering sso as optional, when it is instead required

by Tristan Tarrant (JIRA)

Tristan Tarrant created AS7-3713: ------------------------------------ Summary: JBoss Web module.xml declares clustering sso as optional, when it is instead required Key: AS7-3713 URL: https://issues.jboss.org/browse/AS7-3713 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.Final Reporter: Tristan Tarrant Assignee: Remy Maucherat org/jboss/as/web/main/module.xml contains <module name="org.jboss.as.clustering.web.spi" optional="true"/>, but the clustering classes are imported directly by WebVirtualHostAdd.java, so the optional is kind of required :) -- 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

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (AS7-5962) jaxrs subsystem pulls in javax.xml.bind.api module for every deployment

by Kyle Lape (JIRA)

Kyle Lape created AS7-5962: ------------------------------ Summary: jaxrs subsystem pulls in javax.xml.bind.api module for every deployment Key: AS7-5962 URL: https://issues.jboss.org/browse/AS7-5962 Project: Application Server 7 Issue Type: Bug Components: Class Loading, REST Affects Versions: 7.2.0.Alpha1 Reporter: Kyle Lape Assignee: Kyle Lape Priority: Minor The jaxrs subsystem automatically pulls in the JAXB API module for every single deployment, even if they don't have a JAX-RS component in them. This is normally not noticed since {{javax.xml.bind.api}} is already added to the deployment via {{javaee.api}}, but you want to include your own version of JAXB in your deployment, then you will need to exclude {{javaee.api}}, which is expected. But it's not expected to have to exclude the jaxrs subsystem, too. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5961) FreeBSD native support

by Alexander Yerenkow (JIRA)

Alexander Yerenkow created AS7-5961: --------------------------------------- Summary: FreeBSD native support Key: AS7-5961 URL: https://issues.jboss.org/browse/AS7-5961 Project: Application Server 7 Issue Type: Enhancement Components: Web Affects Versions: 7.1.3.Final (EAP) Reporter: Alexander Yerenkow Assignee: Remy Maucherat There's no native .so for FreeBSD JBoss variant. Could you provide it? -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1547) Problem starting jboss 7 with Java Service Wrapper

by andrei povodyrev (JIRA)

Problem starting jboss 7 with Java Service Wrapper -------------------------------------------------- Key: AS7-1547 URL: https://issues.jboss.org/browse/AS7-1547 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Environment: Red Hat, Windows 7 Reporter: andrei povodyrev Assignee: David Lloyd Fix For: Open To Community Problem starting jboss 7 with Java Service Wrapper We tried to upgrade Java Service Wrapper (JSW) configuration from Jboss 5 to Jboss 7. Jboss fails to start with these messages WARNING: Failed to load the specified logmodule org.jboss.logmanager:main followed by IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") Software: Jboss-as-7.0.0-Final wrapper-windows-x86-64-3.5.10-st (Java Service Wrapper win 64 distribution) Issue: org.jboss.modules.Main generates the warning as LogManager is already initialized to java.util.logging.LogManager by the Wrapper. With jboss 7 org.jboss.logmanager.LogManager is required. Per LogManager design only one instance may exist in jvm. jboss 7 assume that it is the first in line to initialize java.util.logger.LogManager. Wrapper is the one who inits LogManager first (thus triggering primordial configuration initialization). Jboss then fails to start since it requiresits own logging implementation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
5
0 / 0

[JBoss JIRA] (AS7-5959) Get rid of CNFs and NCDFs from clustering TS runs

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-5959: ----------------------------------- Summary: Get rid of CNFs and NCDFs from clustering TS runs Key: AS7-5959 URL: https://issues.jboss.org/browse/AS7-5959 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor Fix For: 7.2.0.Alpha1 [0m[0m12:53:07,775 INFO [org.jboss.weld.ClassLoading] (MSC service thread 1-3) WELD-000119 Not generating any bean definitions from org.jboss.as.test.clustering.ClusterHttpClientUtil because of underlying class loading error [0m[0m12:53:07,776 INFO [org.jboss.weld.ClassLoading] (MSC service thread 1-3) catching: org.jboss.weld.resources.spi.ResourceLoadingException: Error loading class org.jboss.as.test.clustering.ClusterHttpClientUtil at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:167) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.bootstrap.BeanDeployer.loadWeldClass(BeanDeployer.java:116) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:79) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:135) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) [jboss-as-weld-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) [jboss-as-weld-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31] Caused by: java.lang.NoClassDefFoundError: org/apache/http/client/methods/HttpUriRequest at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.6.0_31] at java.lang.Class.privateGetDeclaredFields(Class.java:2291) [rt.jar:1.6.0_31] at java.lang.Class.getDeclaredFields(Class.java:1743) [rt.jar:1.6.0_31] at org.jboss.weld.util.reflection.SecureReflections$4.work(SecureReflections.java:105) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.util.reflection.SecureReflections$4.work(SecureReflections.java:102) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.util.reflection.SecureReflectionAccess.runAndWrap(SecureReflectionAccess.java:63) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.util.reflection.SecureReflections.getDeclaredFields(SecureReflections.java:102) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.introspector.jlr.WeldClassImpl.<init>(WeldClassImpl.java:155) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:121) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:59) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:50) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:163) [weld-core-1.1.10.Final.jar:2012-10-12 10:00] ... 12 more Caused by: java.lang.ClassNotFoundException: org.apache.http.client.methods.HttpUriRequest from [Module "deployment.stateful.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA] ... 30 more -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5956) Http Service TCK testLongRegistrationName() failing

by David Bosschaert (JIRA)

David Bosschaert created AS7-5956: ------------------------------------- Summary: Http Service TCK testLongRegistrationName() failing Key: AS7-5956 URL: https://issues.jboss.org/browse/AS7-5956 Project: Application Server 7 Issue Type: Sub-task Components: OSGi, Web Affects Versions: 7.2.0.Alpha1 Reporter: David Bosschaert Assignee: Thomas Diesler The OSGi HTTP Service TCK test testLongRegistrationName() fails with the following exception: java.io.FileNotFoundException: http://localhost:8080/abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxy... Apparently there is an issue with long registration names. -- 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

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (AS7-5957) Http Service TCK testBundleStopping() failing

by David Bosschaert (JIRA)

David Bosschaert created AS7-5957: ------------------------------------- Summary: Http Service TCK testBundleStopping() failing Key: AS7-5957 URL: https://issues.jboss.org/browse/AS7-5957 Project: Application Server 7 Issue Type: Sub-task Components: OSGi Affects Versions: 7.2.0.Alpha1 Reporter: David Bosschaert Assignee: David Bosschaert The OSGi HTTP Service TCK test testBundleStopping() fails with the following exception: {code}org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: tb1:4.2.0 at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:110) at org.jboss.as.osgi.service.BundleLifecycleIntegration.start(BundleLifecycleIntegration.java:181) at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:292) at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:228) at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:522) at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:127) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.LinkageError: loader constraint violation: when resolving interface method "org.osgi.service.http.HttpService.registerServlet(Ljava/lang/String;Ljavax/servlet/Servlet;Ljava/util/Dictionary;Lorg/osgi/service/http/HttpContext;)V" the class loader (instance of org/jboss/osgi/framework/internal/HostBundleClassLoader) of the current class, org/osgi/test/cases/http/tb1/HttpTestBundle2, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/osgi/service/http/HttpService, have different Class objects for the type javax/servlet/Servlet used in the signature at org.osgi.test.cases.http.tb1.HttpTestBundle2.start(HttpTestBundle2.java:30) at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:84) ... 10 more{code} Seems like a resolution error, it could be related to how the TCK is set up. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5788) HttpService authentication/authorisation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5788: ----------------------------------- Summary: HttpService authentication/authorisation Key: AS7-5788 URL: https://issues.jboss.org/browse/AS7-5788 Project: Application Server 7 Issue Type: Sub-task Components: OSGi, Web Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.2.0.CR1 -- 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

12 years, 1 month

2
1
0 / 0

[JBoss JIRA] (AS7-5944) FreeBSD Generic compile problems

by Alexis Yerenkow (JIRA)

Alexis Yerenkow created AS7-5944: ------------------------------------ Summary: FreeBSD Generic compile problems Key: AS7-5944 URL: https://issues.jboss.org/browse/AS7-5944 Project: Application Server 7 Issue Type: Feature Request Components: Build System Affects Versions: 7.1.3.Final (EAP) Environment: FreeBSD 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Reporter: Alexis Yerenkow Assignee: Paul Gier [ERROR] //jboss-as-7.1.1.Final/connector/src/main/java/org/jboss/as/connector/util/JCAValidatorFactory.java:[95,41] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found :<T>javax.validation.bootstrap.ProviderSpecificBootstrap<T> required: java.lang.Object This easily fixed with changinng Validation.byProvider(HibernateValidator.class) To: Validation.<HibernateValidatorConfiguration,HibernateValidator>byProvider(HibernateValidator.class) This should be done in few more places: jboss-as-7.1.3.Final/ee/src/main/java/org/jboss/as/ee/beanvalidation/LazyValidatorFactory.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

12 years, 1 month

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012