[jira] [Created] (AMQNET-768) default SSL context and protocols being set to TLS 1.0
Patrick Mealey created AMQNET-768: - Summary: default SSL context and protocols being set to TLS 1.0 Key: AMQNET-768 URL: https://issues.apache.org/jira/browse/AMQNET-768 Project: ActiveMQ .Net Issue Type: Bug Components: NMS, OpenWire Affects Versions: OpenWire-1.8.0 Reporter: Patrick Mealey The NMS openwire client is unable to connect to ActiveMQ brokers that do not support TLS 1.0 anymore. If not set via the setter, the SslTransport class' GetAllowedProtocol method will return a default value for the SslProtocols enum. It is currently set to an enum value of "Default" which forces the use of TLS 1.0 --which has known vulnerabilities and is often unavailable on the server-side. Microsoft documentation has long recommended using an enum value of "None" as a default value, which allows the OS to determine the best protocol. In addition to the current default value of GetAllowedProtocol() being undesirable, the SslContext class is explicitly initializing a ThreadStatic to TLS. This should also be changed to "None" so that the OS chooses the best protocol. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (ARTEMIS-3824) browse message screen does not display the reply-to address for amqp messages
[
https://issues.apache.org/jira/browse/ARTEMIS-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp updated ARTEMIS-3824:
---
Description:
When setting the reply-to address an an amqp message, it is clear that the a
reply-to address is present because then the property
{{messageAnnotations.x-opt-jms-reply-to}} is shown.
However, the actual reply-to address is not shown.
I should be able to create a PR for this... --> PR is added
was:
When setting the reply-to address an an amqp message, it is clear that the a
reply-to address is present because then the property
\{{messageAnnotations.x-opt-jms-reply-to}} is shown.
However, the actual reply-to address is not shown.
I should be able to create a PR for this...
> browse message screen does not display the reply-to address for amqp messages
> -
>
> Key: ARTEMIS-3824
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3824
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
>Affects Versions: 2.22.0
>Reporter: Erwin Dondorp
>Priority: Minor
> Attachments: image-2022-05-09-22-13-06-361.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When setting the reply-to address an an amqp message, it is clear that the a
> reply-to address is present because then the property
> {{messageAnnotations.x-opt-jms-reply-to}} is shown.
> However, the actual reply-to address is not shown.
> I should be able to create a PR for this... --> PR is added
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (ARTEMIS-3824) browse message screen does not display the reply-to address for amqp messages
[
https://issues.apache.org/jira/browse/ARTEMIS-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp updated ARTEMIS-3824:
---
Attachment: image-2022-05-09-22-13-06-361.png
> browse message screen does not display the reply-to address for amqp messages
> -
>
> Key: ARTEMIS-3824
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3824
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
>Affects Versions: 2.22.0
>Reporter: Erwin Dondorp
>Priority: Minor
> Attachments: image-2022-05-09-22-13-06-361.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When setting the reply-to address an an amqp message, it is clear that the a
> reply-to address is present because then the property
> \{{messageAnnotations.x-opt-jms-reply-to}} is shown.
> However, the actual reply-to address is not shown.
> I should be able to create a PR for this...
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (ARTEMIS-3824) browse message screen does not display the reply-to address for amqp messages
[
https://issues.apache.org/jira/browse/ARTEMIS-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17534006#comment-17534006
]
Erwin Dondorp commented on ARTEMIS-3824:
added display of the reply-to property
tested ok:
!image-2022-05-09-22-13-06-361.png!
> browse message screen does not display the reply-to address for amqp messages
> -
>
> Key: ARTEMIS-3824
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3824
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
>Affects Versions: 2.22.0
>Reporter: Erwin Dondorp
>Priority: Minor
> Attachments: image-2022-05-09-22-13-06-361.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When setting the reply-to address an an amqp message, it is clear that the a
> reply-to address is present because then the property
> \{{messageAnnotations.x-opt-jms-reply-to}} is shown.
> However, the actual reply-to address is not shown.
> I should be able to create a PR for this...
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Work logged] (ARTEMIS-3824) browse message screen does not display the reply-to address for amqp messages
[
https://issues.apache.org/jira/browse/ARTEMIS-3824?focusedWorklogId=768161=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-768161
]
ASF GitHub Bot logged work on ARTEMIS-3824:
---
Author: ASF GitHub Bot
Created on: 09/May/22 20:09
Start Date: 09/May/22 20:09
Worklog Time Spent: 10m
Work Description: erwindon opened a new pull request, #4071:
URL: https://github.com/apache/activemq-artemis/pull/4071
see https://issues.apache.org/jira/browse/ARTEMIS-3824
Issue Time Tracking
---
Worklog Id: (was: 768161)
Remaining Estimate: 0h
Time Spent: 10m
> browse message screen does not display the reply-to address for amqp messages
> -
>
> Key: ARTEMIS-3824
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3824
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
>Affects Versions: 2.22.0
>Reporter: Erwin Dondorp
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When setting the reply-to address an an amqp message, it is clear that the a
> reply-to address is present because then the property
> \{{messageAnnotations.x-opt-jms-reply-to}} is shown.
> However, the actual reply-to address is not shown.
> I should be able to create a PR for this...
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Work logged] (ARTEMIS-3770) Refactor MQTT handling of client ID
[ https://issues.apache.org/jira/browse/ARTEMIS-3770?focusedWorklogId=768144=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-768144 ] ASF GitHub Bot logged work on ARTEMIS-3770: --- Author: ASF GitHub Bot Created on: 09/May/22 19:51 Start Date: 09/May/22 19:51 Worklog Time Spent: 10m Work Description: asfgit closed pull request #4021: ARTEMIS-3770 refactor MQTT handling of client ID URL: https://github.com/apache/activemq-artemis/pull/4021 Issue Time Tracking --- Worklog Id: (was: 768144) Time Spent: 1h 10m (was: 1h) > Refactor MQTT handling of client ID > --- > > Key: ARTEMIS-3770 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3770 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > Time Spent: 1h 10m > Remaining Estimate: 0h > > It would be useful to allow security manager implementations to modify the > client ID value used by MQTT clients. Refactor the MQTT implementation's > handling of client ID to support this functionality. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ARTEMIS-3770) Refactor MQTT handling of client ID
[ https://issues.apache.org/jira/browse/ARTEMIS-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533994#comment-17533994 ] ASF subversion and git services commented on ARTEMIS-3770: -- Commit 446ff61542f47f50c2299d8ef1cae8fe2b98a5ad in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=446ff61542 ] ARTEMIS-3770 refactor MQTT handling of client ID It would be useful for security manager implementations to be able to alter the client ID of MQTT connections. This commit supports this functionality by moving the code which handles the client ID *ahead* of the authentication code. There it sets the client ID on the connection and thereafter any component (e.g. security managers) which needs to inspect or modify it can do so on the connection. This commit also refactors the MQTT connection class to extend the abstract connection class. This greatly simplifies the MQTT connection class and will make it easier to maintain in the future. > Refactor MQTT handling of client ID > --- > > Key: ARTEMIS-3770 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3770 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > It would be useful to allow security manager implementations to modify the > client ID value used by MQTT clients. Refactor the MQTT implementation's > handling of client ID to support this functionality. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work logged] (ARTEMIS-3770) Refactor MQTT handling of client ID
[ https://issues.apache.org/jira/browse/ARTEMIS-3770?focusedWorklogId=768136=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-768136 ] ASF GitHub Bot logged work on ARTEMIS-3770: --- Author: ASF GitHub Bot Created on: 09/May/22 19:44 Start Date: 09/May/22 19:44 Worklog Time Spent: 10m Work Description: jbertram commented on PR #4021: URL: https://github.com/apache/activemq-artemis/pull/4021#issuecomment-1121505440 > Are you expecting to release this fix with the 2.23? Yes. Issue Time Tracking --- Worklog Id: (was: 768136) Time Spent: 1h (was: 50m) > Refactor MQTT handling of client ID > --- > > Key: ARTEMIS-3770 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3770 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > It would be useful to allow security manager implementations to modify the > client ID value used by MQTT clients. Refactor the MQTT implementation's > handling of client ID to support this functionality. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ARTEMIS-3824) browse message screen does not display the reply-to address for amqp messages
Erwin Dondorp created ARTEMIS-3824:
--
Summary: browse message screen does not display the reply-to
address for amqp messages
Key: ARTEMIS-3824
URL: https://issues.apache.org/jira/browse/ARTEMIS-3824
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Web Console
Affects Versions: 2.22.0
Reporter: Erwin Dondorp
When setting the reply-to address an an amqp message, it is clear that the a
reply-to address is present because then the property
\{{messageAnnotations.x-opt-jms-reply-to}} is shown.
However, the actual reply-to address is not shown.
I should be able to create a PR for this...
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (ARTEMIS-3823) Connection router - consistent hash modulo needs to deal with negative hash values
Gary Tully created ARTEMIS-3823: --- Summary: Connection router - consistent hash modulo needs to deal with negative hash values Key: ARTEMIS-3823 URL: https://issues.apache.org/jira/browse/ARTEMIS-3823 Project: ActiveMQ Artemis Issue Type: Improvement Components: balancer Affects Versions: 2.22.0 Reporter: Gary Tully Assignee: Gary Tully Fix For: 2.23.0 The connection router consistent hash modulo key transformer does not work well if the hash produced a negative value. It makes matching more difficult to configure b/c both -1 and 1 need to be matched for a broker ordinal 1. it would be better if the modulo was confined to positive numbers, rather than the signed remainder. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (ARTEMIS-3822) Get broker name via management
Justin Bertram created ARTEMIS-3822: --- Summary: Get broker name via management Key: ARTEMIS-3822 URL: https://issues.apache.org/jira/browse/ARTEMIS-3822 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Justin Bertram -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work logged] (ARTEMIS-3808) Support starting/stopping the embedded web server via mangement
[
https://issues.apache.org/jira/browse/ARTEMIS-3808?focusedWorklogId=768083=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-768083
]
ASF GitHub Bot logged work on ARTEMIS-3808:
---
Author: ASF GitHub Bot
Created on: 09/May/22 18:11
Start Date: 09/May/22 18:11
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #4061:
URL: https://github.com/apache/activemq-artemis/pull/4061#discussion_r868286574
##
artemis-web/src/test/java/org/apache/activemq/cli/test/WebServerComponentTest.java:
##
@@ -175,31 +166,31 @@ public void testComponentStopBehavior() throws Exception {
Assert.assertFalse(webServerComponent.isStarted());
webServerComponent.configure(webServerDTO, "./src/test/resources/",
"./src/test/resources/");
webServerComponent.start();
- final int port = webServerComponent.getPort();
// Make the connection attempt.
- CountDownLatch latch = new CountDownLatch(1);
- final ClientHandler clientHandler = new ClientHandler(latch);
- bootstrap.group(group).channel(NioSocketChannel.class).handler(new
ChannelInitializer() {
- @Override
- protected void initChannel(Channel ch) throws Exception {
-ch.pipeline().addLast(new HttpClientCodec());
-ch.pipeline().addLast(clientHandler);
- }
- });
- Channel ch = bootstrap.connect("localhost", port).sync().channel();
+ verifyConnection(webServerComponent.getPort());
+ Assert.assertTrue(webServerComponent.isStarted());
- URI uri = new URI(URL);
- // Prepare the HTTP request.
- HttpRequest request = new DefaultFullHttpRequest(HttpVersion.HTTP_1_1,
HttpMethod.GET, uri.getRawPath());
- request.headers().set(HttpHeaderNames.HOST, "localhost");
+ //usual stop won't actually stop it
+ webServerComponent.stop();
+ assertTrue(webServerComponent.isStarted());
- // Send the HTTP request.
- ch.writeAndFlush(request);
- assertTrue(latch.await(5, TimeUnit.SECONDS));
- assertEquals("12345", clientHandler.body.toString());
- // Wait for the server to close the connection.
- ch.close();
- ch.eventLoop().shutdownNow();
+ webServerComponent.stop(true);
+ Assert.assertFalse(webServerComponent.isStarted());
+ }
+
+ @Test
+ public void testComponentStopStartBehavior() throws Exception {
Review Comment:
The default config in `management.xml` should cover these methods.
Issue Time Tracking
---
Worklog Id: (was: 768083)
Time Spent: 2.5h (was: 2h 20m)
> Support starting/stopping the embedded web server via mangement
> ---
>
> Key: ARTEMIS-3808
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3808
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> It would be useful to be able to cycle the embedded web server if, for
> example, one needed to renew the SSL certificates.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Work logged] (ARTEMIS-3808) Support starting/stopping the embedded web server via mangement
[
https://issues.apache.org/jira/browse/ARTEMIS-3808?focusedWorklogId=768079=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-768079
]
ASF GitHub Bot logged work on ARTEMIS-3808:
---
Author: ASF GitHub Bot
Created on: 09/May/22 18:09
Start Date: 09/May/22 18:09
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #4061:
URL: https://github.com/apache/activemq-artemis/pull/4061#discussion_r868284271
##
artemis-server/src/main/java/org/apache/activemq/artemis/core/management/impl/ActiveMQServerControlImpl.java:
##
@@ -4479,5 +4482,39 @@ public void replay(String startScan, String endScan,
String address, String targ
server.replay(startScanDate, endScanDate, address, target, filter);
}
+
+ @Override
+ public void stopEmbeddedWebServer() throws Exception {
+ for (ActiveMQComponent component : server.getExternalComponents()) {
Review Comment:
Done.
Issue Time Tracking
---
Worklog Id: (was: 768079)
Time Spent: 2h 20m (was: 2h 10m)
> Support starting/stopping the embedded web server via mangement
> ---
>
> Key: ARTEMIS-3808
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3808
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> It would be useful to be able to cycle the embedded web server if, for
> example, one needed to renew the SSL certificates.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Work logged] (ARTEMIS-3808) Support starting/stopping the embedded web server via mangement
[
https://issues.apache.org/jira/browse/ARTEMIS-3808?focusedWorklogId=768053=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-768053
]
ASF GitHub Bot logged work on ARTEMIS-3808:
---
Author: ASF GitHub Bot
Created on: 09/May/22 17:25
Start Date: 09/May/22 17:25
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #4061:
URL: https://github.com/apache/activemq-artemis/pull/4061#discussion_r868244998
##
artemis-commons/src/main/java/org/apache/activemq/artemis/core/server/ActiveMQComponent.java:
##
@@ -29,4 +31,8 @@ default void asyncStop(Runnable callback) throws Exception {
}
boolean isStarted();
+
+ default SimpleString getName() {
+ return SimpleString.toSimpleString("");
+ }
Review Comment:
I think using a marker interface is a great idea. I hadn't considered that.
Issue Time Tracking
---
Worklog Id: (was: 768053)
Time Spent: 2h 10m (was: 2h)
> Support starting/stopping the embedded web server via mangement
> ---
>
> Key: ARTEMIS-3808
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3808
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> It would be useful to be able to cycle the embedded web server if, for
> example, one needed to renew the SSL certificates.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (AMQ-2798) Occaional hangs on ensureConnectionInfoSent
[
https://issues.apache.org/jira/browse/AMQ-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533917#comment-17533917
]
Sthala Narasimhan commented on AMQ-2798:
I use CMS version 3.9.5 in my project. Occasionally, the client crashes/hangs
at this location. I guess the problem is not yet solved.
> Occaional hangs on ensureConnectionInfoSent
> ---
>
> Key: AMQ-2798
> URL: https://issues.apache.org/jira/browse/AMQ-2798
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
>Affects Versions: 5.3.2
>Reporter: Mark Chaimungkalanont
>Assignee: Timothy A. Bish
>Priority: Major
> Fix For: 5.5.0
>
> Attachments: blocked-connection-patch3
>
>
> When connecting to the broker, the client occasionally starts to hang. A
> thread dump reveals:
> {noformat}
> "QuartzScheduler_Worker-7" prio=5 tid=0x0116f190 nid=0x1ce2400 waiting on
> condition [0xf1fae000..0xf1fafb30]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1767)
> at
> java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:341)
> at
> org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:40)
> at
> org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:80)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1233)
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1339)
> - locked <0x10b9bdf8> (a java.lang.Object)
> at
> org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:298)
> at org.jencks.amqpool.SessionPool.createSession(SessionPool.java:110)
> at org.jencks.amqpool.SessionPool.makeObject(SessionPool.java:78)
> at
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
> at org.jencks.amqpool.SessionPool.borrowSession(SessionPool.java:53)
> at
> org.jencks.amqpool.ConnectionPool.createSession(ConnectionPool.java:89)
> at
> org.jencks.amqpool.XaConnectionPool.createSession(XaConnectionPool.java:51)
> at
> org.jencks.amqpool.PooledConnection.createSession(PooledConnection.java:132)
> at
> org.springframework.jms.support.JmsAccessor.createSession(JmsAccessor.java:200)
> {noformat}
> Looking closer at the code of {{ensureConnectionInfoSent}} in
> {{ActiveMQConnection}}, it uses the method:
> {code}
> public Response syncSendPacket(Command command) throws JMSException {
> {code}
> which never times out, possibly causing everything to hang eternally. There
> does seem to be an identical method that allows for a timeout.
> {code}
> public Response syncSendPacket(Command command, int timeout) throws
> JMSException {
> {code}
> should / can ensureConnectionInfoSent use the one with the timeout instead?
> We're using the failover transport:
> failover:(tcp://:54663?wireFormat.maxInactivityDuration=30)?maxReconnectAttempts=10initialReconnectDelay=15000
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[
https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-3818:
Fix Version/s: (was: 2.15.0)
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Minor
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (AMQCPP-712) ActiveMQConnection Start() hangs forever/not connecting with Broker
[ https://issues.apache.org/jira/browse/AMQCPP-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533905#comment-17533905 ] Sthala Narasimhan commented on AMQCPP-712: -- Sometimes, the client crashes. Can you give some tips to find out what is going on in the client side? > ActiveMQConnection Start() hangs forever/not connecting with Broker > --- > > Key: AMQCPP-712 > URL: https://issues.apache.org/jira/browse/AMQCPP-712 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: CMS Impl >Affects Versions: 3.9.5 > Environment: Windows server 2012 R2 >Reporter: Sthala Narasimhan >Assignee: Timothy A. Bish >Priority: Major > > My Client application uses CMS Library 3.9.5 with failover protocol.. When I > invoke Start() function to connect to broker it hangs/ not connecting, though > broker is configured correctly > std::string brokerURI = > "failover:(tcp://host1:61400,tcp://host2:61400)=1; > ActiveMQConnection* conn = 0; > ActiveMQConnectionFactory *amqfactory = new > ActiveMQConnectionFactory(brokerURI); > conn = amqfactory->createConnection(); > delete amqfactory; > amqfactory = NULL; > //Hangs here forever or timeout. > conn->start(); > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[ https://issues.apache.org/jira/browse/ARTEMIS-3818 ]
Robbie Gemmell deleted comment on ARTEMIS-3818:
-
was (Author: gemmellr):
Also worth an upgrade, there have been numerous fixes and improvements since
2.15.0.
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Minor
> Fix For: 2.15.0
>
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[
https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533886#comment-17533886
]
Robbie Gemmell commented on ARTEMIS-3818:
-
Also worth an upgrade, there have been numerous fixes and improvements since
2.15.0.
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Minor
> Fix For: 2.15.0
>
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[
https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533887#comment-17533887
]
Robbie Gemmell commented on ARTEMIS-3818:
-
Also worth an upgrade, there have been numerous fixes and improvements since
2.15.0.
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Minor
> Fix For: 2.15.0
>
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[
https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533883#comment-17533883
]
Justin Bertram commented on ARTEMIS-3818:
-
In the future please use the [ActiveMQ users mailing
list|https://activemq.apache.org/contact] for questions like this. Jira is
generally reserved for confirmed bugs and feature requests.
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Minor
> Fix For: 2.15.0
>
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[
https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533881#comment-17533881
]
Justin Bertram commented on ARTEMIS-3818:
-
This message is just indicating that a client connected to a particular
acceptor (i.e. {{mqtts}} in this case) and didn't finish its protocol handshake
within the allotted time (i.e. 10 seconds). This could be caused by all sorts
of things, e.g.:
* A network scanning tool that simply probes the port where the acceptor is
listening.
* A crashing client.
* A network problem that is interrupting normal communication with a client.
The message provides you with the IP address of the remote client. I recommend
you investigate what/who that client is to determine why they are not
completing their protocol handshake.
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Blocker
> Fix For: 2.15.0
>
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[
https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-3818.
-
Resolution: Information Provided
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Blocker
> Fix For: 2.15.0
>
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[
https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-3818:
Priority: Minor (was: Blocker)
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Minor
> Fix For: 2.15.0
>
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[
https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-3818:
Description:
We are facing sudden issue with Artemis service, Service is stopping
frequently. When we verified logs we encountered below issue.
{noformat}
AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
Could you please check this on priority and try help out to get this issue
fixed.
was:
We are facing sudden issue with Artemis service, Service is stopping
frequently. When we verified logs we encountered below issue.
{noformat}
AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
Could you please check this on priority and try help out to get this issue
fixed.
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Blocker
> Fix For: 2.15.0
>
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[
https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-3818:
Description:
We are facing sudden issue with Artemis service, Service is stopping
frequently. When we verified logs we encountered below issue.
{noformat}
AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
Could you please check this on priority and try help out to get this issue
fixed.
was:
Hi Team,
We are facing sudden issue with Artemis service, Service is stopping
frequently. When we verified logs we encountered below issue.
AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
with /xx.xxx.xxx.xx:19493 has occurred.
Could you please check this on priority and try help out to get this issue
fixed.
Thanks in advance!
Regards,
Supriya
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.
> -
>
> Key: ARTEMIS-3818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3818
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.15.0
>Reporter: Supriya Narute
>Priority: Blocker
> Fix For: 2.15.0
>
>
> We are facing sudden issue with Artemis service, Service is stopping
> frequently. When we verified logs we encountered below issue.
> {noformat}
> AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake
> with /xx.xxx.xxx.xx:19493 has occurred.{noformat}
> Could you please check this on priority and try help out to get this issue
> fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[ https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-3818: Component/s: (was: ActiveMQ-Artemis-Native) > AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake > with /xx.xxx.xxx.xx:19493 has occurred. > - > > Key: ARTEMIS-3818 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3818 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.15.0 >Reporter: Supriya Narute >Assignee: Clebert Suconic >Priority: Blocker > Fix For: 2.15.0 > > > Hi Team, > > We are facing sudden issue with Artemis service, Service is stopping > frequently. When we verified logs we encountered below issue. > > AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake > with /xx.xxx.xxx.xx:19493 has occurred. > > Could you please check this on priority and try help out to get this issue > fixed. > > Thanks in advance! > > Regards, > Supriya > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (ARTEMIS-3818) AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake with /xx.xxx.xxx.xx:19493 has occurred.
[ https://issues.apache.org/jira/browse/ARTEMIS-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-3818: --- Assignee: (was: Clebert Suconic) > AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake > with /xx.xxx.xxx.xx:19493 has occurred. > - > > Key: ARTEMIS-3818 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3818 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.15.0 >Reporter: Supriya Narute >Priority: Blocker > Fix For: 2.15.0 > > > Hi Team, > > We are facing sudden issue with Artemis service, Service is stopping > frequently. When we verified logs we encountered below issue. > > AMQ224088: Timeout (10 seconds) on acceptor "mqtts" during protocol handshake > with /xx.xxx.xxx.xx:19493 has occurred. > > Could you please check this on priority and try help out to get this issue > fixed. > > Thanks in advance! > > Regards, > Supriya > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (ARTEMIS-3817) Management schedulePageCleanup operation on AddressControl
[ https://issues.apache.org/jira/browse/ARTEMIS-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17533799#comment-17533799 ] ASF subversion and git services commented on ARTEMIS-3817: -- Commit e420eb47322e27878303f1272e335da27f738a27 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=e420eb4732 ] ARTEMIS-3817 SchedulePageCleanup operation on AddressControl > Management schedulePageCleanup operation on AddressControl > -- > > Key: ARTEMIS-3817 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3817 > Project: ActiveMQ Artemis > Issue Type: New Feature >Affects Versions: 2.22.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.23.0 > > Time Spent: 10m > Remaining Estimate: 0h > > I should add a schedule Page Cleanup operation as a management tool. > the system should do its own scheduling, but sometimes it is useful to try > forcing a cleanup in certain cases. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work logged] (ARTEMIS-3817) Management schedulePageCleanup operation on AddressControl
[ https://issues.apache.org/jira/browse/ARTEMIS-3817?focusedWorklogId=767906=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767906 ] ASF GitHub Bot logged work on ARTEMIS-3817: --- Author: ASF GitHub Bot Created on: 09/May/22 13:17 Start Date: 09/May/22 13:17 Worklog Time Spent: 10m Work Description: clebertsuconic merged PR #4068: URL: https://github.com/apache/activemq-artemis/pull/4068 Issue Time Tracking --- Worklog Id: (was: 767906) Remaining Estimate: 0h Time Spent: 10m > Management schedulePageCleanup operation on AddressControl > -- > > Key: ARTEMIS-3817 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3817 > Project: ActiveMQ Artemis > Issue Type: New Feature >Affects Versions: 2.22.0 >Reporter: Clebert Suconic >Assignee: Clebert Suconic >Priority: Major > Fix For: 2.23.0 > > Time Spent: 10m > Remaining Estimate: 0h > > I should add a schedule Page Cleanup operation as a management tool. > the system should do its own scheduling, but sometimes it is useful to try > forcing a cleanup in certain cases. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work logged] (ARTEMIS-3763) Use configurable time margin for checking offset between database server and broker
[ https://issues.apache.org/jira/browse/ARTEMIS-3763?focusedWorklogId=767814=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767814 ] ASF GitHub Bot logged work on ARTEMIS-3763: --- Author: ASF GitHub Bot Created on: 09/May/22 07:28 Start Date: 09/May/22 07:28 Worklog Time Spent: 10m Work Description: MM53 commented on PR #4017: URL: https://github.com/apache/activemq-artemis/pull/4017#issuecomment-1120743257 Are there any updates on this PR? I checked our setup and there are only a few milliseconds difference between the servers on an average. Therefore I assume this change could also be interesting for others. Additionally it would set a fixed boundary for the time offset instead of relying on striped milliseconds. Issue Time Tracking --- Worklog Id: (was: 767814) Time Spent: 1.5h (was: 1h 20m) > Use configurable time margin for checking offset between database server and > broker > --- > > Key: ARTEMIS-3763 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3763 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration >Affects Versions: 2.21.0 >Reporter: Marlon Müller >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > When using JDBC persistence artemis checks for time differences between the > broker and the database. Currently this check requests the time of the > database and compares it to the system time before and after sending this > query by removing the milliseconds and verifying that the database time is > between the start and the end time. > This leads to somehow random warnings in the log depending on the current > milliseconds when this check is performed. > For example if the time on your artemis server is 00:00:01.000 before the > check and the time on the database is 00:00:00.999 it will log a warning > although there is only 1 millisecond difference. On the other hand if your > artemis server time is 00:00:01.000 after sending the query and the database > time is 00:00:01.999 there will be no warning although the time is 999 > milliseconds after the end time. > Therefore it would be better to use a consistent margin for the database time > during this check. To avoid problems in setups where the system times are not > well synchronized, this time margin should be configurable to allow the user > to fine tune it. -- This message was sent by Atlassian Jira (v8.20.7#820007)
