[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
13 years, 5 months
[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
13 years, 5 months
[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
13 years, 5 months
[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
13 years, 5 months
[JBoss JIRA] (AS7-5954) IIOP tests fail on IBM JDK due to an XSLT error
by Ivo Studensky (JIRA)
Ivo Studensky created AS7-5954:
----------------------------------
Summary: IIOP tests fail on IBM JDK due to an XSLT error
Key: AS7-5954
URL: https://issues.jboss.org/browse/AS7-5954
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1
Environment: IBM JDK 6
IBM JDK 7
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
IIOP tests from AS testsuite fail when running on IBM JDK due to an XSLT error in the enableJTS.xsl template file. The current template creates an invalid configuration file on IBM JDK which causes that server cannot parse the configuration and fails to start up.
Affected tests:
{noformat}
org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase
org.jboss.as.test.iiop.transaction.TransactionIIOPInvocationTestCase
org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingTestCase
{noformat}
I am preparing a pull request with the fix.
--
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
[JBoss JIRA] (AS7-5955) Cannot deploy OSGi fragment as part of an EAR
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5955:
-----------------------------------
Summary: Cannot deploy OSGi fragment as part of an EAR
Key: AS7-5955
URL: https://issues.jboss.org/browse/AS7-5955
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
{code}
15:16:16,156 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "good-fragment.ear"
15:16:16,167 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "good-bundle.jar"
15:16:16,168 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "good-fragment.jar"
15:16:16,185 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: good-bundle.jar:0.0.0
15:16:16,189 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: good-fragment.jar:0.0.0
15:16:16,197 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015970: Defer FIRST_MODULE_USE for good-fragment.ear making it LAZY
15:16:16,206 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015970: Defer FIRST_MODULE_USE for good-bundle.jar making it PASSIVE
15:16:16,438 ERROR [org.jboss.as.server] (OSGi ModelControllerClient Thread) JBAS015870: Deploy of deployment "good-fragment.ear" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"good-fragment.ear\".FIRST_MODULE_USE is missing [jboss.module.spec.service.\"deployment.good-fragment.ear.good-fragment.jar\".main]"]}
{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, 5 months
[JBoss JIRA] (SECURITY-693) The attribute 'roleAttributeIsDN' is not in the list of allowed attributes for the LdapExtLoginModule
by Darran Lofthouse (JIRA)
Darran Lofthouse created SECURITY-693:
-----------------------------------------
Summary: The attribute 'roleAttributeIsDN' is not in the list of allowed attributes for the LdapExtLoginModule
Key: SECURITY-693
URL: https://issues.jboss.org/browse/SECURITY-693
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: PicketBox
Affects Versions: PicketBox_4_0_12.Final
Reporter: Darran Lofthouse
Assignee: Anil Saldhana
The following warning is logged as a result of this attribute being missing: -
04:11:16,582 WARN [org.jboss.security] (http-/127.0.0.1:8080-2) PBOX000234: Invalid or misspelled module option: roleAttributeIsDN
Probably not a major issue but this warning may lead users to believe their configuration is incorectly wrong when trying to diagnose a problem.
--
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