[PATCH] Service/subsystem welcome context proposal
by Jason T. Greene
Using the full war deployment chain for simple static welcome content is
overkill and adds around 600 ms to the boot on my system.
This patch accomplishes the same thing but instead uses a virtual-host
property (enable-welcome-root) to kick off a service that directly
constructs a static web context. This results in pretty much no
additional/measurable increase in our boot. It also fixes some problems
with error handling.
https://github.com/n1hility/jboss-as/commit/c4828e1a303a365aeb3683b7897b8...
If there are no objections, I'll ask that it be merged.
--
Jason T. Greene
JBoss, a division of Red Hat
14 years, 11 months
Two transaction manager feature requests for CR1
by Scott Stark
The following two feature requests for improving transaction subsystem configuration for environments like cloud providers are two I would like to get in next week for CR1. If there are no objections I'll assign these to myself and work on them.
Specify default values for the urn:jboss:domain:transaction object-store
------------------------------------------------------------------------
Key: AS7-775
URL:https://issues.jboss.org/browse/AS7-775
Project: Application Server 7
Issue Type: Feature Request
Components: Transactions
Affects Versions: 7.0.0.Beta3
Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: JBAS-9373
URL:https://issues.jboss.org/browse/JBAS-9373
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transaction Manager Integration (Arjuna)
Affects Versions: 7.0.0.Beta3
Reporter: Scott Stark
14 years, 11 months
Fwd: AS 7 Logging Management?
by Heiko Braun
> Heiko,
>
> Have anyone discussed with you logging management? Just wondering, because I would like to be able to do at least five things with jboss logging. First, I would like to be able to turn on and off CONSOLE logging. I would like to be able to go back and forth between ASYNC and SYNC logging. I would like to be able to change the log format. I would like to be able to change the log location, and finally, I would like to be able to change the log file attributes, like how large, and whether its a rolling log file or not.
>
> Just wondering if anything has happened around this stuff.
>
> Andy
AFAIKT, the isn't much yet.
Apart from the regular model operation (add,remove, etc) there is just:
"remove-root-logger",
"set-root-logger"
The description isn't very details as well:
[domain@localhost:9999 /] /profile=default/subsystem=logging:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "The configuration of the logging subsystem.",
"head-comment-allowed" => true,
"tail-comment-allowed" => true,
"namespace" => "urn:jboss:domain:logging:1.0",
"operations" => undefined,
"children" => {
"root-logger" => {"description" => "Defines the root logger for this log context."},
"handler" => {"description" => "The logging handler."}
}
},
"compensating-operation" => undefined
}
So, to answer your question: No I don't think the management use cases are covered.
But I can take a detailed look next week.
Ike
14 years, 11 months
ejb3 and ee subsystems
by Heiko Braun
there is no reasonable functionality, I tend to exclude these two for 7.0.Final:
[domain@localhost:9999 /] /profile=default/subsystem=ee:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {},
"compensating-operation" => undefined
}
[domain@localhost:9999 /] /profile=default/subsystem=ejb3:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {},
"compensating-operation" => undefined
}
14 years, 11 months
Web subsystem
by paulwerder＠fastmail.co.uk
Hi all,
just a straight question: what kind of Tomcat release will be used in
JBoss 7 ?
Log says
Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
However I couldn't find anything about Tomcat's server.xml file.
Thanks
Paul
--
paulwerder(a)fastmail.co.uk
--
http://www.fastmail.fm - The way an email service should be
14 years, 11 months
access to the ModelNodeRegistration during handling of an operation and during deployment
by Stefano Maestri
Hi All,
I'm trying to resume here the discussion I had yesterday on IRC with
Brian and Jesper.
Basically JCA needs to have and already deployed instance of
ResourceAdapter when adding its metrics and some operation. The reason
for that is because some operation and metrics availability are known
only at runtime, depending from RA status and/or vendor specific feature
known only.
Speaking from a Model point of view the basically issue is to have
access to the ModelNodeRegistration when the RA instance is created and
these runtime infos are available. There are 2 cases:
1) during handling ADD operation for a DataSource or special
ResourceAdapter creation withour rar deployment (like hornetQ).
2) during foo.rar deployment chain
We have also discussed where we can put these operation in the model
tree. Also in this case there are two possible places:
1) at subsystem level for special no-deployment RA (DataSources and
HornetQ atm). So we will obtain something like
/subsystem=datasource/data-source=myDS and /subsystem=hq/ra
2) at DUP level /deployment=foo.rar Having this deployment support we
can remove the current operation in /subsystem=resource-adapters that is
redudant, referring the same RA (or better a subset of deployed ones)
Hoping to have written all the matters discussed, feel free to integrate
and/or ask.
regards
S.
14 years, 11 months
sporadic testsuite failures
by Alexey Loubyansky
Is anybody looking into them? Is the issue in the AS codebase or the tests?
Most often it's a few ejb3 tests.
Thanks,
Alexey
14 years, 11 months
osgi subsystem management use cases
by Heiko Braun
Since OSGI is a beast on it's own, and does actually ship with custom management UI
I would like to postpone the integration with the JBoss7 management console to some release beyond 7.0.Final.
I would suggest we take the time to properly implement a replacement for the current (Felix?) console.
Please let me know if that works for you.
Ike
14 years, 11 months
Re: [jboss-as7-dev] TX subsystem management use cases
by Michael Musgrove
Can you clarify what it is that you need to know. I don't understand where these attributes are coming from nor what their values mean.
We do have various beans that we have, in the past, exposed via JMX or via RHQ. For example, consider the first attribute "core-environment" => .... I guess this is referring to our CoreEnvironment bean which does have a property called socketProcessIdPort which we use to facilitate creation of unique ids and it also has a property called nodeIdentifier which we use to ensure that different recovery managers don't end up recovering each others transactions. But there are also other properties in that bean which your snippet does not mention.
The enable-statistics property simply enables metrics gathering for transaction counts (heuristics, commits etc). Once enabled the statistics can be retrieved from our TxStats MBean.
Mike
----- Original Message -----
> > From: "Heiko Braun"<hbraun(a)redhat.com>
> > To:"jboss-as7-dev(a)lists.jboss.org Development" <jboss-as7-dev(a)lists.jboss.org>
> > Sent: Tuesday, May 10, 2011 9:07:24 AM
> > Subject: [jboss-as7-dev] TX subsystem management use cases
> >
> >
> >
> > Can anyone shed some light on the management op's for the transaction
> > subsystem?
> > The attribute names indicate more sophisticated features, like
> > statistics.
> >
> > I would need to know how to work with this data in order expose
> > reasonable functionality through the web UI.
> >
> > [domain@localhost:9999 /]
> > /profile=default/subsystem=transactions:read-resource(recursive=true)
> > {
> > "outcome" => "success",
> > "result" => {
> > "core-environment" => {
> > "socket-binding" => "txn-socket-process-id",
> > "node-identifier" => undefined
> > },
> > "recovery-environment" => {
> > "socket-binding" => "txn-recovery-environment",
> > "status-socket-binding" => "txn-status-manager"
> > },
> > "coordinator-environment" => {
> > "enable-statistics" => undefined,
> > "default-timeout" => undefined
> > },
> > "object-store" => {
> > "relative-to" => undefined,
> > "path" => undefined
> > }
> > },
> > "compensating-operation" => undefined
> > }
> >
>
14 years, 11 months
web subsystem management use cases
by Heiko Braun
Do any sophisticated web management sue cases exist?
To most if this looks like r/o data.
What about the "virtual-server" and "ssl" attributes?
[domain@localhost:9999 /] /profile=default/subsystem=web:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"configuration" => undefined,
"connector" => {"http" => {
"protocol" => "HTTP/1.1",
"socket-binding" => "http",
"scheme" => "http",
"virtual-server" => undefined,
"ssl" => undefined
}},
"virtual-server" => {"localhost" => {
"alias" => ["example.com"],
"access-log" => undefined,
"rewrite" => undefined
}}
},
"compensating-operation" => undefined
}
Ike
14 years, 11 months
