December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-217) Strict location check of persistence.xml deployments

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-217?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-217: ------------------------------ Fix Version/s: 8.0.0.Final > Strict location check of persistence.xml deployments > ---------------------------------------------------- > > Key: WFLY-217 > URL: https://issues.jboss.org/browse/WFLY-217 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Bartosz Baranowski > Assignee: Scott Marlow > Priority: Minor > Fix For: 8.0.0.CR1, 8.0.0.Final > > > As of: https://github.com/jbossas/jboss-as/commit/38815193011fba624170a7d938118e... it is possible to deploy persistence.xml from invalid location: > As per JPA spec(https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide), valid locations are: > - an EJB-JAR file > - the WEB-INF/classes directory of a WAR file > - a jar file in the WEB-INF/lib directory of a WAR file > - a jar file in the EAR library directory > - an application client jar file -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-229) Expose mgmt client socket binding config through ModelControllerClient Factory

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-229?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-229: ------------------------------ Fix Version/s: 8.0.0.Final > Expose mgmt client socket binding config through ModelControllerClient Factory > ------------------------------------------------------------------------------ > > Key: WFLY-229 > URL: https://issues.jboss.org/browse/WFLY-229 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.CR1, 8.0.0.Final > > > Parent task used a secret system property to configure this to support Open Shift's immediate need, but proper configuration is needed. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-943) XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

by Jan-Willem Mulder (JIRA)

[ https://issues.jboss.org/browse/WFLY-943?page=com.atlassian.jira.plugin.s... ] Jan-Willem Mulder commented on WFLY-943: ---------------------------------------- Dear sir, madam, Thank you, your e-mail has arrived. Unfortunately I am not available to answer your message at the moment. I am out of office, starting from 20-12-2013. As of 02-01-2014, I will be able to answer your e-mail again. Met vriendelijke groet/ Kind regards, ing. Jan-Willem Mulder Head of Back End Development E: jan-willem.mulder(a)isaac.nl<mailto:jan-willem.mulder@isaac.nl> T: 040 215 53 58 - M: 06 11 34 81 48 - F: 040 290 89 80 - W: http://www.isaac.nl/ Marconilaan 16, 5621 AA Eindhoven - The Netherlands Dit e-mailbericht is alleen bestemd voor de geadresseerde(n). Indien dit bericht niet voor u is bedoeld wordt u verzocht de afzender hiervan op de hoogte te stellen door het bericht te retourneren en de inhoud niet te gebruiken. Aan dit bericht kunnen geen rechten worden ontleend. > XML schema; use of elementFormDefault='unqualified'; cannot validate some documents > ----------------------------------------------------------------------------------- > > Key: WFLY-943 > URL: https://issues.jboss.org/browse/WFLY-943 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.0.0.Alpha3 > Reporter: Elias Ross > Fix For: 8.0.0.Final > > Attachments: jboss-deployment-structure.xml > > > When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate. > This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate. > $ git grep elementFormDefault..unqualified > jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified" > jboss-jpa_1_0.xsd: elementFormDefault="unqualified" -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-231) HostControllerConnectionService connection timeout is not configurable

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-231?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-231: ------------------------------ Fix Version/s: 8.0.0.Final > HostControllerConnectionService connection timeout is not configurable > ---------------------------------------------------------------------- > > Key: WFLY-231 > URL: https://issues.jboss.org/browse/WFLY-231 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Dominik Pospisil > Assignee: Bartosz Baranowski > Fix For: 8.0.0.CR1, 8.0.0.Final > > > I am seeing intermittent failures when starting AS7 in domain mode. It seems that this is due to HostControllerConnectionService has hardcoded 15s timeout when trying to connect to DC. I think that this value should be configurable. > HostControllerConnectionService.java: > ... > ProtocolChannelClient.Configuration configuration = new ProtocolChannelClient.Configuration(); > configuration.setEndpoint(endpointInjector.getValue()); > configuration.setConnectionTimeout(15000); > configuration.setUri(new URI("remote://" + hcAddressInjector.getValue().getHostName() + ":" + hcAddressInjector.getValue().getPort())); > client = ProtocolChannelClient.create(configuration); > ... > Exception I am getting: > [Server:server-two] 13:52:54,766 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.host.controller.channel: org.jboss.msc.service.StartException in service jboss.host.controller.channel: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out > [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:103) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] > [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] > [Server:server-two] Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out > [Server:server-two] at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:166) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-230) Add @ValidIdRange annotation to message loggers and message bundles

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-230?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-230: ------------------------------ Fix Version/s: 8.0.0.Final > Add @ValidIdRange annotation to message loggers and message bundles > ------------------------------------------------------------------- > > Key: WFLY-230 > URL: https://issues.jboss.org/browse/WFLY-230 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.CR1, 8.0.0.Final > > > A new release of the logging tooling will include a {{@ValidIdRange}} annotation. This will help document which id ranges allowed as well as provide compile time validation. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-244) Undertow Integration Tracker

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-244?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-244: ------------------------------ Fix Version/s: 8.0.0.Final > Undertow Integration Tracker > ---------------------------- > > Key: WFLY-244 > URL: https://issues.jboss.org/browse/WFLY-244 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Critical > Fix For: 8.0.0.CR1, 8.0.0.Final > > > Tracking issue for all issues related to undertow integration. > as part of https://github.com/wildfly/wildfly/pull/4810 there tests removed that need to be re-added as part of this tracking issue -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-241) Specify and expose mod_cluster runtime information the should be shown within the console

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-241?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-241: ------------------------------ Fix Version/s: 8.0.0.Final > Specify and expose mod_cluster runtime information the should be shown within the console > ----------------------------------------------------------------------------------------- > > Key: WFLY-241 > URL: https://issues.jboss.org/browse/WFLY-241 > Project: WildFly > Issue Type: Clarification > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Heiko Braun > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1, 8.0.0.Final > > -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-249) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-249?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-249: ------------------------------ Fix Version/s: 8.0.0.Final > Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users > --------------------------------------------------------------------------------------------- > > Key: WFLY-249 > URL: https://issues.jboss.org/browse/WFLY-249 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.CR1, 8.0.0.Final > > > Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.) > But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-260) Error

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-260?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-260: ------------------------------ Fix Version/s: 8.0.0.Final > Error > ----- > > Key: WFLY-260 > URL: https://issues.jboss.org/browse/WFLY-260 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Class Loading > Reporter: Pablo Ochoa > Assignee: David Lloyd > Fix For: 8.0.0.CR1, 8.0.0.Final > > > Buenos Días, > Tengo problema con la version 7.1.1 de Jboss por defecto viene creado un Selector y yo intento crea uno nuevo para el manejo de mi classes me arroja el siguiente error > Preferred repository selector not installed because one has already exists. No problem, using existing selector... > Estado investigando de verdad no conseguido algo para poder solventar este problema el la ultima version de Jboss 6 no ocurre este mismo problema agradezco toda la colaboración que me puedan brindar > Te anexo el codigo que utilizo > import java.util.*; > import javax.naming.*; > import org.apache.log4j.Hierarchy; > import org.apache.log4j.Level; > import org.apache.log4j.spi.*; > public class Log4jContextJNDISelector > implements RepositorySelector > { > public Log4jContextJNDISelector(){ > defaultHierarchy = new Hierarchy(new RootLogger(Level.DEBUG)); > } > public LoggerRepository getLoggerRepository() > { > String loggingContextName = null; > try > { > Context ctx = new InitialContext(); > loggingContextName = (String)ctx.lookup("java:comp/env/log4j/logging-context"); > } > catch(NamingException ne) { } > if(loggingContextName == null) > return defaultHierarchy; > Hierarchy hierarchy = (Hierarchy)hierMap.get(loggingContextName); > if(hierarchy == null) > { > hierarchy = new Hierarchy(new RootLogger(Level.DEBUG)); > hierMap.put(loggingContextName, hierarchy); > } > return hierarchy; > } > Archivo web.xml esta configuración > <context-param> > <param-name>log4j-selector</param-name> > <param-value>ve.com.prueba.gdis.cia.config.logging.Log4jContextJNDISelector</param-value> > <description> Selector de repositorios basado en JNDI desde donde se > configurar el repositorio de logs para esta aplicación > </description> > </context-param> -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-255) Improve reporting during deployment hang

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-255?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-255: ------------------------------ Fix Version/s: 8.0.0.Final > Improve reporting during deployment hang > ---------------------------------------- > > Key: WFLY-255 > URL: https://issues.jboss.org/browse/WFLY-255 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Environment: http://java.net/jira/browse/EJB_SPEC-60 > java version "1.7.0_09" > OpenJDK Runtime Environment (IcedTea7 2.3.3) (7u9-2.3.3-0ubuntu1~12.10.1) > OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode) > Ubuntu 12.10 > Reporter: Carlo de Wolf > Fix For: 8.0.0.CR1, 8.0.0.Final > > Attachments: deployment-hang-20130205.txt, server.log > > > Management Thread waits indefinitely for, what seems to be, a finished operation. > {noformat} > "management-handler-thread - 2" prio=10 tid=0x00007fa1380d0000 nid=0x7683 in Object.wait() [0x00007fa136deb000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at java.lang.Object.wait(Object.java:503) > at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158) > - locked <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:464) > at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:148) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:299) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {noformat} -- 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

12 years, 7 months

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 December 2013