Debugging WebLogic Server (WLS) JMS Messaging Bridge [ID 1303870.1]

You can enable the debug flags listed below from the Administration Console by clicking on Managed server to which JMS Messaging Bridge is targeted going to Debug tab and expanding -> weblogic -> messagingbridge

What Are the Supported Platforms for WebLogic Server (WLS)? [ID 1072881.1]

Below you will find the supported platform details for all versions of weblogic

Is It Normal to See Blocked “weblogic.socket.muxer” Threads? [ID 857031.1]

We are observing one of the “weblogic.socket.Muxer” threads is in “Waiting on Condition” state for the managed server and the other Muxer threads in “Blocked” state when thread dumps were taken. Is this is a normal condition? Solution The behavior you’re describing is normal. The muxer threads contend for the poll lock to poll on ...

FAQ: WebLogic JMS File Store [ID 1307241.1]

How Do You Read JMS File Store .DAT file?

How to set max thread count on Weblogic10.3.0 or later [ID 1388000.1]

You can set “max-threads-constraint” to limit max thread count. This setting limits the number of concurrent threads executing requests from the constrained work set. The default is unlimited.

How to Start a WebLogic 10.3.x Domain AdminServer Without Interactively Supplying the Username / Password? [ID 980292.1]

1. Navigate to the current Weblogic Domain Admin Server directory – for example a typical location is MW_HOME /user_projects/domains/<Domain_Name>/server/AdminServer/

How To Reduce Or Shrink The Size Of A WebLogic Server JMS FileStore? [ID 843527.1]

The WebLogic JMS File Store cannot be shrunk or decreased in size in any way. There are two primary ways of dealing with this issue

Maximum Heap Size For A Weblogic Server Process Running on a 64-bit JVM [ID 846267.1]

64-bit platforms are not physically limited by the pointer size, and the process size can grow to the supported limit. The limit is therefore equal to the amount of memory installed.

Oracle WebLogic Server Support Pattern: Troubleshooting Out of Memory and Memory Leak Problems [ID 877172.1]

Out Of Memory (OOM): An Out of Memory error occurs due to memory exhaustion, either in java heap or native memory. In the JVM, OOM errors are thrown when the JVM cannot allocate an object because it is out of heap memory, and no more heap memory could be made available by the garbage collector.

An Explanation Of Restrictions Limiting The Java Max Heap (-Xmx) To Around 1500M For 32bit JDK’s On Microsoft Windows [ID 557813.1]

Although the maximum amount of physical memory that can be addressed by a 32 bit address bus is 4Gb,  this space has to include the program code and some data structures required by the operating system (such as the stack space), shared libraries and any variables they define. Such considerations limit how much of the ...