最近在用parse的时候遇到的BUG.A resource was acquired at attached stack trace but never released.
2014-07-21 20:34
309 查看
这个问题怎么因为是使用第三方的包.所以没办法详细追究代码里面的问题.就先贴出来.后面再看下解决方案吧.
07-21 19:33:53.145: E/StrictMode(21289): A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
07-21 19:33:53.145: E/StrictMode(21289): java.lang.Throwable: Explicit termination method 'close' not called
07-21 19:33:53.145: E/StrictMode(21289): at dalvik.system.CloseGuard.open(CloseGuard.java:184)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:277)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl.getSession(OpenSSLSocketImpl.java:738)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:92)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java:381)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:165)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:360)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:670)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:509)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
07-21 19:33:53.145: E/StrictMode(21289): at com.parse.ParseCommand$6.call(ParseCommand.java:425)
07-21 19:33:53.145: E/StrictMode(21289): at com.parse.ParseCommand$6.call(ParseCommand.java:1)
07-21 19:33:53.145: E/StrictMode(21289): at com.parse.Task$3.run(Task.java:225)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:390)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.FutureTask.run(FutureTask.java:234)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:153)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
07-21 19:33:53.145: E/StrictMode(21289): at java.lang.Thread.run(Thread.java:841)
--------------------------------------------------------------------------------
7/23.
根据查到的一点资料是..在内部产生了死循环.
因为并发的访问服务器..产生了一些混乱.
所以需要我们建立一个队列.来把并发访问变成串.顺序的访问.
07-21 19:33:53.145: E/StrictMode(21289): A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
07-21 19:33:53.145: E/StrictMode(21289): java.lang.Throwable: Explicit termination method 'close' not called
07-21 19:33:53.145: E/StrictMode(21289): at dalvik.system.CloseGuard.open(CloseGuard.java:184)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:277)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl.getSession(OpenSSLSocketImpl.java:738)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:92)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java:381)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:165)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:360)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:670)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:509)
07-21 19:33:53.145: E/StrictMode(21289): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
07-21 19:33:53.145: E/StrictMode(21289): at com.parse.ParseCommand$6.call(ParseCommand.java:425)
07-21 19:33:53.145: E/StrictMode(21289): at com.parse.ParseCommand$6.call(ParseCommand.java:1)
07-21 19:33:53.145: E/StrictMode(21289): at com.parse.Task$3.run(Task.java:225)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:390)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.FutureTask.run(FutureTask.java:234)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:153)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
07-21 19:33:53.145: E/StrictMode(21289): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
07-21 19:33:53.145: E/StrictMode(21289): at java.lang.Thread.run(Thread.java:841)
--------------------------------------------------------------------------------
7/23.
根据查到的一点资料是..在内部产生了死循环.
因为并发的访问服务器..产生了一些混乱.
所以需要我们建立一个队列.来把并发访问变成串.顺序的访问.
相关文章推荐
- A new session could not be created. (Original error: Requested a new session but one was in progress) (WARNING: The server did not provide any stacktrace information)
- Gson 解析时候报错: Expected BEGIN_OBJECT but was BEGIN_ARRAY at line 1 column 2 path $
- 最近安装Eclipse adt的时候会爆出:java was started but returned exit code = 13
- Expected BEGIN_OBJECT but was STRING at line 4 column 1 path $ 错误积累
- 最近在用SDK写俄罗斯的时候遇到了很多问题 ...点亮GDI盲区值得看
- WINDOWS上启动maven nexus的时候报 The nexus service was launched, but failed to start
- java.lang.IllegalStateException: Expected BEGIN_OBJECT but was was STRING at line 1 column 1
- com.mchange.v2.resourcepool.ResourcePoolException: Unexpected Break Stack Trace!
- git pull时遇到git pull error :error: remote ref is at but expected问题的解决办法
- nexus start的时候报 wrapper | The nexus service was launched, but failed to start
- 20140627-IAR平台中Warning[Pe550]: variable "xxxx" was set but never used的问题
- 使用log4j的时候如何输出printStackTrace()的堆栈信息
- solrcloud部署的时候遇到一个solrj版本不一致导致的BUG
- 安装eclipse 遇到Java was started but returned exit code=13
- 记录安卓遇到的两个小bug,望初学者写代码的时候引以为戒
- java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at line 1 column 81
- java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at line 1 column 2 path $
- 最近一段时间在使用zepto.js的tap事件的时候,出现执行两次的bug,并报错
- 最近遇到的一个数组越界的BUG
- 警告: The web application [ROOT] appears to have started a thread named [Thread-48] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: