Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
0.5
-
None
Description
A series of replyInfo already set warnings is seen when upload fails
as a consequence of IOFailure on Bitarchive servers.
The complete monitor-log where this error occurs can be browsed here:
http://asterix.kb.dk/twiki/pub/Netarkiv/TestResultsIteration6/monitor.log
Jun 24 2005 2:11:51 AM
dk.netarkivet.distribute.arcrepository.ArcRepositoryClient store
WARNING: The returned message
'ID:1251-130.226.228.8(e5:89:eb:5:68:de)-35670-1119571907981: To
SVC_COMMON_THE_ARCREPOS ReplyTo SVC_COMMON_THIS_HACO_130_226_228_8_8081 Error:
dk.netarkivet.exceptions.PermissionDenied: replyInfo already set for
5-5-20050623124351-00001-kb-test-har-002.kb.dk.arc
dk.netarkivet.exceptions.PermissionDenied: replyInfo already set for
5-5-20050623124351-00001-kb-test-har-002.kb.dk.arc
at dk.netarkivet.arcrepositoryadmin.AdminData.setReplyInfo(AdminData.java:133)
at dk.netarkivet.arcrepository.ArcRepository.store(ArcRepository.java:728)
at
dk.netarkivet.distribute.arcrepository.ArcRepositoryServer.visit(ArcRepositoryServer.java:65)
at
dk.netarkivet.arcrepository.ArcRepositoryMessageHandler.visit(ArcRepositoryMessageHandler.java:118)
at
dk.netarkivet.distribute.arcrepository.StoreMessage.accept(StoreMessage.java:78)
at
dk.netarkivet.distribute.DefaultMessageHandler.onMessage(DefaultMessageHandler.java:72)
at
com.sun.messaging.jmq.jmsclient.MessageConsumerImpl.deliverAndAcknowledge(MessageConsumerImpl.java:247)
at
com.sun.messaging.jmq.jmsclient.MessageConsumerImpl.onMessage(MessageConsumerImpl.java:210)
at com.sun.messaging.jmq.jmsclient.SessionReader.deliver(SessionReader.java:76)
at com.sun.messaging.jmq.jmsclient.ConsumerReader.run(ConsumerReader.java:153)
at java.lang.Thread.run(Thread.java:595)
Arcfile: 5-5-20050623124351-00001-kb-test-har-002.kb.dk.arc' was not ok while
waiting for reply on store of file
'/home/test/SVC/harvester_8081/5_1119530628970/arcs/5-5-20050623124351-00001-kb-test-har-002.kb.dk.arc'
on attempt number 3 of 3
NOTE: This bug is originally from Bugzilla bug_id=382.