Java Heap Monitor in JDeveloper

Tested with JDeveloper Version 11.1.1.5, 11.1.2.1

Short post, but hopefully a useful productivity tip. Recently I thought if there isn't such a feature as I was used from some other IDEs

Monitoring of the java heap size + the ability to force garbage collection.

Finally I found it as you can see from the screen shot above which shows my right bottom of JDeveloper Statusbar.

So how to activate this one? Well it is quite easy. Locate $MW_HOME/jdeveloper/jdev/bin/jdev.conf and add the following line at the bottom

AddVMOption -DMainWindow.MemoryMonitorOn=true

Restart JDeveloper and you should be able to see the java heap size monitor. Clicking on the recycle bin will force garbage collection.

After garbage collection (in my just started jdeveloper) the used memory dropped from 200M to 105M

Conclusion
That might save you from restarting Jdeveloper to often a day;)

Further Reading
http://docs.oracle.com/cd/E25178_01/fusionapps.1111/e15524/gs_install_e.htm#CDEFEDGC

Monitoring Dashboard in WLS Administration Console introduced

Type: Info
Applies to: Oracle WebLogic Server: 10.3.3

Just after JDeveloper 11.1.1.3 was released of course I had to give it a try;-) Somehow I am always curious about changes the Admin Console of the WLS. Since WLS is integrated it is really easy and quick to do. Just start a simple ADF Fusion Web app and open http://localhost:7101/console

The following things catched my eyes:

a) The Admin Console  is internationalized. On my laptop the login form appears in german by default now:
 
To change the language you just have to change the preferred language in the browser settings and reload the page.

b) On the Homepage I recognized a new entry:
 
This opens the so called “Monitoring Dashboard” which obviously is developed by ADF Faces RC. Cool! No activation of the diagnostic console needed! No slowly loading Applet;) Thanks!

c) the diagnostic-console can still be activated in the preferences but just in order to inform that it has been replaced by the new monitoring dashboard….and the Request Performance

d) Request performance
At the first look the view is a bit disappointing because you will not see anything here until you “…first configure WLDF instrumentation to use the ElapsedTimeAction diagnostic action attached to "Around" diagnostic monitors. Only data from the ElapsedTimeAction action is shown on this page.” See the context help for more information. (Maybe I will blog about it in more detail in a separate post)

It would be nice if this information (to first configure a WLDF inst) would be visible as INFO or WARNING directly on the Request Performance Tab.

WLS: Monitoring Oracle JRockit JVM with JRockit Mission Control remotely

Status: resolved
JRockit Mission Control: 3.1.2
WebLogic: 10.3.2

Use case

You have the need to remotely monitor and profile the JRockit JVM(s) of Oracle WebLogic Server.

Solution

1. Install JRockit Mission Control on the client
2. Configure WebLogic Server Domain with JRockit JVM
3. Configure JRockit Management Server

Components/Products

	Product	Download
	Oracle® WebLogic Server	Download from OTN
	Oracle® JRockit Mission Control	Download from OTN

How to

Bereich	Beschreibung
Putty	Login as oracle on telde.local [oracle@telde ~]$ cd middleware/user_projects/domains/base_domain/ [oracle@telde base_domain]$ vi startWebLogic.sh
Putty/vi	Add the following java Options before starting the WLS instance: JAVA_OPTIONS="-Xmanagement:ssl=false,authenticate=false,port=7091" export JAVA_OPTIONS ${DOMAIN_HOME}/bin/startWebLogic.sh $* Save file and Close vi.
Putty	Start WLS [oracle@telde base_domain]$ ./startWebLogic.sh …. Notice the starting of the management server … [JRockit] Management server started on port 7091, ssl=false, authenticate=false. …
Client	Start JRockit Mission Control
JRMC	Create a new connection Enter Host Enter Port Click: Test connection => Status keeps “Unable to connect” Click: Finish Starting the console on the newly created connection you might receive the following exception: Could not open Management Console for telde.local.   com.jrockit.mc.rjmx.ConnectionException: Connection refused to host: 127.0.0.1; nested exception is:     java.net.ConnectException: Connection refused: connect     com.jrockit.mc.rjmx.ConnectionException: Connection refused to host: 127.0.0.1; nested exception is:         java.net.ConnectException: Connection refused: connect         at com.jrockit.mc.rjmx.ConnectionManager.connect(ConnectionManager.java:63)         at com.jrockit.mc.console.ui.actions.StartConsole$1.preConnect… So how to fix?
Putty	Stop WLS
	Edit startWebLogic.sh Add -Djava.rmi.server.hostname=<remotehost> to the java options so that it looks like
Putty/vi	.. JAVA_OPTIONS="-Djava.rmi.server.hostname=telde.local -Xmanagement:ssl=false,authenticate=false,port=7091" export JAVA_OPTIONS ${DOMAIN_HOME}/bin/startWebLogic.sh $* Save file and exit vi.
Putty	Start WLS once again [oracle@telde base_domain]$ ./startWebLogic.sh
JRMC	Now try to test connection again. Result should be
JRMC	Start the console and monitor CPU, Mem, seak for memory leaks, etc.

Resources

java.rmi.server.hostname (1.1 and later)

The value of this property represents the host name string that should be associated with remote stubs for locally created remote objects, in order to allow clients to invoke methods on the remote object. In 1.1.7 and later, the default value of this property is the IP address of the local host, in "dotted-quad" format.