[JBoss JIRA] (WFLY-4238) Vault script not showing shared key
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-4238?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse reassigned WFLY-4238:
--------------------------------------
Assignee: Peter Skopek (was: Darran Lofthouse)
Peter, just passing your way - doesn't sound like a bug as the format of the String has been changed but maybe worth double checking the referenced doc and either duplicate it and create a link for WF 8 or make that doc applicable for both 7 and 8.
> Vault script not showing shared key
> -----------------------------------
>
> Key: WFLY-4238
> URL: https://issues.jboss.org/browse/WFLY-4238
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.1.0.Final
> Environment: Windows 7 with jdk1.7.0_51
> Reporter: Abhinav Gupta
> Assignee: Peter Skopek
>
> Team,
> while using vault.bat , we are not able to see shared key. For every password entered I get a key as : VAULT::test1::pas::1
> Below is console for vault.bat
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
> D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\bin>vault.bat
> =========================================================================
> JBoss Vault Tool
> JBOSS_HOME: "D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly"
> JAVA: "C:\jdk1.7.0_51\bin\java"
> JAVA_OPTS: ""
> =========================================================================
> **********************************
> **** JBoss Vault ***************
> **********************************
> Please enter a Digit:: 0: Start Interactive Session 1: Remove Interactive Session 2: Exit
> 0
> Starting an interactive session
> Enter directory to store encrypted files:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault
> Enter Keystore URL:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore
> Enter Keystore password:
> Enter Keystore password again:
> Values match
> Enter 8 character salt:12345678
> Enter iteration count as a number (e.g.: 44):50
> Enter Keystore Alias:vault
> Initializing Vault
> Jan 12, 2015 1:03:22 PM org.picketbox.plugins.vault.PicketBoxSecurityVault init
> INFO: PBOX000361: Default Security Vault Implementation Initialized and Ready
> Vault Configuration in WildFly configuration file:
> ********************************************
> ...
> </extensions>
> <vault>
> <vault-option name="KEYSTORE_URL" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-InRT5Cuu6V"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="50"/>
> <vault-option name="ENC_FILE_DIR" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\"/>
> </vault><management> ...
> ********************************************
> Vault is initialized and ready for use
> Handshake with Vault complete
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
> 0
> Task: Store a secured attribute
> Please enter secured attribute value (such as password):
> Please enter secured attribute value (such as password) again:
> Values match
> Enter Vault Block:test1
> Enter Attribute Name:pas
> Secured attribute value has been stored in Vault.
> Please make note of the following:
> ********************************************
> Vault Block:test1
> Attribute Name:pas
> Configuration should be done as follows:
> VAULT::test1::pas::1
> ********************************************
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4238) Vault script not showing shared key
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4238?page=com.atlassian.jira.plugin.... ]
Stuart Douglas reassigned WFLY-4238:
------------------------------------
Assignee: Darran Lofthouse (was: Stuart Douglas)
Component/s: Security
(was: Application Client)
I'm not really sure what you mean? Do you mean that the characters don't show up as you type them?
> Vault script not showing shared key
> -----------------------------------
>
> Key: WFLY-4238
> URL: https://issues.jboss.org/browse/WFLY-4238
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.1.0.Final
> Environment: Windows 7 with jdk1.7.0_51
> Reporter: Abhinav Gupta
> Assignee: Darran Lofthouse
>
> Team,
> while using vault.bat , we are not able to see shared key. For every password entered I get a key as : VAULT::test1::pas::1
> Below is console for vault.bat
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
> D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\bin>vault.bat
> =========================================================================
> JBoss Vault Tool
> JBOSS_HOME: "D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly"
> JAVA: "C:\jdk1.7.0_51\bin\java"
> JAVA_OPTS: ""
> =========================================================================
> **********************************
> **** JBoss Vault ***************
> **********************************
> Please enter a Digit:: 0: Start Interactive Session 1: Remove Interactive Session 2: Exit
> 0
> Starting an interactive session
> Enter directory to store encrypted files:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault
> Enter Keystore URL:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore
> Enter Keystore password:
> Enter Keystore password again:
> Values match
> Enter 8 character salt:12345678
> Enter iteration count as a number (e.g.: 44):50
> Enter Keystore Alias:vault
> Initializing Vault
> Jan 12, 2015 1:03:22 PM org.picketbox.plugins.vault.PicketBoxSecurityVault init
> INFO: PBOX000361: Default Security Vault Implementation Initialized and Ready
> Vault Configuration in WildFly configuration file:
> ********************************************
> ...
> </extensions>
> <vault>
> <vault-option name="KEYSTORE_URL" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-InRT5Cuu6V"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="50"/>
> <vault-option name="ENC_FILE_DIR" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\"/>
> </vault><management> ...
> ********************************************
> Vault is initialized and ready for use
> Handshake with Vault complete
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
> 0
> Task: Store a secured attribute
> Please enter secured attribute value (such as password):
> Please enter secured attribute value (such as password) again:
> Values match
> Enter Vault Block:test1
> Enter Attribute Name:pas
> Secured attribute value has been stored in Vault.
> Please make note of the following:
> ********************************************
> Vault Block:test1
> Attribute Name:pas
> Configuration should be done as follows:
> VAULT::test1::pas::1
> ********************************************
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFCORE-495) WFLY won't startup due to "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"xxx.war\")]"
by Chao Wang (JIRA)
Chao Wang created WFCORE-495:
--------------------------------
Summary: WFLY won't startup due to "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"xxx.war\")]"
Key: WFCORE-495
URL: https://issues.jboss.org/browse/WFCORE-495
Project: WildFly Core
Issue Type: Bug
Components: Server
Affects Versions: 1.0.0.Alpha15
Reporter: Chao Wang
Assignee: Chao Wang
WFLY won't startup due to "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"xxx.war\")]"
If you firstly deploy a .war application by CLI command, then deploy 2nd time same .war application by copying it to /depolyment directory. After server restart, it shows:
{noformat}
15:26:26,913 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha15) starting
15:26:27,133 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "xxx.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"xxx.war\")]"
15:26:27,136 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:26:27,138 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
15:26:27,153 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha15) stopped in 4ms
{noformat}
steps to reproduce:
1. start wildfly and deploy a .war application by CLI.
2. copy same .war application to /deployment directory
3. restart wildfly to see the error message.
This happens because step 2 does a "full-replace-deployment" operation which does not remove content from standalone/data/content/aa/2d0425dd53572294d591b56efdee2680539eaf/content and deployment info from configuration file(standalone.xml). Therefore, you will have xxx.war in standalone/data/content and configuration file(standalone.xml), also a xxx.war and xxx.war.deployed file inside /standalone/deployments. A second time server restart will cause a duplicate resource error.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4238) Vault script not showing shared key
by Abhinav Gupta (JIRA)
Abhinav Gupta created WFLY-4238:
-----------------------------------
Summary: Vault script not showing shared key
Key: WFLY-4238
URL: https://issues.jboss.org/browse/WFLY-4238
Project: WildFly
Issue Type: Bug
Components: Application Client
Affects Versions: 8.1.0.Final
Environment: Windows 7 with jdk1.7.0_51
Reporter: Abhinav Gupta
Assignee: Stuart Douglas
Team,
while using vault.bat , we are not able to see shared key. For every password entered I get a key as : VAULT::test1::pas::1
Below is console for vault.bat
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\bin>vault.bat
=========================================================================
JBoss Vault Tool
JBOSS_HOME: "D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly"
JAVA: "C:\jdk1.7.0_51\bin\java"
JAVA_OPTS: ""
=========================================================================
**********************************
**** JBoss Vault ***************
**********************************
Please enter a Digit:: 0: Start Interactive Session 1: Remove Interactive Session 2: Exit
0
Starting an interactive session
Enter directory to store encrypted files:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault
Enter Keystore URL:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore
Enter Keystore password:
Enter Keystore password again:
Values match
Enter 8 character salt:12345678
Enter iteration count as a number (e.g.: 44):50
Enter Keystore Alias:vault
Initializing Vault
Jan 12, 2015 1:03:22 PM org.picketbox.plugins.vault.PicketBoxSecurityVault init
INFO: PBOX000361: Default Security Vault Implementation Initialized and Ready
Vault Configuration in WildFly configuration file:
********************************************
...
</extensions>
<vault>
<vault-option name="KEYSTORE_URL" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore"/>
<vault-option name="KEYSTORE_PASSWORD" value="MASK-InRT5Cuu6V"/>
<vault-option name="KEYSTORE_ALIAS" value="vault"/>
<vault-option name="SALT" value="12345678"/>
<vault-option name="ITERATION_COUNT" value="50"/>
<vault-option name="ENC_FILE_DIR" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\"/>
</vault><management> ...
********************************************
Vault is initialized and ready for use
Handshake with Vault complete
Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
0
Task: Store a secured attribute
Please enter secured attribute value (such as password):
Please enter secured attribute value (such as password) again:
Values match
Enter Vault Block:test1
Enter Attribute Name:pas
Secured attribute value has been stored in Vault.
Please make note of the following:
********************************************
Vault Block:test1
Attribute Name:pas
Configuration should be done as follows:
VAULT::test1::pas::1
********************************************
Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4237) Disabling weld in wildfly strangely degrad JSF performance
by Mostafa Abdelkhalek (JIRA)
[ https://issues.jboss.org/browse/WFLY-4237?page=com.atlassian.jira.plugin.... ]
Mostafa Abdelkhalek commented on WFLY-4237:
-------------------------------------------
Can anyone re-produce this issue ?
> Disabling weld in wildfly strangely degrad JSF performance
> ----------------------------------------------------------
>
> Key: WFLY-4237
> URL: https://issues.jboss.org/browse/WFLY-4237
> Project: WildFly
> Issue Type: Bug
> Environment: wildfly 8.2.0.Final
> JSF 2.2
> Reporter: Mostafa Abdelkhalek
> Attachments: weld_disabled.png, weld_enabled.png
>
>
> The ajax response time dramatically increases by increasing the number of JSF components when weld is disabled.
> This doesn't make sense and I have no idea why does it occur
> *WELD ENABLED*
> !weld_enabled.png|thumbnail!
> *WELD DISABLED*
> !weld_disabled.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4237) Disabling weld in wildfly strangely degrad JSF performance
by Jozef Hartinger (JIRA)
[ https://issues.jboss.org/browse/WFLY-4237?page=com.atlassian.jira.plugin.... ]
Jozef Hartinger moved WELD-1835 to WFLY-4237:
---------------------------------------------
Project: WildFly (was: Weld)
Key: WFLY-4237 (was: WELD-1835)
> Disabling weld in wildfly strangely degrad JSF performance
> ----------------------------------------------------------
>
> Key: WFLY-4237
> URL: https://issues.jboss.org/browse/WFLY-4237
> Project: WildFly
> Issue Type: Bug
> Environment: wildfly 8.2.0.Final
> JSF 2.2
> Reporter: Mostafa Abdelkhalek
> Attachments: weld_disabled.png, weld_enabled.png
>
>
> The ajax response time dramatically increases by increasing the number of JSF components when weld is disabled.
> This doesn't make sense and I have no idea why does it occur
> *WELD ENABLED*
> !weld_enabled.png|thumbnail!
> *WELD DISABLED*
> !weld_disabled.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4158) The task-keepalive property in the domain:io subsystem is ignored causing an async servlet timeout at 30 seconds
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4158?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4158:
--------------------------------------
task-keepalive has nothing to do with this (it is how long a thread will stay around idle in the thread pool before being destroyed). The relevant IO timeouts are called read-timeout and write-timeout, however these only apply if you are attempting to perform IO and no IO activity happens in this much time.
It sounds like what you are actually hitting is the async servlet timeout, which defaults to 30s. You should make sure you call AsyncContext.setTimeout() to increase this (the 30s timeout is required by the servlet spec).
> The task-keepalive property in the domain:io subsystem is ignored causing an async servlet timeout at 30 seconds
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4158
> URL: https://issues.jboss.org/browse/WFLY-4158
> Project: WildFly
> Issue Type: Bug
> Components: IO
> Affects Versions: 8.2.0.Final
> Environment: Windows Server 2008, Windows 7, Java SE 7u72 and 8u25 64bit
> Reporter: Raul Guerrero Deschamps
> Assignee: Stuart Douglas
> Labels: asynchronous, servlet, timeout
>
> I have a file upload and download asynchronous servlet, I define a ReadListener and WriteListener to process the files.
> To be able to handle really large files, I setted a property in the IO subsystem to have the IO thread timeout at one hour using the task-keepalive property to avoid leaked threads if the request has a problem:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:io:1.1">
> <worker name="default" task-keepalive="3600"/>
> <buffer-pool name="default"/>
> </subsystem>
> {code}
> And also set the max-post-size property to the maximum to avoid limiting the size of the file, so you can upload files of any size as long as it only takes one hour, this is an intranet application so we don't have bandwidth issues or timeouts for the uploads and downloads.
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:undertow:1.2">
> <buffer-cache name="default"/>
> <server name="default-server">
> <http-listener name="default" socket-binding="http" max-post-size="0"/>
> ...
> {code}
> Now, this works perfectly on WildFly 8.1.0 Final, but I upgraded to 8.2.0, and even though I setted the same properties, I get an exception exactly at 30 seconds after a request for an upload or download:
> {noformat}
> ERROR [io.undertow.request] (default task-32) Undertow request failed HttpServerExchange{ PUT /xxx/file}: java.lang.NullPointerException
> Followed by:
> ERROR [org.xnio.listener] (default I/O-1) XNIO001007: A channel event listener threw an exception
> {noformat}
> Which is what happens when an I/O thread times out, so it causes the NullPointerException in the servlet because the IO thread is gone.
> Even though I set any time on the task-keepalive property, still the IO thread gets always killed at 30 seconds.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4158) The task-keepalive property in the domain:io subsystem is ignored causing an async servlet timeout at 30 seconds
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4158?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-4158.
----------------------------------
Resolution: Rejected
> The task-keepalive property in the domain:io subsystem is ignored causing an async servlet timeout at 30 seconds
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4158
> URL: https://issues.jboss.org/browse/WFLY-4158
> Project: WildFly
> Issue Type: Bug
> Components: IO
> Affects Versions: 8.2.0.Final
> Environment: Windows Server 2008, Windows 7, Java SE 7u72 and 8u25 64bit
> Reporter: Raul Guerrero Deschamps
> Assignee: Stuart Douglas
> Labels: asynchronous, servlet, timeout
>
> I have a file upload and download asynchronous servlet, I define a ReadListener and WriteListener to process the files.
> To be able to handle really large files, I setted a property in the IO subsystem to have the IO thread timeout at one hour using the task-keepalive property to avoid leaked threads if the request has a problem:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:io:1.1">
> <worker name="default" task-keepalive="3600"/>
> <buffer-pool name="default"/>
> </subsystem>
> {code}
> And also set the max-post-size property to the maximum to avoid limiting the size of the file, so you can upload files of any size as long as it only takes one hour, this is an intranet application so we don't have bandwidth issues or timeouts for the uploads and downloads.
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:undertow:1.2">
> <buffer-cache name="default"/>
> <server name="default-server">
> <http-listener name="default" socket-binding="http" max-post-size="0"/>
> ...
> {code}
> Now, this works perfectly on WildFly 8.1.0 Final, but I upgraded to 8.2.0, and even though I setted the same properties, I get an exception exactly at 30 seconds after a request for an upload or download:
> {noformat}
> ERROR [io.undertow.request] (default task-32) Undertow request failed HttpServerExchange{ PUT /xxx/file}: java.lang.NullPointerException
> Followed by:
> ERROR [org.xnio.listener] (default I/O-1) XNIO001007: A channel event listener threw an exception
> {noformat}
> Which is what happens when an I/O thread times out, so it causes the NullPointerException in the servlet because the IO thread is gone.
> Even though I set any time on the task-keepalive property, still the IO thread gets always killed at 30 seconds.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (JBAS-8767) Startup fails if a web-fragment.xml references fragment name that's not present
by Jason Peng (JIRA)
[ https://issues.jboss.org/browse/JBAS-8767?page=com.atlassian.jira.plugin.... ]
Jason Peng commented on JBAS-8767:
----------------------------------
Hi there,
i recently found the same exception on EAP 6.3. I'm wondering if the behaviour of AS being changed to terminate init process or bypass the unknown name?
(Restricted to jira-users group)
> Startup fails if a web-fragment.xml references fragment name that's not present
> -------------------------------------------------------------------------------
>
> Key: JBAS-8767
> URL: https://issues.jboss.org/browse/JBAS-8767
> Project: Application Server 3 4 5 and 6
> Issue Type: Bug
> Components: Web (Tomcat) service
> Affects Versions: 6.0.0.CR1
> Reporter: Dan Allen
> Assignee: Remy Maucherat
> Priority: Blocker
> Fix For: 6.0.0.Final
>
> Attachments: webfragref.war
>
>
> Application deployment should not fail if a web-fragment.xml references another fragment by name that isn't part of the deployment. That defeats the whole purpose of the relative ordering in the web-fragment.xml.
> For example, Seam Servlet needs to be ordered after Weld Servlet. So we define ordering the Seam Servlet web-fragment.xml as follows:
> <ordering>
> <after>
> <name>WeldServlet</name>
> </after>
> <before>
> <others/>
> </before>
> </ordering>
> However, we can't guarantee that Weld Servlet will be used. In that case, JBoss AS should just ignore the request.
> Here's the error that's appearing in the log:
> org.jboss.deployers.spi.DeploymentException: Invalid ordering
> Caused by: java.lang.IllegalStateException: Unknown name declared in JAR: seam-servlet-3.0.0-20101222.050701-2.jar
> at org.jboss.web.deployers.MergedJBossWebMetaDataDeployer.resolveOrder(MergedJBossWebMetaDataDeployer.java:711) [:6.0.0-SNAPSHOT]
> at org.jboss.web.deployers.MergedJBossWebMetaDataDeployer.deploy(MergedJBossWebMetaDataDeployer.java:306) [:6.0.0-SNAPSHOT]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years