[Jzjkit-user] SEVERE: Unable to locate callback target

[Tom T. <tom...@se...>]

Hello again,

In my port to jzkit2, I have one more reported error I'd like to clean 
up as well besides the previously posted SocketException.  We have been 
using Z3950SearchTask.getFragment instead of asyncGetFragment to pull 
down records.  Unfortunately, we get a SEVERE error in the logs that 
doesn't seem to affect the result set, but is of concern:

Jan 4, 2006 10:41:15 AM org.jzkit.search.provider.z3950.Z3950SearchTask 
getFragment
FINE: Z3950SearchTask::getFragment(1,20,usmarc:null:F)
Jan 4, 2006 10:41:15 AM org.jzkit.search.provider.z3950.Z3950Origin 
fetchRecords
FINE: Z3950Origin::fetchRecords(15033128,F,1,20,60000)
Jan 4, 2006 10:41:15 AM org.jzkit.search.provider.z3950.Z3950Origin 
fetchRecords
FINE: Z3950Origin::fetchRecords() from null
Jan 4, 2006 10:41:15 AM org.jzkit.search.provider.z3950.Z3950Origin 
fetchRecords
FINE: Set refid to 15033128:0
Jan 4, 2006 10:41:15 AM org.jzkit.search.provider.z3950.Z3950Origin 
fetchRecords
FINE: About to send present request
Jan 4, 2006 10:41:15 AM org.jzkit.z3950.util.ZEndpoint sendPresentRequest
FINE: sendPresentRequest, refid=15033128:0
Jan 4, 2006 10:41:15 AM org.jzkit.z3950.util.ZEndpoint sendPresentRequest
FINE: setname: 15033128
Jan 4, 2006 10:41:15 AM org.jzkit.z3950.util.ZEndpoint sendPresentRequest
FINE: first=1
Jan 4, 2006 10:41:15 AM org.jzkit.z3950.util.ZEndpoint sendPresentRequest
FINE: count=20
Jan 4, 2006 10:41:15 AM org.jzkit.z3950.util.ZEndpoint encodeAndSend
FINE: encodeAndSend...
Jan 4, 2006 10:41:15 AM org.jzkit.search.provider.z3950.Z3950Origin 
fetchRecords
FINE: Waiting for present response PDU with refid 15033128:0
Jan 4, 2006 10:41:18 AM org.jzkit.z3950.util.ZEndpoint run
FINE: Notifiy observers
Jan 4, 2006 10:41:18 AM org.jzkit.z3950.util.ZEndpoint notifyAPDUEvent
FINE: notifyAPDUEvent : 5
Jan 4, 2006 10:41:18 AM org.jzkit.z3950.util.ZEndpoint notifyAPDUEvent
FINE: Incoming PDU refid: 15033128:0
Jan 4, 2006 10:41:18 AM org.jzkit.search.provider.z3950.Z3950Origin 
fetchRecords
FINE: fetchRecords returning presentResponse
Jan 4, 2006 10:41:18 AM org.jzkit.search.provider.z3950.Z3950SearchTask 
processRecords
FINE: Response contains 20 Response Records
Jan 4, 2006 10:41:18 AM org.jzkit.search.provider.z3950.Z3950SearchTask 
processRecords
FINE: Derived record spec : iso2709:usmarc:null
Jan 4, 2006 10:41:18 AM org.jzkit.search.provider.z3950.Z3950SearchTask 
processRecords
FINE: Marc variant
Jan 4, 2006 10:41:18 AM org.jzkit.search.provider.z3950.Z3950Origin 
incomingPresentResponse
FINE: Incoming PresentResponse from 26868203
Jan 4, 2006 10:41:18 AM org.jzkit.search.provider.z3950.Z3950Origin 
incomingPresentResponse
FINE: broken refid - manually setting refid using last present refid
Jan 4, 2006 10:41:18 AM org.jzkit.search.provider.z3950.Z3950Origin 
incomingPresentResponse
FINE: Present Response - Reference ID : "15033128:0" target=null
Jan 4, 2006 10:41:18 AM org.jzkit.search.provider.z3950.Z3950Origin 
incomingPresentResponse
SEVERE: Unable to locate callback target or outstanding operation info 
for refid 15033128:0

It appears that the difference is that the asyncGetFragment is creating 
and passing in a PresentCallbackHandler to asyncFetchRecords.  
fetchRecords doesn't require this and so 
Z3950Origin.incomingPresentResponse is complaining that it can't find 
the handler to notify.    Is there any way to make 
incomingPresentResponse smarter so that it doesn't care when it doesn't 
need to?  Or, is there something we are doing wrong?

Thanks again,
-- 
Tom Talbott
Serials Solutions <http://www.serialssolutions.com>
tom...@se...
206-545-9056 x1081