April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-263) JASPI Support for Web Services

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-263?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-263: ---------------------------------- Assignee: Alessio Soldano (was: Brian Stansberry) > JASPI Support for Web Services > ------------------------------ > > Key: WFLY-263 > URL: https://issues.jboss.org/browse/WFLY-263 > Project: WildFly > Issue Type: Feature Request > Components: Security, Web Services > Reporter: Anil Saldhana > Assignee: Alessio Soldano > Fix For: 8.0.0.Alpha1 > > > Take care of the JASPI requirements for SOAP layer. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-260) Error

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-260?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-260: ---------------------------------- Assignee: David Lloyd (was: Brian Stansberry) > Error > ----- > > Key: WFLY-260 > URL: https://issues.jboss.org/browse/WFLY-260 > Project: WildFly > Issue Type: Feature Request > Components: Class Loading > Reporter: Pablo Ochoa > Assignee: David Lloyd > Fix For: 8.0.0.Alpha1 > > > 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-267) Support updated JCA management API

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-267?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-267: ---------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Support updated JCA management API > ----------------------------------- > > Key: WFLY-267 > URL: https://issues.jboss.org/browse/WFLY-267 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.CR1 > > -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-676) Windows PowerShell scripts in bin

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-676?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned WFLY-676: -------------------------------- Assignee: Tomaz Cerar (was: Jason Greene) > Windows PowerShell scripts in bin > --------------------------------- > > Key: WFLY-676 > URL: https://issues.jboss.org/browse/WFLY-676 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: Awaiting Volunteers > > > Add .psh scripts that match the functionality of our .sh scripts. Leave the .bat scripts in their current limited-functionality form for people still on XP, but use PowerShell as the recommended Windows scripting language. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-160) Reconfigure of JavaMail service on-the-fly

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-160?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned WFLY-160: -------------------------------- Assignee: Tomaz Cerar (was: Alexey Loubyansky) > Reconfigure of JavaMail service on-the-fly > ------------------------------------------ > > Key: WFLY-160 > URL: https://issues.jboss.org/browse/WFLY-160 > Project: WildFly > Issue Type: Bug > Components: Mail > Reporter: Vadim Gusev > Assignee: Tomaz Cerar > Fix For: 8.0.0.Alpha1 > > > Since JavaMail implemented on Jboss AS7 we can't reconfigure JavaMail service on-the-fly. We always should reload the server to apply new configuration. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-258) mod_cluster schema 1.2

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-258?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned WFLY-258: -------------------------------- Assignee: Radoslav Husar (was: Scott Marlow) > mod_cluster schema 1.2 > ---------------------- > > Key: WFLY-258 > URL: https://issues.jboss.org/browse/WFLY-258 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Changes to the schema > * simplified names and sync in line with scheme recommendations > * remove redundant <mod-cluster-config .. /> for good, everything should be element of the subsystem > * fix load factor enum: no pool metric supported > * make load-balancers configurable via socket-outbuound-group mechanism > * add missing load-balancer properties to <proxies/> -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-149) The console-handler in the logging schema still contains a filter element

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-149?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-149: ---------------------------------- Assignee: James Perkins (was: Brian Stansberry) > The console-handler in the logging schema still contains a filter element > ------------------------------------------------------------------------- > > Key: WFLY-149 > URL: https://issues.jboss.org/browse/WFLY-149 > Project: WildFly > Issue Type: Bug > Components: Localization > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-305) Implement mail inflow

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-305?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned WFLY-305: -------------------------------- Assignee: Tomaz Cerar (was: Paul Ferraro) > Implement mail inflow > --------------------- > > Key: WFLY-305 > URL: https://issues.jboss.org/browse/WFLY-305 > Project: WildFly > Issue Type: Feature Request > Components: EE > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.0.0.Alpha1 > > > in previous versions of as we had mail-ra resource adapter that added functionality of handling inflow mails. > there is implementation of this ironjacamar so the code could be reused. > Resource addapter could/should be added the same way hornetq addapter is added in messaging subsystem. > code and documentation from ironjacamer > https://svn.jboss.org/repos/jbossas/projects/jboss-jca/trunk/adapters/src... > http://docs.jboss.org/ironjacamar/userguide/1.1/en-US/html/introduction.h... -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-142) inconsistent usage of min/max-occurs in model description

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-142?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-142: ---------------------------------- Assignee: (was: Brian Stansberry) > inconsistent usage of min/max-occurs in model description > --------------------------------------------------------- > > Key: WFLY-142 > URL: https://issues.jboss.org/browse/WFLY-142 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > Attachments: patch.txt > > > The usages of min/max-occurs in the model description are not consistent - e.g. missing in ResourceDescription, mostly wrong when used in the descriptionProvider or outdated examples in the documentation. > I'll attach a simple patch which should actually fix that issue in line with the documentation [1] (incl. recursive usage) and the usage of the CLI (ls -l). However there might be more to it. > [1] https://docs.jboss.org/author/display/AS71/Description+of+the+Management+... -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-124) Read timed out on server shutdown and DIST SYNC

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-124?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-124: ---------------------------------- Assignee: Paul Ferraro (was: Brian Stansberry) > Read timed out on server shutdown and DIST SYNC > ----------------------------------------------- > > Key: WFLY-124 > URL: https://issues.jboss.org/browse/WFLY-124 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 8.0.0.Alpha1 > > > Some of the clients are getting read timeout when using dist sync and the node is gracefully shut down. > This is even more suspicions since the TOs in clustering are probably all set to max 15 seconds but the client timeout is set to 30 seconds. This looks fishy. > {noformat} > 2012/05/13 17:22:54:388 EDT [WARN ][Runner - 1749] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: IO error: java.net.SocketTimeoutException: Read timed out> > {noformat} > The exceptions seem to correlate with > {noformat} > ./perf20.log:[JBossINF] 17:23:11,344 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20/10.16.90.58:8009-109) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.RuntimeException: JBAS018060: Exception acquiring ownership of K5VcZ4gGFzRaLKYMesOQk0zD > {noformat} > being thrown on the server. -- 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

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013