× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 10/11/2011 10:16 AM, David Gibbs wrote:
On 10/11/2011 9:48 AM, Joe Pluta wrote:
David, I have no idea. I think this is the line that's failing:

ds = (ClientAccessDataStream) fd_.server_.sendAndReceive(req);

This would imply that either fd_ or fd_.server_ is null. fd_ cannot be
null or it would have failed earlier in the delete() method. In fact,
the delete() method calls fd_.connect(), which is supposed to set the
server_ value.

So the only way I can see this happening is if you somehow lost the
connection for your file and were unable to re-establish it. Are you
doing this delete immediately upon creating the IFS File object?
yeah, that's pretty much what was identified last time.

John E, the jt400 development lead, suggested updating the most current version of jt400.jar ... which I did. But the error manifested again. Unfortunately it's completely sporadic. The code in question will work fine for weeks and then fail for no apparent reason.

Against my better judgment, I've added a catch for npe when the delete is performed. I'd rather leave a file behind in the ifs than abort the process.


How about retrying the delete? Which returns me to my question: how long between the time you create the IFSFile object and you try to delete it? If simply retrying the delete doesn't work, could you throw away the object, create a new one and try to delete the new one?

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.