October 2013 - jboss-jira - Jboss List Archives

[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

10 years, 7 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

10 years, 7 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

10 years, 7 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

10 years, 7 months

1
0
0 / 0

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

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-882?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned WFLY-882: --------------------------------- Assignee: Tomaz Cerar > 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

10 years, 7 months

1
0
0 / 0

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

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-882?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-882: ------------------------------ Labels: (was: jug_hackathon_candidate) > 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 > 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) security realms and ldap connections incorrectly hidden by default 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] In that case probably a bad resource definition exposing those resources at domain level. > security realms and ldap connections incorrectly hidden by default 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

10 years, 7 months

1
0
0 / 0

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

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-882?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-882: ------------------------------ Estimated Difficulty: Medium > 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 > 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1675) Threads stuck in FlowControl.decrementIfEnoughCredits

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1675?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1675 at 10/30/13 12:00 PM: ----------------------------------------------------------- Tried to replicate the stress test in JGroups ({{RemoteGetStressTest}} is attached). With 500 threads, the tests completes between 60 and 90 seconds. This is with a random delay de-serializing the BigObject between 1 and 10 ms, and with a DISCARD up-rate of 20%. If {{USE_SLEEPS}} is changed to false, the test finishes within a few seconds (between 2 and 5 secs). This is with an OOB pool of min=1/max=5/no-queue. The delaying and discarding certainly slows things down, but I never experienced a deadlock. was (Author: belaban): Tried to replicate the stress test in JGroups (RemoteGetStressTest ia attached). With 500 threads, the tests completes within 60 and 90 seconds. This is with a random delay de-serializing the BigObject between 1 and 10 ms, and with a DISCARD up-rate of 20%. If {{USE_SLEEPS}} is changed to false, the test finishes within a few second (between 2 and 5 secs). This is with an OOB pool of min=1/max=5/no-queue. The delaying and discarding certainly slows things downm, but I never experience a deadlock. > Threads stuck in FlowControl.decrementIfEnoughCredits > ----------------------------------------------------- > > Key: JGRP-1675 > URL: https://issues.jboss.org/browse/JGRP-1675 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4 > Reporter: Radim Vansa > Assignee: Bela Ban > Fix For: 3.5 > > Attachments: RemoteGetStressTest.java > > > I have recently observed a repeated situation where many (or all) threads have been stuck waiting for credits in FlowControl protocol. > The credit request was not handled on the other node as this is non-oob message and some (actually many of them - cause unknown) messages before the request have been lost - therefore the request was waiting for them to be re-sent. > However, these have not been re-sent properly as the retransmission request was not received - all OOB threads were stuck in the FlowControl protocol as these handled some other request and tried to send a response - but the response could not be sent until FlowControl gets the credits. > The probability of such situation could be lowered by tagging the credit request to be OOB - then it would be handled immediately. If the credit replenish message would then be processed in regular OOB pool, this could get already depleted by many requests, but setting up the internal thread pool would solve the problem. > Other consideration would be to allow releasing thread from FlowControl (let it send the message even without credits) if it waits there for too long. > h3. Workaround > It appears that setting MFC and UFC max_credits to 10M or removing these protocols at all is a workaround for this issue. -- 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-882) Improve error message for bad/incomplete XML in deployment scanner

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-882?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-882: ------------------------------ Summary: Improve error message for bad/incomplete XML in deployment scanner (was: Deploying dynamic VDB with invalid XML will cause incomprehensible error) Labels: jug_hackathon_candidate (was: ) We could improve the error by saying something like "blah.xml is not well-formed waiting in case it is an incomplete copy." > 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 > Priority: Trivial > Labels: jug_hackathon_candidate > 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

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