January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1135) Unable to start Wildfly when FIPS is enabled in Domain Mode

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1135?page=com.atlassian.jira.plugi... ] Jason Greene updated WFCORE-1135: --------------------------------- Fix Version/s: 2.0.8.Final (was: 2.0.7.Final) > Unable to start Wildfly when FIPS is enabled in Domain Mode > ----------------------------------------------------------- > > Key: WFCORE-1135 > URL: https://issues.jboss.org/browse/WFCORE-1135 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Affects Versions: 2.0.1.Final > Reporter: Ryan Emerson > Assignee: Darran Lofthouse > Fix For: 2.0.8.Final > > > Allow FIPS use in Domain mode. This requires additional logic to standalone, due to the connections between controllers and servers. > Resulting stacktrace when attempting to run domain mode with FIPS enabled at the JVM: > 15:47:39,410 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.host.controller.client: org.jboss.msc.service.StartException in service jboss.host.controller.client: java.io.IOException: WFLYSRV0117: Unable to initialise a basic SSLContext 'FIPS mode: only SunJSSE TrustManagers may be used' > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:133) > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [Server:server-one] at java.lang.Thread.run(Thread.java:745) > [Server:server-one] Caused by: java.io.IOException: WFLYSRV0117: Unable to initialise a basic SSLContext 'FIPS mode: only SunJSSE TrustManagers may be used' > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.getAcceptingSSLContext(HostControllerConnectionService.java:212) > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:108) > [Server:server-one] ... 5 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1084) Standalone powershell script does't support SECMGR=true environment variable

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1084?page=com.atlassian.jira.plugi... ] Jason Greene updated WFCORE-1084: --------------------------------- Fix Version/s: 2.0.8.Final (was: 2.0.7.Final) > Standalone powershell script does't support SECMGR=true environment variable > ---------------------------------------------------------------------------- > > Key: WFCORE-1084 > URL: https://issues.jboss.org/browse/WFCORE-1084 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.0.0.CR8 > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > Priority: Minor > Fix For: 2.0.8.Final > > > Standalone powershell script does't support SECMGR=true environment variable. Standalone script should enable security manager with this environment variable. Security manager can be enabled also by using -secmgr (this works correctly in EAP 7.0.0.DR13) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1299) IO Subsystem improperly shuts down the worker

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1299?page=com.atlassian.jira.plugi... ] Jason Greene resolved WFCORE-1299. ---------------------------------- Resolution: Done > IO Subsystem improperly shuts down the worker > --------------------------------------------- > > Key: WFCORE-1299 > URL: https://issues.jboss.org/browse/WFCORE-1299 > Project: WildFly Core > Issue Type: Bug > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 2.0.7.Final > > > The stop operation of the I/O subsystem's worker service should be asynchronous, and should not complete until the worker is fully shut down. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1292) SocketBindingManager.createMulticast/DatagramSocket(...) variants needed for unbound sockets

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1292?page=com.atlassian.jira.plugi... ] Jason Greene updated WFCORE-1292: --------------------------------- Fix Version/s: 2.0.8.Final (was: 2.0.7.Final) > SocketBindingManager.createMulticast/DatagramSocket(...) variants needed for unbound sockets > -------------------------------------------------------------------------------------------- > > Key: WFCORE-1292 > URL: https://issues.jboss.org/browse/WFCORE-1292 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 2.0.5.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 2.0.8.Final > > > In order to modify the SO_REUSEADDR option of a multicast or datagram socket, the socket must be unbound - otherwise the behavior is undefined. See: > http://docs.oracle.com/javase/8/docs/api/java/net/DatagramSocket.html#set... > To support this (as required for JGroups 3.6.7.Final), SocketBindingManager needs methods to create unbound datagram/multicast sockets. The current methods that accept a SocketAddress throw an ISE when a null address is used. > Setting priority to blocker to encourage inclusion into 2.0.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1283) Add version 4.1 of the domain management schema and bump the management model version.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1283?page=com.atlassian.jira.plugi... ] Jason Greene updated WFCORE-1283: --------------------------------- Fix Version/s: 2.0.8.Final (was: 2.0.7.Final) > Add version 4.1 of the domain management schema and bump the management model version. > -------------------------------------------------------------------------------------- > > Key: WFCORE-1283 > URL: https://issues.jboss.org/browse/WFCORE-1283 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.8.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1277) Embed-server from CLI launch shows twice prompt string

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1277?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFCORE-1277: ----------------------------------- Yes, I can see it now. Thanks. > Embed-server from CLI launch shows twice prompt string > ------------------------------------------------------ > > Key: WFCORE-1277 > URL: https://issues.jboss.org/browse/WFCORE-1277 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.5.Final > Reporter: Chao Wang > Assignee: Ståle Pedersen > Priority: Minor > > {noformat} > When I launch an embed-server from CLI, it displays twice [standalone@embedded /] [standalone@embedded /] for the first time. > [wangc@dhcp-128-40 wildfly-10.0.0.Final-SNAPSHOT]$ sh bin/jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server > [standalone@embedded /] [standalone@embedded /] ls > core-service launch-type=EMBEDDED product-version=undefined > deployment management-major-version=4 profile-name=undefined > deployment-overlay management-micro-version=0 release-codename=Kenny > extension management-minor-version=0 release-version=2.0.5.Final > interface name=dhcp-128-40 running-mode=ADMIN_ONLY > path namespaces=[] schema-locations=[] > socket-binding-group organization=undefined server-state=running > subsystem process-type=Server suspend-state=RUNNING > system-property product-name=undefined uuid=8c4ede2f-8e14-48bf-9eaf-73947e23edcf > [standalone@embedded /] quit > {noformat} > This does not happen in 2.0.4.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1277) Embed-server from CLI launch shows twice prompt string

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1277?page=com.atlassian.jira.plugi... ] Ståle Pedersen commented on WFCORE-1277: ---------------------------------------- hm, the pr wasnt updated as i could see so i just added that on line change myself. ive pushed out a new version of 0.66.3-SNAPSHOT if you want to try? > Embed-server from CLI launch shows twice prompt string > ------------------------------------------------------ > > Key: WFCORE-1277 > URL: https://issues.jboss.org/browse/WFCORE-1277 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.5.Final > Reporter: Chao Wang > Assignee: Ståle Pedersen > Priority: Minor > > {noformat} > When I launch an embed-server from CLI, it displays twice [standalone@embedded /] [standalone@embedded /] for the first time. > [wangc@dhcp-128-40 wildfly-10.0.0.Final-SNAPSHOT]$ sh bin/jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server > [standalone@embedded /] [standalone@embedded /] ls > core-service launch-type=EMBEDDED product-version=undefined > deployment management-major-version=4 profile-name=undefined > deployment-overlay management-micro-version=0 release-codename=Kenny > extension management-minor-version=0 release-version=2.0.5.Final > interface name=dhcp-128-40 running-mode=ADMIN_ONLY > path namespaces=[] schema-locations=[] > socket-binding-group organization=undefined server-state=running > subsystem process-type=Server suspend-state=RUNNING > system-property product-name=undefined uuid=8c4ede2f-8e14-48bf-9eaf-73947e23edcf > [standalone@embedded /] quit > {noformat} > This does not happen in 2.0.4.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1277) Embed-server from CLI launch shows twice prompt string

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1277?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFCORE-1277: ----------------------------------- Hi [~stalep] I have rebased the PR and added one more line "consoleBuffer.setPrompted(false);" when I re-opened it. This is missing in the push based on previous commit. > Embed-server from CLI launch shows twice prompt string > ------------------------------------------------------ > > Key: WFCORE-1277 > URL: https://issues.jboss.org/browse/WFCORE-1277 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.5.Final > Reporter: Chao Wang > Assignee: Ståle Pedersen > Priority: Minor > > {noformat} > When I launch an embed-server from CLI, it displays twice [standalone@embedded /] [standalone@embedded /] for the first time. > [wangc@dhcp-128-40 wildfly-10.0.0.Final-SNAPSHOT]$ sh bin/jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server > [standalone@embedded /] [standalone@embedded /] ls > core-service launch-type=EMBEDDED product-version=undefined > deployment management-major-version=4 profile-name=undefined > deployment-overlay management-micro-version=0 release-codename=Kenny > extension management-minor-version=0 release-version=2.0.5.Final > interface name=dhcp-128-40 running-mode=ADMIN_ONLY > path namespaces=[] schema-locations=[] > socket-binding-group organization=undefined server-state=running > subsystem process-type=Server suspend-state=RUNNING > system-property product-name=undefined uuid=8c4ede2f-8e14-48bf-9eaf-73947e23edcf > [standalone@embedded /] quit > {noformat} > This does not happen in 2.0.4.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1297) deploy --url command creates invalid deployment

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1297?page=com.atlassian.jira.plugi... ] Dominik Pospisil commented on WFCORE-1297: ------------------------------------------ I am sending very simple PR to strip leading '/' from deployment name which fixes this issue. Also, deploy --url=http://localhost/test/deployment0.war creates deployment named test/deployment0.war which will deploy with the default root context /test/deployment0 and works OK with the patch. However I am not sure if this is desired or if taking only the last part of the URL (deployment0) would be better. > deploy --url command creates invalid deployment > ----------------------------------------------- > > Key: WFCORE-1297 > URL: https://issues.jboss.org/browse/WFCORE-1297 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Affects Versions: 2.0.6.Final > Reporter: Martin Simka > Assignee: Dominik Pospisil > > Command {{deploy --url=http://localhost/test/simple-servlet.war}} > creates invalid deployment > According to logs everything seems to be fine > {noformat} > 15:03:57,505 INFO [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /tmp/jboss-eap-7.0/standalone/data/content/5e/5e5709be9a06a9ed7bcb2100a4143400fea887/content > 15:03:57,531 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "/test/simple-servlet.war" (runtime-name: "/test/simple-servlet.war") > 15:03:58,238 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Registered web context: //test/simple-servlet > 15:03:58,320 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "/test/simple-servlet.war" (runtime-name : "/test/simple-servlet.war") > {noformat} > but web context {{http://localhost:8080//test/simple-servlet}} isn't accessible, it returns {{404 - Not Found}}. > (simple-servlet.war doesn't contain jboss-web.xml, so no context root is defined there) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5607) EJB Server side is needlessly closing remoting channel

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-5607?page=com.atlassian.jira.plugin.... ] Brad Maxwell commented on WFLY-5607: ------------------------------------ Included in EAP 7.0.0.ER3-dev > EJB Server side is needlessly closing remoting channel > ------------------------------------------------------ > > Key: WFLY-5607 > URL: https://issues.jboss.org/browse/WFLY-5607 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.CR4 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 10.0.0.CR5 > > > When an EJB Bean throws a Runtime exception, it is causing the server side to close the remoting channel. This causes several issues such as performance issue of having to recreate the channel, channel leak on the client side and some occasional EJBCLIENT...25 - no ejb receiver exceptions on the client side. -- 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