This Is A Custom Widget

This Sliding Bar can be switched on or off in theme options, and can take any widget you throw at it or even fill it with your custom HTML Code. Its perfect for grabbing the attention of your viewers. Choose between 1, 2, 3 or 4 columns, set the background color, widget divider color, activate transparency, a top border or fully disable it on desktop and mobile.

This Is A Custom Widget

This Sliding Bar can be switched on or off in theme options, and can take any widget you throw at it or even fill it with your custom HTML Code. Its perfect for grabbing the attention of your viewers. Choose between 1, 2, 3 or 4 columns, set the background color, widget divider color, activate transparency, a top border or fully disable it on desktop and mobile.

Weblogic Realtime

/Tag:Weblogic Realtime

Server instance not coming up when trying to start from Admin Console

By | August 22nd, 2013|Realtime Issues, WebLogic Server|

Description: Server instance not coming up when trying to start from Weblogic Server Admin Console (i.e. through nodemanager) Solution: Logon to windows system Go to services (run > services.msc) Restart the nodemanager service (remember to make it manual from automatic in properties, otherwise windows team will get an alert) Try to start from WL Admin [...]

The persistent store suffered a fatal error and it must be re-opened

By | June 18th, 2013|Realtime Issues, WebLogic Server|

Error Message: Caused By: weblogic.messaging.kernel.KernelException: Error persisting message at weblogic.messaging.kernel.internal.SendRequest.failRequest(SendRequest.java:158) at weblogic.messaging.kernel.internal.SendRequest.onException(SendRequest.java:202) at weblogic.common.CompletionRequest.run(CompletionRequest.java:284) at weblogic.common.CompletionRequest.setResult(CompletionRequest.java:69) at weblogic.store.gxa.internal.GXALocalTransactionImpl$CommitCompletionListener.onException (GXALocalTransactionImpl.java:242) at weblogic.common.CompletionRequest.run(CompletionRequest.java:284) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) Caused By: weblogic.store.PersistentStoreFatalException: [Store:280032]The persistent store suffered a fatal error and it must be re-opened at weblogic.store.io.file.FileStoreIO.checkOpened(FileStoreIO.java:893) at weblogic.store.io.file.FileStoreIO.create(FileStoreIO.java:197) at weblogic.store.internal.CreateRequest.run(CreateRequest.java:40) at weblogic.store.internal.StoreRequest.doTheIO(StoreRequest.java:64) at weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:729) at java.lang.Thread.run(Thread.java:662) [...]

Encountered unrecognized patch ID: XXXX – While Applying Patch in Weblogic Using BSU Tool

By | May 11th, 2013|Realtime Issues, WebLogic Server|

Problem: E:UTILSMiddleware_10.3.5utilsbsu>bsu.cmd -prod_dir=E:/UTILS/Middleware_10.3.5/wlserver_10.3 -patchlist=L5TD -verbose -install -log=E:/UTILS/error.txt Encountered unrecognized patch ID: L5TD Solution: To fix this Rename the file patch-catalog_15563.xml as patch-catalog.xml in the cache_dir. It worked after that.    

Default web application is not loading when tested after upgrade to Weblogic 9.x

By | April 4th, 2013|Realtime Issues, WebLogic Server|

„Possible  Cause The default web application is not specified in the application descriptor file. „Solution In 9.0, BEA does not support the default webapp in the domain configuration. You must specify the default web application in the deployment descriptor, specifying the context root as “”.  In previous versions you could define the default web application [...]

Garbage Collection Tuning Tips

By | January 23rd, 2013|Performance Tuning, Realtime Issues, WebLogic Server|

The heap size influences the following: – The GC frequency and the pause during collections – The number of short and long term objects – Fragmentation and locality problems An undersized heap with the concurrent collector leads to full GCs with an increase in load and also fragmentation problems. An oversized heap leads to increased [...]

Analyzing Out of Memory Issues in Weblogic

By | January 23rd, 2013|Performance Tuning, Realtime Issues, WebLogic Server|

When the memory is insufficient for a deployed application, a java.lang.OutOfMemoryError is thrown. There will be different error messages for OutOfMemoryErrors in each type of memory. The Java Virtual Machine (JVM)has the following types of memory: Heap memory is the runtime data area from which memory for all class instances and arrays is allocated. When [...]

java.lang.OutOfMemoryError: GC overhead limit exceeded" exception with Sun JDK 1.6

By | April 27th, 2012|Realtime Issues, WebLogic Server|

Sep 30, 2010 4:13:27 PM CDT> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed  java.lang.OutOfMemoryError: GC overhead limit exceeded.  java.lang.OutOfMemoryError: GC overhead limit exceeded  at java.util.Arrays.copyOfRange(Arrays.java:3209)  at java.lang.String.<init>(String.java:216)  at java.lang.StringBuilder.toString(StringBuilder.java:430)  at weblogic.servlet.internal.ServletRequestImpl.toString(ServletRequestImpl.java:243)  at java.lang.String.valueOf(String.java:2827)  Truncated. see log file for complete stacktrace Cause The "java.lang.OutOfMemoryError: GC overhead limit exceeded" message means that for some reason the garbage collector is [...]

ORACLE JRockit and Stack Overflow – Troubleshooting

By | April 24th, 2012|Realtime Issues, WebLogic Server|

First of all, a StackOverflowError is an instance of a JVM Error, and from the very reference of the java.lang.StackOverflowError , a JVM might not be able to survive when this condition happens. You might thus discover the Stack Overflow condition in your production application from either repeating core dumping, and/or alert in your application [...]

Troubleshooting redeployment failure in Weblogic

By | April 19th, 2012|Deployments, Performance Tuning, Realtime Issues, WebLogic Server|

If you are doing a redeployment and see that the old application is the one that is still deployed, you need to verify the following: The staging mode used. The target servers use the available deployment files: local copies of the files, if the unit was deployed in stage mode, or the original deployment files for nostage mode. Verify [...]