Message constructor throws NullPointerException with empty string

I discovered this when passing an empty (not null) string into the message constructor. The parseHeader assumes that BeginString, Length, and MsgType will be present in the string, when in fact they might not be. This causes parseHeader to operate on a nul field returned by extractField. Below is a patch with tests.