Getting Unknown exception while submitting asset: Failed to submit asset - testAsset - ID#{B21E1DB8-8953-7BF0-518A-418CF239A147} Version#1.0 - null
When we try to submit/update an asset via an API , it fails with the following exception
[9/7/12 9:51:37:841 GMT] 0000004e RAMClient E com.ibm.cloud.ram.RAMClient updateAsset Unknown exception while submitting asset: Failed to submit asset - testAsset - ID#{B21E1DB8-8953-7BF0-518A-418CF239A147} Version#1.0 - null
com.ibm.ram.common.data.exception.RAMRuntimeException: Unknown exception while submitting asset: Failed to submit asset - testAsset - ID#{B21E1DB8-8953-7BF0-518A-418CF239A147} Version#1.0 - null
at com.ibm.ram.client.RAMSession.putAsset(RAMSession.java:3256)
at com.ibm.ram.client.RAMSession.put(RAMSession.java:4730)
at com.ibm.cloud.ram.RAMClient.updateAsset(RAMClient.java:2193)
We are using RAM in a cluster .
Prior to his , we had an another issue where we were getting "Collision detected error" when trying to update an asset.
To solve this issue , we deleted the index files on the RAM nodes and then started the RAM which rebuilded the index and that solved the collision issue.
However , 70% of times now the update asset fails with above exception . Kindly help in solving the same.
[9/7/12 9:51:37:841 GMT] 0000004e RAMClient E com.ibm.cloud.ram.RAMClient updateAsset Unknown exception while submitting asset: Failed to submit asset - testAsset - ID#{B21E1DB8-8953-7BF0-518A-418CF239A147} Version#1.0 - null
com.ibm.ram.common.data.exception.RAMRuntimeException: Unknown exception while submitting asset: Failed to submit asset - testAsset - ID#{B21E1DB8-8953-7BF0-518A-418CF239A147} Version#1.0 - null
at com.ibm.ram.client.RAMSession.putAsset(RAMSession.java:3256)
at com.ibm.ram.client.RAMSession.put(RAMSession.java:4730)
at com.ibm.cloud.ram.RAMClient.updateAsset(RAMClient.java:2193)
We are using RAM in a cluster .
Prior to his , we had an another issue where we were getting "Collision detected error" when trying to update an asset.
To solve this issue , we deleted the index files on the RAM nodes and then started the RAM which rebuilded the index and that solved the collision issue.
However , 70% of times now the update asset fails with above exception . Kindly help in solving the same.
Comments
Rich Kulp
FORUM MODERATOR / JAZZ DEVELOPER Sep 07 '12, 10:15 a.m.You'll need the host logs for the time [9/7/12 9:51:37:841 GMT]. This error means something went wrong on the host.
Also check if there are any other client log messages around this time. It could of been a previous error caused this one or a subsequent error gives more information. Also when you have a stracktrace make sure you include all of the "caused by:" stacktraces that go with it. I don't know if there are any in this case, but often the first trace in the list is just a catch all that wrappers the real exception that's displayed in the "caused by" list.