January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1316) patch apply command not working as expected in non-interactive mode in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1316?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1316: ------------------------------------------------- Enrique Gonzalez Martinez <egonzale(a)redhat.com> changed the Status of [bug 1290290|https://bugzilla.redhat.com/show_bug.cgi?id=1290290] from ASSIGNED to POST > patch apply command not working as expected in non-interactive mode in domain mode > ----------------------------------------------------------------------------------- > > Key: WFCORE-1316 > URL: https://issues.jboss.org/browse/WFCORE-1316 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > > CLI patch apply command is misleading when the --host option is used. In non-interactive mode applies the patch to the local installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6060) Add --connection-properties to datasource add command

by Martin Simka (JIRA)

Martin Simka created WFLY-6060: ---------------------------------- Summary: Add --connection-properties to datasource add command Key: WFLY-6060 URL: https://issues.jboss.org/browse/WFLY-6060 Project: WildFly Issue Type: Enhancement Components: CLI, JCA Affects Versions: 10.0.0.CR5 Reporter: Martin Simka Assignee: Alexey Loubyansky It isn't possible to add connection-properties using {{datasource add}} command. They can be added after the DS is created by directly working on {{/subsystem=datasources/data-source=XX/connection-properties}} It would be nice to have parameter --connection-properties in datasource add command. It could work the same way as {{xa-data-source add --name=DS --xa-datasource-properties=}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1329) patch apply command not working as expected in non-interactive mode in domain mode

by Enrique González Martínez (JIRA)

Enrique González Martínez created WFCORE-1329: ------------------------------------------------- Summary: patch apply command not working as expected in non-interactive mode in domain mode Key: WFCORE-1329 URL: https://issues.jboss.org/browse/WFCORE-1329 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Enrique González Martínez Assignee: Enrique González Martínez CLI patch apply command is misleading when the --host option is used. In non-interactive mode applies the patch to the local installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4782) ; jsessionid= in URL not supported

by Francesco Pagetti (JIRA)

[ https://issues.jboss.org/browse/WFLY-4782?page=com.atlassian.jira.plugin.... ] Francesco Pagetti commented on WFLY-4782: ----------------------------------------- Well.. at the end I submitted a pull request on Jenkins to enable only cookie based sessions (https://github.com/jenkinsci/jenkins/pull/2003). ATM it looks like that the approach to deal with the problem is to disabling sessions in URL > ;jsessionid= in URL not supported > --------------------------------- > > Key: WFLY-4782 > URL: https://issues.jboss.org/browse/WFLY-4782 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.CR2 > Environment: Linux/jdk1.7/mysql > Reporter: Micheal Delson Nadar > Assignee: Stuart Douglas > Priority: Blocker > > I get the below url with jsessionid after logging in my application and get "Not Found" > http://xxx.yy.xxx.x:pppp/portal/;jsessionid=dDIsgr_KfIXFBmxvClAWbY2Z.wfst... > if i remove the ;jsessionid=dDIsgr_KfIXFBmxvClAWbY2Z.wfstandalone from url then it works fine... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3789) Vault cannot be initialized with external password provided by CLASS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3789?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3789: ----------------------------------------------- hwcert-private-xmlrpc(a)redhat.com changed the Status of [bug 1146006|https://bugweb-01.host.stage.eng.rdu2.redhat.com/show_bug.cgi?id=...] from POST to ASSIGNED > Vault cannot be initialized with external password provided by CLASS > --------------------------------------------------------------------- > > Key: WFLY-3789 > URL: https://issues.jboss.org/browse/WFLY-3789 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Filip Bogyai > Assignee: Peter Skopek > > When vault is configured to use external password obtained from CLASS, e.g. :{code:xml} <vault-option name="KEYSTORE_PASSWORD" value="{CLASS}org.jboss.security.plugins.TmpFilePassword:${java.io.tmpdir}/tmp.password"/> {code} > WildFly is unable to start, because of ClassNotFoundException: > {code} > 11:00:40,696 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("core-service" => "vault")]): java.lang.RuntimeException: WFLYSRV0076: Error initializing vault -- org.jboss.as.server.services.security.VaultReaderException: WFLYSEC0017: Vault Reader Exception: > at org.jboss.as.server.services.security.VaultAddHandler.performRuntime(VaultAddHandler.java:88) [wildfly-server-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:657) [wildfly-controller-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:498) [wildfly-controller-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:299) [wildfly-controller-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:294) [wildfly-controller-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1072) [wildfly-controller-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:375) [wildfly-controller-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:297) [wildfly-controller-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.server.ServerService.boot(ServerService.java:373) [wildfly-server-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.server.ServerService.boot(ServerService.java:348) [wildfly-server-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:259) [wildfly-controller-1.0.0.Alpha4.jar:1.0.0.Alpha4] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > Caused by: org.jboss.as.server.services.security.VaultReaderException: WFLYSEC0017: Vault Reader Exception: > at org.jboss.as.security.vault.RuntimeVaultReader.createVault(RuntimeVaultReader.java:99) [wildfly-security-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.server.services.security.VaultAddHandler.performRuntime(VaultAddHandler.java:86) [wildfly-server-1.0.0.Alpha4.jar:1.0.0.Alpha4] > ... 12 more > Caused by: org.jboss.security.vault.SecurityVaultException: java.lang.ClassNotFoundException: org.jboss.security.plugins.TmpFilePassword from [Module "org.jboss.as.controller:main" from local module loader @4be525ab > at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:210) [picketbox-4.0.21.Beta3.jar:4.0.21.Beta3] > at org.jboss.as.security.vault.RuntimeVaultReader.createVault(RuntimeVaultReader.java:97) [wildfly-security-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > ... 13 more > Caused by: java.lang.ClassNotFoundException: org.jboss.security.plugins.TmpFilePassword from [Module "org.jboss.as.controller:main" from local module loader @4be525ab > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final] > at org.jboss.security.Util.invokePasswordClass(Util.java:174) [picketbox-4.0.21.Beta3.jar:4.0.21.Beta3] > at org.jboss.security.Util.loadPassword(Util.java:126) [picketbox-4.0.21.Beta3.jar:4.0.21.Beta3] > at org.picketbox.plugins.vault.PicketBoxSecurityVault.loadKeystorePassword(PicketBoxSecurityVault.java:343) [picketbox-4.0.21.Beta3.jar:4.0.21.Beta3] > at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:204) [picketbox-4.0.21.Beta3.jar:4.0.21.Beta3] > ... 14 more > {code} > External passwords for vault were introduces by RFE: SECURITY-831 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4782) ; jsessionid= in URL not supported

by Francesco Pagetti (JIRA)

[ https://issues.jboss.org/browse/WFLY-4782?page=com.atlassian.jira.plugin.... ] Francesco Pagetti edited comment on WFLY-4782 at 1/25/16 12:20 AM: ------------------------------------------------------------------- I used incognito navigation, so no existing cookies/sessions and I'm using the default config of Tomcat so I think http sessions are cookie based by default. http://tomcat.apache.org/tomcat-8.0-doc/config/context.html attribute "cookies": Set to true if you want cookies to be used for session identifier communication if supported by the client (this is the default). Set to false if you want to disable the use of cookies for session identifier communication, and rely only on URL rewriting by the application.. FYI EAP 6 behaves exactly like Tomcat 8 by default. was (Author: pagio): Yep I'm using the default config of Tomcat and ,I think http sessions are cookie based by default. http://tomcat.apache.org/tomcat-8.0-doc/config/context.html attribute "cookies": Set to true if you want cookies to be used for session identifier communication if supported by the client (this is the default). Set to false if you want to disable the use of cookies for session identifier communication, and rely only on URL rewriting by the application.. FYI EAP 6 behaves exactly like Tomcat 8 by default. > ;jsessionid= in URL not supported > --------------------------------- > > Key: WFLY-4782 > URL: https://issues.jboss.org/browse/WFLY-4782 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.CR2 > Environment: Linux/jdk1.7/mysql > Reporter: Micheal Delson Nadar > Assignee: Stuart Douglas > Priority: Blocker > > I get the below url with jsessionid after logging in my application and get "Not Found" > http://xxx.yy.xxx.x:pppp/portal/;jsessionid=dDIsgr_KfIXFBmxvClAWbY2Z.wfst... > if i remove the ;jsessionid=dDIsgr_KfIXFBmxvClAWbY2Z.wfstandalone from url then it works fine... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4782) ; jsessionid= in URL not supported

by Francesco Pagetti (JIRA)

[ https://issues.jboss.org/browse/WFLY-4782?page=com.atlassian.jira.plugin.... ] Francesco Pagetti commented on WFLY-4782: ----------------------------------------- Yep I'm using the default config of Tomcat and ,I think http sessions are cookie based by default. http://tomcat.apache.org/tomcat-8.0-doc/config/context.html attribute "cookies": Set to true if you want cookies to be used for session identifier communication if supported by the client (this is the default). Set to false if you want to disable the use of cookies for session identifier communication, and rely only on URL rewriting by the application.. FYI EAP 6 behaves exactly like Tomcat 8 by default. > ;jsessionid= in URL not supported > --------------------------------- > > Key: WFLY-4782 > URL: https://issues.jboss.org/browse/WFLY-4782 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.CR2 > Environment: Linux/jdk1.7/mysql > Reporter: Micheal Delson Nadar > Assignee: Stuart Douglas > Priority: Blocker > > I get the below url with jsessionid after logging in my application and get "Not Found" > http://xxx.yy.xxx.x:pppp/portal/;jsessionid=dDIsgr_KfIXFBmxvClAWbY2Z.wfst... > if i remove the ;jsessionid=dDIsgr_KfIXFBmxvClAWbY2Z.wfstandalone from url then it works fine... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1257) support query filter implementation in MBeanServerConnection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1257?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1257: ------------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1294010|https://bugzilla.redhat.com/show_bug.cgi?id=1294010] from ASSIGNED to POST > support query filter implementation in MBeanServerConnection > ------------------------------------------------------------ > > Key: WFCORE-1257 > URL: https://issues.jboss.org/browse/WFCORE-1257 > Project: WildFly Core > Issue Type: Bug > Components: JMX > Affects Versions: 2.0.5.Final > Reporter: Chao Wang > Assignee: Brian Stansberry > Fix For: 2.0.8.Final > > > There is no implementation for query filter in MBeanServerConnection, marked as TODO > {code:title=ModelControllerMBeanHelper.java|borderStyle=solid} > Set<ObjectName> queryNames(final ObjectName name, final QueryExp query) { > return new RootResourceIterator<Set<ObjectName>>(accessControlUtil, getRootResourceAndRegistration().getResource(), > new ObjectNameMatchResourceAction<Set<ObjectName>>(name) { > Set<ObjectName> set = new HashSet<ObjectName>(); > @Override > public boolean onResource(ObjectName resourceName) { > if (name == null || name.apply(resourceName)) { > //TODO check query > set.add(resourceName); > } > return true; > } > @Override > public Set<ObjectName> getResult() { > if (set.size() == 1 && set.contains(ModelControllerMBeanHelper.createRootObjectName(domain))) { > return Collections.emptySet(); > } > return set; > } > }).iterate(); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6059) Migration for valves does not work properly

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-6059: ------------------------------------ Summary: Migration for valves does not work properly Key: WFLY-6059 URL: https://issues.jboss.org/browse/WFLY-6059 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas This currently has several issues, as valves are just migrated directly without regard for how configuration has changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6058) [Migration][WebToUndertow] CrawlerSessionManagerValve should be migrated rather to its wilfly config than general handler

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6058?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-2994 to WFLY-6058: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6058 (was: JBEAP-2994) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) (was: Migration) Target Release: (was: 7.0.0.GA) Affects Version/s: (was: 7.0.0.ER4) > [Migration][WebToUndertow] CrawlerSessionManagerValve should be migrated rather to its wilfly config than general handler > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6058 > URL: https://issues.jboss.org/browse/WFLY-6058 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Critical > > When migrating CrawlerSessionManagerValve, it is migrated to filter with filter-ref for the handler. The handler requires its CrawlerSessionManagerConfig in constructor, which is not provided in such case resulting in [1] thrown upon request. > The CrawlerSessionManagerValve should be rather migrated to its corresponding wildfly config => adding /subsystem=undertow/servlet-container=default/setting=crawler-session-management > {noformat} > 10:24:07,533 ERROR [io.undertow.request] (default I/O-3) UT005071: Undertow request failed HttpServerExchange{ GET / request {Accept=[*/*], User-Agent=[curl/7.43.0-DEV], Host=[127.0.0.1:8080]} response {}}: java.lang.RuntimeException: WFLYUT0064: Failed to configure handler class io.undertow.servlet.handlers.CrawlerSessionManagerHandler > at org.wildfly.extension.undertow.deployment.ConfiguredHandlerWrapper.wrap(ConfiguredHandlerWrapper.java:78) > at org.wildfly.extension.undertow.filters.CustomFilterDefinition.createHttpHandler(CustomFilterDefinition.java:100) > at org.wildfly.extension.undertow.filters.FilterService.createHttpHandler(FilterService.java:57) > at org.wildfly.extension.undertow.filters.FilterRef.createHttpHandler(FilterRef.java:69) > at org.wildfly.extension.undertow.LocationService.configureHandlerChain(LocationService.java:96) > at org.wildfly.extension.undertow.Host.configureRootHandler(Host.java:117) > at org.wildfly.extension.undertow.Host.getOrCreateRootHandler(Host.java:171) > at org.wildfly.extension.undertow.Host$HostRootHandler.handleRequest(Host.java:285) > at io.undertow.server.handlers.NameVirtualHostHandler.handleRequest(NameVirtualHostHandler.java:64) > at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:76) > at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49) > at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:158) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:229) > at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:127) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:145) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:92) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:51) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:121) > at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:580) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:464) > Caused by: java.lang.NoSuchMethodException: io.undertow.servlet.handlers.CrawlerSessionManagerHandler.<init>(io.undertow.server.HttpHandler) > at java.lang.Class.getConstructor0(Class.java:3082) > at java.lang.Class.getConstructor(Class.java:1825) > at org.wildfly.extension.undertow.deployment.ConfiguredHandlerWrapper.wrap(ConfiguredHandlerWrapper.java:55) > ... 24 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 January 2016