[jira] [Commented] (ARTEMIS-2088) Page.write() should throw exception if file is closed
[ https://issues.apache.org/jira/browse/ARTEMIS-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617021#comment-16617021 ] ASF GitHub Bot commented on ARTEMIS-2088: - Github user gaohoward commented on the issue: https://github.com/apache/activemq-artemis/pull/2305 https://issues.apache.org/jira/browse/ARTEMIS-2088 > Page.write() should throw exception if file is closed > - > > Key: ARTEMIS-2088 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2088 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.6.3 >Reporter: Howard Gao >Assignee: Howard Gao >Priority: Major > Fix For: 2.6.4 > > > In Page.write(final PagedMessage message) if the page file is closed it > returns silently. The caller has no way to know that if the message is paged > to file or not. > It should throw an exception so that the caller can handle it correctly. > This causes random failure in test > org.hornetq.tests.integration.client.PagingTest#testExpireLargeMessageOnPaging(). > The test shows that when the server stops it closes the page file. In the > mean time a message is expired to the expiry queue. > and if the expiry queue is in paging mode, it goes to Page.write() and > returns without any error. The result is that the message is removed from the > original queue and not added to the expiry queue. > If we throw exception here it make the expiration failed, the message will > not be removed from the orginal queue. Next time broker is started, the > message will be reloaded and expired again. no message lost. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-7033) Broker not cleaning up session during high message rate
[
https://issues.apache.org/jira/browse/AMQ-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16616693#comment-16616693
]
Jamie goodyear commented on AMQ-7033:
-
Please supply more information about the broker and client(s).
activemq.xml, any parameters passed in via env/start scripts.
Sample client(s).
What is the broker topology? Single broker, NOB, store & forward, etc.
> Broker not cleaning up session during high message rate
> ---
>
> Key: AMQ-7033
> URL: https://issues.apache.org/jira/browse/AMQ-7033
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.15.4
>Reporter: Yogeshkumar More
>Priority: Major
>
> When we try to send large number of messages from multiple connections we see
> that some of the sockets don't get cleaned up. We initially thought
> [AMQ-6561|https://issues.apache.org/jira/browse/AMQ-6561] AMQ-6561 should
> have fixed this. But even after upgrading the version to 5.15.4 we see socket
> leak. Following stack trace proves that there is some blocking which is not
> clearing up the sockets. This grows gradually and causes out of memory issue
> as we are using non-persistent, embedded broker.
>
> {code:java}
> "ActiveMQ InactivityMonitor Worker" #17953 daemon prio=5 os_prio=0
> tid=0x7fdc64017800 nid=0xb27f waiting for monitor entry
> [0x7fda48fce000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.activemq.broker.TransportConnection.stopAsync(TransportConnection.java:1136)
> - waiting to lock <0x0006c2339d58> (a
> org.apache.activemq.broker.TransportConnection)
> at
> org.apache.activemq.broker.TransportConnection.stopAsync(TransportConnection.java:1131)
> at
> org.apache.activemq.broker.TransportConnection.serviceTransportException(TransportConnection.java:239)
> at
> org.apache.activemq.broker.TransportConnection$1.onException(TransportConnection.java:210)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)
> at
> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:173)
> at
> org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:345)
> at
> org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:92)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMQ-6876) Project website does not render correctly over HTTPS in Firefox
[
https://issues.apache.org/jira/browse/AMQ-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16616691#comment-16616691
]
Jamie goodyear commented on AMQ-6876:
-
Looks like those resources are available via HTTPS.
Not sure whom would have perms to setup the wiki to publish the site with HTTPS
links enforced.
https://wiki.apache.org/httpd/RewriteHTTPToHTTPS
> Project website does not render correctly over HTTPS in Firefox
> ---
>
> Key: AMQ-6876
> URL: https://issues.apache.org/jira/browse/AMQ-6876
> Project: ActiveMQ
> Issue Type: Bug
> Components: Documentation
>Reporter: Jiri Daněk
>Priority: Critical
>
> Compare https://activemq.apache.org/mailing-lists.html (wrong)
> and http://activemq.apache.org/mailing-lists.html (correct).
> The HTTPS version is missing CSS styles.
> Browser log:
> {code}
> Blocked loading mixed active content
> “http://activemq.apache.org/styles/site.css”
> [Learn More]
> mailing-lists.html
> Blocked loading mixed active content
> “http://activemq.apache.org/styles/type-settings.css”
> [Learn More]
> mailing-lists.html
> Blocked loading mixed active content
> “http://activemq.apache.org/styles/prototype.js”
> [Learn More]
> mailing-lists.html
> Blocked loading mixed active content
> “http://activemq.apache.org/styles/rico.js”
> [Learn More]
> mailing-lists.html
> Blocked loading mixed active content
> “http://activemq.apache.org/styles/site.js”
> [Learn More]
> mailing-lists.html
> Blocked loading mixed active content
> “http://activemq.apache.org/styles/site.css”
> [Learn More]
> mailing-lists.html
> Blocked loading mixed active content
> “http://activemq.apache.org/styles/type-settings.css”
> [Learn More]
> mailing-lists.html
> Blocked loading mixed active content
> “http://activemq.apache.org/styles/prototype.js”
> [Learn More]
> mailing-lists.html
> Loading failed for the
