HI All,
I am working on WAS 7 and i am using windows 7 operating system and IE9 so can anyone suggest me what kind of good PC configuration i needed because my PC is getting hanged when i started worked on this... so PC Configuration will be like RAM ? processor ? like that...
Look at this for the bare minimum requirements.
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27012421
Ensure that the memory is far higher than what is stated in this document. 1 GB is certainly not adequate.
It also depends on what you are running on this box (besides WebSphere App Server)
How many instances (or servers) of WAS are you running on it. Have about 1.5 GB (not referring to the JVM Heap here but the whole java process) per server instance as a ball park to have a reasonable performance.
HTH
Manglu
Related
I am developing a portal based on Liferay and I use Eclipse as IDE. I am running a 64 bit windows 7 with 8gb RAM ddr2 and AMD Athlon II X2 255 3.10 GHz. My computers freezes some time when I run service builder or when I want to open an xml file in eclipse. I checked the Process Manager from Task Manager and I have seen that I have two javaw processes running , jaxaw.exe*32 and javaw.exe.Is this normal. If this is a problem can you help me to fix it. Thanks
One process is for Eclipse itself and the other one is for your application. And no that is not a problem.
That's not problem. In most cases, this is caused by two different jvm processes, one for 32 bit jvm, another for 64bit. It's rarely to see that one process can cause this issue, in fact, I have never seen in my past 15 years java career.
I was working on a kind of SMTP kinda protocol, I made it in java and run successfully. It was consuming about 20 to 30 MB in my laptop. Later I decided to make the protocol live on internet. I purchased the servers(VPS), domain. It costed me a lot. But when I tried to run my program over that server I was so shocked that my program was consumption about 800 to 900 MB for each class I was running. I thought it may be my programming fault, I tried a lot to recover from problem but I could not. Later a friend of mine suggested me to test a simple Hello word program on same server, I was so shocked that even that program was eating up to 900 MB of my total RAM.
What kinda of problem can it be ?
Is it the fault in those servers, or their OS and kernels versions ?
Is it problem of JVM with Linux kernels or older linux kernels.
I have even tried with older JVMs but no use. :(
I tried most of popular flavors of Linux but it worked same and had exactly same problem on all Linux flavors. Was eating huge memory in all cases. ( All of them had Linux kernel 2.6.xx)
But it worked very smooth and consumed expected memory in my laptop. (about 30 to 50 Mb). I use Linux in my laptop. But the difference is that my kernel is above 3.1.xx . Can it be the problem ? I am really so disappointed with behavior of my servers and have lost lots of money in it. Please anybody tell me the possible solutions, can it be the problem of Linux kernel or its problem in my programming.
Is your laptop running Windows? I'll assume that the answer is yes. The memory values you see reported in Windows Task Manager are not what Linux reports for total resident memory.
I don't believe that Hello World is taking up 900 MB. If it is, that tells me that the JVM memory is being reported, not your app.
Are you running this app on a Java EE app server like Tomcat or JBOSS? That will make a very big difference indeed.
The best advice is to search SO for other questions that showed how to use Linux tools like nmap to figure out where memory is being consumed.
I have a standalone application that is running in IBM Websphere 7.0.0.19. It is running in Java 6 and we pack an Axis2 JAR in our EAR. We have 'parent last' style class loading and we have disabled the Axis service that is packed with WAS7 by default.
Recently, after 6+ weeks of continuous functioning, the application experienced an OOM. Perplexing point is, the application is deployed seperately on 2 different machines. But only one machine went down. Second machine is still up.
We checked OS, server configuration like classloader policy using WAS console and they are similar in both machines.
When the application crashed, it generated a .phd file which we analysed using Eclipse Memory Analyser Tool (MAT). The analysis is shown in the screenshot.
If I'm correct the bootstrap class loader is repeatedly loading and holding on to references of AxisConfiguraiton and so GC is unable to collect them when it runs. But, if that is the case, then both servers must have come down. But only one server experienced an OOM. Memory allocated to JVM is same in both machines.
We are not sure whether the issue is with WAS 7 or with axis2-kernel-1.4.1.jar or with something else.
http://www.slideshare.net/leefs/axis2-client-memory-leak
https://issues.apache.org/jira/browse/AXIS2-3870
http://java.dzone.com/articles/12-year-old-bug-jdk-still-out
(Links may not refer to the current issue. But they are just pointers)
Has anyone experienced something similar ?
We saw memory growth and sockets left open on WebSphere 6.1 with Axis 2 1.4 in the past. It's been a long time, but my notes suggest it might be worth considering an upgrade to at least Axis 2 1.5.1 to fix this bug with the open sockets and also to ensure you're not creating new objects repeatedly where a singleton exists (e.g. the Service object).
I've installed weblogic 10.3.3, configured simple domain with default configuration. And after starting weblogic I cannot use it via admin console because it is starting too slow (~10 mins). It seems that admin console application is being deployed incorrectly. Even when I enable 'staging' mode in AdminConsole deployment options, it does not help. Does anybody have a solution for this problem? It really bugs me out.
Configuration properties:
Server: Dell PowerEdge r410 server (Six-core Intel® Xeon® x64 CPU, 8GB RAM)
OS: Ubuntu Maverick 10.10 x86_64
Weblogic: 10.3.3 x64 (used wls1033_generic.jar file for installation)
Java: 1.6.0_17_i586 (tried with different jdk's including x64, but it does not work either)
Turns out weblogic uses random number generator during startup. Because of the bug in java it reads random bits from /dev/random. There are almost no problems with /dev/random except that it is extremely slow. It takes sometimes 10 minutes or more to generate one number. Simple solution exists – using /dev/urandom instead. It is not that good as /dev/random, but at least it is instant.
Java somehow maps /dev/urandom file to /dev/random. That’s why default settings in $JAVA_HOME/jre/lib/security/java.security are useless, they just do not make any sense.
Problem fix is very simple – adding string export JAVA_OPTIONS="-Djava.security.egd=file:/dev/./urandom" to the /etc/bash.bashrc file. Usage of /dev/./urandom instead of simple /dev/urandom is another hack. JVM does not understand the option value otherwise.
Be aware of this problem if you try to setup weblogic under UNIX-based OS.
Without looking at the startup logs we could only speculate. Weblogic typically is a beast. It typically takes anywhere fromo 6-8 minutes to start up for me on my development machines, but that seems like a nice server for it to take 10 minutes for you.
The Admin Console should not be this slow, nor should it take 6-8 minute to start a server or deploy the Admin Console. The deployment of the admin console on my machine takes less than 30 seconds, and startup is under 60 seconds. Startup time for WebLogic is a common complaint, but chances are that something is misconfigured if there is a very long startup or admin console deployment time.
Will a vps with 360 megs of ram running Linux be able to support a single user developing a java web application that uses Spring, Hibernate, and MySQL for the database? The server will be for development only so the application will not have more then one or two concurrent users.
edit:
By development I mean a server I can deploy and test on. The actual coding will be done on windows, but I want a Linux server to test on as well.
This could work ok, but it depends a lot on your application setup. If you cache a lot, your appserver caching page content, Hibernate caching query results/objects or MySQL caching query results you probably will need more RAM. So if your content is big it might not fit, otherwise it might just fit. If you have absulutely no option of increasing the amount of memory if you find out you need more I would certainly not recommend this setup.
But maybe more to the point: What is your target platform? I would say that your server should match that.
Just for linux testing it probably is easier to either get a cheap pc or run it inside a virtual machine on your development machine (assuming you've got plenty of ram on that one).
Depends on what you're running for your IDE. If you're using Eclipse, you're going to want somewhere around 1Gb of RAM (Eclipse is a memory hog...and slow as all hell if you don't have enough).
If you're using a more efficient (memory wise) IDE, then you should be good to go with that setup for development.
UPDATE
Since no coding is going to happen on the box...you should be just fine with that box to do your testing. Enjoy!
Short answer - I don't think you will have any problems with the amount of ram. I've deployed a rails app to a 256MB VPS and it worked great for development.