Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Google Groups by dusker, 11 months ago
java.lang.RuntimeException: Response code = 400, msg = Bad Request
via Google Groups by kengimel, 11 months ago
java.lang.RuntimeException: Response code = 400, msg = Bad Request
via Google Groups by Andrew, 11 months ago
Response code = 400, msg = Bad Request
via Google Groups by Viktor Bresan, 11 months ago
java.lang.RuntimeException: Response code = 403, msg = OK
via Google Groups by Sanae, 2 years ago
via Google Groups by NECH, 9 months ago
Response code = 400, msg = Bad Request
java.lang.RuntimeException: Response code = 400, msg = Bad
Request	at com.gc.android.market.api.MarketSession.executeRawHttpQuery(MarketSession.java:261)	at com.gc.android.market.api.MarketSession.executeProtobuf(MarketSession.java:230)	at com.gc.android.market.api.MarketSession.flush(MarketSession.java:201)	at com.gc.android.market.api.Main.main(Main.java:73)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)	at java.lang.reflect.Method.invoke(Method.java:597)	at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)