My favorites | Sign in
Project Home Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 108: [easygou-client]在检索信息列表中,单击查看一条有详细信息的记录时,有时会提示“对不起,本条信息没有详细信息,请选择其它信息”
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  chendequ...@gmail.com
Closed:  Apr 2013


 
Project Member Reported by chenling...@gmail.com, Mar 27, 2013
What steps will reproduce the problem?
1. 检索信息
2. 在检索到的信息列表中,单击一条信息,查看其详细信息
3.

What is the expected output? What do you see instead?

有时会提示“对不起,本条信息没有详细信息,请选择其它信息”,但是这条信息是有详细信息的,可能是因为网络问题,导致返回不了详细信息。所以这个提示语不正确
Please use labels and text to provide additional information.


Mar 27, 2013
Project Member #1 chendequ...@gmail.com
经查看,服务器端报错



The last packet successfully received from the server was 30,541,814 milliseconds ago.  The last packet sent successfully to the server was 1 milliseconds ago.
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
	at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
	at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3589)
	at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3478)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4019)
	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490)
	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2734)
	at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
	at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2322)
	at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:122)
	at org.hibernate.engine.jdbc.internal.proxy.AbstractProxyHandler.invoke(AbstractProxyHandler.java:81)
	at $Proxy8.executeQuery(Unknown Source)
	at org.hibernate.loader.Loader.getResultSet(Loader.java:1926)
	at org.hibernate.loader.Loader.executeQueryStatement(Loader.java:1727)
	... 39 more
Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
	at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:3039)
	at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3489)
	... 54 more
 WARN (?:?) - FindById failed, message:No operations allowed after connection closed.
DEBUG (AbstractTransactionImpl.java:203) - rolling back
 WARN (?:?) - findById message failed, message: rollback failed, cause: org.hibernate.TransactionException: unable to rollback against JDBC connection

Mar 27, 2013
Project Member #2 chendequ...@gmail.com
(No comment was entered for this change.)
Owner: chendequ...@gmail.com
Mar 27, 2013
Project Member #3 chendequ...@gmail.com
(No comment was entered for this change.)
Labels: -Priority-Medium Priority-High
Mar 27, 2013
Project Member #4 chendequ...@gmail.com
(No comment was entered for this change.)
Labels: Milestone-Release1.0
Mar 27, 2013
Project Member #5 chendequ...@gmail.com
目前服务器端返回的代码统一为-1, 但消息提示不一样。目前从后台返回的都是HibernateException,所以无法分辨具体错误类型来确定返回代码,建议在前端把消息提示改成”获取详细出错,请过30秒后重试“,  BUG#76 已经重新开启,会继续进行解决。
Owner: tlyrc2...@gmail.com
Mar 27, 2013
Project Member #6 chendequ...@gmail.com
(No comment was entered for this change.)
Summary: [easygou-client]在检索信息列表中,单击查看一条有详细信息的记录时,有时会提示“对不起,本条信息没有详细信息,请选择其它信息” (was: 在检索信息列表中,单击查看一条有详细信息的记录时,有时会提示“对不起,本条信息没有详细信息,请选择其它信息”)
Mar 28, 2013
Project Member #7 tlyrc2...@gmail.com
建议:1、在服务器端如果出现异常,可以封装一个error code返回api端。
      2、API端向client端抛出的异常加上相应的error code。
      3、定义统一的error code对应的错误描述。
Apr 1, 2013
Project Member #8 chendequ...@gmail.com
先修复client端,Release2.0会修复 Bug#111 
Owner: chendequ...@gmail.com
Apr 1, 2013
Project Member #9 chendequ...@gmail.com
Revision#181
Status: Fixed

Powered by Google Project Hosting