I tested myself and Allcrypt is right - the JSON RPC interface is broken.
I tested sending getmininginfo and receive HTTP (500) Internal Server Error
Some commands work: getaccountaddress, listtransactions, getbalance
Most do not. getpeerinfo, getinfo, getmininginfo, gethashespersec, getgenerate, many more
These commands all work from the debug console in the Windows wallet - they do *NOT* work over a http connection to the wallet. They all return HTTP 500 Internal Server Error
Thanks Mortimer452 - I appreciate the bit of validation there. I had to deal with a lot of "You're compiling it wrong" in this thread. Like I said - it's not us, it's the wallet.
For those who don't run an exchange: The database and background services MUST be able to talk to the wallets to monitor transaction activity, process deposits and withdrawals, and update accounting. The processes do this via RPC calls. If it CANT run the RPC calls, it can't be on the exchange.
I'd love to have Atom on the exchange. But it's clear the developer does not care. Its been weeks now with no response.
I'm sorry guys... if someone manages to fix it, we'd be happy to add it.