Weblogic7.0 starting is taking tomuch of time

i am using windows 2000 server, if i start weblogic 7.0, it is taking almost 10
minutes to start.
i have almost 200 enteprise deploy, i had made single ear to deploy.
if anybody is haveing workaround , please help me out.....

Similar Messages

Java Web Start is taking too long time to fill the bar

Hi All,
I am using Eclipse and using JBOSS from Remote and when I am deploying an applent with Java Web Start, it is taking a very long time for filling the bar(taking more time for verifying and downloading Application).
Can anyone help me for fixing it.
Thanks in Advance.

795697 wrote:
Hi,
when I am deploying an Applet with the help of Java Web Start It is taking too much time for verifying and downloading the application.
I am using Eclipse and JBOSS.
This is the problem.
I think you can understand it.I can't. I don't understand what Eclipse and JBoss have to do with webstart and I can't understand what webstart has to do with deploying an applet.
Its all just completely unrelated! I'm just going to make a dumb assumption and say that it is your computer.

PXI 4472 DAQmx Start VI taking a long time.

I have an issue with DAQmx Start taking up to a secoond to to execute and it's killing my cycle time.
I have a PXI 8360 with 3 PXI 4462's and 3 PXI 4472's. I configure DAQ Task and Commit at the begining of the sequence however every time i do a DAQmx Start it takes about a second to execute. I need to do about 5 in each Test sequence so it's eating up about 5 seconds of cycle time. I am using DAQmx 9.7.5 drivers and Labview 2013. We have the exact same hardware and software setup in another location but we are not seeing this issue there.
Any ideas what might be causing this would be appreciated.
Attachments:
DAMmx Start.png ‏4 KB

Hi Nathan,
I verified this by disabling the Start Task VI.
I've attached the commit code.
Thanks
Attachments:
PXI 4472 Acquire.png ‏8 KB
PXI 4472 and 4462 Commit.png ‏13 KB

How do I stop touchsmart from loading on start up, taking too much time

pc taking too long to boot, touchsmart loading on every boot up, taking way too much time

richardfit wrote:
pc taking too long to boot, touchsmart loading on every boot up, taking way too much time
disable inside application, use msconfig, uninstall other applications, etc.... (as I try to replicate your grammar and style)

After upgrading to lion starting up is taking much more time ??

After upgrading to lion starting up is taking much more time is there any solution to this ?
i do all things about cleaning disk permission or editing .

Have you check what is being started at the same time?
Lion will start more applications then were being started in the past.
Allan

I,tried,using,a,trial,version,of,creative,cloud.,I,signed,up,and,started,the,download.,The ,download,was,taking,a,long,time,so,I,decided,to,cancel,it,and,buy,a,year,plan,paying,mont hly.,I,started,downloading,creative,cloud,again,but,the,download,was,inte

I,tried,using,a,trial,version,of,creative,cloud.,I,signed,up,and,started,the,download.,The ,download,was,taking,a,long,time,so,I,decided,to,cancel,it,and,buy,a,year,plan,paying,mont hly.,I,started,downloading,creative,cloud,again,but,the,download,was,interrupted,by,my,dau ghter,by,inserting,a,usb,device,into,the,usb,port.,I,could,not,find,the,download,,I,signed ,into,adobe,and,now,it,tells,me,that,i,have,a,30,day,trial.,My,account,shows,that,I,have,p aid,my,first,monthly,installment,but,i,can,only,use,a,trial,version,,which,says,will,expir e,in,30,days.,What,can,I,do,to,get,the,full,yearly,plan,version???

Jacobm51486856 please see Sign in, activation, or connection errors | CS5.5 and later for information on how to resolve the connection error preventing your membership from being authorized.

My imac just started taking a long time to turn on. First I have a grat screen, than a gray world globe , a blue screen and finally my desktop. A total of 4 minutes. What is wrong and what do I do?

My IMac , just started, taking a long time to get to the desktop. First I have a gray screen, than a gray screen with a gray globe, a blue screen and finally my desktop. Takes about 4 minutes. What is wrong and what do I do?

Once the desktop is up and the iMac ready to use, open Systeem Preferences (Apple menu) and click the Startup Disk item. In the new screen, make sure that OS X on your hard drive is selected in the top row - click it once to make sure. Then test.

SAP GUI taking too much time to open transactions

Hi guys,
i have done system copy from Production to Quality server completely.
after that i started SAP on Quality server, it is taking too much time for opening SAP transactions (it is going in compilation mode).
i started SGEN, but it is giving time_out errors. please help me on this issue.
MY hardware details on quality server
operating system : SuSE Linux 10 SP2
Database : 10.2.0.2
SAP : ECC 6.0 SR2
RAM size : 8 GB
Hard disk space : 500 GB
swap space : 16 GB.
regards
Ramesh

Hi,
>i started SGEN, but it is giving time_out errors. please help me on this issue.
You are supposed to run SGEN as a batch job and so, it should be possible to get time out errors.
I've seen Full SGEN lasting from 3 hours on high end systems up to 8 full days on PC hardware...
Regards,
Olivier

Taking too much time in Rules(DTP Schedule run)

Hi,
I am Scheduling the DTP which have filters to minimize the load data.
when i run the DTP it is taking too much time in the "rules" (i can see the DTP monitor ststus package by pakage and step by step like "Start routine" "rules" and "End Routine")
here it is consuming too much time in Rules Mapping.
what is the problem and any solutions please...
regards,
sree

Hi,
Time taken at "rules" depends on the complexity involved there in ur routine. If it is a complex calculation it will take time.
Also check ur DTP batch settings, ie how many no. of background processes used to perform DTP, Job class.
U can find these :
goto DTP, select goto menu and select "Settings for Batch Manager".
In the screen increase no of Processes from 3 to higher no(max 9).
ChaNGE job class to 'A'.
If ur DTP is still running , cancel it ie Kill the DTP, delete from the Cube,
Change these settings and run ur DTP one more time.
U can observer the difference.
Reddy

Taking too much time using BufferedWriter to write to a file

Hi,
I'm using the method extractItems() which is given below to write data to a file. This method is taking too much time to execute when the number of records in the enumeration is 10000 and above. To be precise it takes around 70 minutes. The writing pauses intermittently for 20 seconds after writing a few lines and sometimes for much more. Has somebody faced this problem before and if so what could be the problem. This is a very high priority work and it would be really helpful if someone could give me some info on this.
Thanks in advance.
public String extractItems() throws InternalServerException{
try{
               String extractFileName = getExtractFileName();
               FileWriter fileWriter = new FileWriter(extractFileName);
               BufferedWriter bufferWrt = new BufferedWriter(fileWriter);
               CXBusinessClassIfc editClass = new ExploreClassImpl(className, mdlMgr );
System.out.println("Before -1");
               CXPropertyInfoIfc[] propInfo = editClass.getClassPropertyInfo(configName);
System.out.println("After -1");
          PrintWriter out = new PrintWriter(bufferWrt);
System.out.println("Before -2");
          TemplateHeaderInfo.printHeaderInfo(propInfo, out, mdlMgr);
System.out.println("After -2");
XDItemSet itemSet = getItemsForObjectIds(catalogEditDO.getSelectedItems());
Enumeration allitems = itemSet.allItems();
System.out.println("the batch size : " +itemSet.getBatchSize());
XDForm frm = itemSet.getXDForm();
XDFormProperty[] props = frm.getXDFormProperties();
System.out.println("Before -3");
bufferWrt.newLine();
long startTime ,startTime1 ,startTime2 ,startTime3;
startTime = System.currentTimeMillis();
System.out.println("time here is--before-while : " +startTime);
while(allitems.hasMoreElements()){
String aRow = "";
XDItem item = (XDItem)allitems.nextElement();
for(int i =0 ; i < props.length; i++){
     String value = item.getStringValue(props);
     if(value == null || value.equalsIgnoreCase("null"))
          value = "";
                         if(i == 0)
                              aRow = value;
                         else
                              aRow += ("\t" + value);
startTime1 = System.currentTimeMillis();
System.out.println("time here is--before-writing to buffer --new: " +startTime1);
bufferWrt.write(aRow.toCharArray());
bufferWrt.flush();//added by rosmon to check extra time taken for extraction//
bufferWrt.newLine();
startTime2 = System.currentTimeMillis();
System.out.println("time here is--after-writing to buffer : " +startTime2);
startTime3 = System.currentTimeMillis();
System.out.println("time here is--after-while : " +startTime3);
               out.close();//added by rosmon to check extra time taken for extraction//
bufferWrt.close();
fileWriter.close();
System.out.println("After -3");
return extractFileName;
catch(Exception e){
               e.printStackTrace();
throw new InternalServerException(e.getMessage());

Hi fiontan,
Thanks a lot for the response!!!
Yeah!! I kow it's a lotta code, but i thought it'd be more informative if the whole function was quoted.
I'm in fact using the PrintWriter to wrap the BufferedWriter but am not using the print() method.
Does it save any time by using the print() method??
The place where the delay is occurring is the wile loop shown below:
            while(allitems.hasMoreElements()){
            String aRow = "";
                XDItem item = (XDItem)allitems.nextElement();
                for(int i =0 ; i < props.length; i++){
                     String value = item.getStringValue(props);
     if(value == null || value.equalsIgnoreCase("null"))
          value = "";
                         if(i == 0)
                              aRow = value;
                         else
                              aRow += ("\t" + value);
startTime1 = System.currentTimeMillis();
System.out.println("time here is--before-writing to buffer --out.flush() done: " +startTime1);
bufferWrt.write(aRow.toCharArray());
out.flush();//added by rosmon to check extra time taken for extraction//
bufferWrt.flush();//added by rosmon to check extra time taken for extraction//
bufferWrt.newLine();
startTime2 = System.currentTimeMillis();
System.out.println("time here is--after-writing to buffer : " +startTime2);
What exactly happens is that after a few loops it just seems to sleep for around 20 seconds and then again starts off and ............it goes on till the records are done.
Please do lemme know if you have any idea as to why this is happening !!!!! This bug is giving me the scare.
thanks in advance

I having issue with my Iphone 4 while playing music its taking too much time to play

I am using Iphone which is taking too much time to play music & some time its shows one album cover and playing others song please help and let me know whats the issue

Hello Sanjay,
I would recommend steps 1, 3, and 5 from our iPhone Troubleshooting Assistant found here: http://www.apple.com/support/iphone/assistant/phone/#section_1
Here is step 1 to get you started.
Restart iPhone
To restart iPhone, first turn iPhone off by pressing and holding the Sleep/Wake button until a red slider appears. Slide your finger across the slider and iPhone will turn off after a few moments.
Next, turn iPhone on by pressing and holding the Sleep/Wake button until the Apple logo appears.
Is iPhone not responding? To reset iPhone, press and hold the Sleep/Wake button and the Home button at the same time for at least 10 seconds, until the Apple logo appears.
If your device does not turn on or displays a red battery icon, try recharging next.
Take care,
Sterling

Why it is taking too much time to kill the process?

Hi All,
Today,one of my user ran the calc script and the process is taking too much time, then i kill the process. I am wondering about one thing here even it is taking too long to kill the process, generally it will not take more than 2 sec. I did this through EAS.
After that I ran Maxl statement
alter system kill request 552599515;
there is no use at all.
Please reply if you have any solutions to kill this process.
Thanks in advance.
Ram.

Hi Ram,
1. Firstly, How much time does your calculation scripts normally run.
2. While it was running, you can go to the logs and monitor where exactly the script is taking time .
3. Sometimes, it does take time to cancel a transaction ( as it might be in between).
4. Maxl is always good to kill ,as you did . It should be succesful . Check the logs what it says ,and also the "sessions" which might say "terminating" and finish it off.
5. If nothing works ,and in the worst case scenarion , if its taking time without doing anything. Then log off all the users and stop the databas and start it .
6. Do log off all the users, so that you dont corrupt any filter related sec file.
Be very careful , if its production ( and I assume you have latest backups)
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

Full DTP taking too much time to load

Hi All ,
I am facing an issue where a DTP is taking too much time to load data from DSO to Cube via PC and also while manually running it.
There are 6 such similar DTP's which load data for different countries(different DSO's and Cubes as source and target respectively) for last 7 days based on GI Date. All the DTP's are pulling almost same no. of records and finish within 25-30 min. But only one DTP takes around 3 hours. The problem started couple of days back.
I have change the Parallel processes from 3->4->5 and packet size from 50,000->10,000->1.00.000 but no improvement. Also want to mention that all the source DSO's and target Cubes have the same structure. All the transformations have Field Routines and End Routines.
Can you all please share some pointers which can help.
Thanks
Prateek

HI Raman ,
This is what I get when I check the report. Can this be causing issues as 2 rows have % >= 100
ETVC0006           /BIC/DETVC00069     rows:      1.484    ratio:          0 %
ETVC0006           /BIC/DETVC0006C     rows: 15.059.600    ratio:        103 %
ETVC0006           /BIC/DETVC0006D     rows:        242    ratio:          0 %
ETVC0006           /BIC/DETVC0006P     rows:         66    ratio:          0 %
ETVC0006           /BIC/DETVC0006T     rows:        156    ratio:          0 %
ETVC0006           /BIC/DETVC0006U     rows:          2    ratio:          0 %
ETVC0006           /BIC/EETVC0006      rows: 14.680.700    ratio:        100 %
ETVC0006           /BIC/FETVC0006      rows:          0    ratio:          0 %
ETVC0007           rows: 13.939.200    density:              0,0 %

Discoverer reports taking a long time!!!

Hi all,
One of our clients is complaining that the discoverer reports are taking a long time to run for the last few days, the report used to take 30 minutes before but now is running for hours!!
I have checked the SGA and I have killed the idle sessions but still there was no improvement in the performance.
The version of BI discoverer is 10 and database also is 10g and the platform is win server 2003.
I have checked the forums and they talk about explain plan and tkprof and other commands, but my problem is that i am unable to find the query that discoverer is running i mean once the report is clicked the query runs and gives the estimate time it would take. can some one tell me where this query is stored so that i can check this query,
Also there were no changes made in the query or to the database.
The temp space fills up 100%, i increased the size of temp space but still it goes to 100% also i noticed that the CPU utilisation goes to 100%
i also increased the SGA but still no go.
can someone kindly help me as to what could be causing this problem
also kindly guide me to some good documents for tuning the discoverer.
thanks in advance,
regards,
Edited by: user10243788 on Jan 4, 2010 12:47 AM

Hi,
The fact that the report used to work fast and now not can be related to many things but my guess is that the database statistics were changed and so the explain plan has changed.
This can be done due to change in the volume of the data that crossed a level were oracle optimizer change the behavior but it can be other things as well.
Anyway it is not relevant since it will be easier to tune the SQL than to find what have changed.
In order to find whether the problem is with the discoverer or in the SQL extract the SQL as described above and run it in SQL tool (SQL Plus, TOAD, SQL Developer and so on).
The best way to get to the problem is run a trace on your session and then use the TKPROF command to translate it to a text file you can analyze - you can assist your DBA team they should have no problem doing that.
By doing that you will get the problematic statements/ functions/ procedures that the report uses.
From there you can start working on improving the performance.
Performance is expertise for itself so i'm sorry i don't know to tell you where to start from, I guess the start will be from understanding the meaning of the explain plan.
Hope I helped a little although I wish Ii had a magic answer for you
BTW, until you resolve that problem you can use the discoverer scheduler to run the reports in the background and so the users will get the data.
Tamir

Time Machine Taking a Long Time to Index / Back Up

Hi everyone.
I noticed this on the latest backup to my Time Capsule device. I'm backing up over a WiFi connection to a time capsule device. It is taking a long time to index the backup. Here's the code from the latest backup.
10/17/12 9:43:03.799 PM com.apple.backupd: Starting standard backup
10/17/12 9:43:04.091 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
10/17/12 9:43:12.657 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
10/17/12 9:43:34.015 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
10/17/12 9:43:37.440 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
10/17/12 9:43:37.459 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
10/17/12 9:45:23.296 PM com.apple.backupd: 500.1 MB required (including padding), 3.27 GB available
10/17/12 9:46:48.844 PM com.apple.backupd: Copied 1436 files (3.4 MB) from volume Macintosh HD.
10/17/12 9:46:51.897 PM com.apple.backupd: 448.1 MB required (including padding), 3.27 GB available
10/17/12 9:46:51.898 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:47:53.681 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:48:55.642 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:49:56.511 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:50:56.564 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:51:57.643 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:52:57.903 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:53:59.341 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:55:01.281 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:56:03.171 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:57:03.966 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:58:33.083 PM com.apple.backupd: Copied 824 files (1.2 MB) from volume Macintosh HD.
10/17/12 9:58:40.359 PM com.apple.backupd: Starting post-backup thinning
10/17/12 9:59:51.851 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-213620 (5.6 MB)
10/17/12 10:00:17.440 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-113505 (1.6 MB)
10/17/12 10:00:30.046 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-103509 (1.6 MB)
10/17/12 10:00:43.781 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-093513 (1.3 MB)
10/17/12 10:00:43.781 PM com.apple.backupd: Post-back up thinning complete: 4 expired backups removed
10/17/12 10:00:45.207 PM com.apple.backupd: Backup completed successfully.
10/17/12 10:00:56.988 PM com.apple.backupd: Ejected Time Machine disk image.
10/17/12 10:00:57.550 PM com.apple.backupd: Ejected Time Machine network volume.
I am just curious as to why this is, and what I might do to fix it. I did see one suggestion in another website suggesting diabling spolight indexing of the backup image with sudo mdutil -i off /Volumes/Time Machine Backups, but don't know where to type that in. It then states to reenable it, but don't know where to type that in, either. Any advice would be helpful. I did run a verification not too long ago, and here's that code.
10/14/12 3:44:14.289 PM com.apple.backupd: Backup verification requested by user.
10/14/12 3:44:41.503 PM com.apple.backupd: Running backup verification
10/14/12 4:04:31.602 PM com.apple.backupd: Backup verification passed!
If any of you have or had a similar problem, I'd appreciate your help. For the time being, I may just disable time machine during the evening, and only have it run during the day when I'm at work.

Is your sig still current (10.7.3)? Or did you update to 10.7.5? Because 10.7.5 had a Spotlight/Time Machine bug that slowed down a lot of backups. If that's what it is, there's now a 10.7.5 Supplemental Update that fixes the slow Time Machine problem.
If it isn't 10.7.5, I don't know what the problem might be.

Weblogic7.0 starting is taking tomuch of time

Similar Messages

Maybe you are looking for