Weblogic slow server startup and publishing - weblogic12c

I am using Weblogic 12.2.1.3 on Windows 10 to deploy a web application (war) of size ~200 mb.
I have around 3 GB allocated to Weblogic server in setDomainEnv.cmd. The problem is server startup and application deploy takes more than 30 minutes.
How can I speed up abd reduce the time?
I have tried setting different random generator in java.security file but it didn't help.
I have also try disabling xml validation but it didnt help either.
Any pointers on troubleshooting slow start up times?
Thanks

Related

JBoss 7 troubleshooting slowness

We have an application on JBoss 7.1.0 istance, usually running ok but sometime the performance degrading, in this case a restart of JBoss is useful.
I have configured an access.log to record the timing of the pages and when the performance are degrading, we have an increase in recorded time on it for some pages.
How can I better identify and troubleshoot the problem? I think can be a problem related to objects in memory of JBoss server.
I exclude can be a memory issue on client because the access.log record the slow time, is it right or can I be misinterpreting the access.log and the problem can be also on client?
The ram / cpu on server are not under load when there are slowness and the xmx is oversized.
The JBoss is on Windows with JDK 1.7.0_80.
Thanks
UPDATE: Our degrading performance problem was related to an APM configured to record too much data and solved by removing it (are needed to be better configured).
I don't think JBOSS server has a problem. By reading your statement, I think the your code is leaking connections. Login into JBOSS Console and see the stats of your connection pools (you need to enable stats if not enabled already). If the connection count grows linearly and never comes down then you need to fix the leakage at code level. You can also use JConsole to monitor JVM memory and detect problems.

Connection times using Java Mission Control and Wildfly 8.2

I'm starting to move from visualvm to java mission control. I use wildfly 8.2, which doesn't work with JMC out of the box, but have modified the JMC ini to include the required class path as per my answer in the jboss community https://developer.jboss.org/message/955742#955742
I've been able to connect successfully, however the time it takes to connect is ridiculous. Often waiting 1-10 minutes (during which time jmc often becomes unresponsive) when connecting to a local wildfly instance, it's almost instant, the delay happens only when connecting to a remote instance.
Does anyone know what would cause this to be so slow, and if anything can be done to sort it?

Jboss taking long time to start

I am using jboss-4.0.5.GA for project deployment, but it is hanging at startup by displaying message
Trying to install an already registered mbean: jboss.management.local
it is showing this for 6 minutes and it takes total 7-8 minutes to start.
If I start server without deploying application, then also it's taking 7 to 8 min.
You seem to have corrupted the JBoss installation, highly reccomended to use a fresh installation and deploy your application rather than debug this.
I use Jboss 4.2.2 which is taken from a zipped folder. Today I have renamed the existing setup and tried unzipping again and use a fresh copy. This didn't work out as expected and server is in starting mode for several minutes and thrown error in the end. So removed this fresh setup and used the old one and it worked like a gem, though not sure where is the problem here.

IBM RAD 7.5 ... why does it take WebSphere so long to start / publish / republish / debug?

I'm developing an EAR/WAR application with IBM RAD 7.5 and WebSphere 7.
When I run my app on WebSphere 7 within "eclispe", it take forever for WebSphere to start in "Run" mode (2 or 3 minutes). Much longer to start in "Debug" mode (5 to 10 minutes).
I have 'publish automatically' turned off, so I republish manually, and that too take a long long time.
Am I doing something wrong, or is there anyway to speed thing up?
Thanks,
Rob
Try setting metadata-complete="true" in your web.xml I experienced significant improvements doing this.
I wonder if you're hitting memory limits on your system and perhaps doing a lot of swapping. My WebSphere 6.1 under RAD 8 seems to start in an amount of time consistent with WebSphere by itself.
I would suggest you check the Heap for the test environment.
Personally build automatically and auto-publish should be turned off, You run the publish as and when you need it.
This one is still a good reference
http://www.ibm.com/developerworks/wikis/download/attachments/113606723/radtipsv754.pdf?version=1
Sometimes when it takes 5-10 to publish in debug mode, i either revert to export and install via the admin console or use wsadmin scripts to install the application.
Also turn on the heap config for RAD (one of the preference allows you to show this). You might be able to make some inferences if RAD is hitting into memory issues.
HTH
Manglu

How to Speed Up IBM Rational Application Developer/Rational Software Architect

I want to know how can I speed up RSA 7.5( which is an IDE by IBM having eclipse under the hood with websphere server runtimes) mainly server start. The first time I start it after computer reboot it loads after, but after that it takes for ever to start/stop the server. The debug mode for server takes for ever to start.
I am using server 7 run time for IBM RSA 7.5.
So bascially RAD/RSA has websphere run times which allows to configure the server runtime start/stop within RAD/RSA. The run time allows you to develop webapps and test time on the server on deploy it on the websphere run time.
The problem I am facing is with the websphere runtime which works fine after computer reboot but is very slow after several deployments/publishing of the same web app.
I would be grateful you give performance tips for speed up RSA server start/shutdown and overall performance tips. I have plenty of memory like 12 GB with i7 Core 6 cores on Win7.
Of course of your are running the server in debug mode it's going to be a lot slower, but you have a few options like putting the server in development mode or doing some fine tuning as to which applications should start. Take a look at these articles:
Rational Application Developer Performance Tips- Case study: Tuning WebSphere Application Server V7 and V8 for performance
Performance tuning WebSphere Application Server 7 on AIX 6.1
WebSphere tuning for the impatient: How to get 80% of the performance improvement with 20% of the effort
WebSphere Performance Monitoring & Tuning
Some of these are a bit dated but they have some good information that may still be relevent to your issues; especially the first one.
Make sure that the workspaces are stored on a local disk.
edit - forgot this: buy a SSD disk. It makes a huge difference when developing.
If you have a virus scanner, disable on-access scan in the SDP installation directory including the server plugin, and in all your workspaces.
Uninstall any applications (ears) you are not using - the more you have installed the longer the server takes to startup. If your server is taking too long to start, RAD/RSA will assume it has timed out and stop it before it finishes starting - if this happens then increase the start timeout limit by double-clicking your server in the Servers tab and modifying the values in the Timeouts section.
Oh, and If you have a lot of datasources defined, and autostarting connection pools with alot of connections, it may also take a while to start the pools.
But that can't explain it all... I haven't tested, but since WAS and RSA seems to spend a lot of time doing absolutely nothing, I am starting to suspect it's trying to download schemas or something. If you have the time, you could try to trace and see if you find something like that...
I came across this post while trying to troubleshoot my RSA performance. I figured I would update it with a recommendation for improving performance on RSA 8.0.4.
http://publib.boulder.ibm.com/infocenter/radhelp/v8/index.jsp?topic=/com.ibm.performance.doc/topics/cperformance.html has some excellent tips on improving performance in the "Performance Tips" section. After implementing just some of the "Always" tips I've found my memory reducing significantly and performance being much faster.
You should start with the "Always" tips and then move to the "Sometimes" and "Rarely" ones for finer tuning.