January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Issue Comment Edited: (JGRP-100) Large-scale JGroups

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-100?page=com.atlassian.jira.plugin.s... ] Bela Ban edited comment on JGRP-100 at 1/5/11 3:51 AM: ------------------------------------------------------- When we have many nodes in a cluster, the header overhead becomes bigger. E.g. a UUID address is 17 bytes (2 longs + 1 byte). If we have 100 nodes, a View for example is ca 1700 bytes ! A Digest might be even bigger, as it contains addresses and low/high seqnos ! If we have a small MTU (like in Infiniband (2048 bytes !), then we need to add FRAG just on top of the transport. The goal here is to make header and address overhead smaller. Headers by using IDs (shorts) for protocol names rather than strings. Addresses by using canonicalization ("ID" protocol), and replacing UUIDs with shorts. This is https://issues.jboss.org/browse/JGRP-931. However, as JGRP-931 didn't yield any perf improvements (albeit on small clusters), I closed JGRP-931. Might be re-opened later. was (Author: bela(a)jboss.com): When we have many nodes in a cluster, the header overhead becomes bigger. E.g. a UUID address is 17 bytes (2 longs + 1 byte). If we have 100 nodes, a View for example is ca 1700 bytes ! A Digest might be even bigger, as it contains addresses and low/high seqnos ! If we have a small MTU (like in Infiniband (2048 bytes !), then we need to add FRAG just on top of the transport. The goal here is to make header and address overhead smaller. Headers by using IDs (shorts) for protocol names rather than strings. Addresses by using canonicalization ("ID" protocol), and replacing UUIDs with shorts. > Large-scale JGroups > ------------------- > > Key: JGRP-100 > URL: https://issues.jboss.org/browse/JGRP-100 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.0 > > > - Run JGroups on hundreds of nodes (either physical, or simulation). > - Determine a protocol stack that can be used for large-scale execution > - Example: > - Coordinator may be SPOF. If coord is hung, messages will be sent, but no new views will > be generated > - Retransmission: retransmit from anyone (not sender, otherwise we have NAK implosion) > - Look at PBCAST -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMETA-326) Class-level @Asynchronous should only apply to the declared methods on the class

by Andrew Rubinger (JIRA)

Class-level @Asynchronous should only apply to the declared methods on the class -------------------------------------------------------------------------------- Key: JBMETA-326 URL: https://issues.jboss.org/browse/JBMETA-326 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: ejb Affects Versions: jboss-metadata-ejb-2.0.0-alpha-27 Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: jboss-metadata-ejb-2.0.0-alpha-28 Currently we're employing a "*" strategy applying to every business method of the bean. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-546) CLONE - org.jboss.security.plugins.FilePassword requires write permission for decoding

by Brad Maxwell (JIRA)

CLONE - org.jboss.security.plugins.FilePassword requires write permission for decoding -------------------------------------------------------------------------------------- Key: SECURITY-546 URL: https://issues.jboss.org/browse/SECURITY-546 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.1-BETA1, 2.0.1-BETA2, 2.0.2-BETA3, 2.0.2-BETA4, 2.0.2-BETA5, 2.0.2-BETA6, 2.0.2.Beta7, 2.0.2.CR2, 2.0.2.CR3, 2.0.2.CR4, 2.0.2.CR5, 2.0.2.CR6, 2.0.2.CR7, 2.0.2.CR8 Environment: JBoss AS 4.2.3.GA Reporter: Brad Maxwell Assignee: Marcus Moyses Priority: Minor Fix For: JBossSecurity_2.0.4.SP4, PicketBox_v4_0_alpha3 Attachments: SECURITY-292.patch We use org.jboss.security.plugins.FilePassword to avoid storing passwords in clear text. Once created, we'd like to change the file's permission to read-only for regular users in order to ensure that only trusted users can update it. However, this won't work as the class FilePassword always requires write permission even for decoding the password. The class should be modified so that write permission is only required when create / update the password file. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBRULES-2863) Tuple is null when firing an activation

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2863?page=com.atlassian.jira.plug... ] Edson Tirelli updated JBRULES-2863: ----------------------------------- Component/s: drools-core > Tuple is null when firing an activation > --------------------------------------- > > Key: JBRULES-2863 > URL: https://issues.jboss.org/browse/JBRULES-2863 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core > Affects Versions: 5.1.1.FINAL > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Priority: Critical > Fix For: 5.2.0.M1 > > > For some reason, an activation is firing with a nulled tuple, i.e., it seems the activation is being created, but not properly removed from the agenda. There are not many details but the rule in question uses both ruleflow-group and no-loop. > Reported by Dan Quinn. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-269) Use default domain as parent in AbstractClassLoadingDomainDeployer by default

by Ales Justin (JIRA)

Use default domain as parent in AbstractClassLoadingDomainDeployer by default ----------------------------------------------------------------------------- Key: JBDEPLOY-269 URL: https://issues.jboss.org/browse/JBDEPLOY-269 Project: JBoss Deployers Issue Type: Feature Request Components: classloading Affects Versions: JBDEPLOY-2.2.0.Alpha6 Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.2.0.Beta1 We should use DefaultDomain as parent by default in AbstractClassLoadingDomainDeployer. e.g. if there is no explicit parent defined -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBDEPLOY-269) Use default domain as parent in AbstractClassLoadingDomainDeployer by default

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/JBDEPLOY-269?page=com.atlassian.jira.plug... ] Ales Justin updated JBDEPLOY-269: --------------------------------- JBoss Forum Reference: http://community.jboss.org/message/578690#578690 > Use default domain as parent in AbstractClassLoadingDomainDeployer by default > ----------------------------------------------------------------------------- > > Key: JBDEPLOY-269 > URL: https://issues.jboss.org/browse/JBDEPLOY-269 > Project: JBoss Deployers > Issue Type: Feature Request > Components: classloading > Affects Versions: JBDEPLOY-2.2.0.Alpha6 > Reporter: Ales Justin > Assignee: Ales Justin > Fix For: JBDEPLOY-2.2.0.Beta1 > > > We should use DefaultDomain as parent by default in AbstractClassLoadingDomainDeployer. > e.g. if there is no explicit parent defined -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8784) Fix EAR and WAR CL default wrt existing ClassLoadingDomainMetaData

by Ales Justin (JIRA)

Fix EAR and WAR CL default wrt existing ClassLoadingDomainMetaData ------------------------------------------------------------------ Key: JBAS-8784 URL: https://issues.jboss.org/browse/JBAS-8784 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading, Deployers Affects Versions: 6.0.0.Final Reporter: Ales Justin Assignee: Ales Justin Fix For: 6.0.1 With ClassLoadingDomainMetaData present in deployment, we need to adjust the ear and war defaults accordingly. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-685) Perf test

by Bela Ban (JIRA)

Perf test --------- Key: JGRP-685 URL: http://jira.jboss.com/jira/browse/JGRP-685 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 Things to do with the perf test: - Mimick buddy replication: send messages not to self, but only to a selected buddy - Measure time to send 100MB to A, B, C, D - New look at HTOTAL, might help with perf in this scenario - TcpTransport (95MB/sec) versus JGroupsTransport/tcp.xml (54MB/sec): why the diff ? - Members: A (send), B (receive) - Might get better perf with impl of first bullet item (above) - JPerf (between A and B) gets 113MB/sec ! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
12
0 / 0

[JBoss JIRA] Created: (JBAS-8344) System Properties not being parsed in -ds.xml

by Nishanth Alphonse (JIRA)

System Properties not being parsed in -ds.xml --------------------------------------------- Key: JBAS-8344 URL: https://jira.jboss.org/browse/JBAS-8344 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-5.1.0.GA Reporter: Nishanth Alphonse Assignee: Scott M Stark Hi There, Please note the following thread: http://www.coderanch.com/t/506538/JBoss/System-properties-reading-them-co... Looks like the issue from https://jira.jboss.org/browse/JBAS-4585 has not been fixed for version jboss5.1.0-jdk6? Thanks, Nishanth -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

5
4
0 / 0

[JBoss JIRA] Updated: (JBAS-8783) Server fails to start if JAVA_HOME is not set

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBAS-8783?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated JBAS-8783: ----------------------------------- JBoss Forum Reference: http://community.jboss.org/thread/160463?tstart=0 > Server fails to start if JAVA_HOME is not set > --------------------------------------------- > > Key: JBAS-8783 > URL: https://issues.jboss.org/browse/JBAS-8783 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 7.0.0.Alpha1 > Reporter: Brian Stansberry > Priority: Critical > Fix For: 7.0.0.Alpha2 > > > If I there is no JAVA_HOME I see the following error and more importantly - the server freezes and can not be stopped unlesss I manually kill -9 the process. Same happens on HEAD. > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /Users/vladimirralev/Downloads/jboss-7.0.0.Alpha1 > JAVA: java > JAVA_OPTS: > ========================================================================= > Cannot run Java in 64 bit mode. Continuing in 32 bit mode. > 16:22:08,757 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.0.Beta11 > 16:22:09,203 INFO [org.jboss.as.process.Server Manager.status] (main) Starting process 'Server Manager' > [Server Manager] Cannot run Java in 64 bit mode. Continuing in 32 bit mode. > [Server Manager] 16:22:09,589 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.0.Beta11 > [Server Manager] 16:22:10,258 INFO [org.jboss.as.domain.controller] (Thread-3) Starting Domain Controller > [Server Manager] 16:22:10,322 INFO [org.jboss.as.domain.controller] (Thread-3) Parsing Domain Configuration > [Server Manager] 16:22:11,165 INFO [org.jboss.as.server.manager] (Thread-3) Starting server server-three > 16:22:11,260 INFO [org.jboss.as.process.Server:server-three.status] (pool-2-thread-2) Starting process 'Server:server-three' > 16:22:11,279 ERROR [org.jboss.as.process.Server:server-three.status] (pool-2-thread-2) Failed to start process 'Server:server-three': java.io.IOException: Cannot run program "/Users/vladimirralev/Downloads/jboss-7.0.0.Alpha1/java" (in directory "/Users/vladimirralev/Downloads/jboss-7.0.0.Alpha1"): error=2, No such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) [:1.6.0_22] > at org.jboss.as.process.ManagedProcess.doStart(ManagedProcess.java:151) > at org.jboss.as.process.ManagedProcess.start(ManagedProcess.java:129) > at org.jboss.as.process.ProcessManager.startProcess(ProcessManager.java:143) > at org.jboss.as.process.ProcessManagerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessManagerServerHandler.java:160) > at org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:239) > at org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:198) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] > at java.lang.Thread.run(Thread.java:680) [:1.6.0_22] > Caused by: java.io.IOException: error=2, No such file or directory > at java.lang.UNIXProcess.forkAndExec(Native Method) [:1.6.0_22] > at java.lang.UNIXProcess.<init>(UNIXProcess.java:53) [:1.6.0_22] > at java.lang.ProcessImpl.start(ProcessImpl.java:91) [:1.6.0_22] > at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) [:1.6.0_22] > ... 9 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 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 January 2011