The irony of certifications in the Java space is that it is actually the lowest level ones which I think are the most useful.
I have the old Sun Certified Java Programmer for example (the lowest one you can have). While it doesn't really teach you anything that any decent programmer couldn't learn by doing Java tutorials for a few weeks, it does act as a simple filter. To pass it, you simply have to know basic core Java - in this sense, it's probably a somewhat useful filter for junior roles where you're looking for a straight up Java programmer. If they have it, it means they know basic Java.
I've never done any higher certifications than this - but to be honest, from experience I've found that most architects get there by becoming seniors and team leaders and getting promoted in the company simply by being good at what they do. I can't really imagine any of the Java companies I've worked at hiring someone for an architect role off the street. It's essentially in-house senior developers and team leaders who eventually got an architecture role.
At any rate, I think what's important is showing an aptitude for high level system architecture and design by taking ownership of large tasks which exercise these skills. It will probably, in some way, involve being a lower level team lead first. Proven team leading and "architecture-like" high level system design experience goes a much longer way than any certification at this level.
Note: I'm not an architect myself (or even a team lead), but this is what I've observed for over 10 years in various companies. The people who end up architects are people who know how to take ownership of large tasks, lead teams, and get things done. And I don't know any who even had any Java certifications at all.