Archive for October, 2008

Number Format Exception while starting WebLogic Server

Friday, October 24th, 2008

Ok, this has occurred way too many times recently in our environment. This usually happens if your machine is running low on space and WebLogic Server corrupted a file in the embedded LDAP.
To fix this problem you can delete the file /servers//data/ldap/config/replicas.prop or add ‘replica.num=0′ to replicas.prop file.
> NumberFormatException: null
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:415)
at java.lang.Integer.parseInt(Integer.java:497)
at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1035)
at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:212)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>

usemon from google code, anyone?

Thursday, October 23rd, 2008

Today one of my colleagues mentioned about usemon, an open source java monitoring tool from google code. I have also seen news on theserverside about this tool. I have built something like this in my current job with similar concept, but not with all the bells and whistles that this tool comes with. I am going to check this out, but just wondering if anyone out there had any real time experience with it and if you do please drop me a line about your experience.

IDE for WLST

Wednesday, October 22nd, 2008

I have been asked this question many times and recently here, “What IDE should I use for writing WLST/Jython Scripts?” Initially I used PyWin, it was great! After I started using Eclipse as my Java IDE I moved to JyDT. JyDT has all the features I needed, integrates nicely with Eclipse, provides Syntax higlighting and much more. I recommend JyDT if you are just starting of with Jython.

JRockit – Error Message: Illegal memory access. [54]

Thursday, October 2nd, 2008

Recently we upgraded all our WebLogic domains to use JRockit from Sun JDK 1.4. After we restarted our servers we started seeing a JRockit dump in few of our servers. After some research and advice from Oracle Support team we were able to start our servers without the crash only if we add the JVM flag “-Xverify:all”. In case you run into this issue you can get over this by adding this flag. The crash dump looks as shown below:


===== BEGIN DUMP =============================================================
JRockit dump produced after 0 days, 00:02:32 on Wed Oct 1 09:25:47 2008

Additional information is available in:
/opt/satya/fooDomain/jrockit.30205.dump
/opt/satya/fooDomain/core or core.30205
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at
http://forums.bea.com in
the forum jrockit.developer.interest.general.

Error Message: Illegal memory access. [54]
Signal info : si_signo=11, si_code=2 si_addr=(nil)
Version : BEA JRockit(R) R27.2.0-131-78843-1.4.2_13-20070320-1511-linux-ia32
GC Mode : Garbage collection optimized for throughput
GC Strategy : Generational Parallel Mark & Sweep
: Current OC phase is: not running. YC is not running.
: GC strategy for GC 7 was genparpar
: GC strategy for GC 8 was genparpar
: GC strategy for GC 9 was singleparpar
: GC strategy for GC 10 was genparpar
: GC strategy for GC 11 was singleparpar