Windows error 0x00000220, 544

Detailed Error Information


MessageAn invalid unwind target was encountered during an unwind operation.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070220.

HRESULT analysis[2]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
Reserved (X)false
FacilityCode0 (0x000)
DescriptionThe default facility code.[2][1]
Error Code544 (0x0220)

Possible solutions


System.out.println eventually blocks


Well this is not a solution but some guidelines for you to investigate further.

As per Apache Ant FAQ

When Apache Ant forks a new process for example by using the , or tasks, it will also start a new thread reading from standard input and sending everything that it has read to that process. . .

In the following lines they have mentioned an issue on Unix-like systems:

This behaviour leads to strange side effects like the Ant process being suspended when a build forking new process is run as a background process on Unix-like systems.....

See the associated Bug.

Steps you can take now:

  1. Update to latest version of Apache Ant
  2. Update to latest version of Java.
  3. If possible apply the latest patches for your OS
  4. Check once whether the problem still exist when you execute application using Ant
  5. If No then smile :)
  6. Else try one alternative way. Try to execute your application via Java's ProcessBuilder or Runtime.getRuntime().exec() i.e. write a small application launcher code and execute your application via that.
  7. If your application works then the problem is with Ant. File a bug.
  8. If the application still behaves oddly then you need to further investigate your code or can think of filing Java bug.

Hope this helps. Good luck.

answered on Stack Overflow Apr 30, 2011 by Favonius

XMS.NET fails when receiving JMS message with RFH2 header at ParseJmsFolder


Is the sender application a JMS (or XMS) application or they hand crafting JMS headers? What version of XMS .NET are you using? Using RFHUtil,

I sent a message containing the JMS folder data your provided above and I see that XMS .NET V8.0 works fine. I also had to set the message type as jms_bytes. So I am wondering if the sender application is setting the message type correctly. Without the message type, application will get type casting error while receiving message.

answered on Stack Overflow Oct 30, 2015 by Shashi


Leave a comment

(plain text only)


  1. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0