[arquillian-issues] [JBoss JIRA] (ARQ-1183) Allow the use of non-blocking random number generators for deployments against WebLogic Servers
Vineet Reynolds (JIRA)
jira-events at lists.jboss.org
Sat Nov 3 15:45:18 EDT 2012
[ https://issues.jboss.org/browse/ARQ-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vineet Reynolds updated ARQ-1183:
---------------------------------
Description:
The WLS container adapter forks a {{weblogic.Deployer}} task that runs in a separate JVM. This may result in timeouts on Unix/Linux machines where /dev/random does not provide sufficient entropy in a limited period of time. This eventually results in random and inexplicable failures during deployment or undeployment of archives when connecting to an AdminServer through a SSL channel. The stacktraces usually contain errors with the message "java.io.IOException: Stream closed.; No available router to destination".
Allow for configuring /dev/urandom as a PRNG source.
was:
The WLS container adapter forks a {{weblogic.Deployer}} task that runs in a separate JVM. This may result in timeouts on Unix/Linux machines where /dev/random does not provide sufficient entropy in a limited period of time. This eventually results in random and inexplicable failures during deployment or undeployment of archives when connecting to an AdminServer through a SSL channel.
Allow for configuring /dev/urandom as a PRNG source.
> Allow the use of non-blocking random number generators for deployments against WebLogic Servers
> -----------------------------------------------------------------------------------------------
>
> Key: ARQ-1183
> URL: https://issues.jboss.org/browse/ARQ-1183
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: WebLogic Containers
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
> Priority: Minor
> Fix For: wls_1.0.0.next
>
>
> The WLS container adapter forks a {{weblogic.Deployer}} task that runs in a separate JVM. This may result in timeouts on Unix/Linux machines where /dev/random does not provide sufficient entropy in a limited period of time. This eventually results in random and inexplicable failures during deployment or undeployment of archives when connecting to an AdminServer through a SSL channel. The stacktraces usually contain errors with the message "java.io.IOException: Stream closed.; No available router to destination".
> Allow for configuring /dev/urandom as a PRNG source.
--
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
More information about the arquillian-issues
mailing list