March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-670) Node type is not complete at index 0 after tab completion on an empty resource

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-670?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-670: ------------------------------------------------ Sat6QE Jenkins <sat6-jenkins(a)redhat.com> changed the Status of [bug 1277320|https://bugzilla.redhat.com/show_bug.cgi?id=1277320] from POST to MODIFIED > Node type is not complete at index 0 after tab completion on an empty resource > ------------------------------------------------------------------------------ > > Key: WFCORE-670 > URL: https://issues.jboss.org/browse/WFCORE-670 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: James Perkins > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 1.0.0.CR2 > > > Using something like {{/system-property=<TAB>}} with no system properties set results in future commands no longer working. > {code:title=Example Output} > [standalone@localhost:9990 /] /system-property= > The operation name is missing or the format of the operation request is wrong. > [standalone@localhost:9990 /] > [standalone@localhost:9990 /] exit > Node type is not complete at index 0 > [standalone@localhost:9990 /] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-632) Subsystem deployment undeployed at startup

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-632?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-632: ------------------------------------------------ Sat6QE Jenkins <sat6-jenkins(a)redhat.com> changed the Status of [bug 1271673|https://bugzilla.redhat.com/show_bug.cgi?id=1271673] from POST to MODIFIED > Subsystem deployment undeployed at startup > ------------------------------------------ > > Key: WFCORE-632 > URL: https://issues.jboss.org/browse/WFCORE-632 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Beta3, 1.0.0.Beta4 > Reporter: Stan Silvert > Assignee: Brian Stansberry > Labels: affects_elytron > Fix For: 1.0.0.Beta4 > > > {noformat} > @BrianStansberry The "mixed approach" doesn't seem to work any more. https://developer.jboss.org/wiki/ExtendingAS7 > @BrianStansberry I'm using this to deploy keycloak WAR from the subsystem. > @BrianStansberry As soon as the server is started, something is calling stopService() on the Keycloak WAR. > Tomaz Cerar > 1:15 PM > @StanSilvert are you still working on AS7? https://docs.jboss.org/author/display/WFLY8/Extending+WildFly+8 > Stan Silvert > 1:16 PM > @ctomc No. this is WildFly 9. It still works on WildFly 8. > Tomaz Cerar > 1:16 PM > ah the war deployment, that could be regression > Brian Stansberry > 1:17 PM > @ctomc how so? > Stan Silvert > 1:17 PM > FYI. I did a Thread.dumpStack() and got this: > 13:11:35,173 ERROR [stderr] (MSC service thread 1-3) java.lang.Exception: Stack trace > 13:11:35,173 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.dumpStack(Thread.java:1329) > 13:11:35,174 ERROR [stderr] (MSC service thread 1-3) at org.wildfly.extension.undertow.Host.unregisterDeployment(Host.java:168) > 13:11:35,176 ERROR [stderr] (MSC service thread 1-3) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java: > 113) > 13:11:35,179 ERROR [stderr] (MSC service thread 1-3) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > 13:11:35,181 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.Serv > iceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > 13:11:35,184 ERROR [stderr] (MSC service thread 1-3) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > 13:11:35,186 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > 13:11:35,188 ERROR [stderr] (MSC service thread 1-3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > 13:11:35,190 ERROR [stderr] (MSC service thread 1-3) at java.lang.Thread.run(Thread.java:745) > Hide full text > Tomaz Cerar > 1:18 PM > @BrianStansberry just reffering that war deployment from subsystem should still work > 1:19 PM > Jason Greene joined the room. > Tomaz Cerar > 1:19 PM > @StanSilvert what happens? as that thread dump makes no sense > Stan Silvert > 1:21 PM > http://pastebin.com/xQ2DNzEe > The WAR is simply undeployed as soon as WildFly finishes startup. > Brian Stansberry > 1:22 PM > @StanSilvert can you give me a link to your code that's doing the deploy stuff? > Stan Silvert > 1:22 PM > just a sec > Stan Silvert > 1:24 PM > https://github.com/keycloak/keycloak/tree/master/integration > The code that creates the operation is https://github.com/keycloak/keycloak/blob/master/integration > AuthServerUtil ^^^ > click on the second link > 1:27 PM > Darran Lofthouse left the room. > Brian Stansberry > 1:27 PM > @StanSilvert are you doing overlay stuff? I see some code there re: overlays > Stan Silvert > 1:28 PM > Yes, but not in this instance. > Brian Stansberry > 1:28 PM > ok. I'm asking just because that would add more complexity, better scope for some service dependency going missing, triggering stop > Stan Silvert > 1:29 PM > For this simple case there are no overlays. > Brian Stansberry > 1:29 PM > @StanSilvert interesting, your log looks like it's a true undeploy op, not just a service stop > Tomaz Cerar > 1:30 PM > @BrianStansberry should we use 6.x.0 or 6.x.latest for tranformers testing? > Tomaz Cerar goes get some diner > Stan Silvert > 1:30 PM > @BrianStansberry If that's the case then maybe some condition is triggering my own undeploy operation. > @BrianStansberry I'll look into that and see what I find. > Brian Stansberry > 1:31 PM > @ctomc 6.x.0 is ok by me; chasing CPs is too much hassle > @StanSilvert note this: > 13:11:35,294 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "main-auth-server.war" (runtime-name: "main-auth-server.war") > the thread -- DeploymentScanner-threads - 1 > looks like your deployment is exposed to the scanner? > oh, here's a guess! > the scanner sees "persistent" => false and treats it as under scanner control > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-5499) Channel end notification received, closing channel ... should be logged at debug in EjbLogger

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5499?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5499: ----------------------------------------------- Sat6QE Jenkins <sat6-jenkins(a)redhat.com> changed the Status of [bug 1271538|https://bugzilla.redhat.com/show_bug.cgi?id=1271538] from POST to MODIFIED > Channel end notification received, closing channel ... should be logged at debug in EjbLogger > --------------------------------------------------------------------------------------------- > > Key: WFLY-5499 > URL: https://issues.jboss.org/browse/WFLY-5499 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Reporter: Takayuki Konishi > > Remote naming is logging this at ERROR, though it seems normal and no adverse effects are apparent, we should log it at debug instead of error. > {code} > ERROR [org.jboss.as.ejb3] (Remoting "master@ap02:server-apip" task-2) JBAS014141: Channel end notification received, closing channel Channel ID 6b8f00d7 (inbound) of Remoting connection 36e4f81b to /192.168.1.10:64354 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-927) Option roleRecursion does not work in LdapRolesMappingProvider

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-927?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-927: -------------------------------------------------- Sat6QE Jenkins <sat6-jenkins(a)redhat.com> changed the Status of [bug 1269826|https://bugzilla.redhat.com/show_bug.cgi?id=1269826] from POST to MODIFIED > Option roleRecursion does not work in LdapRolesMappingProvider > -------------------------------------------------------------- > > Key: SECURITY-927 > URL: https://issues.jboss.org/browse/SECURITY-927 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: PicketBox_5_0_0.Alpha2 > Reporter: Ondrej Lukas > Assignee: Ryan Emerson > > Option roleRecursion does not work in org.jboss.security.mapping.providers.role.LdapRolesMappingProvider. Only entries without recursion are found. No recursive search is done by LdapRolesMappingProvider since LdapRolesMappingProvider.rolesSearch method tries to make a recursive search with same parameters. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1121) Use script name for file related to Wildfly to allow multiple instances easily

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1121?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1121: ------------------------------------------------- Sat6QE Jenkins <sat6-jenkins(a)redhat.com> changed the Status of [bug 1265740|https://bugzilla.redhat.com/show_bug.cgi?id=1265740] from POST to MODIFIED > Use script name for file related to Wildfly to allow multiple instances easily > ------------------------------------------------------------------------------ > > Key: WFCORE-1121 > URL: https://issues.jboss.org/browse/WFCORE-1121 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Affects Versions: 2.0.1.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Optional > Fix For: 3.0.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > With the current provided init.d script, one cannot start several instances of Wildfly. Indeed, the script will associate the same files (pid file, log) to both instance. If we rename those files using, for instance, the name of the script we can easily use the *exact same script* for all local instances: > {code:bash} > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-1 > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-2 > {code} > And to take the example of the PIDFILE: > {code:bash} > JBOSS_PIDFILE=/var/run/$(basename $0)/jboss-as-domain.pid > {code} > Each links will then look up and creates its own separate file: > /var/run/wildfly-1/jboss-as-domain.pid > /var/run/wildfly-2/jboss-as-domain.pid -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-5381) Fix pom.xml jpda profile and add ability to specify additional surefire forked JVM args via command line

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5381?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5381: ----------------------------------------------- Sat6QE Jenkins <sat6-jenkins(a)redhat.com> changed the Status of [bug 1265229|https://bugzilla.redhat.com/show_bug.cgi?id=1265229] from POST to MODIFIED > Fix pom.xml jpda profile and add ability to specify additional surefire forked JVM args via command line > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-5381 > URL: https://issues.jboss.org/browse/WFLY-5381 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 10.0.0.CR1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > Fix For: 10.0.0.CR4 > > > mvn install -Pjpda should run the tests with debugging enabled but it does not as the surefire.jpda.args property is ignored. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-273) ServerInventory#reconnectServer should take auto-start into account

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-273?page=com.atlassian.jira.plugin... ] Ken Wills edited comment on WFCORE-273 at 3/28/16 5:17 PM: ----------------------------------------------------------- Actually, I think I may have been able to figure out how to cause this (well, I mean "this" as in there are probably other states like this): (1) Start master & slave HCs (2) kill master HC (3) connect to slave HC and start a non-auto-start server (4) restart master HC (5) server shows up in master as disabled, but is running. *edit*, never mind, now it seems to be working. was (Author: luck3y): Actually, I think I may have been able to figure out how to cause this (well, I mean "this" as in there are probably other states like this): (1) Start master & slave HCs (2) kill master HC (3) connect to slave HC and start a non-auto-start server (4) restart master HC (5) server shows up in master as disabled, but is running. > ServerInventory#reconnectServer should take auto-start into account > ------------------------------------------------------------------- > > Key: WFCORE-273 > URL: https://issues.jboss.org/browse/WFCORE-273 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Emanuel Muckenhuber > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > When reconnecting to stopped (but not removed) servers, the ServerInventory should take the auto-start property into account. Otherwise the process will just get removed, however started with the next :reload of the HC. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (AS7-4441) JPA hibernate.cache.region_prefix property fails JConsole to connect to JBoss

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4441?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-4441: ---------------------------------------------- Sat6QE Jenkins <sat6-jenkins(a)redhat.com> changed the Status of [bug 1262401|https://bugzilla.redhat.com/show_bug.cgi?id=1262401] from POST to MODIFIED > JPA hibernate.cache.region_prefix property fails JConsole to connect to JBoss > ----------------------------------------------------------------------------- > > Key: AS7-4441 > URL: https://issues.jboss.org/browse/AS7-4441 > Project: Application Server 7 > Issue Type: Bug > Components: JMX, JPA / Hibernate, Server > Affects Versions: 7.1.1.Final > Environment: Windows Vista 64 bit, JDK 1.6.0_18 > Reporter: Osten Forshed > Assignee: Scott Marlow > Priority: Minor > Fix For: 7.1.2.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > > > If a web app is deployed (standalone) with a persistence.xml containing: > <property name="hibernate.cache.region_prefix" value=""/> > Then it is not possible to connect to the MBean Server with JConsole using instructions here: > https://community.jboss.org/wiki/UsingJconsoleToConnectToJMXOnAS7 > Following stack trace is written to JBoss log: > 12:27:03,406 WARN [org.jboss.remotingjmx.protocol.v1.ServerProxy] (pool-5-thread-16) Unexpected internal error: java.lang.NullPointerException > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) > at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) > at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39) > at org.jboss.as.jmx.model.ModelControllerMBeanHelper.queryNames(ModelControllerMBeanHelper.java:136) > at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.queryNames(ModelControllerMBeanServerPlugin.java:124) > at org.jboss.as.jmx.PluggableMBeanServerImpl.queryNames(PluggableMBeanServerImpl.java:280) > at org.jboss.remotingjmx.protocol.v1.ServerProxy$QueryNamesHandler.handle(ServerProxy.java:1197) > at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_18] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_18] > at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_18] > If property is removed from persistence.xml it is possible to connect using JConsole and browse the MBeans. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-5478) allow custom scoped persistence unit name hint in persistence unit definition

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5478?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5478: ----------------------------------------------- Sat6QE Jenkins <sat6-jenkins(a)redhat.com> changed the Status of [bug 1262401|https://bugzilla.redhat.com/show_bug.cgi?id=1262401] from POST to MODIFIED > allow custom scoped persistence unit name hint in persistence unit definition > ----------------------------------------------------------------------------- > > Key: WFLY-5478 > URL: https://issues.jboss.org/browse/WFLY-5478 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.1.1.Final, 8.0.0.Final, 9.0.0.Final, 10.0.0.CR2 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.CR3 > > > Consider allowing applications to override the scoped persistence unit name, so instead of using names like "test2.ear/w2.war#warPUnit_PU", the application can specify a unique (across all deployments on the app server) name. > The idea is that application deployments can include a persistence unit hint "jboss.as.jpa.scopedname" that specifies the unique scoped persistence unit name that will be used for several internal settings (e.g. hibernate.cache.region_prefix will be set to the scopedname value unless the application specifies a different hibernate.cache.region_prefix value). > The WildFly management console does not yet work with applications that specify the jboss.as.jpa.scopedname. Once this change is merged to WildFly, a management console change should be requested. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-273) ServerInventory#reconnectServer should take auto-start into account

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-273?page=com.atlassian.jira.plugin... ] Ken Wills edited comment on WFCORE-273 at 3/28/16 5:12 PM: ----------------------------------------------------------- Actually, I think I may have been able to figure out how to cause this (well, I mean "this" as in there are probably other states like this): (1) Start master & slave HCs (2) kill master HC (3) connect to slave HC and start a non-auto-start server (4) restart master HC (5) server shows up in master as disabled, but is running. was (Author: luck3y): Actually, I think I may have been able to figure out how to cause this: (1) Start master & slave HCs (2) kill master HC (3) connect to slave HC and start a non-auto-start server (4) restart master HC (5) server shows up in master as disabled, but is running. > ServerInventory#reconnectServer should take auto-start into account > ------------------------------------------------------------------- > > Key: WFCORE-273 > URL: https://issues.jboss.org/browse/WFCORE-273 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Emanuel Muckenhuber > Assignee: Ken Wills > Fix For: 3.0.0.Alpha1 > > > When reconnecting to stopped (but not removed) servers, the ServerInventory should take the auto-start property into account. Otherwise the process will just get removed, however started with the next :reload of the HC. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 March 2016