[JBoss JIRA] (WFLY-6210) Example ec2/gossip server profiles do not have any modifications from the standard profiles (missing proper discovery protocols)
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6210?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6210:
---------------------------------
Summary: Example ec2/gossip server profiles do not have any modifications from the standard profiles (missing proper discovery protocols) (was: docs/examples/configs/ server profiles do not have any modifications from the standard profiles)
> Example ec2/gossip server profiles do not have any modifications from the standard profiles (missing proper discovery protocols)
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6210
> URL: https://issues.jboss.org/browse/WFLY-6210
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 10.1.0.Final
>
>
> [rhusar@syrah configs]$ diff -s standalone-ec2-full-ha.xml ../../../standalone/configuration/standalone-full-ha.xml
> Files standalone-ec2-full-ha.xml and ../../../standalone/configuration/standalone-full-ha.xml are identical
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6210) Example ec2/gossip server profiles do not have any modifications from the standard ha profiles (missing proper discovery protocols)
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6210?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6210:
---------------------------------
Summary: Example ec2/gossip server profiles do not have any modifications from the standard ha profiles (missing proper discovery protocols) (was: Example ec2/gossip server profiles do not have any modifications from the standard profiles (missing proper discovery protocols))
> Example ec2/gossip server profiles do not have any modifications from the standard ha profiles (missing proper discovery protocols)
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6210
> URL: https://issues.jboss.org/browse/WFLY-6210
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 10.1.0.Final
>
>
> [rhusar@syrah configs]$ diff -s standalone-ec2-full-ha.xml ../../../standalone/configuration/standalone-full-ha.xml
> Files standalone-ec2-full-ha.xml and ../../../standalone/configuration/standalone-full-ha.xml are identical
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6210) Example ec2/gossip server profiles do not have any modifications from the standard HA profiles (missing proper discovery protocols)
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6210?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6210:
---------------------------------
Summary: Example ec2/gossip server profiles do not have any modifications from the standard HA profiles (missing proper discovery protocols) (was: Example ec2/gossip server profiles do not have any modifications from the standard ha profiles (missing proper discovery protocols))
> Example ec2/gossip server profiles do not have any modifications from the standard HA profiles (missing proper discovery protocols)
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6210
> URL: https://issues.jboss.org/browse/WFLY-6210
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 10.1.0.Final
>
>
> [rhusar@syrah configs]$ diff -s standalone-ec2-full-ha.xml ../../../standalone/configuration/standalone-full-ha.xml
> Files standalone-ec2-full-ha.xml and ../../../standalone/configuration/standalone-full-ha.xml are identical
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6210) docs/examples/configs/ server profiles do not have any modifications from the standard profiles
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6210?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6210:
---------------------------------
Summary: docs/examples/configs/ server profiles do not have any modifications from the standard profiles (was: Example profiles tcpgossip and ec2 are unmodified standard profiles)
> docs/examples/configs/ server profiles do not have any modifications from the standard profiles
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-6210
> URL: https://issues.jboss.org/browse/WFLY-6210
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 10.1.0.Final
>
>
> [rhusar@syrah configs]$ diff -s standalone-ec2-full-ha.xml ../../../standalone/configuration/standalone-full-ha.xml
> Files standalone-ec2-full-ha.xml and ../../../standalone/configuration/standalone-full-ha.xml are identical
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6210) Example profiles tcpgossip and ec2 are unmodified standard profiles
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6210?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6210:
---------------------------------
Summary: Example profiles tcpgossip and ec2 are unmodified standard profiles (was: Example profiles like tcpgossip and ec2 are are unmodified standard profiles)
> Example profiles tcpgossip and ec2 are unmodified standard profiles
> -------------------------------------------------------------------
>
> Key: WFLY-6210
> URL: https://issues.jboss.org/browse/WFLY-6210
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 10.1.0.Final
>
>
> [rhusar@syrah configs]$ diff -s standalone-ec2-full-ha.xml ../../../standalone/configuration/standalone-full-ha.xml
> Files standalone-ec2-full-ha.xml and ../../../standalone/configuration/standalone-full-ha.xml are identical
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6210) Example profiles like tcpgossip and ec2 are are unmodified standard profiles
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-6210:
------------------------------------
Summary: Example profiles like tcpgossip and ec2 are are unmodified standard profiles
Key: WFLY-6210
URL: https://issues.jboss.org/browse/WFLY-6210
Project: WildFly
Issue Type: Bug
Components: Build System
Affects Versions: 10.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Critical
Fix For: 10.1.0.Final
[rhusar@syrah configs]$ diff -s standalone-ec2-full-ha.xml ../../../standalone/configuration/standalone-full-ha.xml
Files standalone-ec2-full-ha.xml and ../../../standalone/configuration/standalone-full-ha.xml are identical
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6209) Unable to specify custom configuration directory via -Djboss.server.config.dir
by Sergey Lisovoy (JIRA)
[ https://issues.jboss.org/browse/WFLY-6209?page=com.atlassian.jira.plugin.... ]
Sergey Lisovoy updated WFLY-6209:
---------------------------------
Steps to Reproduce:
1. Create file {{config-migration.cli}} with commands:
{code}
embed-server --admin-only --server-config=config.xml
/subsystem=messaging:migrate
/extension=org.jboss.as.messaging:remove
{code}
2. Try to execute from command line following:
{code}
/opt/wildfly-10.0.0.Final/bin/jboss-cli.sh -Djboss.server.config.dir=/opt/myapp/config --file=config-migration.cli
{code}
Produces error:
Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYCTL0214: Could not get main file: config.xml. Specified files must be relative to the configuration dir: /opt/wildfly-10.0.0.Final/standalone/configuration
was:
1. Create file with commands:
{code}
embed-server --admin-only --server-config=config.xml
/subsystem=messaging:migrate
/extension=org.jboss.as.messaging:remove
{code}
2. Try to execute from command line following:
{code}
/opt/wildfly-10.0.0.Final/bin/jboss-cli.sh -Djboss.server.config.dir=/opt/myapp/config --file=config-migration.cli
{code}
Produces error:
Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYCTL0214: Could not get main file: config.xml. Specified files must be relative to the configuration dir: /opt/wildfly-10.0.0.Final/standalone/configuration
> Unable to specify custom configuration directory via -Djboss.server.config.dir
> ------------------------------------------------------------------------------
>
> Key: WFLY-6209
> URL: https://issues.jboss.org/browse/WFLY-6209
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.CR5, 10.0.0.Final
> Reporter: Sergey Lisovoy
> Assignee: Jason Greene
>
> Broken support for server config files location customization via: {{jboss.server.config.dir}}.
> Previous Wildfly 10 versions till CR4 it works as expected. Broken since WF10.0.0.CR5
> See Steps to reproduce.
> Error:
> Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYCTL0214: Could not get main file: config.xml. Specified files must be relative to the configuration dir: /opt/wildfly-10.0.0.Final/standalone/configuration
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months