July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-839) adding org.hibernate to META-INF/MANIFEST.MF as "Dependencies: org.hibernate" doesn't cause cause org.slf4j to be loaded

by Darrin Mison (JIRA)

adding org.hibernate to META-INF/MANIFEST.MF as "Dependencies: org.hibernate" doesn't cause cause org.slf4j to be loaded ------------------------------------------------------------------------------------------------------------------------ Key: AS7-839 URL: https://issues.jboss.org/browse/AS7-839 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Darrin Mison Assignee: Jason Greene hmmm, just logged AS7-836 and noticed that even though I've added "Dependencies: org.hiberate" to my apps META-INF/MANIFEST.MF it seems that org.slf4j doesn't get loaded even though it is a listed as a dependent module in modules/org/hibernate/main/module.xml. Getting a "java.lang.ClassNotFoundException: org.slf4j.LoggerFactory" when my app is invoked. Note: I'm not manually calling slf4j, I think it's getting called by hibernate. {quote} Caused by: java.lang.ExceptionInInitializerError at com.redhat.ecs.topic.webservice.HibernateUtil.buildSessionFactory(HibernateUtil.java:18) [classes:] at com.redhat.ecs.topic.webservice.HibernateUtil.<clinit>(HibernateUtil.java:8) [classes:] at com.redhat.ecs.topic.webservice.TopicManager.getTopic(TopicManager.java:40) [classes:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) [resteasy-jaxrs-2.1.0.GA.jar:] at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:252) [resteasy-jaxrs-2.1.0.GA.jar:] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:217) [resteasy-jaxrs-2.1.0.GA.jar:] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:206) [resteasy-jaxrs-2.1.0.GA.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:503) [resteasy-jaxrs-2.1.0.GA.jar:] ... 18 more Caused by: java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory at org.hibernate.cfg.Configuration.<clinit>(Configuration.java:196) [hibernate-core-3.6.1.Final.jar:3.6.1.Final] at com.redhat.ecs.topic.webservice.HibernateUtil.buildSessionFactory(HibernateUtil.java:13) [classes:] ... 29 more Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory from [Module "org.hibernate:main" from local module loader @63238bd2 (roots: /Applications/Java/EAP6/jboss-7.0.0.Beta3/modules)] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:184) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:329) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100) [:1.0.0.Beta17] ... 31 more {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
11
0 / 0

[JBoss JIRA] Created: (AS7-689) standalone server: If I shutdown the server, the client gets a IOException->ExecutionException->EOFException("Connection closed")

by Andre Dietisheim (JIRA)

standalone server: If I shutdown the server, the client gets a IOException->ExecutionException->EOFException("Connection closed") --------------------------------------------------------------------------------------------------------------------------------- Key: AS7-689 URL: https://issues.jboss.org/browse/AS7-689 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Beta3 Reporter: Andre Dietisheim Assignee: Jason Greene If I shutdown the server by the following operation: {code} ModelNode request = new ModelNode(); request.get(OP).set(SHUTDOWN); {code} the client throws a IOException because it's connection was closed. The actual nesting is the following: IOException->ExecutionException->EOFException("Connection closed") -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
6
0 / 0

[JBoss JIRA] Created: (AS7-674) using -help or -version parameters when starting the server in domain mode causes an infinite loop

by Darrin Mison (JIRA)

using -help or -version parameters when starting the server in domain mode causes an infinite loop -------------------------------------------------------------------------------------------------- Key: AS7-674 URL: https://issues.jboss.org/browse/AS7-674 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.0.Beta3 Reporter: Darrin Mison Assignee: Jason Greene Running domain.sh with the -help or -version parameters appears to put the server into a loop ./domain.sh -help * starts the host controller and passes the -help parameter, * HC displays the help and then exits, * and the reaper restarts the HC with the same parameters and the same thing happens again {quote} dhcp-1-216:bin tabby$ ./domain.sh -version ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /Users/tabby/JBoss_Installs/EAP6/jboss-7.0.0.Beta3 JAVA: java JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 ========================================================================= 15:47:03,546 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.0.Beta17 15:47:03,778 INFO [org.jboss.as.process.Host Controller.status] (main) Starting process 'Host Controller' [Host Controller] 15:47:04,291 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.0.Beta17 [Host Controller] 15:47:04,534 INFO [stdout] (main) JBoss Application Server 7.0.0.Beta3 15:47:04,558 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) Process 'Host Controller' finished with an exit status of 1 15:47:04,559 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) Starting process 'Host Controller' [Host Controller] 15:47:05,071 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.0.Beta17 [Host Controller] 15:47:05,340 INFO [stdout] (main) JBoss Application Server 7.0.0.Beta3 15:47:05,373 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) Process 'Host Controller' finished with an exit status of 1 15:47:05,373 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) Starting process 'Host Controller' {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-586) Rename "build" directory to "dist" in the AS build

by Paul Gier (JIRA)

Rename "build" directory to "dist" in the AS build -------------------------------------------------- Key: JBBUILD-586 URL: https://jira.jboss.org/jira/browse/JBBUILD-586 Project: JBoss Build System Issue Type: Task Components: Maven Builds Reporter: Paul Gier Assignee: Paul Gier Fix For: Maven Build Support 2010 The directory "build" should be renamed to "dist" in the AS build. Clebert suggested that this would make it more clear for new users. -- 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

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-9284) Create AS API TestSuite

by Andrew Rubinger (JIRA)

Create AS API TestSuite ----------------------- Key: JBAS-9284 URL: https://issues.jboss.org/browse/JBAS-9284 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Rubinger To be used to test the AS7 APIs as seen from a user perspective. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9285) Create AS Specification TestSuite

by Andrew Rubinger (JIRA)

Create AS Specification TestSuite --------------------------------- Key: JBAS-9285 URL: https://issues.jboss.org/browse/JBAS-9285 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Rubinger Used to prove EE functions are working as contracted, with no extra dependencies allowed upon the compilation ClassPath for the test deployments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9258) It is possible to create a bad Queue

by Heiko Rupp (JIRA)

It is possible to create a bad Queue ------------------------------------ Key: JBAS-9258 URL: https://issues.jboss.org/browse/JBAS-9258 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Heiko Rupp [localhost:9999 messaging] pwd /profile=default/subsystem=messaging [localhost:9999 messaging] ./queue=newQ:add(queue-name=newQ) returns success [localhost:9999 messaging] ls queue=newQ [localhost:9999 messaging] :read-children-names(child-type=queue) { "outcome" => "success", "result" => ["newQ"], "compensating-operation" => undefined } Now shut down the domain and try to restart - this fails [Host Controller] 20:39:42,134 ERROR [org.jboss.as.domain.controller] (MSC service thread 1-4) failed to start domain controller: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:120) [Host Controller] at org.jboss.as.domain.controller.DomainControllerService.loadLocalDomainModel(DomainControllerService.java:186) [Host Controller] at org.jboss.as.domain.controller.DomainControllerService.startMasterDomainController(DomainControllerService.java:138) [Host Controller] at org.jboss.as.domain.controller.DomainControllerService.start(DomainControllerService.java:92) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] [Host Controller] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] [Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[242,21] [Host Controller] Message: Missing required attribute(s): address Respective content in the domain.xml is <queues> <queue name="newQ"/> </queues> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-7999) Investigate making HASingleton failover "stopOldMaster" RPC synchronous

by Brian Stansberry (JIRA)

Investigate making HASingleton failover "stopOldMaster" RPC synchronous ----------------------------------------------------------------------- Key: JBAS-7999 URL: https://jira.jboss.org/jira/browse/JBAS-7999 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry When a node becomes master, it tells any previous master to stop. That call is async, probably because long ago this was done on a JGroups up thread and making a sync call from that up thread would hang. This is no longer done on an up thread, so investigate adding a config option to allow is call to go synchronous, thus ensuring the old master is fully stopped before new one starts. -- 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

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1348) Weld breaks RichFaces 4

by Juergen Zimmermann (JIRA)

Weld breaks RichFaces 4 ----------------------- Key: AS7-1348 URL: https://issues.jboss.org/browse/AS7-1348 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.0.0.Final Environment: Jenkins build 1402 Reporter: Juergen Zimmermann Assignee: Stuart Douglas I'm migrating an EAR from JBoss 6 to 7. The Web module is based on RichFaces 4 and Weld. However, I'm getting the stacktrace below. I'll attach a testcase. Stacktrace: javax.el.ELException: Cannot convert testcase.PasswordGroup of type class java.lang.String to class [Ljava.lang.Class; at org.apache.el.lang.ELSupport.coerceToType(ELSupport.java:470) at org.apache.el.ExpressionFactoryImpl.coerceToType(ExpressionFactoryImpl.java:46) at org.jboss.weld.util.el.ForwardingExpressionFactory.coerceToType(ForwardingExpressionFactory.java:37) at com.sun.faces.facelets.tag.BeanPropertyTagRule$LiteralPropertyMetadata.applyMetadata(BeanPropertyTagRule.java:88) at com.sun.faces.facelets.tag.MetadataImpl.applyMetadata(MetadataImpl.java:81) at javax.faces.view.facelets.MetaTagHandler.setAttributes(MetaTagHandler.java:129) at javax.faces.view.facelets.DelegatingMetaTagHandler.setAttributes(DelegatingMetaTagHandler.java:102) at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.setAttributes(BehaviorsAddingComponentHandlerWrapper.java:115) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.doNewComponentActions(ComponentTagHandlerDelegateImpl.java:402) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:159) at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:55) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184) at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98) at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137) at org.richfaces.view.facelets.html.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:55) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:184) at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98) at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:98) at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:82) at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:152) at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:744) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:100) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:893) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:626) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2054) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (JBAS-7221) Support recovery scenarios

by Jesper Pedersen (JIRA)

Support recovery scenarios -------------------------- Key: JBAS-7221 URL: https://jira.jboss.org/jira/browse/JBAS-7221 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Jesper Pedersen Assignee: Emanuel Muckenhuber Priority: Blocker Fix For: JBossAS-6.0.0.Alpha1 This is a container task for adding recovery support into the AS build. -- 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

14 years, 8 months

7
12
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 July 2011