OP doesn't seem to know their code is broken. Perhaps due to insufficient testing, but to the best of their knowledge, the code works and produces the expected output.
The "spirit" of the "working code" rule isn't to forbid code with bugs - in fact part of the peer review exercise is to highlight unforeseen edge cases and other issues - it's very possible that a programmer might have written code that works for the input they're feeding it, but that breaks in other situations; if OP isn't aware of this, they won't be asking for solutions to such specific issues.
The "spirit" of the "working code" rule is that on-topic CR questions aren't questions asking things like "my code does X, but it should do Y - how do I fix that?", which would typically be on-topic on Stack Overflow.
A java gold-badger moderator reviewed the code in the close queue, and found no convincing evidence of how badly the code might be broken, and chose to leave it open.
I think the best thing to do is to show everyone what you're seeing that everybody else missed, and then collect the upvotes!