April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-317) Audit logging configuration

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-317?page=com.atlassian.jira.plugin.s... ] Kabir Khan reassigned WFLY-317: ------------------------------- Assignee: Kabir Khan > Audit logging configuration > --------------------------- > > Key: WFLY-317 > URL: https://issues.jboss.org/browse/WFLY-317 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Kabir Khan > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-315) Avoid running out of threads when connecting to the DC from a slave to pull down missing data

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-315?page=com.atlassian.jira.plugin.s... ] Kabir Khan reassigned WFLY-315: ------------------------------- Assignee: Kabir Khan (was: David Lloyd) > Avoid running out of threads when connecting to the DC from a slave to pull down missing data > --------------------------------------------------------------------------------------------- > > Key: WFLY-315 > URL: https://issues.jboss.org/browse/WFLY-315 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Alpha1 > > > For AS7-6808 when a slave connects to the DC to pull down missing data, it does this by either getting a lock for the DC, or by joining the permit of the existing DC lock if the request to update a slave's server-config was executed as part of a composite obtaining a lock on the DC. > The way it works at present there is a thread per slave which is blocked until the transaction completes. The DC threads are a finite resource, so a large number of slaves trying to pull down dats will cause deadlock -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-477) Provide a Bundle version of the javax.persistence API

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-477?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned WFLY-477: --------------------------------- Assignee: Scott Marlow (was: Stuart Douglas) fix invalid assign due to migration > Provide a Bundle version of the javax.persistence API > ----------------------------------------------------- > > Key: WFLY-477 > URL: https://issues.jboss.org/browse/WFLY-477 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, OSGi > Reporter: Thomas Diesler > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha1 > > > This API is currently provided by hibernate-jpa-2.0-api-1.0.1.Final > Here is an [example|http://mvnrepository.com/artifact/org.eclipse.persistence/javax.p...] -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1266) Undertow breaks some JSF apps

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1266?page=com.atlassian.jira.plugin.... ] Jason Greene moved AS7-6923 to WFLY-1266: ----------------------------------------- Project: WildFly (was: Application Server 7) Key: WFLY-1266 (was: AS7-6923) Affects Version/s: 8.0.0.Alpha1 (was: 8.0.0.Alpha1) Component/s: JSF (was: JSF) (was: Web) Fix Version/s: 8.0.0.Alpha1 (was: 8.0.0.Alpha1) > Undertow breaks some JSF apps > ----------------------------- > > Key: WFLY-1266 > URL: https://issues.jboss.org/browse/WFLY-1266 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 8.0.0.Alpha1 > Reporter: Stan Silvert > Assignee: Stuart Douglas > Priority: Critical > Fix For: 8.0.0.Alpha1 > > Attachments: InjectionTest.zip > > > Undertow breaks some JSF apps. I haven't narrowed the problem down yet but I want to go ahead and post this JIRA because it is a blocker for AS8. > I'm attaching a small JSF project that demonstrates the problem. When you run the WAR with -c standalone-jbossweb.xml it works fine. > With Undertow it breaks. You are unable to navigate based on the return value of a MethodExpression. > Also, you get this warning: > {noformat} > 12:17:30,572 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (default task-1) JSF1091: No mime type could be found for file /index.xhtml. To resolve this, add a mime-type mapping to the applications web.xml. > {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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1199) Provide management view for bundle wiring

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1199?page=com.atlassian.jira.plugin.... ] Jason Greene reassigned WFLY-1199: ---------------------------------- Assignee: Thomas Diesler (was: Ondrej Zizka) Fix invalid assign from migration > Provide management view for bundle wiring > ----------------------------------------- > > Key: WFLY-1199 > URL: https://issues.jboss.org/browse/WFLY-1199 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Environment: Mac OS X 10.7.3 > Reporter: Tim Diekmann > Assignee: Thomas Diesler > Labels: Console > > The OSGi management console for AS 7 needs a viewer of the current wiring. The console log showed the following error on start of the bundle and there is no way to inspect the wiring to see where the problem lies and how to solve it. There is some inconsistency in the deployment, but how to find out what? > {code} > 00:09:14,480 ERROR [org.mortbay.log] (HttpManagementService-threads - 3) Error starting handlers: java.lang.IncompatibleClassChangeError: Class org.eclipse.equinox.http.servlet.HttpServiceServlet does not implement the requested interface javax.servlet.Servlet > at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.init(HttpServerManager.java:294) > at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431) > at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:681) > at org.mortbay.jetty.servlet.Context.startContext(Context.java:140) > at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) > at org.mortbay.jetty.Server.doStart(Server.java:224) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) > at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:109) > at org.eclipse.equinox.http.jetty.internal.Activator.start(Activator.java:60) > at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488) > at org.jboss.as.osgi.parser.BundleRuntimeHandler.handleOperation(BundleRuntimeHandler.java:132) > at org.jboss.as.osgi.parser.BundleRuntimeHandler.executeRuntimeStep(BundleRuntimeHandler.java:89) > at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) > at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:461) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) > at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:304) > at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:294) > at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294) > at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201) > at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208) > at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) > at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) > at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {code} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1133) Integration of EventAdmin with AS7 components

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1133?page=com.atlassian.jira.plugin.... ] Jason Greene reassigned WFLY-1133: ---------------------------------- Assignee: Thomas Diesler (was: Ondrej Zizka) Fix invalid assign from migration > Integration of EventAdmin with AS7 components > --------------------------------------------- > > Key: WFLY-1133 > URL: https://issues.jboss.org/browse/WFLY-1133 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > Non-OSGi components should be able to publish/receive events through EventAdmin > and vice versa of course -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1039) Document feature: autoimport of import.sql

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1039?page=com.atlassian.jira.plugin.... ] Jason Greene reassigned WFLY-1039: ---------------------------------- Assignee: (was: Ondrej Zizka) Fix invalid assign from migration > Document feature: autoimport of import.sql > ------------------------------------------ > > Key: WFLY-1039 > URL: https://issues.jboss.org/browse/WFLY-1039 > Project: WildFly > Issue Type: Feature Request > Components: Documentation > Reporter: Karel Piwko > > Following articles mention the feature: > * https://docs.jboss.org/author/display/AS7/The+kitchensink+example+in+depth > * https://docs.jboss.org/author/display/AS7/The+login+example+in+depth > * http://community.jboss.org/wiki/HowDoTheJboss7QuickstartsExamplesAutomati... > However, there is no information about its life cycle, how to enable/disable this, etc. > As this is a part of the all examples, we promote it's usage to all inexperienced users who will definitely search more information about it. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1058) Allow the CLI to deploy maven projects

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1058?page=com.atlassian.jira.plugin.... ] Jason Greene reassigned WFLY-1058: ---------------------------------- Assignee: Alexey Loubyansky (was: Ondrej Zizka) Fix invalid assign from migration > Allow the CLI to deploy maven projects > -------------------------------------- > > Key: WFLY-1058 > URL: https://issues.jboss.org/browse/WFLY-1058 > Project: WildFly > Issue Type: Feature Request > Components: Server > Reporter: Nicholas DiPiazza > Assignee: Alexey Loubyansky > > Allow users to deploy Maven projects directly from the CLI. > Create a new command "mavendeploy" > This will take a pom.xml for a war, ear or ejb project and will maven build, then deploy to the server using the DeployHandler. > First iteration of this would take same parameters as "deploy" except for one, --goals that specifies what goals to build the project with before deploying. (this makes it so you can clean before install, or just install, or call whatever goal that is needed to build the artifact). > Examples: > [standalone@localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml > [standalone@localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml --goals="clean install" -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-786) NicInterfaceCriteriaUnitTestCase testBasic fails on a host configured with a dual IP stack

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-786?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned WFLY-786: --------------------------------- Assignee: Pavel Janousek (was: Ondrej Zizka) Fix invalid assign from migration > NicInterfaceCriteriaUnitTestCase testBasic fails on a host configured with a dual IP stack > ------------------------------------------------------------------------------------------ > > Key: WFLY-786 > URL: https://issues.jboss.org/browse/WFLY-786 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Michael Musgrove > Assignee: Pavel Janousek > > This test fails when we run the test suite with the following IPv6 options: > {noformat} > -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Djboss.bind.address=[::1] -Djboss.bind.address.management=[::1] -Djboss.bind.address.unsecure=[::1] > {noformat} > > It appears that the test is expecting an array containing one nic address but instead gets two (IPv4 and IPv6) addresses. The linked JBTM jira is where we initially reported the issue. Test output is: > {noformat} > Failed tests: > testBasic(org.jboss.as.controller.interfaces.NicInterfaceCriteriaUnitTestCase): expected:<[/0:0:0:0:0:0:0:1%1]> but was:<[/0:0:0:0:0:0:0:1%1, /127.0.0.1]> > testMultipleCriteria(org.jboss.as.controller.interfaces.NotInterfaceCriteriaUnitTestCase): expected:<{name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2]}> but was:<{name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2, /172.17.131.3]}> > testMultipleCriteria(org.jboss.as.controller.interfaces.AnyInterfaceCriteriaUnitTestCase): expected:<{name:lo (lo)=[/0:0:0:0:0:0:0:1%1], name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2]}> but was:<{name:lo (lo)=[/127.0.0.1, /0:0:0:0:0:0:0:1%1], name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2, /172.17.131.3]}> > {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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-464) Domain Management - Add support for database authentication.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-464?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned WFLY-464: --------------------------------- Assignee: Darran Lofthouse (was: Ondrej Zizka) Fix invalid assign from migration > Domain Management - Add support for database authentication. > ------------------------------------------------------------ > > Key: WFLY-464 > URL: https://issues.jboss.org/browse/WFLY-464 > Project: WildFly > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > It should be possible to define a database authentication element for authentication of incoming connections against a database. > Ideally the password should be obtainable from the database to allow us to use DIGEST authentication but if not a fallback to verify the password should be supported. -- 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, 8 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