April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4451) ServerSetupTasks don't get cleaned up if there was a problem

by Kabir Khan (JIRA)

Kabir Khan created AS7-4451: ------------------------------- Summary: ServerSetupTasks don't get cleaned up if there was a problem Key: AS7-4451 URL: https://issues.jboss.org/browse/AS7-4451 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.1.Final Reporter: Kabir Khan Assignee: Stuart Douglas Fix For: 7.1.2.Final-redhat1 Running the testsuite with the Turkish Locale as described in https://issues.jboss.org/browse/AS7-4450 fails during the server setup tasks. The setup task seems to hang around causing problems in later tests using ServerSetupTasks. If LdapLoginModuleTestCase is @Ignored the subsequent tests pass. {code} public synchronized void handleBeforeDeployment(@Observes BeforeDeploy event, Container container) throws Exception { --- SNIP --- final Class<? extends ServerSetupTask>[] classes = setup.value(); if (current.isEmpty()) { for (Class<? extends ServerSetupTask> clazz : classes) { Constructor<? extends ServerSetupTask> ctor = clazz.getDeclaredConstructor(); ctor.setAccessible(true); current.add(ctor.newInstance()); } } else { //this should never happen for (int i = 0; i < current.size(); ++i) { if (classes[i] != current.get(i).getClass()) { // <<<<<<<< This error gets thrown <<<<<<<<<<< throw new RuntimeException("Mismatched ServerSetupTask current is " + current + " but " + currentClass + " is expecting " + Arrays.asList(classes)); } } } {code} -- 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

14 years

2
1
0 / 0

[JBoss JIRA] (AS7-4435) CLONE - EAR deployment with initialize-in-order doesn't wait for persistence-unit if it's not used in the module

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-4435?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-4435. --------------------------------- Resolution: Done > CLONE - EAR deployment with initialize-in-order doesn't wait for persistence-unit if it's not used in the module > ---------------------------------------------------------------------------------------------------------------- > > Key: AS7-4435 > URL: https://issues.jboss.org/browse/AS7-4435 > Project: Application Server 7 > Issue Type: Bug > Components: EE > Affects Versions: 7.1.1.Final > Environment: EAP 6.0.0.ER4.1, Seam 2.3.0.Beta2-SNAPSHOT (2012-04-06) > Reporter: Marek Schmidt > Assignee: Stuart Douglas > Labels: eap6_need_triage > Fix For: 7.1.2.Final-redhat1 > > > I have an Seam2 EAR application (Blog example from Seam distribution) which almost always fails to deploy with > {noformat} > javax.naming.NameNotFoundException: Error looking up blogEntityManagerFactory, service service jboss.naming.context.java.blogEntityManagerFactory is not started > {noformat} > The application.xml looks like this: > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.x > sd" version="6"> > <description>Examples for Seam 2 Framework in Java EE6 environment</description> > <display-name>blog-ear</display-name> > <initialize-in-order>true</initialize-in-order> > <module> > <ejb>blog-ejb.jar</ejb> > </module> > <module> > <web> > <web-uri>blog-web.war</web-uri> > <context-root>/seam-blog</context-root> > </web> > </module> > <module> > <ejb>jboss-seam.jar</ejb> > </module> > <library-directory>lib</library-directory> > </application> > {noformat} > The blog-ejb.jar contains persistence.xml: > {noformat} > > <?xml version="1.0" encoding="UTF-8"?> > <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" > version="1.0"> > <persistence-unit name="entityManager"> > <provider>org.hibernate.ejb.HibernatePersistence</provider> > <jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source> > <properties> > <property name="hibernate.hbm2ddl.auto" value="create-drop"/> > <property name="hibernate.show_sql" value="true"/> > > <property name="hibernate.cache.use_second_level_cache" value="true"/> > <property name="hibernate.cache.use_query_cache" value="true"/> > <property name="jboss.entity.manager.factory.jndi.name" value="java:/blogEntityManagerFactory"/> > <property name="hibernate.search.default.directory_provider" value="filesystem"/> > <property name="hibernate.search.default.indexBase" value="./blogindexes"/> > </properties> > </persistence-unit> > </persistence> > {noformat} > The persistence unit is accessed in Seam via JNDI > (components.xml) > {noformat} > <persistence:managed-persistence-context name="entityManager" > auto-create="true" > persistence-unit-jndi-name="java:/blogEntityManagerFactory"/> > {noformat} > This (usually) fails in the IndexerService, which is started automatically during servlet startup, as the java:/blogEntityManagerFactory is not yet ready. > Note that in the application.xml the "initialize-in-order" is defined, so the web module should not start before the blog-ejb.jar ( which contains the persistence.xml), is started. > Source of IndexerService: > {noformat} > package actions; > import javax.ejb.Remove; > import org.hibernate.search.jpa.FullTextEntityManager; > import org.jboss.seam.ScopeType; > import org.jboss.seam.annotations.Create; > import org.jboss.seam.annotations.Destroy; > import org.jboss.seam.annotations.In; > import org.jboss.seam.annotations.Name; > import org.jboss.seam.annotations.Scope; > import org.jboss.seam.annotations.Startup; > /** > * Index Blog entry at startup > * > * @author Emmanuel Bernard > * @author Sanne Grinovero > */ > @Name("indexerService") > @Scope(ScopeType.APPLICATION) > @Startup > public class IndexerService > { > @In > private FullTextEntityManager entityManager; > @Create > public void index() { > entityManager.createIndexer().start(); > } > @Remove > @Destroy > public void stop() {} > } > {noformat} > Also note that if I add the following bean to seam-ejb.jar it will correctly wait with the deployment of the web archive: > {noformat} > import javax.persistence.PersistenceUnit; > import javax.persistence.EntityManagerFactory; > import javax.ejb.Singleton; > import javax.ejb.Startup; > @Singleton > @Startup > public class Aargh > { > @PersistenceUnit > private EntityManagerFactory emf; > } > {noformat} > I believe this workaround shouldn't be necessary, and the initialize-in-order should also work with persistence units. > This issue affects all Seam2 EAR applications which use seam-managed entity manager in a @Startup bean, or any other legacy applications accessing persistence units through JNDI. -- 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

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4459) Generic / default resource and operation transformation

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4459: ------------------------------------- Summary: Generic / default resource and operation transformation Key: AS7-4459 URL: https://issues.jboss.org/browse/AS7-4459 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Tomaz Cerar Fix For: 7.2.0.Alpha1 Tooling for creating resource and operation transformers based on analyzing differences between model descriptions from various versions. -- 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

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4458) Slave HCs to provide subsystem management API version info to master HC as part of extension=xxx:add operation handling

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4458: ------------------------------------- Summary: Slave HCs to provide subsystem management API version info to master HC as part of extension=xxx:add operation handling Key: AS7-4458 URL: https://issues.jboss.org/browse/AS7-4458 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.2.Final-redhat1 When a slave HC registers with the master, it will provide management API version info for all extensions that are part of the config at that time. This JIRA is for providing the same info for extensions that are added via a management op after the slave is registered. -- 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

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4455) Resource and operation transformation on the master Host Controller

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4455: ------------------------------------- Summary: Resource and operation transformation on the master Host Controller Key: AS7-4455 URL: https://issues.jboss.org/browse/AS7-4455 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Ability of the master Host Controller to recognize that some slaves are running earlier version of the AS and to have the master make necessary transformations to resource models sent during host registration and to operations invoked after registration. The purpose of the transformation is to present data in formats understandable by the earlier version AS. This is a high level task; subtasks will describe smaller pieces. -- 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

14 years

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-3173) drools-compiler depends on antlr 2.7.7

by Marcel May (JIRA)

drools-compiler depends on antlr 2.7.7 -------------------------------------- Key: JBRULES-3173 URL: https://issues.jboss.org/browse/JBRULES-3173 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.3.0.Beta1, 5.2.0.Final Reporter: Marcel May Assignee: Mark Proctor Priority: Trivial drools-compiler uses antlr 3.3 but has an additional dependency on old antlr:antlr 2.7.7 version. The v2 dependency is obsolete since antlr 3.1 (see http://www.antlr.org/jira/browse/ANTLR-180). Please remove the antlr:antlr dependency, for the next 5.2.x / 5.3.x release - thanks! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
9
0 / 0

[JBoss JIRA] (AS7-4115) Jboss Web Connector resources max-threads data not available in ui or cli/json data

by Heiko Rupp (JIRA)

[ https://issues.jboss.org/browse/AS7-4115?page=com.atlassian.jira.plugin.s... ] Heiko Rupp updated AS7-4115: ---------------------------- Priority: Critical (was: Major) > Jboss Web Connector resources max-threads data not available in ui or cli/json data > ------------------------------------------------------------------------------------ > > Key: AS7-4115 > URL: https://issues.jboss.org/browse/AS7-4115 > Project: Application Server 7 > Issue Type: Bug > Environment: Using JBEAP-6.0.0.ER1. > Reporter: Simeon Pinder > Assignee: Jean-Frederic Clere > Priority: Critical > Labels: rhq > > Looks like max-threads is not currently exposed for JBoss Web Connectors. > "connector" => {"http" => { > "bytesReceived" => "0", > "bytesSent" => "0", > "enable-lookups" => false, > "enabled" => true, > "errorCount" => "0", > "max-post-size" => 2097152, > "max-save-post-size" => 4096, > "maxTime" => "0", > "processingTime" => "0", > "protocol" => "HTTP/1.1", > "redirect-port" => 8443, > "requestCount" => "0", > "scheme" => "http", > "secure" => false, > "socket-binding" => "http", > "ssl" => undefined, > "virtual-server" => undefined > }} -- 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

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4454) Implement graphing of real time attributes in CLI GUI

by Stan Silvert (JIRA)

Stan Silvert created AS7-4454: --------------------------------- Summary: Implement graphing of real time attributes in CLI GUI Key: AS7-4454 URL: https://issues.jboss.org/browse/AS7-4454 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.1.Final Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 7.1.2.Final-redhat1 See https://community.jboss.org/wiki/GraphingRealTimeAttributesWithCLIGUI -- 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

14 years

1
1
0 / 0

[JBoss JIRA] (AS7-4345) upgrade to Hibernate 4.1.2, add naturalid second level cache definitions and use new InfinispanRegionFactory methods

by Scott Marlow (JIRA)

Scott Marlow created AS7-4345: --------------------------------- Summary: upgrade to Hibernate 4.1.2, add naturalid second level cache definitions and use new InfinispanRegionFactory methods Key: AS7-4345 URL: https://issues.jboss.org/browse/AS7-4345 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.1.2.Final Leverage changes made for HHH-7204 -- 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

14 years

1
1
0 / 0

[JBoss JIRA] (AS7-4115) Jboss Web Connector resources max-threads data not available in ui or cli/json data

by Heiko Rupp (JIRA)

[ https://issues.jboss.org/browse/AS7-4115?page=com.atlassian.jira.plugin.s... ] Heiko Rupp reopened AS7-4115: ----------------------------- The :read-resource-description says "depends on connector", but the concrete connector instance fails to deliver a value. Either make this return a value, or add something to the resource-connection. Otherwise users don't know the default. > Jboss Web Connector resources max-threads data not available in ui or cli/json data > ------------------------------------------------------------------------------------ > > Key: AS7-4115 > URL: https://issues.jboss.org/browse/AS7-4115 > Project: Application Server 7 > Issue Type: Bug > Environment: Using JBEAP-6.0.0.ER1. > Reporter: Simeon Pinder > Assignee: Jean-Frederic Clere > Labels: rhq > > Looks like max-threads is not currently exposed for JBoss Web Connectors. > "connector" => {"http" => { > "bytesReceived" => "0", > "bytesSent" => "0", > "enable-lookups" => false, > "enabled" => true, > "errorCount" => "0", > "max-post-size" => 2097152, > "max-save-post-size" => 4096, > "maxTime" => "0", > "processingTime" => "0", > "protocol" => "HTTP/1.1", > "redirect-port" => 8443, > "requestCount" => "0", > "scheme" => "http", > "secure" => false, > "socket-binding" => "http", > "ssl" => undefined, > "virtual-server" => undefined > }} -- 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

14 years

1
0
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 April 2012