I'm starting to get a lot of the following errors on my development
UniData server.
==UDT(pid:3416) calling reportIpcState();
logfile:E:\UDAccounts\Allegis\UDT3416c.ipclog;
funcname:U_shmem_alloc(B), errno:0. Current time=Wed Apr 13 11:11:47 2011
.
==UDT(pid:1344) calling reportIpcState();
Have you looked at any of the log files that it's naming?
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
Hi All:
We noticed a problem with locks being left when we delete our temporary
programs using UniObjects for Java on the new code we are using for
XLr8Editor continuous compile. We used the standard
setDefaultReleaseStrategy(). This should release the record when it was
written or deleted, but
I'm thinking that it's got to be a bug SOMEWHERE if Universe Unix and
Universe Windows behave differently. Sounds like a case for Rocket!
...
Doug said...
We noticed a problem with locks being left when we delete our temporary
programs using UniObjects for Java on the new code we are using for
Yes. All the accounts exist and they've been accessed via telnet for
quite a while. This somehow seems like a Windows 7 error because I can
replicate it using a Windows 7 machine loggin in via AccuTerm 7, from
one machine, using the wireless network card. The other ones came from
an unknown
It looks like you need some of the Docs Wally Terhune has written on UD shared
memory.
Coming out the gate, your sbcs shared memory segment is underconfigured. That
may not be the primary issue here, but it's an indication that work needs to be
done in this area. I have no relationship
