An error occured while executing 'IOCPQueueWorkerTask'

Use this forum if you have installed hMailServer and want to ask a question related to a production release of hMailServer. Before posting, please read the troubleshooting guide. A large part of all reported issues are already described in detail here.
Post Reply
Lamprecht
New user
New user
Posts: 6
Joined: 2016-07-24 13:46

An error occured while executing 'IOCPQueueWorkerTask'

Post by Lamprecht » 2016-07-24 13:55

An IMAP Folder read over java mail api, an message getMessag to get an eml creates an folder close event
in hmail log:
"IMAPD" 6740 3 "2016-07-24 13:34:55.243" "87.138.176.236" "RECEIVED: A1606 FETCH 13 (BODY[]<98304.16384>)"
"ERROR" 6740 "2016-07-24 13:34:55.243" "Severity: 3 (Medium), Code: HM5136, Source: TCPConnection::AsyncReadCompleted, Description: An error occured while parsing data. Data length: 36, Data: A1606 FETCH 13 (BODY[]<98304.16384>). Remote IP: 87.138.176.236"
"ERROR" 6740 "2016-07-24 13:34:55.243" "Severity: 2 (High), Code: HM4208, Source: ExceptionHandler::Run, Description: An error occured while executing 'IOCPQueueWorkerTask'"

i attached minidump_2016-07-24 133455_{87353B69-43B7-44C9-8EFF-D0C99ABC4DBE}.dmp
but there is the message in the web frontend : invalidfile extension
i zip it

best regards

Norbert Lamprecht
Attachments
minidump.zip
(33.62 KiB) Downloaded 57 times

User avatar
jimimaseye
Moderator
Moderator
Posts: 8070
Joined: 2011-09-08 17:48

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by jimimaseye » 2016-07-24 14:15

I dont know the full format of an IMAP protocol 'fetch' command but I just tested and compared it to my log. I get

"IMAPD" 2484 40 "2016-07-24 14:02:31.651" "127.0.0.1" "RECEIVED: 28 UID fetch 1563 (UID RFC822.SIZE BODY.PEEK[])"

compare this to yours:

"IMAPD" 6740 3 "2016-07-24 13:34:55.243" "87.138.176.236" "RECEIVED: A1606 FETCH 13 (BODY[]<98304.16384>)"

They look very different.

Mine was done using an known proven mail client (Thunderbird), whereas yours is (you say) with a Java API. So to be sure:

Does the format of your line look the same as every other 'fetch' line?
Do you get the same problem trying to view the same folder/message if you use an established email client (eg, Thunderbird)? (If it works with TB then this would suggest that the cause is with the java API and its command).
HMS 5.6.6 B2383 on Win Server 2008 R2 Foundation, + 5.6.7-B2415 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

User avatar
mattg
Moderator
Moderator
Posts: 19997
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by mattg » 2016-07-24 15:03

Also, what version of hMailsevrer?
This was a known issue back with 5.4, and is fixed in newer releases
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

User avatar
Dravion
Senior user
Senior user
Posts: 1411
Joined: 2015-09-26 11:50
Location: Germany
Contact:

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by Dravion » 2016-07-24 17:53

Kernel Debugger crashdump analyses
Problem: General protectionf ault / EAccessViolation

Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86

APP: hmailserver.exe
FAULTING_MODULE: 76280000 kernel32

EXCEPTION_CODE: (NTSTATUS)
0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_hMailServer.exe!Unknown

Last event: 1314.1a54: Access violation - code c0000005 (first/second chance not available)
debugger time: Sun Jul 24 17:11:38.523 2016 (UTC + 2:00)

Error c0000005 In this case, it simply means the hMailServer function

" IOCPQueueWorkerTask::DoWorkInner() file: IOQueueWorkerTask.cpp "
https://github.com/hmailserver/hmailser ... erTask.cpp

Is trying to access memory which is allready deallocated. If this leads to a stop of hMailServer.exe service this is an flaw. As far as i can see this type of error isnt catched anywhere local and will be redirected to the general, global exception handler.

User avatar
mattg
Moderator
Moderator
Posts: 19997
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by mattg » 2016-07-25 00:10

Yes dravion, that is the fixed version.
Currently these errors will dump a mini-crash anaylsis and keep working.

Quite a few versions back, hmailserver stopped silently with these errors.
The IOCP errors would suddenly appear, sometimes after years of normal use. Once they started it was hard to get them to stop.
Once of the causes was found and a patch built. part of the patch is to do the minidumps (but only 10 of them in a day), but keep working.
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

percepts
Senior user
Senior user
Posts: 5282
Joined: 2009-10-20 16:33
Location: Sceptred Isle

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by percepts » 2016-07-25 02:12

OP posted a minidump. He must have a recent version methinks.

Lamprecht
New user
New user
Posts: 6
Joined: 2016-07-24 13:46

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by Lamprecht » 2016-07-25 10:35

Lamprecht wrote:An IMAP Folder read over java mail api, an message getMessag to get an eml creates an folder close event
in hmail log:
"IMAPD" 6740 3 "2016-07-24 13:34:55.243" "87.138.176.236" "RECEIVED: A1606 FETCH 13 (BODY[]<98304.16384>)"
"ERROR" 6740 "2016-07-24 13:34:55.243" "Severity: 3 (Medium), Code: HM5136, Source: TCPConnection::AsyncReadCompleted, Description: An error occured while parsing data. Data length: 36, Data: A1606 FETCH 13 (BODY[]<98304.16384>). Remote IP: 87.138.176.236"
"ERROR" 6740 "2016-07-24 13:34:55.243" "Severity: 2 (High), Code: HM4208, Source: ExceptionHandler::Run, Description: An error occured while executing 'IOCPQueueWorkerTask'"

i attached minidump_2016-07-24 133455_{87353B69-43B7-44C9-8EFF-D0C99ABC4DBE}.dmp
but there is the message in the web frontend : invalidfile extension
i zip it

best regards

Norbert Lamprecht
java mail api function are used

Lamprecht
New user
New user
Posts: 6
Joined: 2016-07-24 13:46

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by Lamprecht » 2016-07-25 10:36

mattg wrote:Also, what version of hMailsevrer?
This was a known issue back with 5.4, and is fixed in newer releases
last version from last week

Lamprecht
New user
New user
Posts: 6
Joined: 2016-07-24 13:46

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by Lamprecht » 2016-07-25 10:37

percepts wrote:OP posted a minidump. He must have a recent version methinks.
minidump is in attach

Lamprecht
New user
New user
Posts: 6
Joined: 2016-07-24 13:46

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by Lamprecht » 2016-07-25 10:41

jimimaseye wrote:I dont know the full format of an IMAP protocol 'fetch' command but I just tested and compared it to my log. I get

"IMAPD" 2484 40 "2016-07-24 14:02:31.651" "127.0.0.1" "RECEIVED: 28 UID fetch 1563 (UID RFC822.SIZE BODY.PEEK[])"

compare this to yours:

"IMAPD" 6740 3 "2016-07-24 13:34:55.243" "87.138.176.236" "RECEIVED: A1606 FETCH 13 (BODY[]<98304.16384>)"

They look very different.

Mine was done using an known proven mail client (Thunderbird), whereas yours is (you say) with a Java API. So to be sure:

Does the format of your line look the same as every other 'fetch' line?
Do you get the same problem trying to view the same folder/message if you use an established email client (eg, Thunderbird)? (If it works with TB then this would suggest that the cause is with the java API and its command).
problem occurs in a getMessage() function -> java.mail.api -> the function get the massage as .eml file

User avatar
jimimaseye
Moderator
Moderator
Posts: 8070
Joined: 2011-09-08 17:48

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by jimimaseye » 2016-07-25 10:47

Lamprecht wrote:problem occurs in a getMessage() function -> java.mail.api -> the function get the massage as .eml file
And what happens if you try a normal email client to read the same account/message? Does it still crash the same way?
HMS 5.6.6 B2383 on Win Server 2008 R2 Foundation, + 5.6.7-B2415 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

percepts
Senior user
Senior user
Posts: 5282
Joined: 2009-10-20 16:33
Location: Sceptred Isle

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by percepts » 2016-07-25 15:52

Lamprecht wrote:
percepts wrote:OP posted a minidump. He must have a recent version methinks.
minidump is in attach
I think that's what I said!

User avatar
Dravion
Senior user
Senior user
Posts: 1411
Joined: 2015-09-26 11:50
Location: Germany
Contact:

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by Dravion » 2016-07-25 17:44

Manual Telnet IMAP sequence

Thunderbird Message compose:
tb_mail.png
Telnet manual login and message fetch
telnet_imap.png

Lamprecht
New user
New user
Posts: 6
Joined: 2016-07-24 13:46

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by Lamprecht » 2016-07-26 15:47

jimimaseye wrote:
Lamprecht wrote:problem occurs in a getMessage() function -> java.mail.api -> the function get the massage as .eml file
And what happens if you try a normal email client to read the same account/message? Does it still crash the same way?
the problem exits only with java mail api, on thunderbird and emClient the is no problem
but hmail should not crash i think ?

percepts
Senior user
Senior user
Posts: 5282
Joined: 2009-10-20 16:33
Location: Sceptred Isle

Re: An error occured while executing 'IOCPQueueWorkerTask'

Post by percepts » 2016-07-26 16:10

you should email the minidump direct to martin at hmailserver dot com
that way you'll get a faster more direct response with action for this sort of problem. That is what minidumps are for.

Having said that, it looks highly likely that your java api has either got a bug or is not being used correctly (but it could be hmailserver too).

Post Reply