This document discusses common mistakes made when configuring Oracle WebLogic Server that can negatively impact performance and reliability. It outlines several anti-patterns to avoid such as using too many JDBC datasources without XA configuration, which can cause data corruption, and inadvertently coupling transactions between services without proper transaction requirements. The document also warns against practices like excessive logging, not properly configuring JMS for delivery errors, giving the operating system too much RAM, and not configuring node managers and datasources correctly for automatic restart and recovery. The overall message is that WebLogic configuration requires expertise to perform correctly in a production environment.

1. Tales from the WebLogic Front Line(What NOT to do with WebLogic)Steve MillidgeC2B2 Consulting Limited

2. AgendaHealth WarningSetting the SceneCommon Anti-patternsAin’t misbehavingThis could kill

3. C2B2 ConsultingFastPerformance and ScalabilityReliableHigh Availability and RecoverabilityManageableMonitoring and SupportingSecureSecurity

4. First Day At Work

5. It’s All Gone to *#*@!

8. Meet the Project Manager

11. PhilosophyDon’t Panic you didn’t #@#@ it up.Suspect Configuration over CodingSuspect bespoke code over WebLogic codeWebLogic is FASTComputers are Logical and Rational

12. Common Anti-patterns

13. Too Many Datasources

14. Too Many DatasourcesData Source per ComponentAll to the Same DatabaseJNDI Name per ComponentC1C1C1DS1DS1DS1Oracle

15. Why It’s BadRequires XA for all DatasourcesDevelopers receive strange “XA” exceptionUntick Honour Global TransactionsMakes Exception “go away”Datasources now in autocommitDATA CORRUPTION!!Requires more DB connectionsBIND same Datasource to multiple JNDI locations

16. Inadvertent TX Coupling

17. Inadvertent TX CouplingWLS 1WLS 2EJB 1REQUIREDInvokeEJB 2 REQUIREDOracle1Oracle2

18. Why It’s BADResults in “Strange Exceptions” if not All XAIs the REALLY what you wantXA is very heavyweightAnd not guaranteedXA requires particular database configurationYou have 4 minimum XA resources to coordinateFix using REQUIRES NEW

19. Clustering is TOO Heavy

20. WLS ClusterWLS Session ClusteringWLS 1WLS 2WLS 3WLS 412Don’t Use the Session as a CacheUSE A CACHE

21. Too Much logging

22. Too Much LoggingToo SynchronizedNew Application 30% SlowerTx TimeoutsHigh CPUMany Threads waiting on Logging MonitorDebug turned on, on one nodeIn Memory BufferEach Thread Logged to in memory queueWriter thread writes messages to fileUnder heavy load memory queues grew unbounded1.5Gb heap in log messages

23. Ain’tMisbehavin’

24. Session ShenanigansSerializationSession Attributes must be SerializableSee this one all the timeNo Failover!!!Working as per SpecNo PutYou must Put dirtied objects back in the SessionDon’t Get modify then no PutNo Failover!!!Working as per Spec

25. Exceptions and TXWhat happens to the TX when you throw an Exception from an EJB method?Application ExceptionCommitSystem ExceptionRollback

26. Poisoned JMS

27. Poisoned JMSEats CPUPrevents DeliveryKills Server PerformanceJMSQRepeatForeverSet Redeliver DelaySet Redelivery LimitSet Error DestinationException

28. Poisoned JMS (Paging)WLS Keeps Messages in MemoryCauses OutOfMemory ExceptionsConfigure Paging Thresholds Configure at JMS Server level

29. This Can Kill You

30. Too Much RAM-XMS2G –XMX2G32 bit Can be Too MuchO/S Reserves RAMVM Starts upWhen you need it!HOTSPOT DUMP

31. Node Manager ConfigurationNot Good Out of the BoxAuto Kill If Failed = TRUEAuto Restart = TRUERestart Delay should be setRestart Max should be setSet Panic Action to System.exit

32. Disappearing DatasourceStart WebLogic when DB not AvailableDatasource is not createdConnection Creation Retry Frequency Seconds should be non-zero

33. SummaryProduction Configuration is ComplexCall in the Professionals

34. Example Bullet SlideBullet 1