[JBoss JIRA] Created: (AS7-1190) Spring Loading not documented
by Jim Tyrrell (JIRA)
Spring Loading not documented
-----------------------------
Key: AS7-1190
URL: https://issues.jboss.org/browse/AS7-1190
Project: Application Server 7
Issue Type: Feature Request
Reporter: Jim Tyrrell
Since Jason in the video I watched mentioned that class loading isolation was a setting and I have a customer provided Spring/hibernate war file provided, I would like to explore these settings, but I can not seem to find where they are documented. I would think since it was mentioned in the webinar this is a blocker.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[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
12 years, 11 months
[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
12 years, 11 months
[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
12 years, 11 months