6:17 a.m.
Paul Hinds created AS7-5759:
-------------------------------
Summary: monolithic config file and modules make deploying to JBossAS7 nasty
Key: AS7-5759
URL: https://issues.jboss.org/browse/AS7-5759
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Priority: Critical
Previous versions of JBoss could be configured by copying files to the correct place. Each
server in the cluster had identical config, this made configuring JBoss just a case of
running rsync with files that you had an interest in.
Consider jboss-log4j.xml which was one file you could copy to setup logging. Now to setup
logging we need to hack standalone.xml with XSLT or some tool that we dont yet have in our
simple deployment system.
Previously we could rsync a new file to each server in the cluster and it would apply the
new logging at runtime. Now we would have to updates standalone.xml at runtime which is
not something that seems safe.
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
Port bindings ditto.
JMS ditto.
Is there any way the monolithic config could be split up? most importantly bringing back
external runtime configurable log4j config.
--
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
7:22 a.m.
[
https://issues.jboss.org/browse/AS7-5759?page=com.atlassian.jira.plugin.s...
]
jaikiran pai updated AS7-5759:
------------------------------
Priority: Major (was: Critical)
monolithic config file and modules make deploying to JBossAS7 nasty
-------------------------------------------------------------------
Key: AS7-5759
URL: https://issues.jboss.org/browse/AS7-5759
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Previous versions of JBoss could be configured by copying files to the correct place.
Each server in the cluster had identical config, this made configuring JBoss just a case
of running rsync with files that you had an interest in.
Consider jboss-log4j.xml which was one file you could copy to setup logging. Now to setup
logging we need to hack standalone.xml with XSLT or some tool that we dont yet have in our
simple deployment system.
Previously we could rsync a new file to each server in the cluster and it would apply the
new logging at runtime. Now we would have to updates standalone.xml at runtime which is
not something that seems safe.
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
Port bindings ditto.
JMS ditto.
Is there any way the monolithic config could be split up? most importantly bringing back
external runtime configurable log4j config.
--
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
7:24 a.m.
[
https://issues.jboss.org/browse/AS7-5759?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-5759:
-----------------------------------
If this is just about logging configuration (which is what you are highlighting) then why
not just package the log4j configuration file within your application?
monolithic config file and modules make deploying to JBossAS7 nasty
-------------------------------------------------------------------
Key: AS7-5759
URL: https://issues.jboss.org/browse/AS7-5759
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Previous versions of JBoss could be configured by copying files to the correct place.
Each server in the cluster had identical config, this made configuring JBoss just a case
of running rsync with files that you had an interest in.
Consider jboss-log4j.xml which was one file you could copy to setup logging. Now to setup
logging we need to hack standalone.xml with XSLT or some tool that we dont yet have in our
simple deployment system.
Previously we could rsync a new file to each server in the cluster and it would apply the
new logging at runtime. Now we would have to updates standalone.xml at runtime which is
not something that seems safe.
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
Port bindings ditto.
JMS ditto.
Is there any way the monolithic config could be split up? most importantly bringing back
external runtime configurable log4j config.
--
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
7:26 a.m.
[
https://issues.jboss.org/browse/AS7-5759?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-5759:
-----------------------------------
{quote}
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
{quote}
You can still deploy -ds.xml in AS 7.1.x.
monolithic config file and modules make deploying to JBossAS7 nasty
-------------------------------------------------------------------
Key: AS7-5759
URL: https://issues.jboss.org/browse/AS7-5759
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Previous versions of JBoss could be configured by copying files to the correct place.
Each server in the cluster had identical config, this made configuring JBoss just a case
of running rsync with files that you had an interest in.
Consider jboss-log4j.xml which was one file you could copy to setup logging. Now to setup
logging we need to hack standalone.xml with XSLT or some tool that we dont yet have in our
simple deployment system.
Previously we could rsync a new file to each server in the cluster and it would apply the
new logging at runtime. Now we would have to updates standalone.xml at runtime which is
not something that seems safe.
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
Port bindings ditto.
JMS ditto.
Is there any way the monolithic config could be split up? most importantly bringing back
external runtime configurable log4j config.
--
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
7:28 a.m.
[
https://issues.jboss.org/browse/AS7-5759?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-5759:
-----------------------------------
{quote}
JMS ditto
{quote}
You can deploy JMS queues/topics too via individual deployment files instead of from the
managed subsystems.
Out of curiosity - Have you read the AS 7.1 admin and getting started guides? Whatever you
want to achieve can already be done via either individual deployment files or via CLI
scripting (an alternate approach to rsync) to setup your configurations.
monolithic config file and modules make deploying to JBossAS7 nasty
-------------------------------------------------------------------
Key: AS7-5759
URL: https://issues.jboss.org/browse/AS7-5759
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Previous versions of JBoss could be configured by copying files to the correct place.
Each server in the cluster had identical config, this made configuring JBoss just a case
of running rsync with files that you had an interest in.
Consider jboss-log4j.xml which was one file you could copy to setup logging. Now to setup
logging we need to hack standalone.xml with XSLT or some tool that we dont yet have in our
simple deployment system.
Previously we could rsync a new file to each server in the cluster and it would apply the
new logging at runtime. Now we would have to updates standalone.xml at runtime which is
not something that seems safe.
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
Port bindings ditto.
JMS ditto.
Is there any way the monolithic config could be split up? most importantly bringing back
external runtime configurable log4j config.
--
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
7:56 a.m.
[
https://issues.jboss.org/browse/AS7-5759?page=com.atlassian.jira.plugin.s...
]
Tomaz Cerar commented on AS7-5759:
----------------------------------
for syncing across server, you do not need that anymore.
As7 comes with domain mode that enables you to configure group of servers from one
location.
take a look at management documentation
https://docs.jboss.org/author/display/AS71/Core+management+concepts especially part about
"domain mode"
monolithic config file and modules make deploying to JBossAS7 nasty
-------------------------------------------------------------------
Key: AS7-5759
URL: https://issues.jboss.org/browse/AS7-5759
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Previous versions of JBoss could be configured by copying files to the correct place.
Each server in the cluster had identical config, this made configuring JBoss just a case
of running rsync with files that you had an interest in.
Consider jboss-log4j.xml which was one file you could copy to setup logging. Now to setup
logging we need to hack standalone.xml with XSLT or some tool that we dont yet have in our
simple deployment system.
Previously we could rsync a new file to each server in the cluster and it would apply the
new logging at runtime. Now we would have to updates standalone.xml at runtime which is
not something that seems safe.
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
Port bindings ditto.
JMS ditto.
Is there any way the monolithic config could be split up? most importantly bringing back
external runtime configurable log4j config.
--
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
11:34 a.m.
[
https://issues.jboss.org/browse/AS7-5759?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5759:
---------------------------------------
The port bindings can be customized on a per server basis via expressions (fka system
property substitution).
monolithic config file and modules make deploying to JBossAS7 nasty
-------------------------------------------------------------------
Key: AS7-5759
URL: https://issues.jboss.org/browse/AS7-5759
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Previous versions of JBoss could be configured by copying files to the correct place.
Each server in the cluster had identical config, this made configuring JBoss just a case
of running rsync with files that you had an interest in.
Consider jboss-log4j.xml which was one file you could copy to setup logging. Now to setup
logging we need to hack standalone.xml with XSLT or some tool that we dont yet have in our
simple deployment system.
Previously we could rsync a new file to each server in the cluster and it would apply the
new logging at runtime. Now we would have to updates standalone.xml at runtime which is
not something that seems safe.
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
Port bindings ditto.
JMS ditto.
Is there any way the monolithic config could be split up? most importantly bringing back
external runtime configurable log4j config.
--
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
11:36 a.m.
[
https://issues.jboss.org/browse/AS7-5759?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-5759:
----------------------------------
Component/s: Domain Management
monolithic config file and modules make deploying to JBossAS7 nasty
-------------------------------------------------------------------
Key: AS7-5759
URL: https://issues.jboss.org/browse/AS7-5759
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Previous versions of JBoss could be configured by copying files to the correct place.
Each server in the cluster had identical config, this made configuring JBoss just a case
of running rsync with files that you had an interest in.
Consider jboss-log4j.xml which was one file you could copy to setup logging. Now to setup
logging we need to hack standalone.xml with XSLT or some tool that we dont yet have in our
simple deployment system.
Previously we could rsync a new file to each server in the cluster and it would apply the
new logging at runtime. Now we would have to updates standalone.xml at runtime which is
not something that seems safe.
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
Port bindings ditto.
JMS ditto.
Is there any way the monolithic config could be split up? most importantly bringing back
external runtime configurable log4j config.
--
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
11:38 a.m.
[
https://issues.jboss.org/browse/AS7-5759?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5759:
---------------------------------------
I was tempted to resolve this as "Won't Fix" because we have no plans to
support a modularized config file (it's been considered and rejected a few times
already) and I don't expect that to change any time soon. But this is a valid feature
request, so I'm not going to do that. But you shouldn't expect this to change.
monolithic config file and modules make deploying to JBossAS7 nasty
-------------------------------------------------------------------
Key: AS7-5759
URL: https://issues.jboss.org/browse/AS7-5759
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Previous versions of JBoss could be configured by copying files to the correct place.
Each server in the cluster had identical config, this made configuring JBoss just a case
of running rsync with files that you had an interest in.
Consider jboss-log4j.xml which was one file you could copy to setup logging. Now to setup
logging we need to hack standalone.xml with XSLT or some tool that we dont yet have in our
simple deployment system.
Previously we could rsync a new file to each server in the cluster and it would apply the
new logging at runtime. Now we would have to updates standalone.xml at runtime which is
not something that seems safe.
Adding a DataSource used to be a case of copy driver jar to /lib, copy -ds.xml to /deploy
that process is now complicated.
Port bindings ditto.
JMS ditto.
Is there any way the monolithic config could be split up? most importantly bringing back
external runtime configurable log4j config.
--
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
4406
days inactive
4406
days old
8 comments
4 participants
participants (4)
-
Brian Stansberry (JIRA) -
jaikiran pai (JIRA)
-
Paul Hinds (JIRA)
-
Tomaz Cerar (JIRA)