May I add my experience here? 1. A uniobjects daemon application timed out and dropped the connection after 1 hour of inactivity. This was resolved by having a periodic "tick" that performs a command, reads a record or calls a subroutine. I now have a java servlet/service that keeps a persistent connection through a timer thread that "ticks" every 15 minutes.
2. I would run out of licenses until I realized I must explicitly disconnect the session. Each uniobjects session requires a license unless you have device licensing. 3. On my VB applications I connect only when I need them and then disconnect. Most connections last less than one second so I don't consume a license for very long. 4. Session.IsActive is useless. On Wed, 2008-08-06 at 09:27 +0100, Anthony Youngman wrote: > I've looked up the notes on our error and found the following > > The object invoked has disconnected from its clients (-2147417848) > > I don't know where that came from but it's the same error that you've got, > and I guess we found that somewhere in some documentation on OLE or whatever. > So what is happening is that the connection between UniObjects and your VB > app has disapppeared (note with us it was our app and Word that stopped > talking to each other, both running on the same PC if I've got it right). > > So it looks like it's local to the affected PC(s), and is a time-out issue. > Good luck tracking it down - it took us ages! Have you tried explicitly > trapping that error and just retrying the read? > > You saying UniObjects "just dies" looks a good clue - it might well have gone > to sleep ... we found the failed connection attempt woke Word up again so > that the second try worked. > > Cheers, > Wol > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Chanco > Sent: 06 August 2008 03:34 > To: [email protected] > Subject: RE: [U2] uniobjects help needed! > > Hello all, > I was joking about the voodoo chants when I first posted but several > days later and little progress made I am now seriously willing to consider > any chants anyone knows. > > on a more serious note does anyone know if it's possible to "talk" directly > to a uvrpc daemon? (uniobjects) I know you can with smtp and other socket > programs if you know the language/syntax, so I think it should be possible > with uvrpc ("uniobjects"). Any suggestions/ideas on how (if possible) to do > this would be appreciated! > > What we are seeing are users (who are ALL using the EXACT same VB 6 program) > having problems with writes and receiving back corrupted data (to a universe > database using uniobjects). We have turned on logging in uniobjects but I > am having some trouble reading the log files (its hard to tell if the > corruption is coming to uniobjects or from universe). We have tested the > universe programs that the VB app. calls and they work exactly as they > should. We have tested the VB 6 apps and they too appear to be working as > expected (but obviously something is wrong)/ We have > tested/checked/rebooted the entire network (to include the aix machine). > What is throwing me is that if the basic program does not find a match to > whatever was passed to it, it returns null but sometimes we get back garbage > to the VB app, which to me means that the basic program got a valid value > and returned a valid response that somewhere in the chain got corrupted. > > We have even done an iptrace on the aix box to see what it gets/sends as > well as on the windows PC(s) but sadly I am not able to fully comprehend > what I am seeing. > > If anyone is willing (and this is asking a lot, so please forgive me) to > look at an iptrace I would be incredibly grateful! I have two trace files, > > 1. one from a windows PC that was not able to edit an order > 2. one that logged all the traffic coming/going to the aix machine on the > uvrpc port > > any suggestions/chants/thoughts would be extremely welcome! > > I hope all this makes sense, if not this is what working 96+ hours in the > last 7 days does to you > > thanks again > > dougc > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Anthony W. Youngman > Sent: Sunday, August 03, 2008 12:29 PM > To: [email protected] > Subject: Re: [U2] uniobjects help needed! > > In message <[EMAIL PROTECTED]>, doug chanco > <[EMAIL PROTECTED]> writes > >Hey, > > > >We are having a problem with uniobjects that started a couple of days > >ago. We have a VB app that uses uniobjects to access an aix system > >running universe 10.1 and a few days ago we started getting errors > >where uniobjects would just die, its starting to look like it might > >be a network issue but so far nothing we can discover. > > > >Our Cisco guy is not seeing any errors in the cisco switches, I am > >not seeing any errors on the aix system (5.2.6). > > > >While is may or may not be a universe/uniobjects issue, so far we have > >been stumped as to what the problem is. We even called an IBM > >uniobjects engineer for several hours and he could not find a problem > >as neither could our VAR or IBM tech support for aix. > > > >So I thought I would throw this out to youll who vast knowledge may > >hold the key to the answers we seek! The fact that in the past 3 days I > >have works close to 60 hours is a testimony to the amount of effort we > >have been putting in to try and solve this problem. > > > >Basically what we are seeing that is > > > >Run-TIme error '-2147417848 (80010108)': > >Method 'Read' of object 'IUniFileEx' Failed > > > >So any suggestions/thoughts/ideas/crystal balls/magic spells/voodoo > >chants are welcomed! > > > This, I think, will fall into the Voodoo Chant school of hopeful wishing > ... but the message number looks vaguely familiar to me. Do you know > which line of your code is returning your error? What happens if the > code just retries the read? > > The problem I'm thinking of that we had was our program talking to Word. > Word would "go to sleep" and you'd get an error looking a bit like that. > Retry, Word would have woken up, and it was fine 2nd time. Try trapping > the error and retrying, and see what happens... > > Cheers, > Wol > -- > Anthony W. Youngman <[EMAIL PROTECTED]> > 'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the > thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man > lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998 > Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source > Pick > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > > > __________ Information from ESET NOD32 Antivirus, version of virus signature > database 3326 (20080804) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > > __________ Information from ESET NOD32 Antivirus, version of virus signature > database 3326 (20080804) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
