October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-882) Improve error message for bad/incomplete XML in deployment scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-882?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on WFLY-882: --------------------------------------- An additional INFO message saying that would be good. There's a specific method that detects malformed xml that could log that without any changes elsewhere. Note the message in the JIRA description is at INFO. > Improve error message for bad/incomplete XML in deployment scanner > ------------------------------------------------------------------ > > Key: WFLY-882 > URL: https://issues.jboss.org/browse/WFLY-882 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Filip Nguyen > Assignee: Tomaz Cerar > Priority: Trivial > Attachments: loop-vdb.xml > > > Deploying VDB with invalid XML (closed translator tag). Causes following error: > [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment standalone/deployments/loop-vdb.xml. Deployment changes will not be processed until all content is complete. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2413) UnsupportedOperationException in WeldComponentService#findManagedBeanForWSComponent

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-2413: ------------------------------------- Summary: UnsupportedOperationException in WeldComponentService#findManagedBeanForWSComponent Key: WFLY-2413 URL: https://issues.jboss.org/browse/WFLY-2413 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: CDI / Weld Reporter: Alessio Soldano Assignee: Stuart Douglas Fix For: 8.0.0.CR1 Attachments: jaxws-cxf-mixtype.war I'm getting a java.lang.UnsupportedOperationException when deploying one of the jbossws-cxf testsuite test archive (attached to the case). 17:17:31,212 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."jaxws-cxf-mixtype.war".component.Ep1Servlet.WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-cxf-mixtype.war".component.Ep1Servlet.WeldInstantiator: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1900) [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: java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableCollection$1.remove(Collections.java:1069) [rt.jar:1.7.0_17] at org.jboss.as.weld.injection.WeldComponentService.findManagedBeanForWSComponent(WeldComponentService.java:174) at org.jboss.as.weld.injection.WeldComponentService.start(WeldComponentService.java:129) 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] ... 3 more 17:17:31,235 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jaxws-cxf-mixtype.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator: Failed to start service Caused by: java.lang.UnsupportedOperationException"}} 17:17:31,238 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jaxws-cxf-mixtype.war" was rolled back with the following failure message: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator: Failed to start service Caused by: java.lang.UnsupportedOperationException"}} The problem is introduced by one of the commits in WFLY master listed at http://jbossws.jboss.org:8180/hudson/job/AS-8.0.0/267/changes -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2413) UnsupportedOperationException in WeldComponentService#findManagedBeanForWSComponent

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-2413?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-2413: ---------------------------------- Attachment: jaxws-cxf-mixtype.war > UnsupportedOperationException in WeldComponentService#findManagedBeanForWSComponent > ----------------------------------------------------------------------------------- > > Key: WFLY-2413 > URL: https://issues.jboss.org/browse/WFLY-2413 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Reporter: Alessio Soldano > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > Attachments: jaxws-cxf-mixtype.war > > > I'm getting a java.lang.UnsupportedOperationException when deploying one of the jbossws-cxf testsuite test archive (attached to the case). > 17:17:31,212 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."jaxws-cxf-mixtype.war".component.Ep1Servlet.WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-cxf-mixtype.war".component.Ep1Servlet.WeldInstantiator: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1900) [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: java.lang.UnsupportedOperationException > at java.util.Collections$UnmodifiableCollection$1.remove(Collections.java:1069) [rt.jar:1.7.0_17] > at org.jboss.as.weld.injection.WeldComponentService.findManagedBeanForWSComponent(WeldComponentService.java:174) > at org.jboss.as.weld.injection.WeldComponentService.start(WeldComponentService.java:129) > 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] > ... 3 more > 17:17:31,235 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jaxws-cxf-mixtype.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator: Failed to start service > Caused by: java.lang.UnsupportedOperationException"}} > 17:17:31,238 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jaxws-cxf-mixtype.war" was rolled back with the following failure message: > {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jaxws-cxf-mixtype.war\".component.Ep1Servlet.WeldInstantiator: Failed to start service > Caused by: java.lang.UnsupportedOperationException"}} > The problem is introduced by one of the commits in WFLY master listed at http://jbossws.jboss.org:8180/hudson/job/AS-8.0.0/267/changes -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2412: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> made a comment on [bug 1024930|https://bugzilla.redhat.com/show_bug.cgi?id=1024930] Yes is it a one line fix (two if you count the closing bracket of the if statement) ;-) Pull requests coming shortly. > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2412: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1024930|https://bugzilla.redhat.com/show_bug.cgi?id=1024930] from CLOSED to ASSIGNED > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2412: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 1024930|https://bugzilla.redhat.com/show_bug.cgi?id=1024930] Good catch Darran. I'm re-opening with a changed title. The fix is to remove those from the metadata. > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1717) Bundling reduces performance in scenario mimicking Inifinispan

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1717?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1717: -------------------------------- Added option to enable / disable DONT_BUNDLE for GETs and PUTs in UPerf. Preliminary tests with 4 members / 10 sender threads per member and each member sending 100'000 messages showed that *disabling DONT_BUNDLE* is a clear winner: +DONT_BUNDLE ca. 6'000 msgs/sec/node, -DONT_BUNDLE ca. 8'500 msgs/sec/node > Bundling reduces performance in scenario mimicking Inifinispan > -------------------------------------------------------------- > > Key: JGRP-1717 > URL: https://issues.jboss.org/browse/JGRP-1717 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.3 > Reporter: Radim Vansa > Assignee: Bela Ban > Fix For: 3.5 > > Attachments: benchmark-jgroups.xml, jgroups-udp.pdf, jgroups-udp.xml > > > In Radargun benchmark of JGroups mimicking the behaviour of Infinispan we can see that performance with bundling on actually reduces the performance. > See attached configurations and results. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2412: ----------------------------------- Summary: Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. (was: security realms and ldap connections incorrectly hidden by default in domain mode.) > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Running WildFly master in domain mode and connect using the CLI. > {code} > [domain@localhost:9990 /] :whoami(verbose=true) > { > "outcome" => "success", > "result" => { > "identity" => { > "username" => "$local", > "realm" => "ManagementRealm" > }, > "mapped-roles" => ["SuperUser"] > } > } > {code} > Although this shows the user has been authenticated against the ManagementRealm is apparently does not exist! > {code} > [domain@localhost:9990 /] ./core-service=management/security-realm=ManagementRealm:read-resource > { > "outcome" => "failed", > "failure-description" => "JBAS014807: Management resource '[ > (\"core-service\" => \"management\"), > (\"security-realm\" => \"ManagementRealm\") > ]' not found", > "rolled-back" => true > } > {code} > First impression is that access control is hiding a sensitive resource even though with the default config it should not. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2412: ----------------------------------- Description: Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. was: Running WildFly master in domain mode and connect using the CLI. {code} [domain@localhost:9990 /] :whoami(verbose=true) { "outcome" => "success", "result" => { "identity" => { "username" => "$local", "realm" => "ManagementRealm" }, "mapped-roles" => ["SuperUser"] } } {code} Although this shows the user has been authenticated against the ManagementRealm is apparently does not exist! {code} [domain@localhost:9990 /] ./core-service=management/security-realm=ManagementRealm:read-resource { "outcome" => "failed", "failure-description" => "JBAS014807: Management resource '[ (\"core-service\" => \"management\"), (\"security-realm\" => \"ManagementRealm\") ]' not found", "rolled-back" => true } {code} First impression is that access control is hiding a sensitive resource even though with the default config it should not. > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1129) Add VisualVm launch scripts to the AS7 distribution

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1129?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1129: ------------------------------- Assignee: (was: Jason Greene) > Add VisualVm launch scripts to the AS7 distribution > --------------------------------------------------- > > Key: WFLY-1129 > URL: https://issues.jboss.org/browse/WFLY-1129 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts > Environment: All > Reporter: John O'Hara > Priority: Trivial > > Launching VisualVM with remoting-jmx requires additional jars to be on the classpath, in the same way that launching jconsole does. > Can we provice a .sh and a .bat with the correct classpath in the AS7 distribution to launch visualvm -- 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

12 years, 8 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 October 2013