[jira] [Commented] (AMQ-9287) activemq 5.18.1 with jdk 17
[ https://issues.apache.org/jira/browse/AMQ-9287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737442#comment-17737442 ] Jean-Baptiste Onofré commented on AMQ-9287: --- ActiveMQ 5.18.x is JDK11 only. ActiveMQ 5.19.x (currently in preparation) will support JDK17/21. > activemq 5.18.1 with jdk 17 > --- > > Key: AMQ-9287 > URL: https://issues.apache.org/jira/browse/AMQ-9287 > Project: ActiveMQ > Issue Type: Bug >Reporter: Nagaraju >Assignee: Jean-Baptiste Onofré >Priority: Major > > While attempting to use ActiveMQ 5.18.1 with JDK 17, we encountered some > errors during the startup process. The documentation indicated that this > version of ActiveMQ should be compatible with JDK 11 and higher. However, > despite meeting the compatibility requirements, the following errors were > encountered while starting ActiveMQ. These errors indicate that there may be > compatibility issues between ActiveMQ 5.18.1 and JDK 17. > Below is how we are starting activemq > ./activemq console > > > 2023-06-26T16:30:15.266950813Z INFO: Loading '/opt/activemq//bin/env' > 2023-06-26T16:30:15.268183358Z INFO: Using java '/usr/jdk-17.0.7+7/bin/java' > 2023-06-26T16:30:15.269974321Z INFO: Starting in foreground, this is just for > debugging purposes (stop process by pressing CTRL+C) > 2023-06-26T16:30:15.269988755Z INFO: Creating pidfile > /opt/activemq//data/activemq.pid > 2023-06-26T16:30:16.377906222Z INFO | Error when creating PropertyDescriptor > for public final void > org.apache.commons.configuration2.AbstractConfiguration.setProperty(java.lang.String,java.lang.Object)! > Ignoring this property. > 2023-06-26T16:30:17.828054047Z ERROR | Failed to load: URL > [file:/opt/activemq/conf/activemq.xml|file://opt/activemq/conf/activemq.xml], > reason: Unexpected exception parsing XML document from URL > [file:/opt/activemq/conf/camel.xml|file://opt/activemq/conf/camel.xml]; > nested exception is java.lang.ExceptionInInitializerError > 2023-06-26T16:30:17.828085004Z > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from URL > [file:/opt/activemq/conf/camel.xml|file://opt/activemq/conf/camel.xml]; > nested exception is java.lang.ExceptionInInitializerError > 2023-06-26T16:30:17.828118085Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:417) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828120590Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828122545Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828125880Z at > org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.importBeanDefinitionResource(XBeanBeanDefinitionDocumentReader.java:143) > ~[xbean-spring-4.22.jar:4.22] > 2023-06-26T16:30:17.828127720Z at > org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseDefaultElement(XBeanBeanDefinitionDocumentReader.java:109) > ~[xbean-spring-4.22.jar:4.22] > 2023-06-26T16:30:17.828129563Z at > org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:95) > ~[xbean-spring-4.22.jar:4.22] > 2023-06-26T16:30:17.828131860Z at > org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:149) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828133744Z at > org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:96) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828135503Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:511) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828137184Z at > org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79) > ~[xbean-spring-4.22.jar:4.22] > 2023-06-26T16:30:17.828138960Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828140760Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828142482Z at > org.springframework.beans.facto
[jira] [Assigned] (AMQ-9287) activemq 5.18.1 with jdk 17
[ https://issues.apache.org/jira/browse/AMQ-9287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-9287: - Assignee: Jean-Baptiste Onofré > activemq 5.18.1 with jdk 17 > --- > > Key: AMQ-9287 > URL: https://issues.apache.org/jira/browse/AMQ-9287 > Project: ActiveMQ > Issue Type: Bug >Reporter: Nagaraju >Assignee: Jean-Baptiste Onofré >Priority: Major > > While attempting to use ActiveMQ 5.18.1 with JDK 17, we encountered some > errors during the startup process. The documentation indicated that this > version of ActiveMQ should be compatible with JDK 11 and higher. However, > despite meeting the compatibility requirements, the following errors were > encountered while starting ActiveMQ. These errors indicate that there may be > compatibility issues between ActiveMQ 5.18.1 and JDK 17. > Below is how we are starting activemq > ./activemq console > > > 2023-06-26T16:30:15.266950813Z INFO: Loading '/opt/activemq//bin/env' > 2023-06-26T16:30:15.268183358Z INFO: Using java '/usr/jdk-17.0.7+7/bin/java' > 2023-06-26T16:30:15.269974321Z INFO: Starting in foreground, this is just for > debugging purposes (stop process by pressing CTRL+C) > 2023-06-26T16:30:15.269988755Z INFO: Creating pidfile > /opt/activemq//data/activemq.pid > 2023-06-26T16:30:16.377906222Z INFO | Error when creating PropertyDescriptor > for public final void > org.apache.commons.configuration2.AbstractConfiguration.setProperty(java.lang.String,java.lang.Object)! > Ignoring this property. > 2023-06-26T16:30:17.828054047Z ERROR | Failed to load: URL > [file:/opt/activemq/conf/activemq.xml|file://opt/activemq/conf/activemq.xml], > reason: Unexpected exception parsing XML document from URL > [file:/opt/activemq/conf/camel.xml|file://opt/activemq/conf/camel.xml]; > nested exception is java.lang.ExceptionInInitializerError > 2023-06-26T16:30:17.828085004Z > org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected > exception parsing XML document from URL > [file:/opt/activemq/conf/camel.xml|file://opt/activemq/conf/camel.xml]; > nested exception is java.lang.ExceptionInInitializerError > 2023-06-26T16:30:17.828118085Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:417) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828120590Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828122545Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828125880Z at > org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.importBeanDefinitionResource(XBeanBeanDefinitionDocumentReader.java:143) > ~[xbean-spring-4.22.jar:4.22] > 2023-06-26T16:30:17.828127720Z at > org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseDefaultElement(XBeanBeanDefinitionDocumentReader.java:109) > ~[xbean-spring-4.22.jar:4.22] > 2023-06-26T16:30:17.828129563Z at > org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:95) > ~[xbean-spring-4.22.jar:4.22] > 2023-06-26T16:30:17.828131860Z at > org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:149) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828133744Z at > org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:96) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828135503Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:511) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828137184Z at > org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79) > ~[xbean-spring-4.22.jar:4.22] > 2023-06-26T16:30:17.828138960Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828140760Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) > ~[spring-beans-5.3.25.jar:5.3.25] > 2023-06-26T16:30:17.828142482Z at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) > ~[spring-beans-5.3.25.jar:
[jira] [Resolved] (ARTEMIS-4231) Configure EmbeddedWebServer programmatically
[
https://issues.apache.org/jira/browse/ARTEMIS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-4231.
-
Resolution: Information Provided
> Configure EmbeddedWebServer programmatically
>
>
> Key: ARTEMIS-4231
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4231
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Configuration
>Affects Versions: 2.28.0
>Reporter: Raymond
>Priority: Major
>
> I would like to use the management console within my embedded broker.
> 1) I have Spring Boot application (using Jetty as a web server).
> 2) In the application I use an embedded broker.
> I use [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/embedding-activemq.html].
> The code:
> {code:java}
> EmbeddedActiveMQ server = new EmbeddedActiveMQ();
> server.setConfiguration(config);
> server.start();{code}
> Now as a second step, I like to enable the management console. I checked
> [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/web-server.html]
> page. There it says that the embedded webserver can be managed through
> various operations on the {{ActiveMQServerControl}}. The configuration is
> done through "{{etc/bootstrap.xml}}". I of course don't have any
> configuration files. Is there a way to programmatically run and configure the
> management console together with my Spring Boot application?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4231) Configure EmbeddedWebServer programmatically
[
https://issues.apache.org/jira/browse/ARTEMIS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737401#comment-17737401
]
Justin Bertram edited comment on ARTEMIS-4231 at 6/27/23 1:17 AM:
--
You can enable the management console via an embedded instance of Jetty managed
by the broker using the following code:
{code:java}
System.setProperty("hawtio.realm", "hawtio");
System.setProperty("hawtio.role", "myRole");
System.setProperty("hawtio.rolePrincipalClasses",
"org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal");
System.setProperty("java.security.auth.login.config", "/path/to/login.config");
String pathToArtemis = "/path/to/artemis";
EmbeddedActiveMQ server = new EmbeddedActiveMQ();
server.setMbeanServer(ManagementFactory.getPlatformMBeanServer());
server.setConfiguration(config.setJMXManagementEnabled(true));
server.start();
WebServerComponent webServerComponent = new WebServerComponent();
WebServerDTO webServerDTO = new WebServerDTO();
webServerDTO.path = "web";
BindingDTO bindingDTO = new BindingDTO();
bindingDTO.uri = "http://localhost:8161";;
AppDTO branding = new AppDTO();
branding.name = "branding";
branding.url = "activemq-branding";
branding.war = "activemq-branding.war";
AppDTO plugin = new AppDTO();
plugin.name = "plugin";
plugin.url = "artemis-plugin";
plugin.war = "artemis-plugin.war";
AppDTO console = new AppDTO();
console.name = "console";
console.url = "console";
console.war = "console.war";
bindingDTO.addApp(branding);
bindingDTO.addApp(plugin);
bindingDTO.addApp(console);
webServerDTO.addBinding(bindingDTO);
webServerComponent.configure(webServerDTO, pathToArtemis, pathToArtemis);
server.getActiveMQServer().addExternalComponent(webServerComponent, true);{code}
Your {{login.config}} might look something like this:
{noformat}
hawtio {
org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule
required
debug=false
reload=true
org.apache.activemq.jaas.properties.user="hawtio-users.properties"
org.apache.activemq.jaas.properties.role="hawtio-roles.properties";
};{noformat}
{{hawtio-users.properties}}:
{noformat}
myUser=myPass{noformat}
{{hawtio-roles.properties}}:
{noformat}
myRole=myUser{noformat}
Then you can login to the console with the user {{myUser}} and the password
{{myPass}}.
was (Author: jbertram):
You can enable the management console via an embedded instance of Jetty managed
by the broker using the following code:
{code:java}
String pathToArtemis = "/path/to/artemis";
EmbeddedActiveMQ server = new EmbeddedActiveMQ();
server.setMbeanServer(ManagementFactory.getPlatformMBeanServer());
server.setConfiguration(config.setJMXManagementEnabled(true));
server.start();
WebServerComponent webServerComponent = new WebServerComponent();
WebServerDTO webServerDTO = new WebServerDTO();
webServerDTO.path = "web";
BindingDTO bindingDTO = new BindingDTO();
bindingDTO.uri = "http://localhost:8161";;
AppDTO branding = new AppDTO();
branding.name = "branding";
branding.url = "activemq-branding";
branding.war = "activemq-branding.war";
AppDTO plugin = new AppDTO();
plugin.name = "plugin";
plugin.url = "artemis-plugin";
plugin.war = "artemis-plugin.war";
AppDTO console = new AppDTO();
console.name = "console";
console.url = "console";
console.war = "console.war";
bindingDTO.addApp(branding);
bindingDTO.addApp(plugin);
bindingDTO.addApp(console);
webServerDTO.addBinding(bindingDTO);
webServerComponent.configure(webServerDTO, pathToArtemis, pathToArtemis);
server.getActiveMQServer().addExternalComponent(webServerComponent, true);{code}
> Configure EmbeddedWebServer programmatically
>
>
> Key: ARTEMIS-4231
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4231
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Configuration
>Affects Versions: 2.28.0
>Reporter: Raymond
>Priority: Major
>
> I would like to use the management console within my embedded broker.
> 1) I have Spring Boot application (using Jetty as a web server).
> 2) In the application I use an embedded broker.
> I use [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/embedding-activemq.html].
> The code:
> {code:java}
> EmbeddedActiveMQ server = new EmbeddedActiveMQ();
> server.setConfiguration(config);
> server.start();{code}
> Now as a second step, I like to enable the management console. I checked
> [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/web-server.html]
> page. There it says that the embedded webserver can be managed through
> various operations on the {{ActiveMQServerControl}}. The configuration is
> done through "{{etc/bootstrap.xml}}". I of course don't have any
> configuration files. Is there a way to progr
[jira] [Assigned] (ARTEMIS-4231) Configure EmbeddedWebServer programmatically
[
https://issues.apache.org/jira/browse/ARTEMIS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram reassigned ARTEMIS-4231:
---
Assignee: Justin Bertram
> Configure EmbeddedWebServer programmatically
>
>
> Key: ARTEMIS-4231
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4231
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Configuration
>Affects Versions: 2.28.0
>Reporter: Raymond
>Assignee: Justin Bertram
>Priority: Major
>
> I would like to use the management console within my embedded broker.
> 1) I have Spring Boot application (using Jetty as a web server).
> 2) In the application I use an embedded broker.
> I use [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/embedding-activemq.html].
> The code:
> {code:java}
> EmbeddedActiveMQ server = new EmbeddedActiveMQ();
> server.setConfiguration(config);
> server.start();{code}
> Now as a second step, I like to enable the management console. I checked
> [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/web-server.html]
> page. There it says that the embedded webserver can be managed through
> various operations on the {{ActiveMQServerControl}}. The configuration is
> done through "{{etc/bootstrap.xml}}". I of course don't have any
> configuration files. Is there a way to programmatically run and configure the
> management console together with my Spring Boot application?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4231) Configure EmbeddedWebServer programmatically
[
https://issues.apache.org/jira/browse/ARTEMIS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737401#comment-17737401
]
Justin Bertram edited comment on ARTEMIS-4231 at 6/27/23 1:17 AM:
--
You can enable the management console via an embedded instance of Jetty managed
by the broker using the following code:
{code:java}
System.setProperty("hawtio.realm", "hawtio");
System.setProperty("hawtio.role", "myRole");
System.setProperty("hawtio.rolePrincipalClasses",
"org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal");
System.setProperty("java.security.auth.login.config", "/path/to/login.config");
String pathToArtemis = "/path/to/artemis";
EmbeddedActiveMQ server = new EmbeddedActiveMQ();
server.setMbeanServer(ManagementFactory.getPlatformMBeanServer());
server.setConfiguration(config.setJMXManagementEnabled(true));
server.start();
WebServerComponent webServerComponent = new WebServerComponent();
WebServerDTO webServerDTO = new WebServerDTO();
webServerDTO.path = "web";
BindingDTO bindingDTO = new BindingDTO();
bindingDTO.uri = "http://localhost:8161";;
AppDTO branding = new AppDTO();
branding.name = "branding";
branding.url = "activemq-branding";
branding.war = "activemq-branding.war";
AppDTO plugin = new AppDTO();
plugin.name = "plugin";
plugin.url = "artemis-plugin";
plugin.war = "artemis-plugin.war";
AppDTO console = new AppDTO();
console.name = "console";
console.url = "console";
console.war = "console.war";
bindingDTO.addApp(branding);
bindingDTO.addApp(plugin);
bindingDTO.addApp(console);
webServerDTO.addBinding(bindingDTO);
webServerComponent.configure(webServerDTO, pathToArtemis, pathToArtemis);
server.getActiveMQServer().addExternalComponent(webServerComponent, true);{code}
Your {{login.config}} might look something like this:
{noformat}
hawtio {
org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule
required
debug=false
reload=true
org.apache.activemq.jaas.properties.user="hawtio-users.properties"
org.apache.activemq.jaas.properties.role="hawtio-roles.properties";
};{noformat}
{{hawtio-users.properties}}:
{noformat}
myUser=myPass{noformat}
{{hawtio-roles.properties}}:
{noformat}
myRole=myUser{noformat}
Then you can login to the console at {{http://localhost:8161/console}} with the
user {{myUser}} and the password {{myPass}}.
was (Author: jbertram):
You can enable the management console via an embedded instance of Jetty managed
by the broker using the following code:
{code:java}
System.setProperty("hawtio.realm", "hawtio");
System.setProperty("hawtio.role", "myRole");
System.setProperty("hawtio.rolePrincipalClasses",
"org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal");
System.setProperty("java.security.auth.login.config", "/path/to/login.config");
String pathToArtemis = "/path/to/artemis";
EmbeddedActiveMQ server = new EmbeddedActiveMQ();
server.setMbeanServer(ManagementFactory.getPlatformMBeanServer());
server.setConfiguration(config.setJMXManagementEnabled(true));
server.start();
WebServerComponent webServerComponent = new WebServerComponent();
WebServerDTO webServerDTO = new WebServerDTO();
webServerDTO.path = "web";
BindingDTO bindingDTO = new BindingDTO();
bindingDTO.uri = "http://localhost:8161";;
AppDTO branding = new AppDTO();
branding.name = "branding";
branding.url = "activemq-branding";
branding.war = "activemq-branding.war";
AppDTO plugin = new AppDTO();
plugin.name = "plugin";
plugin.url = "artemis-plugin";
plugin.war = "artemis-plugin.war";
AppDTO console = new AppDTO();
console.name = "console";
console.url = "console";
console.war = "console.war";
bindingDTO.addApp(branding);
bindingDTO.addApp(plugin);
bindingDTO.addApp(console);
webServerDTO.addBinding(bindingDTO);
webServerComponent.configure(webServerDTO, pathToArtemis, pathToArtemis);
server.getActiveMQServer().addExternalComponent(webServerComponent, true);{code}
Your {{login.config}} might look something like this:
{noformat}
hawtio {
org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule
required
debug=false
reload=true
org.apache.activemq.jaas.properties.user="hawtio-users.properties"
org.apache.activemq.jaas.properties.role="hawtio-roles.properties";
};{noformat}
{{hawtio-users.properties}}:
{noformat}
myUser=myPass{noformat}
{{hawtio-roles.properties}}:
{noformat}
myRole=myUser{noformat}
Then you can login to the console with the user {{myUser}} and the password
{{myPass}}.
> Configure EmbeddedWebServer programmatically
>
>
> Key: ARTEMIS-4231
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4231
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Configuration
>Affects Versions: 2.28.0
>Reporter: Raymond
>Assignee: Justin
[jira] [Commented] (ARTEMIS-4231) Configure EmbeddedWebServer programmatically
[
https://issues.apache.org/jira/browse/ARTEMIS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737401#comment-17737401
]
Justin Bertram commented on ARTEMIS-4231:
-
You can enable the management console via an embedded instance of Jetty managed
by the broker using the following code:
{code:java}
String pathToArtemis = "/path/to/artemis";
EmbeddedActiveMQ server = new EmbeddedActiveMQ();
server.setMbeanServer(ManagementFactory.getPlatformMBeanServer());
server.setConfiguration(config.setJMXManagementEnabled(true));
server.start();
WebServerComponent webServerComponent = new WebServerComponent();
WebServerDTO webServerDTO = new WebServerDTO();
webServerDTO.path = "web";
BindingDTO bindingDTO = new BindingDTO();
bindingDTO.uri = "http://localhost:8161";;
AppDTO branding = new AppDTO();
branding.name = "branding";
branding.url = "activemq-branding";
branding.war = "activemq-branding.war";
AppDTO plugin = new AppDTO();
plugin.name = "plugin";
plugin.url = "artemis-plugin";
plugin.war = "artemis-plugin.war";
AppDTO console = new AppDTO();
console.name = "console";
console.url = "console";
console.war = "console.war";
bindingDTO.addApp(branding);
bindingDTO.addApp(plugin);
bindingDTO.addApp(console);
webServerDTO.addBinding(bindingDTO);
webServerComponent.configure(webServerDTO, pathToArtemis, pathToArtemis);
server.getActiveMQServer().addExternalComponent(webServerComponent, true);{code}
> Configure EmbeddedWebServer programmatically
>
>
> Key: ARTEMIS-4231
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4231
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Configuration
>Affects Versions: 2.28.0
>Reporter: Raymond
>Priority: Major
>
> I would like to use the management console within my embedded broker.
> 1) I have Spring Boot application (using Jetty as a web server).
> 2) In the application I use an embedded broker.
> I use [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/embedding-activemq.html].
> The code:
> {code:java}
> EmbeddedActiveMQ server = new EmbeddedActiveMQ();
> server.setConfiguration(config);
> server.start();{code}
> Now as a second step, I like to enable the management console. I checked
> [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/web-server.html]
> page. There it says that the embedded webserver can be managed through
> various operations on the {{ActiveMQServerControl}}. The configuration is
> done through "{{etc/bootstrap.xml}}". I of course don't have any
> configuration files. Is there a way to programmatically run and configure the
> management console together with my Spring Boot application?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4231) Configure EmbeddedWebServer programmatically
[
https://issues.apache.org/jira/browse/ARTEMIS-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-4231:
Description:
I would like to use the management console within my embedded broker.
1) I have Spring Boot application (using Jetty as a web server).
2) In the application I use an embedded broker.
I use [this
documentation|https://activemq.apache.org/components/artemis/documentation/latest/embedding-activemq.html].
The code:
{code:java}
EmbeddedActiveMQ server = new EmbeddedActiveMQ();
server.setConfiguration(config);
server.start();{code}
Now as a second step, I like to enable the management console. I checked [this
documentation|https://activemq.apache.org/components/artemis/documentation/latest/web-server.html]
page. There it says that the embedded webserver can be managed through various
operations on the {{ActiveMQServerControl}}. The configuration is done through
"{{etc/bootstrap.xml}}". I of course don't have any configuration files. Is
there a way to programmatically run and configure the management console
together with my Spring Boot application?
was:
I would like to use the management console within my embedded broker.
1) I have Spring Boot application (using Jetty as a web server).
2) In the application I use an embedded broker
I use this documentation:
[https://activemq.apache.org/components/artemis/documentation/latest/embedding-activemq.html]
The code:
{{}}
{code:java}
EmbeddedActiveMQ server = new EmbeddedActiveMQ();{code}
{code:java}
server.setConfiguration(config);
server.start();{code}
Now as a second step, I like to enable the management console. I checked this
documentation page:
[https://activemq.apache.org/components/artemis/documentation/latest/web-server.html]
There it says that the embedded webserver can be managed through various
operations on the {{{}ActiveMQServerControl{}}}. The configuration is done
through "{{{}etc/bootstrap.xml{}}}". I of course don't have any configuration
files. Is there a way to programmatically run and configure the management
console together with my Spring Boot application?
> Configure EmbeddedWebServer programmatically
>
>
> Key: ARTEMIS-4231
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4231
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Configuration
>Affects Versions: 2.28.0
>Reporter: Raymond
>Priority: Major
>
> I would like to use the management console within my embedded broker.
> 1) I have Spring Boot application (using Jetty as a web server).
> 2) In the application I use an embedded broker.
> I use [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/embedding-activemq.html].
> The code:
> {code:java}
> EmbeddedActiveMQ server = new EmbeddedActiveMQ();
> server.setConfiguration(config);
> server.start();{code}
> Now as a second step, I like to enable the management console. I checked
> [this
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/web-server.html]
> page. There it says that the embedded webserver can be managed through
> various operations on the {{ActiveMQServerControl}}. The configuration is
> done through "{{etc/bootstrap.xml}}". I of course don't have any
> configuration files. Is there a way to programmatically run and configure the
> management console together with my Spring Boot application?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-8149) Create Docker Image
[ https://issues.apache.org/jira/browse/AMQ-8149?focusedWorklogId=867584&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867584 ] ASF GitHub Bot logged work on AMQ-8149: --- Author: ASF GitHub Bot Created on: 26/Jun/23 19:44 Start Date: 26/Jun/23 19:44 Worklog Time Spent: 10m Work Description: jbonofre commented on PR #1036: URL: https://github.com/apache/activemq/pull/1036#issuecomment-1608128970 @mattrpav good catch, I will fix that. Thanks ! Issue Time Tracking --- Worklog Id: (was: 867584) Time Spent: 40m (was: 0.5h) > Create Docker Image > --- > > Key: AMQ-8149 > URL: https://issues.apache.org/jira/browse/AMQ-8149 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.2 > > Time Spent: 40m > Remaining Estimate: 0h > > Create an Apache ActiveMQ docker image > Draft: > [X] -jib- or jkube mvn plugin [Use jkube for support of multiple base images > (debian, alpine, ubi etc)] > [ ] Create a general container that supports most use cases (enable all > protocols on default ports, etc) > [ ] Provide artifacts for users to build customized containers > Tasks: > [DONE] Creation of Docker repository for ActiveMQ INFRA-21430 > [ ] Add activemq-docker module to 5.17.x (activemq-assembly) > [ ] Add dockerhub deployment to release process -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-8149) Create Docker Image
[
https://issues.apache.org/jira/browse/AMQ-8149?focusedWorklogId=867575&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867575
]
ASF GitHub Bot logged work on AMQ-8149:
---
Author: ASF GitHub Bot
Created on: 26/Jun/23 19:19
Start Date: 26/Jun/23 19:19
Worklog Time Spent: 10m
Work Description: mattrpav commented on code in PR #1036:
URL: https://github.com/apache/activemq/pull/1036#discussion_r1242650760
##
assembly/src/docker/docker-compose.yml:
##
@@ -0,0 +1,39 @@
+
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+
+version: "2.1"
+services:
+ activemq:
+image: ${ACTIVEMQ_DOCKER_IMAGE_NAME:-qctivemq}
Review Comment:
Looks like minor type-o here. Should be 'activemq' instead of 'qctivemq'?
Issue Time Tracking
---
Worklog Id: (was: 867575)
Time Spent: 0.5h (was: 20m)
> Create Docker Image
> ---
>
> Key: AMQ-8149
> URL: https://issues.apache.org/jira/browse/AMQ-8149
> Project: ActiveMQ
> Issue Type: New Feature
>Reporter: Matt Pavlovich
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.19.0, 5.18.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Create an Apache ActiveMQ docker image
> Draft:
> [X] -jib- or jkube mvn plugin [Use jkube for support of multiple base images
> (debian, alpine, ubi etc)]
> [ ] Create a general container that supports most use cases (enable all
> protocols on default ports, etc)
> [ ] Provide artifacts for users to build customized containers
> Tasks:
> [DONE] Creation of Docker repository for ActiveMQ INFRA-21430
> [ ] Add activemq-docker module to 5.17.x (activemq-assembly)
> [ ] Add dockerhub deployment to release process
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (AMQ-9287) activemq 5.18.1 with jdk 17
[ https://issues.apache.org/jira/browse/AMQ-9287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nagaraju updated AMQ-9287: -- Description: While attempting to use ActiveMQ 5.18.1 with JDK 17, we encountered some errors during the startup process. The documentation indicated that this version of ActiveMQ should be compatible with JDK 11 and higher. However, despite meeting the compatibility requirements, the following errors were encountered while starting ActiveMQ. These errors indicate that there may be compatibility issues between ActiveMQ 5.18.1 and JDK 17. Below is how we are starting activemq ./activemq console 2023-06-26T16:30:15.266950813Z INFO: Loading '/opt/activemq//bin/env' 2023-06-26T16:30:15.268183358Z INFO: Using java '/usr/jdk-17.0.7+7/bin/java' 2023-06-26T16:30:15.269974321Z INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C) 2023-06-26T16:30:15.269988755Z INFO: Creating pidfile /opt/activemq//data/activemq.pid 2023-06-26T16:30:16.377906222Z INFO | Error when creating PropertyDescriptor for public final void org.apache.commons.configuration2.AbstractConfiguration.setProperty(java.lang.String,java.lang.Object)! Ignoring this property. 2023-06-26T16:30:17.828054047Z ERROR | Failed to load: URL [file:/opt/activemq/conf/activemq.xml|file://opt/activemq/conf/activemq.xml], reason: Unexpected exception parsing XML document from URL [file:/opt/activemq/conf/camel.xml|file://opt/activemq/conf/camel.xml]; nested exception is java.lang.ExceptionInInitializerError 2023-06-26T16:30:17.828085004Z org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [file:/opt/activemq/conf/camel.xml|file://opt/activemq/conf/camel.xml]; nested exception is java.lang.ExceptionInInitializerError 2023-06-26T16:30:17.828118085Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:417) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828120590Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828122545Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828125880Z at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.importBeanDefinitionResource(XBeanBeanDefinitionDocumentReader.java:143) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828127720Z at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseDefaultElement(XBeanBeanDefinitionDocumentReader.java:109) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828129563Z at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:95) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828131860Z at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:149) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828133744Z at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:96) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828135503Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:511) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828137184Z at org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828138960Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828140760Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828142482Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828144286Z at org.apache.xbean.spring.context.ResourceXmlApplicationContext.loadBeanDefinitions(ResourceXmlApplicationContext.java:116) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828145990Z at org.apache.xbean.spring.context.ResourceXmlApplicationContext.loadBeanDefinitions(ResourceXmlApplicationContext.java:104) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828147892Z at org.springframework.context.support.AbstractRefreshableApplicationContext.refresh
[jira] [Updated] (AMQ-9287) activemq 5.18.1 with jdk 17
[ https://issues.apache.org/jira/browse/AMQ-9287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nagaraju updated AMQ-9287: -- Description: We are trying to use Activemq 5.18.1 with JDK 17 (As per the documentation this version of ActiveMQ is compatible with JDK11+). But we are getting the following errors while starting the Activemq. 2023-06-26T16:30:15.266950813Z INFO: Loading '/opt/activemq//bin/env' 2023-06-26T16:30:15.268183358Z INFO: Using java '/usr/jdk-17.0.7+7/bin/java' 2023-06-26T16:30:15.269974321Z INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C) 2023-06-26T16:30:15.269988755Z INFO: Creating pidfile /opt/activemq//data/activemq.pid 2023-06-26T16:30:16.377906222Z INFO | Error when creating PropertyDescriptor for public final void org.apache.commons.configuration2.AbstractConfiguration.setProperty(java.lang.String,java.lang.Object)! Ignoring this property. 2023-06-26T16:30:17.828054047Z ERROR | Failed to load: URL [file:/opt/activemq/conf/activemq.xml|file://opt/activemq/conf/activemq.xml], reason: Unexpected exception parsing XML document from URL [file:/opt/activemq/conf/camel.xml|file://opt/activemq/conf/camel.xml]; nested exception is java.lang.ExceptionInInitializerError 2023-06-26T16:30:17.828085004Z org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [file:/opt/activemq/conf/camel.xml|file://opt/activemq/conf/camel.xml]; nested exception is java.lang.ExceptionInInitializerError 2023-06-26T16:30:17.828118085Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:417) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828120590Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828122545Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828125880Z at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.importBeanDefinitionResource(XBeanBeanDefinitionDocumentReader.java:143) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828127720Z at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseDefaultElement(XBeanBeanDefinitionDocumentReader.java:109) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828129563Z at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:95) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828131860Z at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:149) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828133744Z at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:96) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828135503Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:511) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828137184Z at org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828138960Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828140760Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828142482Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828144286Z at org.apache.xbean.spring.context.ResourceXmlApplicationContext.loadBeanDefinitions(ResourceXmlApplicationContext.java:116) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828145990Z at org.apache.xbean.spring.context.ResourceXmlApplicationContext.loadBeanDefinitions(ResourceXmlApplicationContext.java:104) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828147892Z at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130) ~[spring-context-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828149599Z at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:671) ~[spring-context-5.3.25.jar:5.3.
[jira] [Created] (AMQ-9287) activemq 5.18.1 with jdk 17
Nagaraju created AMQ-9287: - Summary: activemq 5.18.1 with jdk 17 Key: AMQ-9287 URL: https://issues.apache.org/jira/browse/AMQ-9287 Project: ActiveMQ Issue Type: Bug Reporter: Nagaraju We are trying to use Activemq 5.18.1 with JDK 17 (As per the documentation this is compatible with 11+). But we are getting the following errors while starting the Activemq. 2023-06-26T16:30:15.266950813Z INFO: Loading '/opt/activemq//bin/env' 2023-06-26T16:30:15.268183358Z INFO: Using java '/usr/jdk-17.0.7+7/bin/java' 2023-06-26T16:30:15.269974321Z INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C) 2023-06-26T16:30:15.269988755Z INFO: Creating pidfile /opt/activemq//data/activemq.pid 2023-06-26T16:30:16.377906222Z INFO | Error when creating PropertyDescriptor for public final void org.apache.commons.configuration2.AbstractConfiguration.setProperty(java.lang.String,java.lang.Object)! Ignoring this property. 2023-06-26T16:30:17.828054047Z ERROR | Failed to load: URL [file:/opt/activemq/conf/activemq.xml], reason: Unexpected exception parsing XML document from URL [file:/opt/activemq/conf/camel.xml]; nested exception is java.lang.ExceptionInInitializerError 2023-06-26T16:30:17.828085004Z org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [file:/opt/activemq/conf/camel.xml]; nested exception is java.lang.ExceptionInInitializerError 2023-06-26T16:30:17.828118085Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:417) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828120590Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828122545Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828125880Z at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.importBeanDefinitionResource(XBeanBeanDefinitionDocumentReader.java:143) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828127720Z at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseDefaultElement(XBeanBeanDefinitionDocumentReader.java:109) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828129563Z at org.apache.xbean.spring.context.v2.XBeanBeanDefinitionDocumentReader.parseBeanDefinitions(XBeanBeanDefinitionDocumentReader.java:95) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828131860Z at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:149) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828133744Z at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:96) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828135503Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:511) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828137184Z at org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader.registerBeanDefinitions(XBeanXmlBeanDefinitionReader.java:79) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828138960Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828140760Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828142482Z at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) ~[spring-beans-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828144286Z at org.apache.xbean.spring.context.ResourceXmlApplicationContext.loadBeanDefinitions(ResourceXmlApplicationContext.java:116) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828145990Z at org.apache.xbean.spring.context.ResourceXmlApplicationContext.loadBeanDefinitions(ResourceXmlApplicationContext.java:104) ~[xbean-spring-4.22.jar:4.22] 2023-06-26T16:30:17.828147892Z at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130) ~[spring-context-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828149599Z at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:671) ~[spring-context-5.3.25.jar:5.3.25] 2023-06-26T16:30:17.828151234Z
[jira] [Created] (ARTEMIS-4336) Upgrade mockserver version to 5.15.0
Domenico Francesco Bruscino created ARTEMIS-4336: Summary: Upgrade mockserver version to 5.15.0 Key: ARTEMIS-4336 URL: https://issues.apache.org/jira/browse/ARTEMIS-4336 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Domenico Francesco Bruscino Assignee: Domenico Francesco Bruscino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4335) Upgrade bcprov to bcprov-jdk18on:1.75
Domenico Francesco Bruscino created ARTEMIS-4335: Summary: Upgrade bcprov to bcprov-jdk18on:1.75 Key: ARTEMIS-4335 URL: https://issues.apache.org/jira/browse/ARTEMIS-4335 Project: ActiveMQ Artemis Issue Type: Dependency upgrade Reporter: Domenico Francesco Bruscino Assignee: Domenico Francesco Bruscino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9260) Upgrade to maven-assembly-plugin 3.6.0
[ https://issues.apache.org/jira/browse/AMQ-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737114#comment-17737114 ] ASF subversion and git services commented on AMQ-9260: -- Commit 4cf77b777ad0777c3b2a405ac0a4f9f84856b845 in activemq's branch refs/heads/activemq-5.17.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=4cf77b777a ] Revert "[AMQ-9260] Upgrade to maven-assembly-plugin 3.6.0" This reverts commit e07950ba9d35b7b4575de24dc41d3aa7ff178af5. > Upgrade to maven-assembly-plugin 3.6.0 > -- > > Key: AMQ-9260 > URL: https://issues.apache.org/jira/browse/AMQ-9260 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9260) Upgrade to maven-assembly-plugin 3.6.0
[ https://issues.apache.org/jira/browse/AMQ-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737113#comment-17737113 ] ASF subversion and git services commented on AMQ-9260: -- Commit a782c24e9447269c69f76b42c4311ae80b3e5a64 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=a782c24e94 ] Revert "[AMQ-9260] Upgrade to maven-assembly-plugin 3.6.0" This reverts commit d284bce16fbe6faa71d58c181f4e9d50fce80e11. > Upgrade to maven-assembly-plugin 3.6.0 > -- > > Key: AMQ-9260 > URL: https://issues.apache.org/jira/browse/AMQ-9260 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9260) Upgrade to maven-assembly-plugin 3.6.0
[ https://issues.apache.org/jira/browse/AMQ-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737110#comment-17737110 ] ASF subversion and git services commented on AMQ-9260: -- Commit 4d81ef595f767e5a9ce992a0584a71ed48c6e2d3 in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=4d81ef595f ] Revert "[AMQ-9260] Upgrade to maven-assembly-plugin 3.6.0" This reverts commit 6dacd4875d88f05f433abd8cc024e53ab1f495e0. > Upgrade to maven-assembly-plugin 3.6.0 > -- > > Key: AMQ-9260 > URL: https://issues.apache.org/jira/browse/AMQ-9260 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (AMQ-9260) Upgrade to maven-assembly-plugin 3.6.0
[ https://issues.apache.org/jira/browse/AMQ-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reopened AMQ-9260: --- > Upgrade to maven-assembly-plugin 3.6.0 > -- > > Key: AMQ-9260 > URL: https://issues.apache.org/jira/browse/AMQ-9260 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.17.5, 5.18.2 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9260) Upgrade to maven-assembly-plugin 3.6.0
[ https://issues.apache.org/jira/browse/AMQ-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9260: -- Fix Version/s: 5.18.3 5.17.6 (was: 5.17.5) (was: 5.18.2) > Upgrade to maven-assembly-plugin 3.6.0 > -- > > Key: AMQ-9260 > URL: https://issues.apache.org/jira/browse/AMQ-9260 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9273) Upgrade to maven-shade-plugin 3.4.1
[ https://issues.apache.org/jira/browse/AMQ-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737107#comment-17737107 ] ASF subversion and git services commented on AMQ-9273: -- Commit 98c9c1aebfca401ff2548df9e0e6faf30c851462 in activemq's branch refs/heads/activemq-5.18.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=98c9c1aebf ] Revert "[AMQ-9273] Upgrade to maven-shade-plugin 3.4.1" This reverts commit f9f3e381a0c6824c2dc8c4ec332d3eedbd1ddea3. > Upgrade to maven-shade-plugin 3.4.1 > --- > > Key: AMQ-9273 > URL: https://issues.apache.org/jira/browse/AMQ-9273 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9273) Upgrade to maven-shade-plugin 3.4.1
[ https://issues.apache.org/jira/browse/AMQ-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737108#comment-17737108 ] ASF subversion and git services commented on AMQ-9273: -- Commit 528990da014793d70946462ac82dace9f980e714 in activemq's branch refs/heads/activemq-5.17.x from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=528990da01 ] Revert "[AMQ-9273] Upgrade to maven-shade-plugin 3.4.1" This reverts commit ee22483c59eb51088f0ac70512647f9f12a25fc2. > Upgrade to maven-shade-plugin 3.4.1 > --- > > Key: AMQ-9273 > URL: https://issues.apache.org/jira/browse/AMQ-9273 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9273) Upgrade to maven-shade-plugin 3.4.1
[ https://issues.apache.org/jira/browse/AMQ-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737106#comment-17737106 ] ASF subversion and git services commented on AMQ-9273: -- Commit 2205677143968a9a2cf36842141777f4c95e42ff in activemq's branch refs/heads/main from JB Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=2205677143 ] Revert "[AMQ-9273] Upgrade to maven-shade-plugin 3.4.1" This reverts commit b2176cbf73782a975101a3e6dd09c51ad2772c5f. > Upgrade to maven-shade-plugin 3.4.1 > --- > > Key: AMQ-9273 > URL: https://issues.apache.org/jira/browse/AMQ-9273 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (AMQ-9273) Upgrade to maven-shade-plugin 3.4.1
[ https://issues.apache.org/jira/browse/AMQ-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reopened AMQ-9273: --- > Upgrade to maven-shade-plugin 3.4.1 > --- > > Key: AMQ-9273 > URL: https://issues.apache.org/jira/browse/AMQ-9273 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.17.5, 5.18.2 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9273) Upgrade to maven-shade-plugin 3.4.1
[ https://issues.apache.org/jira/browse/AMQ-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9273: -- Fix Version/s: 5.17.6 5.18.3 (was: 5.17.5) (was: 5.18.2) > Upgrade to maven-shade-plugin 3.4.1 > --- > > Key: AMQ-9273 > URL: https://issues.apache.org/jira/browse/AMQ-9273 > Project: ActiveMQ > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.19.0, 5.18.3, 5.17.6 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4328) Test can hang indefinitely
[
https://issues.apache.org/jira/browse/ARTEMIS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737100#comment-17737100
]
ASF subversion and git services commented on ARTEMIS-4328:
--
Commit b82419634ab5bcd9069d5bce09e554ca4a82b4b8 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=b82419634a ]
ARTEMIS-4328 add timeout to test which can hang
`org.apache.activemq.artemis.core.server.embedded.MainTest` expects the
broker to throw a `java.io.IOException` when it is started due to its
inability to find the file app/data/server.lock. However, if that files
just happens to exist then the test will simply hang indefinitely. This
commit adds a timeout to avoid hanging.
> Test can hang indefinitely
> --
>
> Key: ARTEMIS-4328
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4328
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{org.apache.activemq.artemis.core.server.embedded.MainTest}} expects the
> broker to throw a {{java.io.IOException}} when it is started due to its
> inability to find the file {{app/data/server.lock}}. However, if that files
> just happens to exist then the test will simply hang indefinitely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4328) Test can hang indefinitely
[
https://issues.apache.org/jira/browse/ARTEMIS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved ARTEMIS-4328.
-
Fix Version/s: 2.30.0
Resolution: Fixed
> Test can hang indefinitely
> --
>
> Key: ARTEMIS-4328
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4328
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.30.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{org.apache.activemq.artemis.core.server.embedded.MainTest}} expects the
> broker to throw a {{java.io.IOException}} when it is started due to its
> inability to find the file {{app/data/server.lock}}. However, if that files
> just happens to exist then the test will simply hang indefinitely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4328) Test can hang indefinitely
[
https://issues.apache.org/jira/browse/ARTEMIS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated ARTEMIS-4328:
Component/s: Tests
> Test can hang indefinitely
> --
>
> Key: ARTEMIS-4328
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4328
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Tests
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Fix For: 2.30.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{org.apache.activemq.artemis.core.server.embedded.MainTest}} expects the
> broker to throw a {{java.io.IOException}} when it is started due to its
> inability to find the file {{app/data/server.lock}}. However, if that files
> just happens to exist then the test will simply hang indefinitely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4328) Test can hang indefinitely
[
https://issues.apache.org/jira/browse/ARTEMIS-4328?focusedWorklogId=867448&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867448
]
ASF GitHub Bot logged work on ARTEMIS-4328:
---
Author: ASF GitHub Bot
Created on: 26/Jun/23 11:13
Start Date: 26/Jun/23 11:13
Worklog Time Spent: 10m
Work Description: gemmellr merged PR #4523:
URL: https://github.com/apache/activemq-artemis/pull/4523
Issue Time Tracking
---
Worklog Id: (was: 867448)
Time Spent: 20m (was: 10m)
> Test can hang indefinitely
> --
>
> Key: ARTEMIS-4328
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4328
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{org.apache.activemq.artemis.core.server.embedded.MainTest}} expects the
> broker to throw a {{java.io.IOException}} when it is started due to its
> inability to find the file {{app/data/server.lock}}. However, if that files
> just happens to exist then the test will simply hang indefinitely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4334) tidyup around artemis-website module used to generate docs for website
[ https://issues.apache.org/jira/browse/ARTEMIS-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4334. - Resolution: Fixed > tidyup around artemis-website module used to generate docs for website > -- > > Key: ARTEMIS-4334 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4334 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.30.0 > > > The artemis-website module is used to build various documentation (user > manual, developer guide, migration guide, javadocs) used to update the > content of the standalone activemq-website repo, particularly during > releases. Historically some of the artemis-website output was actually used > by the binary distribution, but that is no longer the case. Various cruft > remains in the build due to this, it can now be removed to simplify the > module and also make the remaining build and output clearer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4334) tidyup around artemis-website module used to generate docs for website
[ https://issues.apache.org/jira/browse/ARTEMIS-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737086#comment-17737086 ] ASF subversion and git services commented on ARTEMIS-4334: -- Commit 4e9f5fd3aae772a498bb6a6308b88c4f16a3fb67 in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=4e9f5fd3aa ] ARTEMIS-4334: update assembly scripts handling, exclude some that can be generated earlier by artemis-website build > tidyup around artemis-website module used to generate docs for website > -- > > Key: ARTEMIS-4334 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4334 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.30.0 > > > The artemis-website module is used to build various documentation (user > manual, developer guide, migration guide, javadocs) used to update the > content of the standalone activemq-website repo, particularly during > releases. Historically some of the artemis-website output was actually used > by the binary distribution, but that is no longer the case. Various cruft > remains in the build due to this, it can now be removed to simplify the > module and also make the remaining build and output clearer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4334) tidyup around artemis-website module used to generate docs for website
[ https://issues.apache.org/jira/browse/ARTEMIS-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737085#comment-17737085 ] ASF subversion and git services commented on ARTEMIS-4334: -- Commit db18db6a7f1d31c043cf90261fba36e592310a87 in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=db18db6a7f ] ARTEMIS-4334: remove old assembly placeholder content+build from artemis-website, the assembly no longer uses the module > tidyup around artemis-website module used to generate docs for website > -- > > Key: ARTEMIS-4334 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4334 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.30.0 > > > The artemis-website module is used to build various documentation (user > manual, developer guide, migration guide, javadocs) used to update the > content of the standalone activemq-website repo, particularly during > releases. Historically some of the artemis-website output was actually used > by the binary distribution, but that is no longer the case. Various cruft > remains in the build due to this, it can now be removed to simplify the > module and also make the remaining build and output clearer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4334) tidyup around artemis-website module used to generate docs for website
[ https://issues.apache.org/jira/browse/ARTEMIS-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737087#comment-17737087 ] ASF subversion and git services commented on ARTEMIS-4334: -- Commit e59fb0233ecaaf17d07fb843dba9ab840b30fcd1 in activemq-artemis's branch refs/heads/main from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e59fb0233e ] ARTEMIS-4334: move artemis-website into the release profile since it now does nothing outwith it > tidyup around artemis-website module used to generate docs for website > -- > > Key: ARTEMIS-4334 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4334 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 2.30.0 > > > The artemis-website module is used to build various documentation (user > manual, developer guide, migration guide, javadocs) used to update the > content of the standalone activemq-website repo, particularly during > releases. Historically some of the artemis-website output was actually used > by the binary distribution, but that is no longer the case. Various cruft > remains in the build due to this, it can now be removed to simplify the > module and also make the remaining build and output clearer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4334) tidyup around artemis-website module used to generate docs for website
Robbie Gemmell created ARTEMIS-4334: --- Summary: tidyup around artemis-website module used to generate docs for website Key: ARTEMIS-4334 URL: https://issues.apache.org/jira/browse/ARTEMIS-4334 Project: ActiveMQ Artemis Issue Type: Task Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 2.30.0 The artemis-website module is used to build various documentation (user manual, developer guide, migration guide, javadocs) used to update the content of the standalone activemq-website repo, particularly during releases. Historically some of the artemis-website output was actually used by the binary distribution, but that is no longer the case. Various cruft remains in the build due to this, it can now be removed to simplify the module and also make the remaining build and output clearer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4333) Document web SNI settings
[ https://issues.apache.org/jira/browse/ARTEMIS-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-4333: Description: Document sniHostCheck and sniRequired settings added in 2.29.0 / ARTEMIS-4245. (was: Document sniHostCheck and sniRequired settings.) > Document web SNI settings > - > > Key: ARTEMIS-4333 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4333 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.30.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Document sniHostCheck and sniRequired settings added in 2.29.0 / ARTEMIS-4245. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4333) Document web SNI settings
[ https://issues.apache.org/jira/browse/ARTEMIS-4333?focusedWorklogId=867381&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867381 ] ASF GitHub Bot logged work on ARTEMIS-4333: --- Author: ASF GitHub Bot Created on: 26/Jun/23 08:48 Start Date: 26/Jun/23 08:48 Worklog Time Spent: 10m Work Description: gemmellr merged PR #4527: URL: https://github.com/apache/activemq-artemis/pull/4527 Issue Time Tracking --- Worklog Id: (was: 867381) Time Spent: 40m (was: 0.5h) > Document web SNI settings > - > > Key: ARTEMIS-4333 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4333 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Document sniHostCheck and sniRequired settings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4333) Document web SNI settings
[ https://issues.apache.org/jira/browse/ARTEMIS-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737049#comment-17737049 ] ASF subversion and git services commented on ARTEMIS-4333: -- Commit 137e1ed52d1ca32f4c68a48d4b78399f1e3e5b12 in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=137e1ed52d ] ARTEMIS-4333 Document web SNI settings > Document web SNI settings > - > > Key: ARTEMIS-4333 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4333 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Document sniHostCheck and sniRequired settings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ARTEMIS-4333) Document web SNI settings
[ https://issues.apache.org/jira/browse/ARTEMIS-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved ARTEMIS-4333. - Fix Version/s: 2.30.0 Resolution: Fixed > Document web SNI settings > - > > Key: ARTEMIS-4333 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4333 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Fix For: 2.30.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Document sniHostCheck and sniRequired settings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4333) Document web SNI settings
[ https://issues.apache.org/jira/browse/ARTEMIS-4333?focusedWorklogId=867352&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867352 ] ASF GitHub Bot logged work on ARTEMIS-4333: --- Author: ASF GitHub Bot Created on: 26/Jun/23 07:13 Start Date: 26/Jun/23 07:13 Worklog Time Spent: 10m Work Description: brusdev commented on PR #4527: URL: https://github.com/apache/activemq-artemis/pull/4527#issuecomment-1606846934 @michalxo good point! I added default values. Issue Time Tracking --- Worklog Id: (was: 867352) Time Spent: 0.5h (was: 20m) > Document web SNI settings > - > > Key: ARTEMIS-4333 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4333 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Document sniHostCheck and sniRequired settings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4333) Document web SNI settings
[ https://issues.apache.org/jira/browse/ARTEMIS-4333?focusedWorklogId=867349&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867349 ] ASF GitHub Bot logged work on ARTEMIS-4333: --- Author: ASF GitHub Bot Created on: 26/Jun/23 07:00 Start Date: 26/Jun/23 07:00 Worklog Time Spent: 10m Work Description: michalxo commented on PR #4527: URL: https://github.com/apache/activemq-artemis/pull/4527#issuecomment-1606827604 LGTM. Thank you Issue Time Tracking --- Worklog Id: (was: 867349) Time Spent: 20m (was: 10m) > Document web SNI settings > - > > Key: ARTEMIS-4333 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4333 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Document sniHostCheck and sniRequired settings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
