OpenAMQ

Reported by mclaughlin77 (1235085258|%O ago)

Here was how I started the server:

amq_server —heartbeat 45 —direct 1 —direct_heartbeat 45 —log_path /opt/ibase/logs

Here's the gdb backtrace:

[root@vm3-test-125 bin]# gdb amq_server core.28736
GNU gdb Red Hat Linux (6.5-37.el5_2.2rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"…Using host libthread_db library "/lib/libthread_db.so.1".

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/libm.so.6…done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libpthread.so.0…done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libc.so.6…done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2…done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_files.so.2…done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_dns.so.2…done.
Loaded symbols for /lib/libnss_dns.so.2
Reading symbols from /lib/libresolv.so.2…done.
Loaded symbols for /lib/libresolv.so.2
Core was generated by ‘amq_server —heartbeat 45 —direct 1 —direct_heartbeat 45 —log_path /opt/ibas’.
Program terminated with signal 6, Aborted.
#0 0x0068f402 in __kernel_vsyscall ()
(gdb) bt
#0 0x0068f402 in __kernel_vsyscall ()
#1 0x00891c10 in raise () from /lib/libc.so.6
#2 0x00893521 in abort () from /lib/libc.so.6
#3 0x080b348b in report_unrecognised_event_error (thread=0x88a8cb8) at amq_server_agent.c:15548
#4 0x080b8daa in amq_server_agent_manager (thread_p=0xb42f23a8) at amq_server_agent.c:4795
#5 0x081763fc in s_execute (apr_thread=0x87ebf18, data=0x87c3b40) at smt_os_thread.c:3216
#6 0x0819d396 in dummy_worker (opaque=0x87ebf18) at threadproc/unix/thread.c:138
#7 0x009df43b in start_thread () from /lib/libpthread.so.0
#8 0x00936fde in clone () from /lib/libc.so.6
(gdb) quit

I dont' see this problem if I run the server with direct mode disabled.Please let me know if I can provide more information to help resolve this problem.

Attachments:

Comments

Show Comments

Hide All Comments | Unfold All | Fold All

Fold

Console output?

pieterh 19 Feb 2009 23:36

Kelly, thanks for reporting this. It's been a while since we had a decent crash in OpenAMQ. There will be a diagnostic printed to the console along the lines of ""amq_server_agent: unrecognised event…". If you can recover this, from the log files (assuming stdout/stderr was captured) or by reproducing the error, we can fix it.

Without this diagnostic, we can guess but not properly fix the error. I'm going to in any case change the code so that it saves this to a file rather than the console, given the difficulty of picking up messages after the fact.

---

Portfolio

Reply  |  Options

Unfold Console output? by pieterh, 19 Feb 2009 23:36

Fold

Re: Console output?

mclaughlin77 20 Feb 2009 00:05

It was no problem. I should have included this in the first place. Thanks for the quick response.

2009-02-19 16:01:38: amq_server_agent: Unrecognised event 'Socket-Error' in 'Master' thread number: 6, state: New-Connection

Reply  |  Options

Unfold Re: Console output? by mclaughlin77, 20 Feb 2009 00:05

Fold

pieterh 20 Feb 2009 08:11

Kelly: a few questions

• Can you reproduce this crash?
• Did the crash start to happen in 1.3c5?

Thanks

---

Portfolio

Reply  |  Options

Unfold by pieterh, 20 Feb 2009 08:11

Fold

OK, solved

pieterh 20 Feb 2009 08:20

@Kelly,

I reviewed the 1.3c5 package and it looks like we fixed this issue but the fix did not make it into the release. This is the same as 45 and is caused by the process running out of socket handles. Direct Mode uses up more sockets than normal mode.

You can work around the issue by increasing the number of sockets available to your process. If you tell us what OS you're on, we'll help you if you need it.

I'm going to close this issue and we'll include that fix in the next 1.3c release..

---

Portfolio

Reply  |  Options

Unfold OK, solved by pieterh, 20 Feb 2009 08:20

Fold

Re: OK, solved

mclaughlin77 20 Feb 2009 15:30

Pieter,

Thanks for the explanation. That does make sense with what I was seeing. I'll try increasing the socket limit on my machine and give it another try.

Reply  |  Options

Unfold Re: OK, solved by mclaughlin77, 20 Feb 2009 15:30

Add a New Comment

Permanent Link | Edit | Delete

Edit | Files | Tags | Print

Who's following this issue?

pieterh

martin_sustrik

mclaughlin77

Cybarite

Submitted by mclaughlin77

Use one of these tags to say what kind of issue it is:

• issue - a fault in the software or the packaging or the documentation.
• change - a change or feature request.

Use one of these tags to say what state the issue is in:

• open - a new, open issue.
• closed - issue has been closed.
• rejected - the issue has been rejected.

Use one of these tags to say how urgent the issue is:

• fatal - the issue is stopping all work.
• urgent - it's urgent.

All open

Most recent