[jboss-user] [JBossCache] - Re: java.io.NotSerializableException: java.lang.Object -Clus
It might help to add some debug print code to java.util.ArrayList.writeObject() (in java.util.ArrayList.java around line 529). There are some hoops that you have to jump through to get the updated class ArrayList class file in to be used. It should be worthwhile if you get information about which field it is that isn't serializable, as you will then know which one needs to change. Don't do this in your production app server installation and don't leave the debug ArrayList in your production app server installation. I hope makes sense as my sleeping pill is kicking in. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960862#3960862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960862 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: java.io.NotSerializableException: java.lang.Object -Clus
1. Based on some further research, I did not find any "java.lang.Object" declaration in the (Beans/VO, Action forms, Decorators) of the application classes. 2. The Mappings are clean and theres no DB -> field mapping of type Object. 3. Although, In "com.ibatis.db.sqlmap.cache.memory" package, MemoryCacheController has a inner class declaration "StrongReference", which has java.lang.Object declaration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960495#3960495 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960495 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: java.io.NotSerializableException: java.lang.Object -Clus
>From looking at that, it would seem the the type of the object put in the list >would be controlled by the mapping iBatis is using. If some db field is >mapped to java.lang.Object, that's what you'll get. Hard to see why a db >field would be mapped to java.lang.Object, though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960486#3960486 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960486 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: java.io.NotSerializableException: java.lang.Object -Clus
Well, I think this has got to do with the way Ibatis is implemented. Here's an
example.
private List runQueryForList(SqlStatement localSql, Connection conn, Object
parameterObject, int skipResults, int maxResults, RowHandler rowHandler)
throws SQLException
{
List list;
if(log.isDebugEnabled())
{
log.debug("executeQueryForList: " + name);
conn = ConnectionLogProxy.newInstance(conn);
}
ErrorField errorField = new ErrorField();
if(rowHandler == null)
list = new ArrayList();
else
list = null;
ResultSet rs = null;
PreparedStatement ps = null;
String errorMessage = "Check the SQL statement.";
try
{
sqlMap.incrementExecutionThrottle(conn);
ps = createStatement(conn, localSql, parameterObject);
if(sqlMap.isDriverHintsEnabled() && maxResults != -1 && skipResults
!= -1)
{
ps.setFetchSize(maxResults + skipResults);
ps.setMaxRows(maxResults + skipResults);
}
errorMessage = "Check the Parameter Map (or inline parameters).";
applyParameterMap(localSql, ps, parameterObject, errorField);
errorField.errorField = null;
errorMessage = "Check the SQL statement.";
rs = ps.executeQuery();
for(int i = 0; i < skipResults; i++)
if(!rs.next())
break;
errorMessage = "Check the Result Map.";
int n = 0;
if(rowHandler == null)
{
for(; (maxResults == -1 || n < maxResults) && rs.next(); n++)
{
Object object = applyResultMap(conn, rs, null, errorField);
list.add(object);
}
errorField.errorField = null;
} else
{
for(; (maxResults == -1 || n < maxResults) && rs.next(); n++)
{
Object object = applyResultMap(conn, rs, null, errorField);
rowHandler.handleRow(object);
}
errorField.errorField = null;
}
}
catch(Throwable t)
{
Throwable tt = unwrapProxyException(t);
String msg = "";
if(errorField.errorField != null)
msg = "Error executing '" + name + "' in '" + resourceName +
"'. " + errorMessage + " Check the '" + errorField + "' property. Cause: " + t;
else
msg = "Error executing '" + name + "' in '" + resourceName +
"'. " + errorMessage + " Cause: " + t;
if(log.isErrorEnabled())
log.error(msg, t.fillInStackTrace());
if(t instanceof SQLException)
throw (SQLException)t;
else
throw new SQLException(msg);
}
finally
{
closeResultSet(rs);
closeStatement(ps);
sqlMap.decrementExecutionThrottle(conn);
}
notifyListeners();
return list;
}
BELOW IS THE applyResultMap METHOD
private Object applyResultMap(Connection conn, ResultSet rs, Object
resultObject, ErrorField errorField)
throws SQLException
{Object object = resultObject;
String typeName = null;
if(getResultMapName() != null)
{
ResultMap map = getSqlMap().getResultMap(getResultMapName());
typeName = map.getClassName();
if(object == null)
object = instantiate(map.getClassName());
ResultMapping mapping;
for(Iterator names = map.getMappedPropertyNames(); names.hasNext();
setBeanProperty(mapping, object, conn, rs, errorField))
{
String propertyName = (String)names.next();
mapping = map.getResultMapping(propertyName);
}
} else
if(resultClass != null)
{
typeName = resultClass;
if(object == null)
object = instantiate(resultClass);
if(object instanceof BaseValue)
{
ResultMapping mapping = new ResultMapping();
mapping.setPropertyName("value");
mapping.setColumnName("VALUE");
mapping.setColumnIndex(new Integer(1));
setBeanProperty(mapping, object, conn, rs, errorField);
} else
if(object instanceof Map)
{
ResultSetMetaData rsmd = rs.getMetaData();
int i = 0;
for(int n = rsmd.getColumnCount(); i < n; i++)
{
String columnName = rsmd.getColumnLabel(i + 1);
((Map)object).put(columnName, rs.getObject(i + 1));
}
} else
{
autoMapResultSet(conn, rs, object, errorField
[jboss-user] [JBossCache] - Re: java.io.NotSerializableException: java.lang.Object -Clus
The problem isn't that any application class or iBatis class isn't Serializable. It's that one of the fields of one of those classes is of type java.lang.Object. That field is not Serializable, because java.lang.Object isn't. You need to find that field. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960444#3960444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960444 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: java.io.NotSerializableException: java.lang.Object -Clus
We investigated the application code and Ibatis sources. 1. All the application classes (Beans, Actionforms, Decorators) are serializable. (This takes care of all the objects in chain) 2. We suspected that Ibatis could be problem area and made all the classes serializable (For sanity sake) Yet the java.io.NotSerializableException: java.lang.Object is seen. Its becomming impossible to understand what could be the reason for this. Help Appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960438#3960438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960438 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: java.io.NotSerializableException: java.lang.Object -Clus
Somewhere in the object graph is an instance of java.lang.Object, which does not implement Serializable. Looks like the ref is held by a fairly deep object graph rooted in an ArrayList; the ArrayList is object stored as a session attribute. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960374#3960374 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960374 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
