Hanging synchronization sessions
We just have another problem - 2 users are facing "server busy" message when trying to synchronize using MSync. I just found out that there are some hanging sync sessions which are probably blocking the synchronization (their duration is few thousand seconds and I'm not able to kill them from mobile server). I restarted the OL server so the freezing sync sessions were killed, but when users try to synchronize after the restart, the result is the same - they get "server busy" message and their sessions remain in the active sessions list forever.
The server is 10gR2 and the clients are both PPC2003 XScale. The In queue and error queue are empty.
Anybody has an idea what should I try to solve this kind of problem?
Oracle response on the SR was
This might be due to Bug 5553375 SYNCHRONIZATION HANGS BETWEEN SENDING AND RECEIVING PHASE.
According to the bug 5553375, this might be because of the file_size during sending and receiving phase. The default value of
RESUME_FILE_SIZE is 16MB sync session failure might occur when it reaches this l
imit. So suggest to increase the value to higher value. can increase slowly also
as first use 256, if the issue occurs, can increase to 512, which is the file s
ize
In webtogo.ora under [CONSOLIDATOR] section set the value as RESUME_FILE_SIZE=256 (or 512).
After changing restart the mobileserver.
Enable tracing in both server and client as below
At the Server :
1. Stop the server.
2. Set trace level ALL and trace type RESUME for the Global and the Sync
components in webtogo.ora. Other component logs can disabled.
e.g.
GLOBALLogger=TRACE_LEVEL=ALL|TRACE_TYPE=RESUME|TRACE_DESTINATION=TEXTFILE|TRAC
E_FILE_SIZE=15
SYNCLogger=TRACE_LEVEL=ALL|TRACE_TYPE=RESUME|TRACE_DESTINATION=TEXTFILE|TRACE_
FILE_SIZE=15
3. Start the Mobile server
4. When the problem is reproduced, collect the following :-
- err.log
- log files under GLOBAL
- log files under SYNC
- details for the sync session as shown by the Mobile Manager. the
Compressed Byte count. (this session shows a success on the server side)
At the Client:
1. set debug=1 in polite.ini under the [SYNC] section
2. When the error occurs, upload the following files
- timeout_err.txt
- debug*.txt
Please note that the timeout_err.txt file will be created only if there were any errors during the receive phase.
Apart from this, for your information, one of the customer had similar issue and was resolved when they upgraded RDBM
S from 102020 to 102030.
Hence, let me know the possibility of upgrading the database.
this suggests that there may be a limiting factor on the file transfer (did not help in terms of our problem, burt since we fixed the PDA hanging by a re-build, i do not have a case to trace at the moment)
We have found that sessions hanging on upload are always hanging on C$SEQ_CLIENTS_PI, so pretty sure it is client side corruption/bug
on download the problem tends to be a disconnect, in which case the server session finishes, but the client hangs (as it has not recieved an end message) - we deal with that via comms timeout. In most cases the large the download, the more likely failure, but this seems more related to server side query time to select the data for streaming to the client, rather than the actual volume of the data
Similar Messages
-
Lion slow performance due to hanging TCP sessions
After upgrading to 10.7.2 I experienced that Safari and Mail hangs.
After a reboot the problem was gone but occured again after a while.
I found out that a lot of TCP sessions were in the CLOSE_WAIT state.
The affekted deamon was ocspd.
I killed the deamon and it restarted automatically. The problem related to hanging https sessions Safari an Mail was gone.
The problem occurs again and again.
Does someboda have an idea how to solve this issue.
Bellow I listed some output:
Hinkelstein:~ mav$ sudo lsof -i -P | grep CLOSE_WAIT
applepush 372 root 13u IPv4 0xffffff801434e320 0t0 TCP 192.168.10.52:53317->nk11p01st-courier018-bz.push.apple.com:443 (CLOSE_WAIT)
WebProces 3720 mav 16u IPv4 0xffffff802e9ce880 0t0 TCP 192.168.66.154:54481->tls_server.uslendernetwork.com:80 (CLOSE_WAIT)
WebProces 3720 mav 17u IPv4 0xffffff80330fac20 0t0 TCP 172.20.1.73:58913->172.20.5.7:443 (CLOSE_WAIT)
PubSubAge 7794 mav 19u IPv4 0xffffff80344426c0 0t0 TCP 172.20.1.73:59003->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 3u IPv4 0xffffff802f6b84e0 0t0 TCP 172.20.1.73:58847->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 7u IPv4 0xffffff803310d6c0 0t0 TCP 172.20.1.73:59014->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 8u IPv4 0xffffff802e03ba40 0t0 TCP 172.20.1.73:58849->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 9u IPv4 0xffffff802e952c00 0t0 TCP 172.20.1.73:58845->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 10u IPv4 0xffffff8033150fa0 0t0 TCP 172.20.1.73:58850->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 11u IPv4 0xffffff80330f6c00 0t0 TCP 172.20.1.73:58878->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 12u IPv4 0xffffff8034443c20 0t0 TCP 172.20.1.73:58843->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 13u IPv4 0xffffff802e8b0160 0t0 TCP 172.20.1.73:58844->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 14u IPv4 0xffffff80331404e0 0t0 TCP 172.20.1.73:58856->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 15u IPv4 0xffffff802e9b54e0 0t0 TCP 172.20.1.73:58892->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 18u IPv4 0xffffff802e8afa40 0t0 TCP 172.20.1.73:58867->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 19u IPv4 0xffffff802f6bafa0 0t0 TCP 172.20.1.73:58863->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 20u IPv4 0xffffff803317dc20 0t0 TCP 172.20.1.73:58885->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 21u IPv4 0xffffff8033164c20 0t0 TCP 172.20.1.73:58884->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 22u IPv4 0xffffff8033141320 0t0 TCP 172.20.1.73:58871->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 23u IPv4 0xffffff80331396c0 0t0 TCP 172.20.1.73:58874->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 24u IPv4 0xffffff802e9b7160 0t0 TCP 172.20.1.73:58881->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 25u IPv4 0xffffff8033171c00 0t0 TCP 172.20.1.73:58897->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 26u IPv4 0xffffff801434f880 0t0 TCP 172.20.1.73:58918->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 27u IPv4 0xffffff80330f7320 0t0 TCP 172.20.1.73:58877->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 28u IPv4 0xffffff802f6c4880 0t0 TCP 172.20.1.73:58899->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 29u IPv4 0xffffff802e8bac00 0t0 TCP 172.20.1.73:58917->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 30u IPv4 0xffffff803316afa0 0t0 TCP 172.20.1.73:58964->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 31u IPv4 0xffffff8034441160 0t0 TCP 172.20.1.73:58906->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 32u IPv4 0xffffff802e956500 0t0 TCP 172.20.1.73:58985->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 33u IPv4 0xffffff8033172a40 0t0 TCP 172.20.1.73:58905->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 34u IPv4 0xffffff8033106c20 0t0 TCP 172.20.1.73:58935->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 35u IPv4 0xffffff802e9b6a40 0t0 TCP 172.20.1.73:58904->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 36u IPv4 0xffffff8033136c00 0t0 TCP 172.20.1.73:58965->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 37u IPv4 0xffffff8033138880 0t0 TCP 172.20.1.73:58980->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 38u IPv4 0xffffff8033147c00 0t0 TCP 172.20.1.73:58915->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 39u IPv4 0xffffff802e954160 0t0 TCP 172.20.1.73:58966->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 40u IPv4 0xffffff8033138fa0 0t0 TCP 172.20.1.73:58938->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 41u IPv4 0xffffff8033149160 0t0 TCP 172.20.1.73:58933->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 42u IPv4 0xffffff8033103a40 0t0 TCP 172.20.1.73:58939->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 43u IPv4 0xffffff8033142880 0t0 TCP 172.20.1.73:58930->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 44u IPv4 0xffffff80331056c0 0t0 TCP 172.20.1.73:58940->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 45u IPv4 0xffffff8033173fa0 0t0 TCP 172.20.1.73:58937->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 46u IPv4 0xffffff801434dc00 0t0 TCP 172.20.1.73:58941->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 47u IPv4 0xffffff803314fa40 0t0 TCP 172.20.1.73:58992->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 48u IPv4 0xffffff803312ffa0 0t0 TCP 172.20.1.73:58975->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 49u IPv4 0xffffff803314b500 0t0 TCP 172.20.1.73:58981->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 50u IPv4 0xffffff8033104880 0t0 TCP 172.20.1.73:58967->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 51u IPv4 0xffffff80330fa500 0t0 TCP 172.20.1.73:58982->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 52u IPv4 0xffffff802e9cf6c0 0t0 TCP 172.20.1.73:59033->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 53u IPv4 0xffffff8033142160 0t0 TCP 172.20.1.73:58969->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 54u IPv4 0xffffff802e9ccc00 0t0 TCP 172.20.1.73:58989->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 55u IPv4 0xffffff8033149880 0t0 TCP 172.20.1.73:58970->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 56u IPv4 0xffffff802e9b8de0 0t0 TCP 172.20.1.73:59004->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 57u IPv4 0xffffff80331516c0 0t0 TCP 172.20.1.73:58971->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 58u IPv4 0xffffff803317cde0 0t0 TCP 172.20.1.73:58972->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 59u IPv4 0xffffff8034623500 0t0 TCP 172.20.1.73:59023->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 60u IPv4 0xffffff802e03a4e0 0t0 TCP 172.20.1.73:59081->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 61u IPv4 0xffffff803461fc00 0t0 TCP 172.20.1.73:59034->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 62u IPv4 0xffffff803314a6c0 0t0 TCP 172.20.1.73:59042->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 63u IPv4 0xffffff802e9944e0 0t0 TCP 172.20.1.73:59075->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 64u IPv4 0xffffff802e9cda40 0t0 TCP 172.20.1.73:59016->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 65u IPv4 0xffffff803312ea40 0t0 TCP 172.20.1.73:59026->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 66u IPv4 0xffffff8033161a40 0t0 TCP 172.20.1.73:59036->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 67u IPv4 0xffffff80331364e0 0t0 TCP 172.20.1.73:59018->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 68u IPv4 0xffffff80331684e0 0t0 TCP 172.20.1.73:59056->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 69u IPv4 0xffffff8034621fa0 0t0 TCP 172.20.1.73:59019->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 70u IPv4 0xffffff8033173880 0t0 TCP 172.20.1.73:59020->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 71u IPv4 0xffffff802e8b0880 0t0 TCP 172.20.1.73:59035->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 72u IPv4 0xffffff803310cfa0 0t0 TCP 172.20.1.73:59021->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 73u IPv4 0xffffff8033175500 0t0 TCP 172.20.1.73:59067->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 74u IPv4 0xffffff80331794e0 0t0 TCP 172.20.1.73:59022->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 75u IPv4 0xffffff803314e4e0 0t0 TCP 172.20.1.73:59148->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 76u IPv4 0xffffff8033172320 0t0 TCP 172.20.1.73:59052->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 77u IPv4 0xffffff802f6c5de0 0t0 TCP 172.20.1.73:59095->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 78u IPv4 0xffffff803443f4e0 0t0 TCP 172.20.1.73:59064->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 79u IPv4 0xffffff8034443500 0t0 TCP 172.20.1.73:59082->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 80u IPv4 0xffffff8033169320 0t0 TCP 172.20.1.73:59068->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 81u IPv4 0xffffff8034622de0 0t0 TCP 172.20.1.73:59130->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 82u IPv4 0xffffff8034629de0 0t0 TCP 172.20.1.73:59119->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 83u IPv4 0xffffff802e8bba40 0t0 TCP 172.20.1.73:59054->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 84u IPv4 0xffffff8033131500 0t0 TCP 172.20.1.73:59061->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 85u IPv4 0xffffff8033139de0 0t0 TCP 172.20.1.73:59071->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 86u IPv4 0xffffff8033163de0 0t0 TCP 172.20.1.73:59058->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 87u IPv4 0xffffff802e9cd320 0t0 TCP 172.20.1.73:59096->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 88u IPv4 0xffffff8034628fa0 0t0 TCP 172.20.1.73:59084->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 89u IPv4 0xffffff803310a4e0 0t0 TCP 172.20.1.73:59080->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 90u IPv4 0xffffff802e8ba4e0 0t0 TCP 172.20.1.73:59115->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 91u IPv4 0xffffff802e8bec20 0t0 TCP 172.20.1.73:59085->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 92u IPv4 0xffffff802e8bd6c0 0t0 TCP 172.20.1.73:59094->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 93u IPv4 0xffffff802f6bb6c0 0t0 TCP 172.20.1.73:59138->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 94u IPv4 0xffffff802e8b16c0 0t0 TCP 172.20.1.73:59117->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 95u IPv4 0xffffff8033130de0 0t0 TCP 172.20.1.73:59103->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 96u IPv4 0xffffff8033104160 0t0 TCP 172.20.1.73:59134->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 97u IPv4 0xffffff802e954fa0 0t0 TCP 172.20.1.73:59104->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 98u IPv4 0xffffff8033149fa0 0t0 TCP 172.20.1.73:59135->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 99u IPv4 0xffffff803312f880 0t0 TCP 172.20.1.73:59114->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 100u IPv4 0xffffff802e9cc4e0 0t0 TCP 172.20.1.73:59140->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 101u IPv4 0xffffff8034620320 0t0 TCP 172.20.1.73:59150->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 102u IPv4 0xffffff803310ec20 0t0 TCP 172.20.1.73:59120->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 103u IPv4 0xffffff802e9b6320 0t0 TCP 172.20.1.73:59116->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 104u IPv4 0xffffff802e9cfde0 0t0 TCP 172.20.1.73:59126->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 105u IPv4 0xffffff8033131c20 0t0 TCP 172.20.1.73:59127->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 106u IPv4 0xffffff803317aa40 0t0 TCP 172.20.1.73:59183->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 107u IPv4 0xffffff802f6bcc20 0t0 TCP 172.20.1.73:59129->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 109u IPv4 0xffffff8033162fa0 0t0 TCP 172.20.1.73:59144->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 110u IPv4 0xffffff8033144500 0t0 TCP 172.20.1.73:59156->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 111u IPv4 0xffffff802e998500 0t0 TCP 172.20.1.73:59158->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 112u IPv4 0xffffff803312f160 0t0 TCP 172.20.1.73:59154->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 113u IPv4 0xffffff80330f8160 0t0 TCP 172.20.1.73:59185->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 115u IPv4 0xffffff8033174de0 0t0 TCP 172.20.1.73:59177->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 116u IPv4 0xffffff802f6c2c00 0t0 TCP 172.20.1.73:59187->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 117u IPv4 0xffffff803314ade0 0t0 TCP 172.20.1.73:59172->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 118u IPv4 0xffffff8034441880 0t0 TCP 172.20.1.73:59164->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 119u IPv4 0xffffff803317d500 0t0 TCP 172.20.1.73:59179->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 120u IPv4 0xffffff803316a160 0t0 TCP 172.20.1.73:59173->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 121u IPv4 0xffffff80346226c0 0t0 TCP 172.20.1.73:59196->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 122u IPv4 0xffffff802f6c6c20 0t0 TCP 172.20.1.73:59170->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 123u IPv4 0xffffff803310ac00 0t0 TCP 172.20.1.73:59206->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 124u IPv4 0xffffff80331636c0 0t0 TCP 172.20.1.73:59239->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 125u IPv4 0xffffff80331306c0 0t0 TCP 172.20.1.73:59242->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 126u IPv4 0xffffff801434f160 0t0 TCP 172.20.1.73:59215->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 128u IPv4 0xffffff8033144c20 0t0 TCP 172.20.1.73:59208->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 129u IPv4 0xffffff8033102c00 0t0 TCP 172.20.1.73:59209->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 130u IPv4 0xffffff80331604e0 0t0 TCP 172.20.1.73:59233->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 131u IPv4 0xffffff803461f4e0 0t0 TCP 172.20.1.73:59210->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 132u IPv4 0xffffff803313a500 0t0 TCP 172.20.1.73:59211->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 133u IPv4 0xffffff8033150160 0t0 TCP 172.20.1.73:59218->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 135u IPv4 0xffffff802e03e500 0t0 TCP 172.20.1.73:59213->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 136u IPv4 0xffffff80330f8880 0t0 TCP 172.20.1.73:59214->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 137u IPv4 0xffffff8033104fa0 0t0 TCP 172.20.1.73:59241->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 138u IPv4 0xffffff802e8be500 0t0 TCP 172.20.1.73:59234->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 140u IPv4 0xffffff802e9524e0 0t0 TCP 172.20.1.73:59235->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 143u IPv4 0xffffff803314f320 0t0 TCP 172.20.1.73:59237->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 144u IPv4 0xffffff803316bde0 0t0 TCP 172.20.1.73:59225->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 145u IPv4 0xffffff802e03dde0 0t0 TCP 172.20.1.73:59232->172.20.5.7:443 (CLOSE_WAIT)Hi
Is ther anybody having the same problem?
I still didn't got rid of it. -
Hanging Active Sessions in EM from webservice
I've developed a webservice that uses appmodules for DB persistence. In the OAS 10g (v10.1.3) EM, I'm seeing Active Sessions hanging around for 20 minutes or more after only 2 requests. We're experiencing OAS crashes on OutOfMemoryError events, and seems to be tied to this long hang around time. Heap usage skyrockets with any significant traffic.
We've scoured the code for hints of open resources such as as open file streams, but can't find any.
The appmodule is used for one call in each service request. The appmodule is gained from a call to Configuration.createRootApplicationModule(...) and released with a call to Configuration.releaseRootApplicationModule(module, true).
I've changed the configuration of the appmodule in JDeveloper, reducing jbo.pooltimtolive to 10 mins and jbo.ampool.monitorsleepinterval to 4 mins. I test with the old, default appmodule config in one service instance and the new, reduced-time config in a second service instance on the same server. I send two requests to each instance nearly simultaneously. The active sessions chart in the EM shows identical activity.
Any hints on how I can get the server to recover memory quickly after the end of a service call? My understanding is that in the servlet model, the server keeps a reference to the servlet, but that after completion on a request of the service method, all other object references should be eligible for garbage collection. We're using the standard Sun JVM, so it seems like we should be seeing more efficient heap recovery and not experiencing OutOfMemoryError. We're only receiving about 100 service calls in a day at present.
Thanks for any insights.
Bonus question: Any know how to prevent the heap usage from skyrocketing when the EM is invoked? It's insane!!!Hi,
usually, sessions expire after some time. However, you can manually terminate sessions using the Visual Administrator
Go to => <System> => <Server> => Services => Security Provider
Select tab "Login Sessions"
Switch to "Edit Mode"
Select session
Click "Terminate" button
Best regards,
Martin -
Server hangs and session variable value not maintained.
dear all,
this is exteremetly urgent. i upgraded my tomcat to 4.1.24.but i have problems running the same code which was working earlier, i get null in the value of session variable. and also get the following error
////////////////error got /////////////
Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:842)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:317)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext
.java:473)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:190)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2
95)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:
2415)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:22
3)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:594)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:565)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:619)
at java.lang.Thread.run(Thread.java:536)
///////////////end of error messsge ////////////
the code where i am getting this message is as follows
<%@ page session="true"%>
<HTML>
<HEAD><TITLE> LOGGED IN ok</TITLE> </HEAD>
<%@ page import="java.sql.*" %>
<%! // declaring variables
String s = "";
java.sql.ResultSet rs=null;
java.sql.Connection con;
java.sql.Statement stmt=null,stmt1=null;
String username = "";
String password = "";
String Ousername = "";
String Opassword = "";
String changepass="";
String usertype ="",useremail="",EmpName="";
%>
<body>
<%
try
//set session for max of 100 milliseconds
// session.setMaxInactiveInterval(10000);
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con = java.sql.DriverManager.getConnection("jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};" +"DBQ=c:/vishal/HelpDesk.mdb;DriverID=22;READONLY=false","","");
stmt = con.createStatement();
s = "select * from LoginUser";
username = request.getParameter("LogonId"); //get this through prev. form
password = request.getParameter("txtPassword");
out.println(username + " " + password);
// make explicitly to lower case
username = username.toLowerCase();
rs = stmt.executeQuery(s);
while(rs.next())
//getting data from database
Ousername = rs.getString("EmpName");
Opassword = rs.getString("Password");
useremail = rs.getString("EmailId");
usertype = rs.getString("UserType");
if(Opassword.equals(password) && Ousername.equals(username)) //found match correct entry
changepass = request.getParameter("PasswordNew");
if(changepass != null)
stmt1 = con.createStatement(java.sql.ResultSet.TYPE_SCROLL_INSENSITIVE,java.sql.ResultSet.CONCUR_UPDATABLE);
s = "update LoginUser set Password = '" + changepass + "' where EmpName = '" + username +"'";
out.println(s);
stmt1.executeUpdate(s);
stmt1.close();
if(usertype.equals("User") == false)//ie admin
session.setAttribute("username",username);
************************this value not maintained *********************
session.setAttribute("useremail",useremail);
session.setAttribute("usertype",usertype);
************************this value not maintained *********************
//closing connections
%>
<jsp:forward page= "ComplaintType.jsp" />
<%
else //user
EmpName = username;
session.setAttribute("EmpName",EmpName);
session.setAttribute("useremail",useremail);
//closing connections
%>
<jsp:forward page="ComplaintCategory.jsp" />
<%
}//end if
}//while loop
//first closing connections then forwarding
%>
<jsp:forward page="InvalidLOGIN.jsp" />
<%
///rs.close();
////closing
//stmt.close();
// con.close();
}//try
catch(Exception ep)
out.println(ep);
System.exit(1);
%>
</BODY>
</HTML>hi all,
thanx a lot for your help,specially hari52
hari52 strangely enough the code started working,but
now i have another problem
after a while my server hangs or gets shutdown ,a
message is shown as
"java.exe has generated error and will be shutdown"
i know that more connections can be a prob. but i
make sure that connections r closed on each page,also
i am a newbie and do not have the time at present to
learn abt. connection pool ,can this problem be
solved easily?
it would be a great help again on your part,
thanx again,You remove the System.exit(1) line from the code inside the catch block
and try again. That's the reason tomcat getting down. System.exit(1) should not be used inside jsp. it will make the underlaying Servlet Engine to shutdown. -
Do I need to Synchronize session connection??
I am working on a project in which requires sending out emails.
Multiple users may send out emails at the same time by using same email account and session. Question is do I need to synchronize this or just let mail server handle this concurrency. Or session's getDefaultsession method have already considered this? Looking forward to your answer!! Best regards,Multiple users may send out emails at the same time by using
same email account and session.Don't do that. Each thread should have its own session. Otherwise you'll have chaos. Sure, you could synchronize so the threads take turns using a single session, but if you do that there isn't much point in having separate threads, since 99% of the time they will be lining up to use the session.
However if those "users" are running in separate JVMs, perhaps even on separate computers, then the question doesn't arise. They would automatically have their own sessions. -
User login screen hangs - AFP session idle
This is an issue that only happens to 2 of my users on a network of about 8/9 mac's.
When the user logs in the server accepts the password but then hangs indefinately. One can see a beach ball in the corner twirling away!
If I log into the server and go the the AFP console I can see the afp connection is idle for x minutes. (We have 3 shares that mount up on login). Once i kill it the user then goes on the the desktop with an error that it was not able to connect to its home folder etc.
I get the user to log out and log back in 9/10 it works fine!
This could be ok for a week or 2 but then out of the blue the afp session just hangs and the only way to stop this is to log back in the server and kill the AFP session for that user. Restarting the client wont work as the session will still exist.
Only happens to 2 users?
Any ideas what this could be?
Corrupt home folder?
Server im running is 10.4.9 PPC
Client is 10.3.9 afaikSo I printed those instructions out. I went thru it and the drive came back with the ok msg. I continued what it said and then rebooted.. It went to the login screen, then flashed, then went into darwin etc etc.. i put the username and pw in and then it went to a command prompt, after 30 seconds or so it continued on its boot process after giving a few random messages of code. Nothing saying erros or anything weird. It went to a solid blue screen and the wheel kept spinning.
This happened a few times after i tried booting it up. Now it doesn't goes to the darwin unix promot thing anymore. Just goes back to what it was doing before. Spinning wheel at user login screen.
I did though explore through a couple directories during the prompt earlier. Basically I know that I can get the files that are needed off the drive if I remove the drive and put it into this machine. I don't want to take my friends drive out. His cd/dvd drive doesn't work so using the boot up disk really isn't an option. Unless i can get the external dvd drive to read on boot up.
Any suggestions?
Still freezes, even after doing kappy's instructions line by line.
Sigh....
Cheers,
Scott -
Query over Oracle Transparent Gateway on DB2 hangs the session
I am on Database release 10gR2 using the Oracle Transparent Gateway (v9) installed on a DB2 i*series machine.
The Oracle database is located in the same data center as the DB2 database. When I issue very simple queries such as select count(*) from t, I get a result immediately. However when I issue something like select * from t, I very rarely get any rows back (I will sometimes 39 out of 4000) and the session appears to hang. Our DB2 administrators report that everything looks ok on their end. It's like the query is executed in DB2 but the gateway has trouble replying to the Oracle DB
As a side note, the hung session prevents the database from shutting down but does not prevent the database from closing some processes while trying to shutdown (e.g. J000, MXXX, etc.). This results in an open database with missing processes (non critical).
I think this is a network/firewall issue, has anyone had any similar experiences with the gateway? How can I diagnose the problem?
I should note, other Oracle databases in different locations (and different versions) do not have a problem when running the same queries.
Message was edited by:
SamBIf I remember correctly the V9 TG4DB2/400 was not certified with Oracle database 10gR2; only 10.1. See also Metalink certify page which states:
Operating System: IBM AS/400 Version V5R1 - V5R3
Oracle Transparent Gateway for DB2/400 Version 9.2.0
Oracle Database - Enterprise Edition V10 Version 10g
Status: Desupported
Side Note: the certify version states 10g; this means 10gR1; not 10gR2.
You can crosscheck it while checking out the V10.1/2 gateway certification which explicite lists 10gR2.
So it would be interesting if any 10gR2 database can successfully query the table. -
Dba_dml_lock hang the session?
frequently, the user session occurs the lock wait.... to check, i run the dba_dml_lock, after executing my session will get hang... i run the catblock.sql again, still problem, my oracle binary 9.2.0.6 in hp itanium 11.23v. any suggestion
please try the following queries
select sw.username Waiting User,bu.ussername Locking User,
dw.username Locking User, dw.lock_type, dw.mode_held, dw.mode_requested,
from dba_Waiters dw, v$session sw, v$session bu
where dw.waiting_session = sw.sid
and dw.holding_Session = bu.sid
select lpad(' ', decode(l.xidusn,0,3,0 )) || l.oracle_username,
o.owner,o.object_name, o.object_type
from v$locked_object l, dba_objects o
where l.object_id = o.object_id
order by o.object_id, 1 desc
And if they also hang
Best Regards
Krystian Zieja / mob -
Disk Utility Hangs "Closing Session" when attempting to burn a disk image
I have been trying to burn a DVD of a disk image created with Disk Utility and the process repeatedly gets hung up on "Closing session". I have let it go for 15 hours (I assume that is long enough) before force quitting DU. Additionally, the drive is completely unresponsive until a complete reboot is made.
I have searched the discussions but can't find the same problem addressed elsewhere. Does anyonw have any suggestions?
Thank you.
PMG5 - Dual 2GHz Mac OS X (10.4.3)Hi Marc,
Did you got any reply on this issue as I have exactly the same problem.
I actually broke up after 12 hours for 13GB to image.
best regards
Jean-Claude -
How to diagnose a hanging process/session?
Hello,
I've got a user that has a stored procedure that (I'm still waiting to get the code from him) he says basically drops a table, then recreates it by a select on another table. He says this only involves tables of about 600 rows.
He has run this numerous times with no problems and it usually completes immediately.
However, since yesterday, he fires this off, and it seems to just sit there hung forever. Even killing it takes a good bit of time.
Strangely enough, this seems to have started happening on all 3 instances on the same box (3 different test environments, all approximately the same) at the same time.
Can someone give me some good steps and suggestions to try to help troubleshoot this?
Thank you,
cayenneOracle prevents modification of a procedure under certain conditions.
1) Procedure does DML
2) No COMMIT has been issued.
No session is allowed to change procedure until either COMMIT or ROLLBACK is issued by session that did DML.
In other words, user is blocking himself by invoking multiple sessions & never issuing COMMIT or ROLLBACK.
Edited by: sb92075 on Sep 1, 2009 7:11 AM -
Hi all,
i have big problems using objects in session.
Perhaps i only have a wrong view of this technology.
1. Session objects could be used by serveral request.
2. Requests of one user could run simultaneously (user click double on a link or opens two browser windows)
=> Every Read/Change on session object must be synchronized
=> And this must be done global for the app (could be that the access to a session object is done in different business logic methods)
If this is ok, using helpful tags of additional technologies like JSTL (sessionScope.ObjectName) are absolutly wrong.
Did i make an important mistake in my view.
cu
JohnnySession objects are usually implemented using cookies, which is also the same method your browser uses when it asks you if you want to save username/password information for a given site.
But, as far as keeping information, why do you need to store the password in the session? Shouldn't the username (and possibly some permissions) be all the user data you need? -
Procedure call through InstantClient 10.1.0.4 (ODBC) hangs the session
Hello,
The application has been made by Visual Basic 6.0 sp5, it uses MDAC 2.5. RDBMS version is 9.2, server OS Aix 5.2, client OS XP Professional SP2.
In other ways the application is working properly, but when a user tries to start a report which calls a procedure through ODBC the following happens:
(1) The workstation processor starts working under a permanent load of 100%.
(2) The ODBC trace stops here:
{? = call XXXX_YYYY.ZZZ_AAAAAAAA
['BB_BBBB','200511','200511','CCC',null,null,'null','null'}
(3) The database listener trace (admin, on the server) stops here (287 rows follow which are the result of trying to start a report):
nsevwait: 1 newly-posted event(s)
nsevfnt: cxd: 0x1057c390 stage 0: NT events set:
CONNECTION REQUEST
nsevfnt: cxd: 0x1057c390 stage 0: NS events set:
INCOMING CALL
nsevwait: event is 0x1, on 3
nsevwait: 1 posted event(s)
nsglhe: entry
nsmal: 752 bytes at 0x11060b090
nsmal: 2800 bytes at 0x110616030
nsopen: opening transport...
nttcon: entry
nttcon: toc = 3
nttcnp: entry
ntvlin: entry
ntvlin: exit
nttcnp: Validnode Table IN use; err 0x0
nttcnp: getting sockname
nttcnp: exit
nttcnr: entry
nttcnr: waiting to accept a connection.
nttcnr: getting sockname
nttvlser: entry
nttvlser: valid node check on incoming node xxx.yyy.z.50
nttvlser: Accepted Entry: xxx.yyy.z.50
nttcnr: exit
nttcon: set TCP_NODELAY on 18
nttcon: exit
nsopen: transport is open
nsnainit: answer
nsnasvnainfo: NA disabled for this connection
nainit: entry
nagblini: entry
nau_gin: entry
nau_gparams: entry
nam_gbp: Reading parameter "sqlnet.authentication_required" from parameter file
nam_gbp: Parameter not found
nau_gparams: Using default value "FALSE"
nau_gslf: entry
nam_gic: entry
nam_gic: Counting # of items in "sqlnet.authentication_services" parameter
nam_gic: Parameter not found
nam_gic: Found 0 items
nam_gic: exit
nau_gslf: Using default value "all available adapters"
nauss_set_state: entry
nauss_set_state: exit
nau_gslf: exit
nau_gparams: exit
nau_gin: exit
nagblini: exit
na_saveprot: entry
na_saveprot: exit
nacomin: entry
nas_init: entry
nas_init: exit
nau_ini: entry
naugcp_get_connect_parameters: entry
nauss_set_state: entry
nauss_set_state: exit
naugcp_get_connect_parameters: exit
nau_gettab: entry
nau_tadv: entry
nau_fad: entry
nau_fad: exit
nau_fad: entry
nau_fad: exit
nau_fad: entry
nau_fad: exit
nau_fad: entry
nau_fad: exit
nau_tadv: exit
nau_gettab: exit
nau_sini: entry
nau_sini: exit
nau_ini: exit
naeeinit: entry
nam_gbp: Reading parameter "SQLNET.FIPS_140" from parameter file
nam_gbp: Parameter not found
nam_gnsp: Reading parameter "SQLNET.ENCRYPTION_SERVER" from parameter file
nam_gnsp: Parameter not found
naequad: Using default value "ACCEPTED"
nam_gic: entry
nam_gic: Counting # of items in "SQLNET.ENCRYPTION_TYPES_SERVER" parameter
nam_gic: Parameter not found
nam_gic: exit
naesno: Using default value "all available algorithms"
naeshow: entry
naeshow: exit
naeeinit: exit
naecinit: entry
nam_gnsp: Reading parameter "SQLNET.CRYPTO_CHECKSUM_SERVER" from parameter file
nam_gnsp: Parameter not found
naequad: Using default value "ACCEPTED"
nam_gic: entry
nam_gic: Counting # of items in "SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER" parameter
nam_gic: Parameter not found
nam_gic: exit
naesno: Using default value "all available algorithms"
naeshow: entry
naeshow: exit
naecinit: exit
nadisc: entry
nacomtm: entry
nacompd: entry
nacompd: exit
nacompd: entry
nacompd: exit
nacomtm: exit
nas_dis: entry
nas_dis: exit
nau_dis: entry
nau_dis: exit
naeetrm: entry
naeetrm: exit
naectrm: entry
naectrm: exit
nagbltrm: entry
nau_gtm: entry
nau_gtm: exit
nagbltrm: exit
nadisc: exit
nainit: exit
nsnainit: NS Connection version: 311
nsnainit: inf->nsinfflg[0]: 0xd inf->nsinfflg[1]: 0xd
nsnainit: "or" info flags: 0xd Translations follow:
native service(s) is (are) wanted
NA disabled remotely for this connection
NA services unavailable on both processes - negotiation not needed
nsnainit: "or" info flags: 0xd Translations follow:
native service(s) is (are) wanted
NA disabled remotely for this connection
NA services unavailable on both processes - negotiation not needed
"and" info flags: 0xd Translations follow:
native service(s) is (are) wanted
NA disabled remotely for this connection
NA services unavailable on both processes - negotiation not needed
nsopen: global context check-in (to slot 11) complete
nsopen: lcl[0]=0x7fe9ff, lcl[1]=0x12003, gbl[0]=0x7e3f, gbl[1]=0x2001, tdu=32767, sdu=8192
nsdo: cid=11, opcode=65, bl=0, what=0, uflgs=0x0, cflgs=0x2
nsdo: rank=64, nsctxrnk=0
nsdo: nsctx: state=7, flg=0x4200, mvd=0
nsdo: nsctxrnk=0
nsanswer: deferring connect attempt; at stage 5
nsevreg: begin registration process for 11
nsevreg: sgt=0, evn=1, evt[2]=0x0
nsevreg: begin notification process for 11
nsevreg: rdm=0, sgt=0, evt[0]=0x20, [1]=0x20, [2]=0x0, nrg=0
nsevreg: registering for 0x20
nsglhe: exit
nsevwait: 10 registered connection(s)
nsevwait: 0 pre-posted event(s)
nsevwait: waiting for transport event (1 thru 11)...
nsevwait: 1 newly-posted event(s)
nsevfnt: cxd: 0x10606bb0 stage 5: NT events set:
READ
nsevfnt: cxd: 0x10606bb0 stage 5: NS events set:
OUTGOING CALL COMPLETE
nsevdansw: at STAGE 5
nsdo: cid=11, opcode=68, bl=2040, what=8, uflgs=0x0, cflgs=0x3
nsdo: rank=64, nsctxrnk=0
nsdo: nsctx: state=14, flg=0x4204, mvd=0
nsdo: gtn=0, gtc=0, ptn=10, ptc=8163
nscon: doing connect handshake...
nscon: recving a packet
nsprecv: reading from transport...
nttrd: entry
nttrd: socket 18 had bytes read=262
nttrd: exit
nsprecv: 262 bytes from transport
nsprecv: tlen=262, plen=262, type=1
nscon: got NSPTCN packet
nsconneg: vsn=313, lov=300, opt=0x0, sdu=2048, tdu=32767, ntc=0x860e
nsconneg: vsn=311, gbl=0x1, sdu=2048, tdu=32767
nscon: got 204 bytes connect data
nsdo: nsctxrnk=0
nsevdansw: exit
nttctl: entry
nttctl: Clearing non-blocking mode
nsevwait: event is 0x20, on 11
nsevwait: 1 posted event(s)
nsglhe: entry
nsglfc: Assume establishing a connection: look for SID
nsglfc: command = establish
nttaddr2bnd: entry
nttaddr2bnd: exit
nlpcaini: entry
nlpcaini: prg = /oracle9/app/product/9.2.0/bin/oracle
nlpcaini: arg[0] = oracleaaaaa
nlpcaini: arg[1] = (LOCAL=NO)
nlpcaini: env[0] = _=/ddddddd/app/product/9.0.2/bin/lsnrctl
nlpcaini: env[1] = TMPDIR=/lisatmp
nlpcaini: env[2] = LANG=en_US
nlpcaini: env[3] = LOGIN=ddddddd
nlpcaini: env[4] = PATH=/ddddddd/app/product/9.0.2/dcm/bin:/ddddddd/app/product/9.0.2/opm/bin:/ddddddd/app/product/9.0.2/bin:/usr/local/bin:/usr/ccs/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home/ddddddd/bin:/usr/bin/X11:/sbin:.
nlpcaini: env[5] = NLS_LANG=American_America.we8iso8859P1
nlpcaini: env[6] = ORACLE_BASE=/ddddddd/app/product
nlpcaini: env[7] = LC__FASTMSG=true
nlpcaini: env[8] = CGI_DIRECTORY=/var/docsearch/cgi-bin
nlpcaini: env[9] = LOGNAME=ddddddd
nlpcaini: env[10] = TMP=/lisatmp
nlpcaini: env[11] = USER_NLS_LANG=Finnish_Finland.we8iso8859P1
nlpcaini: env[12] = MAIL=/usr/spool/mail/ddddddd
nlpcaini: env[13] = LOCPATH=/usr/lib/nls/loc
nlpcaini: env[14] = PS1=$PWD[SID=$ORACLE_SID]>$
nlpcaini: env[15] = LDR_CNTRL=MAXDATA=0x20000000
nlpcaini: env[16] = DOCUMENT_SERVER_MACHINE_NAME=localhost
nlpcaini: env[17] = USER=ddddd
nlpcaini: env[18] = AUTHSTATE=files
nlpcaini: env[19] = TNS_ADMIN=/ddddddd/app/product/9.0.2/network/admin
nlpcaini: env[20] = DEFAULT_BROWSER=netscape
nlpcaini: env[21] = DISPLAY=cccc:0.0
nlpcaini: env[22] = SHELL=/usr/bin/ksh
nlpcaini: env[23] = ODMDIR=/etc/objrepos
nlpcaini: env[24] = DOCUMENT_SERVER_PORT=49213
nlpcaini: env[25] = ORA_NLS33=/ddddddd/app/product/9.0.2/ocommon/nls/admin/data
nlpcaini: env[26] = HOME=/home/ddddddd
nlpcaini: env[27] = TERM=dumb
nlpcaini: env[28] = MAILMSG=[YOU HAVE NEW MAIL]
nlpcaini: env[29] = ORACLE_HOME=/oracle9/app/product/9.2.0
nlpcaini: env[30] = ITECONFIGSRV=/etc/IMNSearch
nlpcaini: env[31] = PWD=/home/ddddddd
nlpcaini: env[32] = DOCUMENT_DIRECTORY=/usr/docsearch/html
nlpcaini: env[33] = TZ=WET-2WET-3,M3.5.0/03:00:00,M10.5.0/04:00:00
nlpcaini: env[34] = ITECONFIGCL=/etc/IMNSearch/clients
nlpcaini: env[35] = ITE_DOC_SEARCH_INSTANCE=search
nlpcaini: env[36] = A__z=! LOGNAME
nlpcaini: env[37] = ORA_NET2_DESC=4,7
nlpcaini: env[38] = LIBPATH=/ddddddd/app/product/9.0.2/lib32:/ddddddd/app/product/9.0.2/lib
nlpcaini: env[39] = NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat
nlpcaini: env[40] = ORACLE_SID=aaaaa
nlpcaini: exit
nsbeqaddr: connecting...
ntpcon: entry
ntpcon: toc = 1
sntpcall: entry
sntpcall: About to exec /oracle9/app/product/9.2.0/bin/oracle
sntpcall: environ[41] = ""
sntpcall: detaching from parent with additional fork
sntpcall: result string is NTP0 33240
sntpcall: hdl[IR]=23, hdl[IW]=22
sntpcall: exit
ntpcon: NT layer IPC connection has been established
ntpcon: exit
nttaddr2bnd: entry
nttaddr2bnd: exit
nsbeqaddr: doing connect handshake...
nsbequeath: doing connect handshake...
ntpwr: entry
ntpwr: exit
ntpwr: entry
ntpwr: exit
ntpwr: entry
ntpwr: exit
ntprd: entry
ntprd: exit
ntprd: entry
ntprd: exit
nsbequeath: NSE=0
ntpdisc: entry
ntpdisc: exit
nsbeqaddr: connect handshake is complete
nstimarmed: no timer allocated
nsdo: cid=11, opcode=98, bl=0, what=0, uflgs=0x40, cflgs=0x2
nsdo: rank=64, nsctxrnk=0
nsdo: nsctx: state=2, flg=0x4200, mvd=0
nsevunreg: cid=11, sgt=0, rdm=0
nsevunreg: 9 registered connection(s)
nsdo: nsctxrnk=0
nsclose: closing transport
nttdisc: entry
nttdisc: Closed socket 18
nttdisc: exit
nsclose: global context check-out (from slot 11) complete
nsmfr: 2800 bytes at 0x110616030
nsmfr: 752 bytes at 0x11060b090
nsglhe: exit
nsevwait: 9 registered connection(s)
nsevwait: 0 pre-posted event(s)
nsevwait: waiting for transport event (1 thru 10)...
The procedure call through ODBC is working when we use Oracle9i Client.
So. All comments are much appreciated!
Terhoin addition:
my main problem is that Oracle ODBC driver does not understand something like
{call types.test_procedure (?, ?,,?)}
to pass not all parameters (I whant to use default value for some of parameters) -
Webaccess hanging browser sessions
Hi
Anyone else getting slow interactions using webaccess in 2014?
Just upgraded from 2012. Smooth and quick upgrade process for a single domain single PO system with a few users but webaccess seems to be extremely sluggish to use, eventually it seems to hog the browser enough that it crashes (chrome wants to kill the tab). Almost as if there is a delay before and after the "loading" graphics appears.
2012 webaccess was lightening fast in our environment across pretty much any browser on any device.
Have tried Windows 7 chrome (assuming latest version) across two computers with same results, ditto with firefox. Anytime webaccess has to load a list of emails after say clicking on a folder, it seems to take an unusually long period of time to display and free the browser thread.
Running sles 11 sp2, tested locally to the server.
(Have been very impressed with everything else in this release so far. Especially the attention to little things like keyboard shortcuts in the windows client, I'm going to be flying along in this new client!)
Aaron.I tried another user and it's not as sluggish on first login although there are some folders that I click on that will never display and time out with a "timed out wait for stream search" for that user, haven't seen any errors generated with my own account. I did a structural rebuild on my own mailbox but it made no difference.
Doesn't seem like something playing up server side, feels like a javascript type CPU hog event to me (if you know what I mean).
If no one else is seeing this behaviour I guess I'll log an SR.
Thick client performance using 2014 client seems good, fast as and possibly slightly faster than 2012.
Originally Posted by dzanre
foccer wrote:
> but webaccess seems to be
> extremely sluggish to use
Since you have tried multiple browsers, my next question I guess is does this
happen for all users? Or are only you noticing the issue?
Danita
Novell Knowledge Partner
Are you a GroupWise Power Administrator? Join our site.
http://www.caledonia.net/register
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below... -
I am having a problem with my users clicking on a link which kicks off
a database intensive task. The user then gets frustrated if the
response is not back right away and they click on the link again and
again and again kicking off this database intensive task each time.
My question is, can I stop this behaviour by simply doing:
synchronize session { do database task } ?? Will this work or is
there a better way to do this? I've been told that some applications
will display an hour glass after a link is clicked but I don't know
how to do this. Any help would be greatly appreciated.
In addition to Dimitri's note, you can store the fact that an active request
is occurring for the user in the HTTP session object, and label that task
such that subsequent requests can return the same answer (i.e. "still
working") and will not start another process. Upon completion, the same
request would show the result.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
Tangosol Server: Enabling enterprise application customization
"housecube" <[email protected]> wrote in message
news:[email protected]..
> I am having a problem with my users clicking on a link which kicks off
> a database intensive task. The user then gets frustrated if the
> response is not back right away and they click on the link again and
> again and again kicking off this database intensive task each time.
> My question is, can I stop this behaviour by simply doing:
> synchronize session { do database task } ?? Will this work or is
> there a better way to do this? I've been told that some applications
> will display an hour glass after a link is clicked but I don't know
> how to do this. Any help would be greatly appreciated.
-
Well I wrote a ShellSkript that downloades the data from a SFTP Server and then uses the sqlldr to import the data.
The Problem is : The sqlldr script does not end. It "hangs" after trying to import all lines.
Here is the Screen :
Verwerk shop_orders_2008-03-09_150000_2008-03-10_010000_postpaid_1205107921.csv
SQL*Loader: Release 9.2.0.7.0 - Production on Mon Mar 10 12:47:49 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Commit point reached - logical record count 25
Commit point reached - logical record count 50
Commit point reached - logical record count 54
Commit point reached - logical record count 55
Here is the matching Log :
Record 49: Rejected - Error on table DM_WEBSALES_POSTPAID_LOAD.
ORA-00001: unique constraint (HANS.PK_WEBSALES_POSTPAID_LOAD1) violated
Record 50: Rejected - Error on table DM_WEBSALES_POSTPAID_LOAD.
ORA-00001: unique constraint (HANS.PK_WEBSALES_POSTPAID_LOAD1) violated
Record 51: Rejected - Error on table DM_WEBSALES_POSTPAID_LOAD.
ORA-00001: unique constraint (HANS.PK_WEBSALES_POSTPAID_LOAD1) violated
Record 52: Rejected - Error on table DM_WEBSALES_POSTPAID_LOAD.
ORA-00001: unique constraint (HANS.PK_WEBSALES_POSTPAID_LOAD1) violated
Record 53: Rejected - Error on table DM_WEBSALES_POSTPAID_LOAD.
ORA-00001: unique constraint (HANS.PK_WEBSALES_POSTPAID_LOAD1) violated
Record 54: Rejected - Error on table DM_WEBSALES_POSTPAID_LOAD.
ORA-00001: unique constraint (HANS.PK_WEBSALES_POSTPAID_LOAD1) violated
Record 55: Rejected - Error on table DM_WEBSALES_POSTPAID_LOAD, column TRANSFERT_ACCEPT_CONDITIONS.
ORA-01401: inserted value too large for column
Table DM_WEBSALES_POSTPAID_LOAD:
0 Rows successfully loaded.
55 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Space allocated for bind array: 251550 bytes(25 rows)
Read buffer bytes: 1048576
Total logical records skipped: 1
Total logical records read: 55
Total logical records rejected: 55
Total logical records discarded: 0
Run began on Mon Mar 10 12:47:49 2008
Run ended on Mon Mar 10 12:47:49 2008
Elapsed time was: 00:00:00.46
CPU time was: 00:00:00.01
Ok, I see that I've imported the same data many times (as you can see in the key violation) but nevertheless the script should end...
Have any ideas ???
Thanks in advance,
CarstenWell.... thanks for the help but it has been another problem (hanging sql+ session after sqlldr Command).
Sorry guys!!
- can be closed -
Maybe you are looking for
-
Problems with Adobe Speedgrade CS6 in Windows 7
I am having problem with Adobe Speedgrade CS6 on my Windows 7 machine with the following specs: Windows 7 Ultimate SP1 Gateway FX 6800-01e 2.67 GHz i7 Quad-core processor 16.0 GB RAM 750GB primary hard drive (Seagate ST3750528AS) 2 - 2TB secondary ho
-
Wrong Calculation of Total Cost in Travel management in PR05
Dear Gurus, We have filled the expense type in PR05 like, Paid by company -- 3000 Own Exp. - 1000 Other Exp.---- 1000 5000. So the paid by company is 3000 and Reimbursement is 2000. But when I check rep
-
PC Suite installs fonts to temp directory!
I have been trying to clear out my temp folders and noticed some files that wouldn't delete. It seems that PC Suite is permanently installing some of it's fonts into the temp directory, in a folder called NGLATempNokia. I was able to delete it by shu
-
Hiding declined events in iCal when using Office365 (or Exchange)?
Events are appearing cancelled on our Exchange/Office365 calendars but do not delete from iCal on our iPads. The cancelled meetings will instead show up in a different color. Anyone else having this same problem or know of a solution? Thanks!
-
Viewing mac HDD in windows installation on boot camp?
title pretty much explains it. i have windows xp pro installed on bootcamp but i want to view the mac hdd on windows. i can see the windows hdd in mac osx but not the other way around. the hdd is formatted to fat32. thanks