Location of server write dirs in a managed domain
by Brian Stansberry
This relates to https://issues.jboss.org/browse/AS7-2342, particularly
Fernando Nasser's comment thereon.
By default in a managed domain we store each server's writable
directories (data, log, and tmp) underneath domain/server/<server-name>.
The proposal is to provide an option(1) to instead group the output
based on the type of output:
domain/data/servers/<server-name>
domain/tmp/servers/<server-name>
domain/log/servers/<server-name>
I'm fine with that as long as it's easy to configure. Users could
configure this now using a bunch of <system-property> elements in each
host.xml <server> element, but that's not a practical solution
A think a single piece of configuration in host.xml is sufficient to
control this (i.e. there is no need to independently configure it for
each server.
<host>
....
<servers group-server-output-by-type="true">
<server ...>
The DMR representation would be an attribute on the root resource for
the host (e.g. on /host=xyz).
If anyone has a better name for the attribute, I'd love to hear it.
(1) An option because the current directory structure has been in place
for over a year and 4 final releases now.
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
14 years, 1 month
JNDI Resource Dependencies
by Rob Cernich
Hey all,
I was wondering if a non-JEE application needed to do anything special in its deployment if the application makes use of any JNDI resources (e.g. queues)? Specifically, do I need to add service dependencies on those JNDI entries in the deployer?
Thanks in advance,
Rob
14 years, 1 month
Source RPMs
by Peter Larsen
I'm looking for the source RPMs for at least jbossas*.rpm. Somehow
they're just not available through our normal channels - or at least I'm
unable to get them using yumdownloader. What is the best way to get a
hold of the src RPMs for the JBossAS channel?
--
Regards,
Peter Larsen, RHCE
Solutions Architect
JBoss by Red Hat
Email: plarsen(a)redhat.com
Phone: 540 738 0733
14 years, 1 month
No Debuggers
by Darran Lofthouse
Now that we are at a point that we are a bit more focussed on fixing
bugs than developing new features could I suggest that we try to resolve
issues only using the configuration and logging.
At this point I think we need to be sure that we can understand issues
in remote installations that we have no access to where the log files
are the only view as to what is happening.
Regards,
Darran Lofthouse.
14 years, 1 month
Do you need property substitutions in XSLT-augmented configs?
by Ondrej Zizka
Currently, during XSLT transformation,
<socket-binding name="management-native" interface="management"
port="${jboss.management.native.port:9999}"/>
becomes
<socket-binding name="management-native" interface="management"
port="<new-value>"/>
Is it ok or do you need it to be
<socket-binding name="management-native" interface="management"
port="${jboss.management.native.port:<new-value>}"/>
?
Ondra
14 years, 1 month
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, 1 month
Lifecycle notifications on AS7
by Klaus Benary
Hi all,
in earlier versions of the JBoss AS we could register to the server
(jboss.system:type=Server) and/or to deployers
(jboss.system:service=MainDeployer, jboss.system:service=JARDeployer,
jboss.j2ee:service=EARDeployer) in order to receive notifications on
server startup, server shutdown, and application status changes. Is
there any way to achieve this or something similar on AS7?
Thanks in advance.
Klaus Benary
14 years, 1 month
jboss-cli.bat with Thunder: Duplicate argument '--command'/'--commands'.
by Panzer, Robert
Hi,
just tried the final version and wanted to execute a cli script using jboss-cli.bat.
But jboss-cli.bat my.cli fails with:
Duplicate argument '--command'/'--commands'.
Is there anyone else having the same problem?
The effective Java call in jboss-cli.bat is
"c:\Program Files\Java\jdk1.6.0_29\bin\java" -Dprogram.name=jboss-cli.bat -jar "e:\git\jboss-as\build\target\jboss-as-7.1.0.Final\jboss-modules.jar" -mp "e:\git\jboss-as\build
\target\jboss-as-7.1.0.Final\modules" org.jboss.as.cli -c --file deployDataSource.cli
Duplicate argument '--command'/'--commands'.type
My cli file currently contains only:
/subsystem=datasources/xa-data-source="MY_XA_DATASOURCE":disable
This worked in any case with commit ID 945edc.
Kind regards,
Robert
WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193
Diese E-Mail enthält vertrauliche Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.
This e-mail may contain confidential information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
14 years, 1 month
