BEA has addressed this problem. Two solutions are available:
- A patch for existing WebLogic 10 installations, and
- Updated installers
The patch is available from the BEA Patch Repository; the Patch ID is 2VJT.
Until a solution is applied, the implications of this problem are as follows:
- If you attempt to boot a WebLogic Server 10 or WebLogic Portal 10 server prior to May 14, you will receive a warning that "sales@bea.com for information on extending your license.>".
- If you attempt to boot a WebLogic Server 10 or WebLogic Portal 10 server on May 14 or afterwards, the server will not boot.
- If you have booted a WebLogic Server 10 or WebLogic Portal 10 server prior to May 14, it will continue to run past May 14. However after May 14, attempts to make policy changes in the console will fail, and the server cannot be rebooted after May 14.
Please monitor http://support.bea.com for updates on this problem.
Hi,
ReplyDeleteI am trying to get information about Weblogic 10.0.
So far, we have had a very hard time trying to migrate from Weblogic 8.1 to Weblogic 10.0.
Do you know of anybody with experience on doing this migration? What type of problems did they found and how they got resolved?
We keep having OutOfMemory Exceptions when compiling EJBs...and servers not even start. We migrated from 8.1 all applications using Weblogic's domain upgrade utility. The configuration is preserved, and the applications are deployed, but when it tries to start, it is not able to do it. If it starts then it keeps finding OutOfMemory exceptions.
I am told from BEA support that this is caused by SUN JDK bug with zip files... What are my options?
Hi Anonymous, I created an article on my blog that partially answer your question.
ReplyDeleteNeed some more info to be able to help you more.
You might send a personal message to mail email (at) gmail.com or at gtalk, the username is the same as my subdomain at blogspot.com.
http://dbaktiar.blogspot.com/2008/09/somebody-posted-question-on-old-entry.html