October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2400) org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase fails

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-2400?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-2400: --------------------------------------- I was running smoke test with "-DnoWebProfile". If I omit this option, problem disappears. So test seems to be not compatible with full profile. > org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase fails > --------------------------------------------------------------------- > > Key: WFLY-2400 > URL: https://issues.jboss.org/browse/WFLY-2400 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server, Test Suite > Affects Versions: 8.0.0.Beta1 > Environment: Solaris SPARC 10, Oracle Java 1.7.0_45 > Reporter: Frank Langelage > Assignee: Stefano Maestri > Attachments: org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase-output.txt, org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase.txt > > > Running a build of current sources with complete testsuite this test is failing with > testValidateModel(org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase): The model failed validation -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2401) org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase fails

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-2401?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-2401: --------------------------------------- I was running smoke test with "-DnoWebProfile". If I omit this option, problem disappears. So test seems to be not compatible with full profile. > org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase fails > -------------------------------------------------------------- > > Key: WFLY-2401 > URL: https://issues.jboss.org/browse/WFLY-2401 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Environment: Solaris SPARC 10, Oracle Java 1.7.0_45 > Reporter: Frank Langelage > Assignee: Ondrej Zizka > Attachments: org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase.txt > > > Running a build of current sources with complete testsuite this test is failing with > testReadAttributeWildcards(org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase) -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2399) org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase fails

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-2399?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-2399: --------------------------------------- I was running smoke test with "-DnoWebProfile". If I omit this option, problem disappears. So test seems to be not compatible with full profile. > org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase fails > -------------------------------------------------------------------- > > Key: WFLY-2399 > URL: https://issues.jboss.org/browse/WFLY-2399 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA, Test Suite > Affects Versions: 8.0.0.Beta1 > Environment: Solaris SPARC 10, Oracle Java 1.7.0_45 > Reporter: Frank Langelage > Assignee: Stefano Maestri > Attachments: org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase-output.txt, org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase.txt > > > Running a build of current sources with complete testsuite this test is failing with > testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase): expected:<1> but was:<2> -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2417) Support URL Connection Factory Resource Injection

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-2417: ------------------------------------- Summary: Support URL Connection Factory Resource Injection Key: WFLY-2417 URL: https://issues.jboss.org/browse/WFLY-2417 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: EE Reporter: Eduardo Martins Assignee: Eduardo Martins Wildfly needs to support URL Connection Factories @Resource injection, such as: {code:java} @Resource(lookup="http://www.wildfly.org") private URL url; {code} -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2416) Deployment fails with Atmosphere (probable regression from WFLY-2333)

by John Teller (JIRA)

John Teller created WFLY-2416: --------------------------------- Summary: Deployment fails with Atmosphere (probable regression from WFLY-2333) Key: WFLY-2416 URL: https://issues.jboss.org/browse/WFLY-2416 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Undertow) Affects Versions: 8.0.0.CR1 Environment: wildfly-8.0.0.Beta2-SNAPSHOT build #762 Atmosphere-runtime 2.0.3 Reporter: John Teller Assignee: Stuart Douglas Deploying a WAR file containing atmosphere-runtime jar fails with the following error: 14:16:33,411 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."jboss-as-helloworld.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jboss-as-helloworld.war" .INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "jboss-as-helloworld.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8. 0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017327: Deployment error processing SCI for jar: atmosphere-runtime-2.0.3.jar at org.wildfly.extension.undertow.deployment.ServletContainerInitializerDeploymentProcessor.loadSci(ServletContainerInitializerDeploymentProcessor.java:205) at org.wildfly.extension.undertow.deployment.ServletContainerInitializerDeploymentProcessor.deploy(ServletContainerInitializerDeploymentProcessor.java:128) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT] ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017327: Deployment error processing SCI for jar: atmosphere-runtime-2.0.3.jar at org.wildfly.extension.undertow.deployment.ServletContainerInitializerDeploymentProcessor.loadSci(ServletContainerInitializerDeploymentProcessor.java:197) ... 7 more Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0 at java.lang.String.charAt(String.java:658) [rt.jar:1.7.0_17] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:435) [jboss-modules.jar:1.3.0.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) [jboss-modules.jar:1.3.0.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) [jboss-modules.jar:1.3.0.Final] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) [jboss-modules.jar:1.3.0.Final] at org.wildfly.extension.undertow.deployment.ServletContainerInitializerDeploymentProcessor.loadSci(ServletContainerInitializerDeploymentProcessor.java:190) ... 7 more -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2415) Add configuration option to enable/disable Infinispan statistics

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2415?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2415: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1025023 > Add configuration option to enable/disable Infinispan statistics > ---------------------------------------------------------------- > > Key: WFLY-2415 > URL: https://issues.jboss.org/browse/WFLY-2415 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Scott Marlow > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > When the Infinispan MBean is enabled, Infinispan statistics are enabled by default. Could we allow Infinispan statistics to be enabled/disabled via a WF configuration setting? -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2415) Add configuration option to enable/disable Infinispan statistics

by Scott Marlow (JIRA)

Scott Marlow created WFLY-2415: ---------------------------------- Summary: Add configuration option to enable/disable Infinispan statistics Key: WFLY-2415 URL: https://issues.jboss.org/browse/WFLY-2415 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Clustering Reporter: Scott Marlow Assignee: Paul Ferraro Fix For: 8.0.0.CR1 When the Infinispan MBean is enabled, Infinispan statistics are enabled by default. Could we allow Infinispan statistics to be enabled/disabled via a WF configuration setting? -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1487) AUTH: X509Token Authentication is vulnerable to replay attacks

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/JGRP-1487?page=com.atlassian.jira.plugin.... ] Divya Mehra updated JGRP-1487: ------------------------------ Labels: jdg620_dm jdg62GAblocker (was: jdg620_dm) > AUTH: X509Token Authentication is vulnerable to replay attacks > -------------------------------------------------------------- > > Key: JGRP-1487 > URL: https://issues.jboss.org/browse/JGRP-1487 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.0.9 > Reporter: sreenivas chinimilli > Assignee: Bela Ban > Labels: jdg620_dm, jdg62GAblocker > Fix For: 3.5 > > > In the implementation of X509Token Authentication > The auth_value is enrypted with the certificate within the keystore and > during verification encrypted auth value is decrypted with the private key > compared against the orignial auth value. > This implementation is prone to replay attacks, that is > any user with out having any knowledge of the auth value can join the group > by replaying the enrypted auth value captured in earlier sessions. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1721) AUTH and ENCRYPT protocols configured with plain text passwords

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/JGRP-1721?page=com.atlassian.jira.plugin.... ] Divya Mehra updated JGRP-1721: ------------------------------ Labels: jdg620_dm jdg62GAblocker (was: jdg620_dm) > AUTH and ENCRYPT protocols configured with plain text passwords > --------------------------------------------------------------- > > Key: JGRP-1721 > URL: https://issues.jboss.org/browse/JGRP-1721 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Labels: jdg620_dm, jdg62GAblocker > Fix For: 3.5 > > > The following parameters of AUTH protocol are stored as plain text: > * keystore_password > The following parameters of ENCRYPT protocol are stored as plain text: > * store_password > * key_password > Example: > {code} > <ENCRYPT key_store_name="defaultStore.keystore" store_password="changeit" alias="myKey"/> > {code} > Requirements for storing passwords: https://docspace.corp.redhat.com/docs/DOC-131628 -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1722) Improve performance of ENCRYPT protocol

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/JGRP-1722?page=com.atlassian.jira.plugin.... ] Divya Mehra updated JGRP-1722: ------------------------------ Labels: jdg620_dm jdg62GAblocker (was: jdg620_dm) > Improve performance of ENCRYPT protocol > --------------------------------------- > > Key: JGRP-1722 > URL: https://issues.jboss.org/browse/JGRP-1722 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Labels: jdg620_dm, jdg62GAblocker > Fix For: 3.5 > > > A stress tests with the following setup showed that performance (reads and writes/sec) is halved when ENCRYPT protocol is enabled: > Infinispan had distributed sync cache with 2 owners on 4 nodes, no transactions. The stress test used 10 threads on each node accessing 1024 byte entries, no conflicts on keys, 20 % writes, 80 % reads. > It would be great if we could improve the performance of ENCRYPT protocol. -- 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

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013