July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1036) Arquillian Managed Container does not honor configured ports

by Karel Piwko (JIRA)

Arquillian Managed Container does not honor configured ports ------------------------------------------------------------ Key: AS7-1036 URL: https://issues.jboss.org/browse/AS7-1036 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Karel Piwko When starting a managed container, following configuration is not used by Arquillian: {code} <container qualifier="container" default="true"> <configuration> <property name="jbossHome">target/jbossas-2</property> <property name="managementPort">19999</property> <property name="jmxPort">1190</property> <property name="httpPort">8180</property> <property name="startupTimeoutInSeconds">180</property> </configuration>  <protocol type="jmx-as7"> <configuration> <property name="executionType">REMOTE</property> </configuration> </protocol> </container> {code} The standalone container is always started on default ports, e.g. 9999, 1099, 8180. The ports are defined in standalone.xml and it seems difficult to change them without touching the file. See http://community.jboss.org/thread/168140 for related question. This makes customization of the test runs with managed containers difficult and for clusters even more difficult. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1011) JBoss AS lifecycle controlling tests

by Karel Piwko (JIRA)

JBoss AS lifecycle controlling tests ------------------------------------ Key: AS7-1011 URL: https://issues.jboss.org/browse/AS7-1011 Project: Application Server 7 Issue Type: Task Components: Test Suite Affects Versions: 7.0.0.Beta3 Reporter: Karel Piwko Assignee: Karel Piwko Create a test suite that uses Arquillian to control JBoss AS 7 lifecycle in a more precise way, that is: * DomainClient specific controller * Asynchronous start, stop * Manual start after modifying a domain configuration * Monitoring of container and deployment status * Forced / programmable kill (cleanup to be investigated here though) Some of the features would require modifications of Arquillian. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1018) Allow TM to run in local only recover mode

by Scott Stark (JIRA)

Allow TM to run in local only recover mode ------------------------------------------ Key: AS7-1018 URL: https://issues.jboss.org/browse/AS7-1018 Project: Application Server 7 Issue Type: Feature Request Components: Transactions Reporter: Scott Stark Assignee: Scott Stark When running under constrained environments (either resources, and or selinux), it would be good if the transaction manager could run in a local only recover mode that did not require any network interfaces to be brought up. I have an example prototype of this change in my https://github.com/starksm64/jboss-as/tree/tmwork branch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-696) Console in standalone mode: deploy / undeploy / enable / disable

by Stan Silvert (JIRA)

Console in standalone mode: deploy / undeploy / enable / disable ---------------------------------------------------------------- Key: AS7-696 URL: https://issues.jboss.org/browse/AS7-696 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.0.0.Beta3 Reporter: Stan Silvert Assignee: Stan Silvert -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
3
0 / 0

[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

13 years, 2 months

3
3
0 / 0

[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

13 years, 2 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

13 years, 2 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

13 years, 2 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

13 years, 2 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

13 years, 2 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011