Archive for the ‘weblogic server’ Category

No WLST cachedir with python.cachedir.skip

Friday, September 11th, 2009

In one of my previous post I have talked about python.cachedir and how it may cause some errors during WLST/Jython initialization.
With WebLogic 11g Oracle has upgraded the Jython Version from 2.1 to 2.2 (see my post here), which opens up yet another way of getting rid of these errors. In fact you can get rid of the cachedir entirely by starting WLST with -Dpython.cachedir.skip=true, this will instruct Jython not to create the CacheDir.
I haven’t done extensive testing with this option but so far I haven’t seen any issues by not creating this cachedir.

Monitoring your WebLogic SSL Certificates is important

Wednesday, August 19th, 2009

I was talking to my friend yesterday and he mentioned that he was up all night due to an outage that happened to the WebLogic environments he manages, when asked why?

Expired SSL Certificates!!! (more…)

My takeaways from Oracle Fusion Middleware 11g Forum

Wednesday, July 29th, 2009

I attended the Oracle Fusion Middleware 11g Forum in Bridgewater, NJ. It was a pretty informational session and I got to talk directly to Oracle management about some questions I had regarding Oracle’s Portal and JVM Strategies. (more…)

Can WebLogic 10.3 run on JDK 1.4?

Wednesday, July 29th, 2009

One of my colleague asked me whether he can upgrade to WebLogic 10.3 from WebLogic 8.1 and not upgrade his JDK to 1.6. (more…)

Default protocol in WebLogic and why is it important

Sunday, July 26th, 2009

If your WebLogic Server makes outbound connections to other systems it is wise to know what a DefaultProtocol is. Generally, when you create a WebLogic domain and haven’t configured SSL you will not have to do anything. (more…)

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)
>