Typically when you see an error message like this, the relevant information
(if any) is in the other process's logs. So if you're seeing this in the
client's logs, look at the broker's logs for the same time.
Tim
On Thu, Nov 11, 2021, 10:49 AM JB Onofré wrote:
> Can you please provide some
I have also been fiddling around with the ActiveMQ redeliveryPolicy (again),
but can NOT get it to work like the documentation says:
https://activemq.apache.org/redelivery-policy
My requirement:
If you submit a failing message to the broker,
I would like it to stay in the queue forever (until
hmm... then at least I understand why the script is like it is :)
Still, I am surprised if no one else has already reported this;
to me the script as it stands, seems quite unworkable in any
real-world/prod environment...
If one can somehow detect that the environment is busybox (uname -a ,
According to the PR [1] (and the commit message) this change was made in
order to make the script work with busybox. However, according to the
documentation [2] the only options which ps supports on busybox is -o and
-t. In other words, it doesn't support -e (i.e. the change being suggested
here).
Yes I remember the change but it was ok afair. Let me check if it’s not an
assuming option/version of ps.
I will fix that for 5.16.4.
Regards
JB
> Le 11 nov. 2021 à 19:02, J P a écrit :
>
> Hi JB.
> I checked the previous versions -- yes, you are right.
> The change is between 5.16.1 and
FWIW, here's the commit [1] that changed it.
Justin
[1]
https://github.com/apache/activemq/commit/2d78f118d059cbf3fe62d12fb344721820be0f9c
On Thu, Nov 11, 2021 at 12:02 PM J P wrote:
> Hi JB.
> I checked the previous versions -- yes, you are right.
> The change is between 5.16.1 and 5.16.2.
Hi JB.
I checked the previous versions -- yes, you are right.
The change is between 5.16.1 and 5.16.2.
In 5.16.1, the script uses:
ps -p {process-id} -- that also works fine, since it doesn't care which
session started the process.
In 5.16.2, the script is identical to 5.16.3.
So it was
Can you please provide some details ? Versions, transport used, … ?
Thanks
Regards
JB
> Le 8 nov. 2021 à 11:06, Chintapanti, Sai
> a écrit :
>
> Hi -
>
> Sometimes, we are seeing below error when we try to push request into MQ.
> Could someone please help me to understand this error
Hi
I don’t think we changed that in 5.16.3. I will check (I have Mac and Linux
machines to test).
I will keep you posted.
Regards
JB
> Le 11 nov. 2021 à 17:43, J P a écrit :
>
> Isn't there a bug in the ActiveMQ-5.16.3 Linux start-script?
>
> bin/activemq, line 485 reads:
>
>
Isn't there a bug in the ActiveMQ-5.16.3 Linux start-script?
bin/activemq, line 485 reads:
local RET="`ps -o "pid,args" | grep "^\s*$activemq_pid\s.*java"`"
The problem is (from ps man page):
"By default, ps selects all processes with the same effective user
ID (euid=EUID) as the
Justin,
> I think the preference would probably just need to change to be which tab is
> selected by default.
I'll keep that in mind. I was also thinking of just keeping the "last-one-used"
as preference for the next time the screen is used.
Anyway, I'll avoid the case where the first tab is
I like this idea. I think the preference would probably just need to change
to be which tab is selected by default.
Justin
On Thu, Nov 11, 2021 at 7:20 AM Dondorp, Erwin
wrote:
> Sometimes the shortest responses are the most useful!
> thx,
> e.
>
> -Oorspronkelijk bericht-
> Van:
Sometimes the shortest responses are the most useful!
thx,
e.
-Oorspronkelijk bericht-
Van: Domenico Francesco Bruscino
Verzonden: donderdag 11 november 2021 14:07
Aan: users@activemq.apache.org
Onderwerp: Re: Browse Queue (message view) using tabs proposal
EXTERNAL SENDER: Do not
+1
On Mon, 8 Nov 2021 at 17:01, Dondorp, Erwin
wrote:
> [repost, now with the image as a link]
> Hello,
>
> One of the screens that I use often is the Browse Queue screen for a
> single message, so that I can verify all details of the message.
> The screen has some logic to decide on the
14 matches
Mail list logo
