You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Clebert Suconic <cl...@gmail.com> on 2022/07/01 16:34:02 UTC
[HEADS-UP] ActiveMQ Artemis Native some time between 5th and 11th
We should release activemq artemis native within the next 2 weeks.
I am in vacation mode next week but I may try to do a release
anyways... it will be unlikely though as I need some hardware to
compile the native bits (I need that even if I use the Docker).
so, it will be most likely on the week of the 11th.. unless Robbie
Gemmel or anyone else would like to go ahead before me.
--
Clebert Suconic
Re: Need help
Posted by Arthur Naseef <ar...@amlinv.com>.
That error can happen under normal (non-errant) conditions - are there
other symptoms that raise concerns related to it?
One cause of such an error is an unstable network that is dropping
connections. Another could be a simple race between the connection being
closed on the other end and the publisher.
Another consideration - if the application is failing on this exception,
consider using the failover transport - *especially* if their is any type
of intermittent network instability. In such a case, the failover
transport will block until it can successfully connect and the application
won't receive the exception. Just make sure to have adequate logging in
place so you can tell when the application is disconnected.
Art
On Sat, Jul 2, 2022 at 2:32 AM Rupali Lalwani <
rupali.lalwani@eclinicalworks.com> wrote:
>
> Hi All,
>
>
>
> Hope this email find you in good health. I need help, we are using
> activemq 5.13. Recently we started encountering intermittent issue.
>
> Not able to find the solution though, can you please suggest looking at
> the logs?
>
>
>
> javax.jms.JMSException: Cannot send, channel has already failed:
> tcp://XX.XXX.XX.XX:8001
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1421)
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1486)
> at
> org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:527)
> at
> com.ecw.components.ActiveMQPublishService.publishNAV(ActiveMQPublishService.java:73)
> at
> com.ecw.components.RequestProcesssor.insertPHRMessage(RequestProcesssor.java:325)
> at
> org.apache.jsp.jsp.jspnew.requestPHR_jsp._jspService(requestPHR_jsp.java:195)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:476)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>
>
>
>
>
>
>
> Regards,
>
> Rupali Lalwani
>
> 2 Technology Drive | Westborough, MA 01581
>
> T: 508-475-0450<tel:508-475-0450> x17002
>
> rupali.lalwani@eclinicalworks.com<mailto:rupali.lalwani@eclinicalworks.com
> >
>
>
>
> ________________________________
> From: Clebert Suconic <cl...@gmail.com>
> Sent: Friday, July 1, 2022 12:34 PM
> To: dev@activemq.apache.org <de...@activemq.apache.org>
> Subject: [HEADS-UP] ActiveMQ Artemis Native some time between 5th and 11th
>
> [You don't often get email from clebert.suconic@gmail.com. Learn why this
> is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Attention! - This email has originated from an External Source outside of
> eClinicalWorks. Always use caution when opening attachments, clicking
> links, or when responding to this email. If you feel this is a phishing
> scam, please use the Phish Alert Report button in Outlook.
>
>
> We should release activemq artemis native within the next 2 weeks.
>
>
> I am in vacation mode next week but I may try to do a release
> anyways... it will be unlikely though as I need some hardware to
> compile the native bits (I need that even if I use the Docker).
>
>
> so, it will be most likely on the week of the 11th.. unless Robbie
> Gemmel or anyone else would like to go ahead before me.
>
>
> --
> Clebert Suconic
>
> CONFIDENTIALITY NOTICE TO RECIPIENT: This transmission contains
> confidential information belonging to the sender that is legally privileged
> and proprietary and may be subject to protection under the law, including
> the Health Insurance Portability and Accountability Act (HIPAA). If you are
> not the intended recipient of this e-mail, you are prohibited from sharing,
> copying, or otherwise using or disclosing its contents. If you have
> received this e-mail in error, please notify the sender immediately by
> reply e-mail and permanently delete this e-mail and any attachments without
> reading, forwarding or saving them. Thank you.
>
> CONFIDENTIALITY NOTICE TO RECIPIENT: This transmission contains
> confidential information belonging to the sender that is legally privileged
> and proprietary and may be subject to protection under the law, including
> the Health Insurance Portability and Accountability Act (HIPAA). If you are
> not the intended recipient of this e-mail, you are prohibited from sharing,
> copying, or otherwise using or disclosing its contents. If you have
> received this e-mail in error, please notify the sender immediately by
> reply e-mail and permanently delete this e-mail and any attachments without
> reading, forwarding or saving them. Thank you.
>
Need help
Posted by Rupali Lalwani <ru...@eclinicalworks.com>.
Hi All,
Hope this email find you in good health. I need help, we are using activemq 5.13. Recently we started encountering intermittent issue.
Not able to find the solution though, can you please suggest looking at the logs?
javax.jms.JMSException: Cannot send, channel has already failed: tcp://XX.XXX.XX.XX:8001
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1421)
at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1486)
at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:527)
at com.ecw.components.ActiveMQPublishService.publishNAV(ActiveMQPublishService.java:73)
at com.ecw.components.RequestProcesssor.insertPHRMessage(RequestProcesssor.java:325)
at org.apache.jsp.jsp.jspnew.requestPHR_jsp._jspService(requestPHR_jsp.java:195)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:476)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
Regards,
Rupali Lalwani
2 Technology Drive | Westborough, MA 01581
T: 508-475-0450<tel:508-475-0450> x17002
rupali.lalwani@eclinicalworks.com<ma...@eclinicalworks.com>
________________________________
From: Clebert Suconic <cl...@gmail.com>
Sent: Friday, July 1, 2022 12:34 PM
To: dev@activemq.apache.org <de...@activemq.apache.org>
Subject: [HEADS-UP] ActiveMQ Artemis Native some time between 5th and 11th
[You don't often get email from clebert.suconic@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
Attention! - This email has originated from an External Source outside of eClinicalWorks. Always use caution when opening attachments, clicking links, or when responding to this email. If you feel this is a phishing scam, please use the Phish Alert Report button in Outlook.
We should release activemq artemis native within the next 2 weeks.
I am in vacation mode next week but I may try to do a release
anyways... it will be unlikely though as I need some hardware to
compile the native bits (I need that even if I use the Docker).
so, it will be most likely on the week of the 11th.. unless Robbie
Gemmel or anyone else would like to go ahead before me.
--
Clebert Suconic
CONFIDENTIALITY NOTICE TO RECIPIENT: This transmission contains confidential information belonging to the sender that is legally privileged and proprietary and may be subject to protection under the law, including the Health Insurance Portability and Accountability Act (HIPAA). If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you.
CONFIDENTIALITY NOTICE TO RECIPIENT: This transmission contains confidential information belonging to the sender that is legally privileged and proprietary and may be subject to protection under the law, including the Health Insurance Portability and Accountability Act (HIPAA). If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you.
Re: [HEADS-UP] ActiveMQ Artemis Native some time between 5th and 11th
Posted by Robbie Gemmell <ro...@gmail.com>.
Change completed, branch renamed to main. Please update your forks and
checkouts accordingly for simplicity and to avoid pushes to the wrong
branch.
On Mon, 4 Jul 2022 at 11:26, Robbie Gemmell <ro...@gmail.com> wrote:
>
> Request raised as https://issues.apache.org/jira/browse/INFRA-23452
>
> On Mon, 4 Jul 2022 at 11:11, Robbie Gemmell <ro...@gmail.com> wrote:
> >
> > I think it makes sense to just wait until next week, there are still
> > probably some cleanups to be made.
> >
> > E.g I have just tidied up (lifted the commits from then deleted) the
> > secondary main branch just created, and will now raise an INFRA JIRA
> > to have the default renamed to main like all the others done
> > previously, and hopefully that can be completed before you return.
> >
> > On Fri, 1 Jul 2022 at 17:34, Clebert Suconic <cl...@gmail.com> wrote:
> > >
> > > We should release activemq artemis native within the next 2 weeks.
> > >
> > >
> > > I am in vacation mode next week but I may try to do a release
> > > anyways... it will be unlikely though as I need some hardware to
> > > compile the native bits (I need that even if I use the Docker).
> > >
> > >
> > > so, it will be most likely on the week of the 11th.. unless Robbie
> > > Gemmel or anyone else would like to go ahead before me.
> > >
> > >
> > > --
> > > Clebert Suconic
Re: [HEADS-UP] ActiveMQ Artemis Native some time between 5th and 11th
Posted by Robbie Gemmell <ro...@gmail.com>.
Request raised as https://issues.apache.org/jira/browse/INFRA-23452
On Mon, 4 Jul 2022 at 11:11, Robbie Gemmell <ro...@gmail.com> wrote:
>
> I think it makes sense to just wait until next week, there are still
> probably some cleanups to be made.
>
> E.g I have just tidied up (lifted the commits from then deleted) the
> secondary main branch just created, and will now raise an INFRA JIRA
> to have the default renamed to main like all the others done
> previously, and hopefully that can be completed before you return.
>
> On Fri, 1 Jul 2022 at 17:34, Clebert Suconic <cl...@gmail.com> wrote:
> >
> > We should release activemq artemis native within the next 2 weeks.
> >
> >
> > I am in vacation mode next week but I may try to do a release
> > anyways... it will be unlikely though as I need some hardware to
> > compile the native bits (I need that even if I use the Docker).
> >
> >
> > so, it will be most likely on the week of the 11th.. unless Robbie
> > Gemmel or anyone else would like to go ahead before me.
> >
> >
> > --
> > Clebert Suconic
Re: [HEADS-UP] ActiveMQ Artemis Native some time between 5th and 11th
Posted by Robbie Gemmell <ro...@gmail.com>.
I think it makes sense to just wait until next week, there are still
probably some cleanups to be made.
E.g I have just tidied up (lifted the commits from then deleted) the
secondary main branch just created, and will now raise an INFRA JIRA
to have the default renamed to main like all the others done
previously, and hopefully that can be completed before you return.
On Fri, 1 Jul 2022 at 17:34, Clebert Suconic <cl...@gmail.com> wrote:
>
> We should release activemq artemis native within the next 2 weeks.
>
>
> I am in vacation mode next week but I may try to do a release
> anyways... it will be unlikely though as I need some hardware to
> compile the native bits (I need that even if I use the Docker).
>
>
> so, it will be most likely on the week of the 11th.. unless Robbie
> Gemmel or anyone else would like to go ahead before me.
>
>
> --
> Clebert Suconic