Preventing merge commits
by Jason T. Greene
If you want to prevent merge commits from ever entering a particular
branch of yours, say master, just do this:
git config branch.master.mergeoptions --ff-only
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
13 years, 10 months
Limiting Server Thread Usage
by Jason T. Greene
Moving to a new thread.
The big problem we run into with this is that almost every application
of a thread pool that we have needs to be highly tailored to its usage
to get the most optimal performance. So we end up with quite a few
different pools and it becomes difficult to impose a server wide limit.
There however some potential strategies we could take. Although I am
unsure as to how the overall effectiveness would be:
1. Sharing idle threads between pools
2. Force everything to go through a special blocking thread factory via
instrumentation of java.lang.Thread. Any attempt to allocate over the
max would lead to thread reclamation attempts and finally blocking until
a timeout is reached.
3. Some kind of auto-tuning weighting model. If the max total threads is
N, force all thread pools to use a percentage of N, potentially based on
establishing current config value divided by combined total.
One thing I wonder though is if cloud providers are "barking up the
wrong tree"? It seems a better limitation of an application is raw CPU
clock time and max memory usage. How they split that time into threads
doesn't really affect the scalability of the physical server, it's all
virtual process performance (who cares if someone wastes time context
switching?).
On 9/14/11 10:39 AM, Scott Stark wrote:
> The other big cross cutting concern is controlling the total number of
> threads in use by the application server. When running under a
> constrained environment that uses something like pam_limits module to
> control how many process(==java threads) a user can have, it is
> difficult to know what the server max thread usage is right now.
>
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
13 years, 11 months
Testsuite update
by Ondřej Žižka
Hi everyone,
as was discussed on this list, the current testsuite harness had some
problems fulfilling even basic requirements for various use cases,
including but not limited to:
* Using from IDE through pure maven
* -DallTests vs. individial modules vs. distinctive groups vs. even
overlaying groups
* Configuring AS using kind of hierarchical templates
* Imposing certain test groups order
* Invoking only some steps of the testsuite
* Running same tests with different AS configuration
etc etc.
I've been working on an updated concept, which is currently at
https://github.com/OndraZizka/jboss-as/commits/TS-modules-tmp .
I would like you to review it, run it, and send me some comments.
cd testsuite/integration
mvn clean install -f pom2.xml -DallTests -fae
mvn clean install -f pom2.xml -Dts.iiop
(There are 2 pom.xml's so I can compare two harnesses easily.)
The scripts are not updated yet so they do not work.
CLI and OSGi tests fail. To be sorted out.
The big news are:
* Execution split to modules
* Code and resources remained in the same location
* Added few system properties which provide paths to important
directories - see https://docs.jboss.org/author/display/AS71/AS+7
+Testsuite+Test+Developer+Guide
* Work directory is now in target/workdir
These cahnges exposed some issues in test code which need to be fixed -
hardcoded relative paths.
Since there were no system properties to use, there was no other way,
but from now on please use those properties, and fix your existing
tests.
(This would happen anyway because some tests clutter workdir (which
happens to be module's root dir) with various temp files.)
Thanks,
Ondra
14 years, 2 months
AS7-1807
by Paul Gier
I started working on a way to modularize the product name and version in
the startup/shutdown logs of AS7 [1][2]. There is a new module called
"product" which contains the product name and version. However this
approach doesn't seem good to me because the "host-controller",
"process-controller", and "server" modules all now have dependencies on
this new module.
Ideally, I want to set this up so that there is sort of a placeholder
product name/version used during the build or these modules, but then
this can be overridden by the product module later in the build. Anyone
have suggestions about how to do this?
Thanks!
[1]https://github.com/pgier/jboss-as/commits/AS7-1807
[2]https://issues.jboss.org/browse/AS7-1807
14 years, 4 months
Access to public API jars from (remote) client applications
by Jaikiran Pai
I'm writing up the documentation for invoking remote EJBs from a
(really) remote application like standalone Java applications. One of
the things that we have to decide about is how we want the users to
access some of our public API jars (I'm not calling this "client" jars
since one of the previous discussions around this suggested that it
would confuse things). Right now we don't have a way where users can
*easily* add these public API jars to their classpath. Some of the
requirements that I can think of are:
1) These jars must be available at a well known location within the AS
distribution. i.e. the users shouldn't have to drill down into
individual module path to find the jars.
2) The jar names shouldn't contain the version names (since that will
require changes to client scripts if some API jar version changes)
3) Modular environment on the client side is not a requirement. i.e. the
client application should just be able add these jars to their classpath
and use them
4) IDE and build tool requirements should be taken into account
separately. i.e. a "bom" or some other IDE specific way of getting
access to these API jars _shouldn't_ be the only way of referencing
these jars.
5) Identifying the public API jars
Thoughts? Is this something that we could target for 7.1 Beta1?
-Jaikiran
14 years, 4 months
Quickstarts unused/undeclared dependencies
by Paul Gier
The quickstarts currently have some possibly incorrect dependencies.
For example, using "mvn dependency:analyze" against the helloworld
quickstart reports the following dependency warnings. Should these be
fixed, or is there a reason to keep it as is?
[WARNING] Used undeclared dependencies found:
[WARNING] javax.inject:javax.inject:jar:1:provided
[WARNING] Unused declared dependencies found:
[WARNING] javax.enterprise:cdi-api:jar:1.0-SP4:provided
[WARNING]
org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar:1.0.0.Final:provided
14 years, 4 months
JBWEB CLIENT_CERT in web.xml, why?
by Radoslaw Rodak
Hello
I wrote custom Authenticator Valve which extends BaseAuthenticator. We have some legacy stuff...
I also have jboss-web.xml which reference this custome Valve and the Configured Security Realm in AS7.
Every thing is working fine, but only if I put in web.xml
<auth-method>CLIENT_CERT</auth-method>
when I put
<auth-method>CLIENT-CERT</auth-method>
My custom Valve is never called.
I see in Jboss AS7 stdout message about "no security constrain".
With CLIENT_CERT it works....
Mabe someone can give me a hint what I'm missing...
I wonder why I need CLIENT_CERT instead of CLIENT-CERT....
Radek Rodak
14 years, 4 months
