New Socket takes too long / how to stop a Thread ?

Hello to everyone,
I have a problem that I have been hunting this ol' Sun website all day for a suitable answer, and have found people who have asked this same question and not gotten answers. Finally, with but a shred of hope left, I post...
My really short version:
A call to the Socket(InetAddress,int) constructor can take a very long time before it times out. How to limit the wait?
My really detailed version:
I have a GUI for which the user enters comm parameters, then the program does some I/O while the user waits (but there is a Cancel button for the Impatient), then the results are displayed. Here is quick pseudocode (which, by the way, worked great before there were Sockets in this program -- only serial ports):
Main (GUI) thread:
     --> reset the stop request flag
     --> calls workerThread.start(), then brings up a Cancel dialog with a Cancel button (thus going to sleep)
     --> (awake by dialog closing -- dialog may have been closed by workerThread or by user)
     --> set stop request flag that worker thread checks (in case he's still alive)
     --> call workerThread.interrupt() (in case he's alive but asleep for some reason (???))
     --> call workerThread.join() to wait for worker thread to be dead (nothing to wait for if he's dead already)
     --> display worker thread's result data or "Cancelled..." information, whichever worker thread has set
Worker thread:
     --> yield (to give main thread a chance to get the Cancel Dialog showing)
     --> do job, checking (every few code lines) that stop request flag is not set
     --> if stop request, stop and set cancelled flag for Main thread to handle
     --> if finish with no stop request, set result data for Main thread to handle
     --> take down Cancel Dialog (does nothing if not still up, takes down and wakes main thread if still up)
THE PROBLEM: Worker thread's job involves doing IO, and it may need to instantiate a new Socket. If it is attempting to instantiate Socket with bad arguments, it can get stuck... The port int is hardcoded by the program, but the IPAddress must be typed by user.
If the arguments to Socket(InetAddress, int) constructor contain a valid-but-not-in-use IP address, the worker thread will get stuck in the Socket constructor for a LONG time (I observed 1m:38s). There is nothing the Main thread can do to stop this wait?
EVEN WORSE: If the user clicks the Cancel Button during this time, the dialog goes away soon/immediately, but then the GUI appears to be hanging (single-threaded look) until the long wait is over (after which the "Cancelled..." info is displayed).
MY QUESTION: Is there nothing the Main thread can do to stop this wait?
Your answers will be sincerely appreciated. Despite my hopeless attitude (see above), the folks at this forum really have yet to let me down ...
/Mel

http://developer.java.sun.com/developer/technicalArticles/Networking/timeouts/

Similar Messages

Login to the SAP System and opening a new modus takes too long

Hello friends
I have a problem on my SAP ECC 6.0 system. When some users (but not all users) try to login (via SAPGUI) or open new modi this takes within 5 minutes to happen. I have allready excluded local hardware problems on the client PCs (You can logon on the same computer with another user without having that delay).
In Sapgui the Option "Extras - Settings - Do not display picture" is already set.
Could anyone give me a hint please in which direction I could search for the solution? This would be very helpful.
Thanks a lot in advance!
Greetings
Marco

Was a hardware issue...

With iTunes 11, genius syncing takes too long, how to fix?

Genius is now linked with Match and cannot be turned off separately. How can Genius syncing be sped up?

For reporting bugs, go here:
https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/wa/signIn
you will be required to give a good bit of info as it
should be for reporting and diagnosing a bug.
If you are simply dissatisfied with iTunes 11 and its features
(or elimination of features) and also its bugginess, post here:
http://www.apple.com/feedback/itunesapp.html
The former, if given sufficient info, will be sent to software
engineers. The latter will be sent to marketing, etc.

Sometimes my computer takes too long to connect to new website. I am running a pretty powerful work program at same time, what is the best solution? Upgrading speed from cable network, is it a hard drive issue? do I need to "clean out" the computer?

Many times my computer takes too long to connect to new website. I have wireless internet (time capsule) and I am running a pretty powerful real time financial work program at same time, what is the best solution? Upgrading speed from cable network? is it a hard drive issue? do I only need to "clean out" the computer? Or all of the above...not to computer saavy. It is a Macbook Pro osx 10.6.8 (late 2010).

Almost certainly none of the above! Try each of the following in this order:
Select 'Reset Safari' from the Safari menu.
Close down Safari; move <home>/Library/Caches/com.apple.Safari/Cache.db to the trash; restart Safari.
Change the DNS servers in your network settings to use the OpenDNS servers: 208.67.222.222 and 208.67.220.220
Turn off DNS pre-fetching by entering the following command in Terminal and restarting Safari:
defaults write com.apple.safari WebKitDNSPrefetchingEnabled -boolean false

AME CS6 rendering with AE and Pr takes too long

Hi Guys,
Need some help here. i have rendered a 30 secs mp4 video with 1920 x 1080 HD format 25 frames w/o scripting in AME for 4 hours!
Why does it take too long? I have rendered a 2 minute video with same format w/ scripting but only spare less than 30 minutes for rendering.
Im using After Effects and Premium Pro both CS6 and using Dynamic Link in AME.
What seems to be wrong in my current settings?
Any help would be appreciated.
Thanks!

This may be a waste of time, but it won't take a minute and is something you should always do whenever things go strangely wrong ............ trash the preferences, assuming you haven't done it already.
Many weird things happen as a result of corrupt preferences which can create a vast range of different symptoms, so whenever FCP X stops working properly in any way, trashing the preferences should be the first thing you do using this free app.
http://www.digitalrebellion.com/prefman/
Shut down FCP X, open PreferenceManager and in the window that appears:-
1. Ensure that only FCP X is selected.
2. Click Trash
The job is done instantly and you can re-open FCP X.
There is absolutely no danger in trashing preferences and you can do it as often as you like.
The preferences are kept separately from FCP X and if there aren't any when FCP X opens it automatically creates new ones . . . instantly.

This report cannot be executed because it may take too long to execute

Dear expert,
i am getting below message when user is trying to execute the report. I am new to Basis support, can any one let me know how to resolve this problem. This in R3 4.6 version
"This report cannot be executed because it may take too long to execute"
Thanks in advance for your help.
Regards.
Ameture

Hi Ameture,
This is not permanant solution, for better and running smooth business pls inform to ababper to change bad codding and provide expert coding so that you can run this report at any time. Becuase same problem already done with me. I have checked all the thing even the coding also and inform to abaper to change specific coding and expert coding. I found result immediately, earlier that report took 3-4 hours and now take 15-20 minuts only. Now user and myself both are happy.
Regards,
Anil

Why finding replication stream matchpoint takes too long

hi,
I am using bdb je 5.0.58 HA(two nodes group,JVM 6G for each node).
Sometimes, I found bdb node takes too long to restart(about 2 hours).
When this occurs, I catch the process stack of bdb(jvm process) by jstack.
After analyzing stack,I found "ReplicaFeederSyncup.findMatchpoint()" taking all the time.
I want to know why this method takes so much time,and how can I avoid this bad case.
Thanks.
帖子经 liang_mic编辑过

Liang,
2 hours is indeed a huge amount of time for a node restart. It's hard be sure without doing more detailed analysis of your log as to what may be going wrong, but I do wonder if it is related to the problem you reported in outOfMemory error presents when cleaner occurs [#21786]. Perhaps the best approach is for me to describe in more detail what happens when a replicated node is connecting with a new master, which might give you more insight into what is happening in your case.
The members of a BDB JE HA replication group share the same logical stream of replicated records, where each record is identified with a virtual log sequence number, or VLSN. In other words, the log record described by VLSN x on any node is the same data record, although it may be stored in a physically different place in the log of each node.
When a replica in a group connects with a master, it must find a common point, the matchpoint, in that replication stream. There are different situations in which a replica may connect with a master. For example, it may have come up and just joined the group. Another case is when the replica is up already but a new master has been elected for the group. One way or another, the replica wants to find the most recent point in its log, which it has in common with the log of the master. Only certain kinds of log entries, tagged with timestamps, are eligible to be used for such a match, and usually, these are transaction commits and aborts.
Now, in your previous forum posting, you reported an OOME because of a very large transaction, so this syncup issue at first seems like it might be related. Perhaps your replication nodes need to traverse a great many records, in an incomplete transaction, to find the match point. But the syncup code does not blindly traverse all records, it uses the vlsn index metadata to skip to the optimal locations. In this case, even if the last transaction was very long, and incomplete, it should know where the previous transaction end was, and find that location directly, without having to do a scan.
As a possible related note, I did wonder if something was unusual about your vlsn index metadata. I did not explain this in outOfMemory error presents when cleaner occurs but I later calculated that the transaction which caused the OOME should only have contained 1500 records. I think that you said that you figured out that you were deleting about 15 million records, and you figured out that it was the vlsn index update transaction which was holding many locks. But because the vlsn index does not record every single record, it should only take about 1,500 metadata records in the vlsn index to cover 15 million application data records. It is still a bug in our code to update that many records in a single transaction, but the OOME was surprising, because 1,500 locks shouldn't be catastrophic.
There are a number of ways to investigate this further.
- You may want to try using a SyncupProgress listener described at http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/SyncupProgress.html to get more information on which part of the syncup process is taking a long time.
- If that confirms that finding the matchpoint is the problem, we have an unadvertised utility, meant for debugging, to examine the vlsn index. The usage is as follows, and you would use the -dumpVLSN option, and run thsi on the replica node. But this would require our assistance to interpret the results. We would be looking for the records that mention where "sync" points are, and would correlate that to the replica's log, and that might give more information if this is indeed the problem, and why the vlsn index was not acting to optimize the search.
$ java -jar build/lib/je.jar DbStreamVerify
usage: java { com.sleepycat.je.rep.utilint.DbStreamVerify | -jar je-<version>.jar DbStreamVerify }
-h <dir> # environment home directory
-s <hex> # start file
-e <hex> # end file
-verifyStream # check that replication stream is ascending
-dumpVLSN # scan log file for log entries that make up the VLSN index, don't run verify.
-dumpRepGroup # scan log file for log entries that make up the rep group db, don't run verify.
-i # show invisible. If true, print invisible entries when running verify mode.
-v # verbose

11gR2:crsctl, srvctl commands takes too long to respond

Hi,
I have successfully configured *11gR2 two node RAC on ASM on Win 2008 64bit.*
Everything work very well like connecting to database, querying database. Node restart also takes acceptable time to go down & restart the clusterware & database.
But when I execute crsctl status resource -t or srvctl status database -d db_name commands from any node takes 10-15min to give output.
They give output & everything completes successfully but takes too long to respond.
The questions are:
- If everything works fine then why crsctl, srvctl takes too long to respond?
- what could be blocking these command to gather clusterware and database status on all nodes?
- what additional info would be helpful that I can provide?

dag wrote:
I dont have this issue either. are you auto starting mpd?
that time is how long it is up in other words you opened it then closed it at that time
I'm not sure if you are referring to me or not, but in my screenshot I am timing the lag in ncmpcpp by pressing 'q' in the terminal during the delay, so it quits ncmpcpp immediately after the lag. The lag is longer for ncmpc because the interface loads before the program connects to mpd, so I have to stop it manually immediatly after it connects.
WonderWoofy wrote:I don't have this problem... if you are starting it as a systemd user service, maybe there is relevant information in the journal.
The journal did not reveal anything relevant sadly. I have now tried launching mpd without systemd, and the lag remains. I have also noticed that a small mpd programming project I am writing also experiences the same lag when it tries to connect to mpd.

Having lagging problems with YouTube videos, it simply takes so long for the red bar to completely load and the videos frequently pause and take too long to restart playing again.

I have been having lagging problems with YouTube videos for a number of months now. It simply takes so long for the red bar to completely load and the videos frequently pause and take too long to restart playing again. Even with little 2 and 3 minute videos.
I have a fast computer and my webpages load really, really fast. I have FireFox 4 browser and a Vista Home Premium 64-bit OS. So I don't have a slow computer or web browser. But these slow YouTube vids take way too long to load for some reason.
Does anyone have any idea how I can speed up YouTube?

Hi
The forums are customer to customer in the first instance, Only the mods (BT) will ask for personal information through a email link. Would you mind posting your Hub stats & BT speed test results this will help all with diagnosis-
To post the full stats from your router
for home hub - 192.168.1.254
Navigate to ADSL Settings or use the A-Z at the top right
Click on More Details and then post the results.
Run BT speed tester and post the results from http://speedtester.bt.com/
If possible it would be best to connect to the BT master socket this will rule out any telephone/broadband extension wiring also consider the housing of the hub/router as anything electrical can cause problems as these are your responsibility, if these are found to be the case Openreach (engineer) will charge BT Broadband, which will be passed onto you, around £130.00.
Noisy line! When making telephone calls, if so this is not good for your broadband, you can check-
Quite line test dial 17070 option 2 and listen - should hear nothing best done with old type analogue phone digital (dect) will do but may have slight hiss If you hear noise- crackling pops etc, report it as a noisy line on your phone, don’t mention broadband, Bt Faults on 151.
As for your FTTC its available in some areas between 40% & 80% of customers in enabled areas can receive it!
Mortgage Advisor 2000-2008
Green Energy Advisor 2008-2010
Charity Health Care Provider Advisor 2010-
I'm alright Jack....

Page takes too long to load because of videos

Hi. I have a website that I made, but the page takes too long to load because there are videos on it. Is there any way to stop the videos from auto-loading and instead only load when someone clicks on them to play?

There are several ways to have videos on a page without having them load until they are selected to play. A couple are:
1 - Opening Item in a New, Precisely Sized Window. This test site has 9 videos on the page: PhotoPresenter Animated Slideshow Themes.
2 - QT Movies via Export for Web in QT Player. This method is more difficult to implement.
OT

Report Takes Too Long Time

Hi!
I am in troubble
following is the query
SELECT inv_no, inv_name, inv_desc, i.cat_id, cat_name, i.sub_cat_id,
sub_cat_name, asset_cost, del_date, i.bl_id, gen_desc bl_desc, p.prvcode, prvdesc, cur_loc,
pldesc, i.pmempno, pmname, i.empid, empname
FROM inv_reg i,
cat_reg c,
sub_cat_reg s,
gen_desc_reg g,
ploc p,
province r,
pmaster m,
iemp_reg e
WHERE i.sub_cat_id = s.sub_cat_id
AND i.cat_id = s.cat_id
AND s.cat_id = c.cat_id
AND i.bl_id = g.gen_id
AND i.cur_loc = p.plcode
AND p.prvcode = r.prvcode
AND i.pmempno = m.pmempno(+)
AND i.empid = e.empid(+)
&wc
order by prvdesc, pldesc, cat_name, sub_cat_name, inv_no
and this query returns 32000 records
when i run this query on reports 10g
then it takes 10 to 20 minuts to generate report
how can i optimize it...?

Hi Waqas Attari
Pls study & try this ....
When your query takes too long ...
hope it helps....
Regards,
Abdetu...

OPM process execution process parameters takes too long time to complete

PROCESS_PARAMETERS are inserted every 15 min. using gme_api_pub packages. some times it takes too long time to complete the batch ,ie completion of request. it takes about 5-6 hrs long time ,in other time s it takes only 15-20 mins.This happens at regular interval...if anybody can guide me I will be thankful to him/her..
thanks in advance.
regds,
Shailesh

Generally the slowest part of the process is in the extraction itself...
Check in your source system and see how long the processes are taking, if there are delays, locks or dumps in the database... If your source is R/3 or ECC transactions like SM37, SM21, ST22 can help monitor this activity...
Consider running less processes in parallel if you have too many and see some delays in jobs... Also indexing some of the tables in the source system to expedite the extraction, make sure there are no heavy processes or interfaces running in the source system at the same time you're trying to load... Check with your Basis guys for activity peaks and plan accordingly...
In BW also check in your SM21 for database errors or delays...
Just some ideas...

Web application deployment takes too long?

Hi All,
We have a wls 10.3.5 clustering environment with one admin server and two managered servers separately. When we try to deploy a sizable web application, it takes about 1 hour to finish. It seems that it takes too long to finish the deployment. Here is the output from one of two managerd server system log. Could anyone tell me it is normal or not? If not, how can I improve this?
Thanks in advance,
John
+####<Feb 29, 2012 12:11:03 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535463373> <BEA-149059> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] is transitioning from STATE_NEW to STATE_PREPARED on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:05 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <9baa7a67b5727417:26f76f6c:135ca05cff2:-8000-00000000000000b0> <1330535465664> <BEA-149060> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] successfully transitioned from STATE_NEW to STATE_PREPARED on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466493> <BEA-149059> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] is transitioning from STATE_PREPARED to STATE_ADMIN on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466493> <BEA-149060> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466809> <BEA-149059> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] is transitioning from STATE_ADMIN to STATE_ACTIVE on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466809> <BEA-149060> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server Pinellas1tMS3.>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442300> <BEA-320143> <Scheduled 1 data retirement tasks as per configuration.>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320144> <Size based data retirement operation started on archive HarvestedDataArchive>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320145> <Size based data retirement operation completed on archive HarvestedDataArchive. Retired 0 records in 0 ms.>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320144> <Size based data retirement operation started on archive EventsDataArchive>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320145> <Size based data retirement operation completed on archive EventsDataArchive. Retired 0 records in 0 ms.>+
+####<Feb 29, 2012 1:10:23 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <weblogic.cluster.MessageReceiver> <<WLS Kernel>> <> <> <1330539023098> <BEA-003107> <Lost 2 unicast message(s).>+
+####<Feb 29, 2012 1:10:36 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330539036105> <BEA-000111> <Adding Pinellas1tMS2 with ID -9071779833610528123S:entwl2t-vm:[7005,7005,-1,-1,-1,-1,-1]:entwl2t-vm:7005,entwl3t-vm:7007:Pinellas1tDomain:Pinellas1tMS2 to cluster: Pinellas1tCluster1 view.>+
+####<Feb 29, 2012 1:11:24 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330539084375> <BEA-000128> <Updating -9071779833610528123S:entwl2t-vm:[7005,7005,-1,-1,-1,-1,-1]:entwl2t-vm:7005,entwl3t-vm:7007:Pinellas1tDomain:Pinellas1tMS2 in the cluster.>+
+####<Feb 29, 2012 1:11:24 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330539084507> <BEA-000128> <Updating -9071779833610528123S:entwl2t-vm:[7005,7005,-1,-1,-1,-1,-1]:entwl2t-vm:7005,entwl3t-vm:7007:Pinellas1tDomain:Pinellas1tMS2 in the cluster.>+
Edited by: john wang on Feb 29, 2012 10:36 AM
Edited by: john wang on Feb 29, 2012 10:37 AM
Edited by: john wang on Feb 29, 2012 10:38 AM

Hi John,
There may be some circumstances like when there are many files in the WEB-INF folder and JPS don't use TLD.
I don't think a 1hour deployment is normal, it should be much more faster.
Since you are using 10.3.5, I suggesto you to install the corresponding patch:
1. Download patch 10118941p10118941_1035_Generic.zip
2. Uncompress the file p10118941_1035_Generic.zip
3. Copy the required files (patch-catalog_XXXXX.xml, CIRF.jar ) to the Patch Download Directory (typically, this folder is <WEBLOGIC_HOME>/utils/bsu/cache_dir).
4. Rename the file patch-catalog_XXXXX.xml into patch-catalog.xml .
5. Start Smart Update from <WEBLOGIC_HOME>/utils/bsu/bsu.sh .
6. Select "Work Offline" mode.
7. Go to File->Preferences, and select "Patch Download Directory".
8. Click "Manage Patches" on the right panel.
9. You will see the patch in the panel below (Downloaded Patches)
10. Click "Apply button" of the downloaded patch to apply it to the target installation and follow the instructions on the screen.
11. Add "-Dweblogic.jsp.ignoreTLDsProcessingInWebApp=true" to the Java options to ignore additional findTLDs cost.
12. Restart servers.
Hope this helps.
Thanks,
Cris

New LUN Takes A long Time To Format and Errors Out

Good afternoon,<o:p></o:p>
I have a Hyper-V Cluster composed of 4 nodes and these nodes are able to access multiple CSVs (14 in total). I recently requested a new LUN (LUN 15)to be provisioned
to my Hyper-V cluster in the size of 500GB. Here is my problem:<o:p></o:p>
1. Formatting of a 500GB LUN (with quick format selected) should not take more than a few seconds. Instead, the quick format takes about 2hrs if not longer. I have actually
seen it go for half the day.<o:p></o:p>
2. Once the formatting has completed (no errors), taking the formatted LUN offline freezes the Computer Management screen and shows the status (Not Responding). This
will take place for 30 minutes or less and show that the LUN has been taken offline.<o:p></o:p>
3. In the Failover Cluster Manager, detecting the disks takes about 15 minutes. Once the available LUNs have been detected I can add the 500GB LUN to the Disks screen
without any problems.<o:p></o:p>
4. While in the Disks screen, adding the LUN to the Clustered Shared Volumes takes about 5 minutes (too long).<o:p></o:p>
Already seeing that there is a problem, I went ahead and used the Hyper-V Manager to create a 200GB vhd on the new LUN which has been added to the CSV. The bar indicating
the progress of the vhd creation does not display any progress (no green progress bar appears, not even a tiny bit of it) and after 3 hours (more or less) I receive an error, stating that the creation of the vhd failed.
<o:p>NOTE: The vhd shows up in Volume 9 (LUN 15) but I can only bet that it will not work, plus I would not want to work with a vhd file which failed during the
creation process.</o:p>
<o:p>Long story short, I repeated the above steps to see if that was a temporary problem, but it is not. The same problem occurs no matter which Hyper-V cluster
node the operations are performed on. I would like to add, that I tested the creation of a vhd on an already configured LUN and the creation was completed successfully, and within a n expected time frame.</o:p>
NOTE: When LUN 15 errors out, it's status shows "Failed" in the Failover Cluster Manager. This in turn, causes the re-scanning of available disks to take forever (in Computer Management) and it keeps searching. Pretty
much, the fail of one LUN affects the entire functionality of the entire Hyper-V Cluster.
Errors Listed In Event Details For LUN 15:
1. Cluster Shared Volume 'Volume9' ('Cluster Disk 5') is no longer accessible from this cluster node because of error 'ERROR_TIMEOUT(1460)'. Please troubleshoot this node's connectivity to the storage device and
network connectivity.
Event ID: 5142; Source: Microsoft-Windows Failover Clustering;Task Category: Cluster Shared Volume
2. Cluster Shared Volume 'Volume9' ('Cluster Disk 5') is no longer available on this node because of 'STATUS_IO_TIMEOUT(c00000b5)'. All I/O will temporarily be queued until a path to the volume is reestablished.
Event ID: 5120; Source: Microsoft-Windows Failover Clustering;Task Category: Cluster Shared Volume
3.Cluster resource 'Cluster Disk 5' of type 'Physical Disk' in clustered role '4530acc9-8552-4696-b6c3-636ff8d58c46' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover
Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event ID: 1069; Source: Microsoft-Windows Failover Clustering;Task Category: Resource Control Manager
4.
Cluster resource 'Cluster Disk 5' (resource type 'Physical Disk', DLL 'clusres.dll') did not respond to a request in a timely fashion. Cluster health detection will attempt to automatically recover by terminating the Resource Hosting Subsystem (RHS)
process running this resource. This may affect other resources hosted in the same RHS process. The resources will then be restarted.
The suspect resource 'Cluster Disk 5' will be marked to run in an isolated RHS process to avoid impacting multiple resources in the event that this resource failure occurs again. Please ensure services, applications, or underlying infrastructure
(such as storage or networking) associated with the suspect resource is functioning properly.
Event ID: 1230; Source: Microsoft-Windows FailoverClustering;Task Category: Resource Control Manager
Any and all help will be appreciated!

Hi AquilaXXIII,
What server edition you are using? If you are using 2012r2 as cluster node, please install Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
update first,
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://social.technet.microsoft.com/Forums/en-US/f9c1a5f7-4fcf-409a-8d7e-388b85512bfe/new-lun-takes-a-long-time-to-format-and-errors-out?forum=winserv
Before you install the new shared storage please first validation this storage first, you can refer the following KB to validation the new LUN.
Understanding Cluster Validation Tests: Storage
http://technet.microsoft.com/en-us/library/cc771259.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

My Query takes too long ...

Hi ,
Env   , DB 10G , O/S Linux Redhat , My DB size is about 80G
My query takes too long , about 5 days to get results , can you please help to rewrite this query in a better way ,
declare
x number;
y date;
START_DATE DATE;
MDN VARCHAR2(12);
TOPUP VARCHAR2(50);
begin
for first_bundle in
select min(date_time_of_event) date_time_of_event ,account_identifier ,top_up_profile_name
from bundlepur
where account_profile='Basic'
AND account_identifier='665004664'
and in_service_result_indicator=0
and network_cause_result_indicator=0
and   DATE_TIME_OF_EVENT >= to_date('16/07/2013','dd/mm/yyyy')
group by account_identifier,top_up_profile_name
order by date_time_of_event
loop
select sum(units_per_tariff_rum2) ,max(date_time_of_event)
into x,y
from OLD_LTE_CDR
where account_identifier=(select first_bundle.account_identifier from dual)
and date_time_of_event >= (select first_bundle.date_time_of_event from dual)
and -- no more than a month
date_time_of_event < ( select add_months(first_bundle.date_time_of_event,1) from dual)
and -- finished his bundle then buy a new one
date_time_of_event < ( SELECT MIN(DATE_TIME_OF_EVENT)
                         FROM OLD_LTE_CDR
                         WHERE DATE_TIME_OF_EVENT > (select (first_bundle.date_time_of_event)+1/24 from dual)
                         AND IN_SERVICE_RESULT_INDICATOR=26);
select first_bundle.account_identifier ,first_bundle.top_up_profile_name
,FIRST_BUNDLE.date_time_of_event
INTO MDN,TOPUP,START_DATE
from dual;
insert into consumed1 VALUES(X,topup,MDN,START_DATE,Y);
end loop;
COMMIT;
end;

> where account_identifier=(select first_bundle.account_identifier from dual)
Why are you doing this? It's a completely unnecessary subquery.
Just do this:
where account_identifier = first_bundle.account_identifier
Same for all your other FROM DUAL subqueries. Get rid of them.
More importantly, don't use a cursor for loop. Just write one big INSERT statement that does what you want.

New Socket takes too long / how to stop a Thread ?

Similar Messages

Maybe you are looking for