[JBoss JIRA] (WFLY-1610) clueter full-ha
by Emilio Navarrete (JIRA)
Emilio Navarrete created WFLY-1610:
--------------------------------------
Summary: clueter full-ha
Key: WFLY-1610
URL: https://issues.jboss.org/browse/WFLY-1610
Project: WildFly
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 8.0.0.Alpha2
Environment: Ubuntu Server 12.04LST 64bits
Reporter: Emilio Navarrete
Assignee: Brian Stansberry
two or more server on the same full-ha profile cause this error:
[Server:server-fourth] 22:42:10,205 ERROR [org.hornetq.core.server] (Old I/O server worker (parentId: 427107561, [id: 0x197524e9, /0.0.0.0:5945])) HQ224018: Failed to create session: HornetQException[errorType=SECURITY_EXCEPTION message=HQ119031: Unable to validate user: HORNETQ.CLUSTER.ADMIN.USER]
there was an workaround but it stop working since jboss as 7.3:
<subsystem xmlns="urn:jboss:domain:messaging:1.2">
<hornetq-server>
<cluster-user>admin</cluster-user>
<cluster-password>admin1</cluster-password>
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1381) OSGi: "Web-ContextPath" header is not supported to install/start WAB bundle from repository
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1381?page=com.atlassian.jira.plugin.... ]
Thomas Diesler commented on WFLY-1381:
--------------------------------------
Unfortunately yes (for non-technical reason)
> OSGi: "Web-ContextPath" header is not supported to install/start WAB bundle from repository
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-1381
> URL: https://issues.jboss.org/browse/WFLY-1381
> Project: WildFly
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 8.0.0.Alpha2
> Reporter: Igor Shulika
>
> I am using the latest WildFly 8.0.0.Alpha2-SNAPSHOT server to install/start all of my OSGi bundles from Maven repository. The WAB is not starting if I am just declare capability in the standalone-osgi.xml file.
>
> Here is my capability configuration.
> <capability name="org.test.sample.webapp:my-sample-webapp:1.0" startlevel="4"/>
>
> Note: When I just simply drop my WAB file inside "deployments" directory the web application starting successfully.
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1609) Remove references to osgi from domain test suite
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1609?page=com.atlassian.jira.plugin.... ]
Thomas Diesler updated WFLY-1609:
---------------------------------
Description:
{code}
[tdiesler@localhost domain]$ git grep osgi
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", returnVal.asSt
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", profile.asStri
src/test/java/org/jboss/as/test/integration/domain/suites/ReadEnvironmentVariablesTestCase.java: env = getEnvironmentVariables(
src/test/resources/domain-configs/domain-standard.xml: <extension module="org.jboss.as.osgi"/>
src/test/resources/domain-configs/domain-standard.xml: <profile name="osgi">
src/test/resources/domain-configs/domain-standard.xml: <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
src/test/resources/domain-configs/domain-standard.xml: <property name="org.osgi.framework.startlevel.beginning">1</prop
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.osgi.logging" startlevel="1"/>
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group name="osgi-sockets" default-interface="public">
src/test/resources/domain-configs/domain-standard.xml: <server-group name="other-server-group" profile="osgi">
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group ref="osgi-sockets"/>
src/test/resources/host-configs/host-slave.xml: <socket-bindings socket-binding-group="osgi-sockets" port-offset="550"/>
{code}
was:
{code}
[tdiesler@localhost domain]$ gti grep osgi
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", returnVal.asSt
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", profile.asStri
src/test/java/org/jboss/as/test/integration/domain/suites/ReadEnvironmentVariablesTestCase.java: env = getEnvironmentVariables(
src/test/resources/domain-configs/domain-standard.xml: <extension module="org.jboss.as.osgi"/>
src/test/resources/domain-configs/domain-standard.xml: <profile name="osgi">
src/test/resources/domain-configs/domain-standard.xml: <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
src/test/resources/domain-configs/domain-standard.xml: <property name="org.osgi.framework.startlevel.beginning">1</prop
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.osgi.logging" startlevel="1"/>
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group name="osgi-sockets" default-interface="public">
src/test/resources/domain-configs/domain-standard.xml: <server-group name="other-server-group" profile="osgi">
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group ref="osgi-sockets"/>
src/test/resources/host-configs/host-slave.xml: <socket-bindings socket-binding-group="osgi-sockets" port-offset="550"/>
[tdiesler@localhost domain]$ git grep osgi
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", returnVal.asSt
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", profile.asStri
src/test/java/org/jboss/as/test/integration/domain/suites/ReadEnvironmentVariablesTestCase.java: env = getEnvironmentVariables(
src/test/resources/domain-configs/domain-standard.xml: <extension module="org.jboss.as.osgi"/>
src/test/resources/domain-configs/domain-standard.xml: <profile name="osgi">
src/test/resources/domain-configs/domain-standard.xml: <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
src/test/resources/domain-configs/domain-standard.xml: <property name="org.osgi.framework.startlevel.beginning">1</prop
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.osgi.logging" startlevel="1"/>
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group name="osgi-sockets" default-interface="public">
src/test/resources/domain-configs/domain-standard.xml: <server-group name="other-server-group" profile="osgi">
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group ref="osgi-sockets"/>
src/test/resources/host-configs/host-slave.xml: <socket-bindings socket-binding-group="osgi-sockets" port-offset="550"/>
{code}
> Remove references to osgi from domain test suite
> ------------------------------------------------
>
> Key: WFLY-1609
> URL: https://issues.jboss.org/browse/WFLY-1609
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Reporter: Thomas Diesler
> Assignee: Ondrej Zizka
> Fix For: 8.0.0.Alpha3
>
>
> {code}
> [tdiesler@localhost domain]$ git grep osgi
> src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", returnVal.asSt
> src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", profile.asStri
> src/test/java/org/jboss/as/test/integration/domain/suites/ReadEnvironmentVariablesTestCase.java: env = getEnvironmentVariables(
> src/test/resources/domain-configs/domain-standard.xml: <extension module="org.jboss.as.osgi"/>
> src/test/resources/domain-configs/domain-standard.xml: <profile name="osgi">
> src/test/resources/domain-configs/domain-standard.xml: <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
> src/test/resources/domain-configs/domain-standard.xml: <property name="org.osgi.framework.startlevel.beginning">1</prop
> src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.osgi.logging" startlevel="1"/>
> src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/
> src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group name="osgi-sockets" default-interface="public">
> src/test/resources/domain-configs/domain-standard.xml: <server-group name="other-server-group" profile="osgi">
> src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group ref="osgi-sockets"/>
> src/test/resources/host-configs/host-slave.xml: <socket-bindings socket-binding-group="osgi-sockets" port-offset="550"/>
> {code}
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1609) Remove references to osgi from domain test suite
by Thomas Diesler (JIRA)
Thomas Diesler created WFLY-1609:
------------------------------------
Summary: Remove references to osgi from domain test suite
Key: WFLY-1609
URL: https://issues.jboss.org/browse/WFLY-1609
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Thomas Diesler
Assignee: Ondrej Zizka
Fix For: 8.0.0.Alpha3
{code}
[tdiesler@localhost domain]$ gti grep osgi
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", returnVal.asSt
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", profile.asStri
src/test/java/org/jboss/as/test/integration/domain/suites/ReadEnvironmentVariablesTestCase.java: env = getEnvironmentVariables(
src/test/resources/domain-configs/domain-standard.xml: <extension module="org.jboss.as.osgi"/>
src/test/resources/domain-configs/domain-standard.xml: <profile name="osgi">
src/test/resources/domain-configs/domain-standard.xml: <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
src/test/resources/domain-configs/domain-standard.xml: <property name="org.osgi.framework.startlevel.beginning">1</prop
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.osgi.logging" startlevel="1"/>
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group name="osgi-sockets" default-interface="public">
src/test/resources/domain-configs/domain-standard.xml: <server-group name="other-server-group" profile="osgi">
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group ref="osgi-sockets"/>
src/test/resources/host-configs/host-slave.xml: <socket-bindings socket-binding-group="osgi-sockets" port-offset="550"/>
[tdiesler@localhost domain]$ git grep osgi
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", returnVal.asSt
src/test/java/org/jboss/as/test/integration/domain/suites/ManagementAccessTestCase.java: Assert.assertEquals("osgi", profile.asStri
src/test/java/org/jboss/as/test/integration/domain/suites/ReadEnvironmentVariablesTestCase.java: env = getEnvironmentVariables(
src/test/resources/domain-configs/domain-standard.xml: <extension module="org.jboss.as.osgi"/>
src/test/resources/domain-configs/domain-standard.xml: <profile name="osgi">
src/test/resources/domain-configs/domain-standard.xml: <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
src/test/resources/domain-configs/domain-standard.xml: <property name="org.osgi.framework.startlevel.beginning">1</prop
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.osgi.logging" startlevel="1"/>
src/test/resources/domain-configs/domain-standard.xml: <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group name="osgi-sockets" default-interface="public">
src/test/resources/domain-configs/domain-standard.xml: <server-group name="other-server-group" profile="osgi">
src/test/resources/domain-configs/domain-standard.xml: <socket-binding-group ref="osgi-sockets"/>
src/test/resources/host-configs/host-slave.xml: <socket-bindings socket-binding-group="osgi-sockets" port-offset="550"/>
{code}
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1608) Add back support for maxEmptyLife in clustered SSO.
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-1608:
----------------------------------
Summary: Add back support for maxEmptyLife in clustered SSO.
Key: WFLY-1608
URL: https://issues.jboss.org/browse/WFLY-1608
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 8.0.0.Alpha2
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 8.0.0.Alpha3
The new clustered SSO implementation removes empty SSOs automatically. Instead, the SSO credentials should remain valid for the period specified by maxEmptyLife.
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1606) Publicly export wildfly-clustering-api
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-1606?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-1606:
-------------------------------
Description:
The goal is to create a single publicly exported clustering module, with a refined, stable public API.
The current wildfly-clustering-api module is too cluttered.
Once the api module is cleaned up, we can merge it with the current wildfly-clustering-annotations module - which does not need to be separate.
As part of this, we will also clean up the wildfly-clustering-impl module. CoreGroupCommunicationService needs to be overhauled, and split into smaller, light-weight components. The distributed lock manager components are obsolete.
was:
The goal is to create a single publicly exported clustering module, with a refined, stable public API.
The current wildfly-clustering-api module is too cluttered.
Once the api module is cleaned up, we can merge it with the current wildfly-clustering-annotations module - which does not need to be separate.
We should also clean up the wildfly-clustering-impl module. CoreGroupCommunicationService needs to be overhauled, and split into smaller, light-weight components.
> Publicly export wildfly-clustering-api
> --------------------------------------
>
> Key: WFLY-1606
> URL: https://issues.jboss.org/browse/WFLY-1606
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 8.0.0.Alpha2
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Alpha3
>
>
> The goal is to create a single publicly exported clustering module, with a refined, stable public API.
> The current wildfly-clustering-api module is too cluttered.
> Once the api module is cleaned up, we can merge it with the current wildfly-clustering-annotations module - which does not need to be separate.
> As part of this, we will also clean up the wildfly-clustering-impl module. CoreGroupCommunicationService needs to be overhauled, and split into smaller, light-weight components. The distributed lock manager components are obsolete.
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1606) Publicly export wildfly-clustering-api
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-1606?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-1606:
-------------------------------
Summary: Publicly export wildfly-clustering-api (was: Refactor wildfly-clustering-api/wildfly-clustering-impl modules)
> Publicly export wildfly-clustering-api
> --------------------------------------
>
> Key: WFLY-1606
> URL: https://issues.jboss.org/browse/WFLY-1606
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 8.0.0.Alpha2
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Alpha3
>
>
> The goal is to create a single publicly exported clustering module, with a refined, stable public API.
> The current wildfly-clustering-api module is too cluttered.
> Once the api module is cleaned up, we can merge it with the current wildfly-clustering-annotations module - which does not need to be separate.
> We should also clean up the wildfly-clustering-impl module. CoreGroupCommunicationService needs to be overhauled, and split into smaller, light-weight components.
--
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
12 years, 10 months