Wednesday Jul 23, 2014
Thursday Jul 17, 2014
By Monica Riccelli on Jul 17, 2014
One of the most exciting new features in WebLogic
Server 12.1.3 is a JTA new feature
“XA Transaction without Transaction Logs.” This feature does not only provide performance optimization when applications use XA transactions, but also has great advantages for Disaster Recovery scenarios.
XA transactions provide a standards-based mechanism to preserve data integrity for mission-critical applications. Traditionally XA transaction recovery requires the transaction manager to persist transaction records to stable storage (TLog) after all of the transactions resources have been prepared, and purging them after all of the transactions resources have been completed. However, recording pending transactions for recovery purposes requires additional I/O which affects performance. In cases of disaster recovery transaction logs need to be replicated to make sure that global transactions can be recovered.
“XA Transaction without Transaction Logs,” uses a determiner resource which can be either a DataSource or a WebLogic JMS resource to determine the recover outcome of pending transactions. When using a determiner resource, WebLogic Server will no longer write and purge transaction checkpoints to TLogs. “XA Transaction without Transaction Logs,” takes advantage of the two-phase-commit protocol, as well as prepare and commit ordering of resources participating in the global transaction to determine if pending transactions need to be recovered with a commit or a rollback.
The advantages of this feature are:
· Up to three times performance throughput improvement
· Prepare and Commit ordering
· I/O latency removed by not writing to TLOG (default file store)
· Resource and/or batch blocking removed (JDBC Tlog)
· Memory consumption reduced
· Capacity requirements reduced
· TLOG replication made easy
In WebLogic Server 12.1.3 “XA Transaction without Transaction Logs,” is restricted to transactions that involve a single Transaction Manager (WebLogic Server). The mixture of transactions that enlist determiner resources and span single Transaction Managers, with those who do not enlist a determiner resource and/or span multiple Transaction Managers is supported. In the future, WebLogic will support not logging transactions that involve multiple Transaction Managers.
Check out the YouTube recordings that go into detail how this feature works "JTA 12.1.3 New Feature and Optimization". There is even a demo that shows you how it is configured, how it works, and how you can debug your transactions to verify if the determiner is working "XA Transaction without Transaction Logs" and Demo.
Monday Jun 30, 2014
By Will Lyons on Jun 30, 2014
One of the most significant areas of investment in WebLogic Server 12.1.3 has been in developer productivity and API updates, as I summarized in my blog from last week. However, a brief summary is typically not enough for developers who want a more detailed description of the improvements we have delivered. And although product documentation contains all of the relevant updates, sometime it does not capture the overall background on the topic that puts the improvements into context.
Steve Button from the WebLogic Server product management team has published an excellent whitepaper on OTN - Oracle WebLogic Server 12.1.3 Whitepaper - Developing with WebLogic Server - which provides a detailed description of the new features, along with the background which explains why we delivered the improvements, and the benefits they offer. The whitepaper covers new WebLogic Server 12.1.3 features in the areas of WebSocket, JSON, JAX-RS, JPA, Server-Sent Events, Maven and more.
If you are a WebLogic Server user looking for a detailed description of the latest development features in WebLogic Server 12.1.3, and how you can leverage them in your applications, this is an excellent resource. Please take a look!
Thursday Jun 26, 2014
By Will Lyons on Jun 26, 2014
We're proud to announce that Oracle WebLogic Server 12.1.3 has been released as part of the Cloud Application Foundation and Oracle Fusion Middleware 12.1.3 release as described at the Cloud Application Foundation Blog. Oracle WebLogic Server is the industry's leading application server, providing unparalleled choice for deploying applications in public clouds, on-premise private clouds, engineered systems such as Oracle Exalogic Elastic Cloud, Oracle SPARC SuperClusters, and Oracle Database Appliance systems, and conventional systems.
Oracle WebLogic Server 12.1.3 is a new version release of Oracle WebLogic Server 12c. It builds on the features provided in WebLogic Server 12.1.2 to improve developer productivity, performance and high availability, and manageability. It enables you to develop and deliver innovative applications, to meet the application service level requirements for your business, and to manage your application infrastructure efficiently to achieve low total cost of ownership.
For developers we have placed specific focus on enabling development of server applications that support rich client applications running in HTML5 browsers or mobile devices. Such applications typically rely on REST based Web Services, use JSON as the data format for message payloads, and often require dynamic updates between clients and servers. In Oracle WebLogic Server 12.1.3, we have implemented support for selected Java EE 7 APIs including JAX-RS 2.0, Java API for JSON Processing, Java API for WebSocket, and JPA 2.1, to enable and support development of such applications. We have also delivered related value-added capabilities like support for Server-Sent Events and unique WebSocket emulation capability.
High availability and performance improvements include improvements to Oracle Database 12c integration support - we have bundled the latest version of the Oracle Database 12c driver for ready access to database integration features, and have certified Oracle Database 12c AQ JMS as a Foreign JMS Server within Oracle WebLogic Server. Innovations to the Oracle WebLogic Server transaction processing subsystem enable elimination of transaction logs in many cases, increasing performance and simplifying distaster recover configuration. Optimizations for Oracle Exalogic systems include JMS performance improvements, and Cooperative Memory Management to adapt server memory usage based on memory consumption on Oracle Exalogic systems.
Manageability enhancements include improvements to dynamic clusters introduced in Oracle WebLogic Server 12.1.2. In Oracle WebLogic Server 12.1.3 we support use of whole server migration to provide improved availability for dynamic clusters environments using JMS. We have expanded our support for REST-based management, adding lifecycle management, application deployment, and datasource configuration support via REST. We have also made similar improvements to support for Oracle WebLogic Server management in Oracle Fusion Middleware Control.
Finally, Oracle WebLogic Server 12.1.3 is the foundation of the Oracle Fusion Middleware 12.1.3 release, which adds Oracle SOA Suite 12c and other Oracle Fusion Middleware products to the family of products that is supported with Oracle WebLogic Server 12c. This will make it easy for Oracle WebLogic Server 12.1.3 customers to adopt the latest releases of these products, and will also enable Oracle Fusion Middleware users to take advantage of the latest features in WebLogic Server 12.1.3. To learn more:
...and look for more information from us in the coming days and weeks. Thanks!
By Ruma Sanyal-Oracle on Jun 26, 2014
Monday Jun 16, 2014
By Laurent Goldsztejn-Oracle on Jun 16, 2014
The following thread was extracted from a thread dump taken on a JVM instance running WebLogic Server.
In this post I will deconstruct this thread and describe the data it contains and the potential issues it may illuminate.
[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' id=73 idx=0x128 nid=13410 prio=1 alive, in native, daemon
This thread is considered Stuck by WebLogic because it's been running for over the time defined in MaxStuckThreadTime (600 seconds by default). Weblogic Server waits for this time to be reached before marking a thread as stuck if the thread is still working after this time. If you deem that 600 seconds is too long before a running thread is considered stuck then you can change the value of the this parameter using the WebLogic Console (as shown below), or use setMaxStuckThreadTime from the ServerFailureTriggerMBean interface.
An error including BEA-000337 will be logged in the server log file when the thread changes its status to stuck but the server won't take further action on this thread. However, you might want to investigate why this thread is taking such a long time to process the work assigned to it.
Lets now look at the thread itself. From its header, you can spot the thread identifier (2 in this example) and the queue where it originated. The term Self-tuning indicates that the associated thread pool consistently checks the overall throughput to determine if the thread count should change.
id (or tid) is the thread identifier, a unique process-wide number that identifies this thread within the JVM process. This id is unique but can be reused by another thread once this thread is terminated.
nid is the OS-level native thread identifier. It can be used effectively to correlate with high CPU usage threads identified at the OS level (e.g. with Linux watch command). See Unexpected High CPU Usage with WebLogic Server (WLS) Support Pattern (Doc ID 779349.1) for detailed steps.
idx is the thread index in the threads array.
prio refers to the thread priority, a number inherited from the thread that created it. You can learn more about thread priorities at Class Thread but basically threads with higher priority are executed in preference to threads with lower priority.
alive refers to the fact that this thread has not ended yet and is still active.
in native means that the thread uses the operating system's native ability to manage multi-threaded processes.
daemon indicates that this thread can't prevent the JVM from exiting.
The thread header is accompanied with a full java stack which lists each method and class invoked since the first assignement to the thread up to its most recent action. This thread consists of obtaining a connection to an Oracle database using a Type 4 JDBC driver and then issuing a call but getting no response from the back end database server. The database failed to respond, and the thread has probably been in the same waiting mode (unchanged and not progressing java stack) for a long time since it's now considered stuck; the most recent invocation being java.net.SocketInputStream.socketRead0.
At this point the back end database needs to be checked to understand why it's not responding to the java thread request. A starting point could be to query v$session to find potential blocking sessions at the database level.
Blocking sessions occur when one session holds an exclusive lock on an object and doesn't release it.
Needless to say, the communication with the database needs to be confirmed as healthy with none to very limited latency. Firewall issues should be ruled out as well. Firewalls could time out idle sockets used by JDBC connections to the database and lead to not closing the socket the JDBC driver is using.
Tuesday May 13, 2014
By jeckels on May 13, 2014
|Dr. Frank Munz, one of our most esteemed Oracle Aces, has just released an updated book on Oracle WebLogic 12c, which contains more than 130 additional pages, half a dozen new webcasts and more than 16 new or rewritten recipes.|
|From the book abstract:
Imagine you need to know about a problem with your car's engine. You could plough through the 1000-page manual. Or you could chat to the mechanic over a cup of coffee. That's WebLogic 12c Advanced Recipes. It's WebLogic for software architects, administrators and developers. For people like you who know quite a bit about WebLogic. What you don't want is the typical 'recipe book' full of screenshots. Click here. Click there. Do this. Do that. That's WebLogic by numbers. What you really want are the things you won't find in the manual, like recommendations, discussions, best practices, deployable projects, webcast videos and directions on when to use a feature - and when not to. With all this and more, this book is the perfect complement to official courses and manuals. In short, this gem of a book is almost as good as attending one of Frank's renowned workshops.
Friday May 09, 2014
BA, the German federal employment agency, ensures labor market services availability and performance
By Ruma Sanyal-Oracle on May 09, 2014
Thursday May 08, 2014
By Ruma Sanyal-Oracle on May 08, 2014
Reliance Commercial Finance provides loans for real estate, commercial and private vehicles, construction equipment, and infrastructure to more than 70,000 customers, including businesses and individuals. The company has an operational presence that spans 66 locations in India, and it is one of the fasting growing nonbanking financial companies in the country.
With more than 2,000 users accessing the company’s core applications every day, the legacy IT
infrastructure was struggling to process more than 6,000 daily
transactions, especially during peak periods, such as the last five days
of each month. It was also time-consuming and costly to manage and
track customer-loan applications and approvals across multiple systems.
The legacy system increased customer churn and time to market.
To address these issues, the company implemented Oracle WebLogic Suite and Oracle Exalogic Elastic Cloud to ensure high-performance, high availability, and scalability for its core applications. It also enabled seamless integration with Oracle Exadata Database Machine. These implementations accelerated loan transaction speed by 30% and increased IT staff members’ productivity by 70%. In addition, the financial institution improved its competitiveness by accelerating the customer loan approval process by 3x and slashing new application deployments from eight weeks to one day, thereby increasing customer satisfaction. Complete details of Reliance Commercial Finance's use case can be found here.
Wednesday Apr 30, 2014
By Ruma Sanyal-Oracle on Apr 30, 2014
Japanese multinational, NEC corporation, plans on offering the unique Active GridLink for RAC, providing intelligent integration between Oracle WebLogic Server and Oracle Real Application Clusters (RAC), to customers for its higher performance, availability, and simplified operations. Check out Naoto Kashiwagi, Assistant Manager, NEC discuss Active GridLink benefits in great detail.
Monday Apr 28, 2014
Oracle, yet again, #1 in the Application Platform [previously known as Application Server] Market for 2013
By Ruma Sanyal-Oracle on Apr 28, 2014
Oracle takes the top spot for market share in the Application Platform Market Segment for 2013 according to the March 2014 Gartner “Market Share: All Software Markets, Worldwide 2013” report.
· For more information on the report, please contact Gartner Inc.
By jeckels on Apr 28, 2014
Migrating Apps from GlassFish to WebLogic
Wednesday, April 30
10am Pacific Time
Note if you are unable to attend, the webinar will be archived about 48 hours following the event on our DevCast page in the "On-Demand" section.
Friday Apr 25, 2014
By jeckels on Apr 25, 2014
Coming in just a few days, Oracle is hosting a Virtual Developer Day giving Java developers of all levels another opportunity to learn more about how they can build amazing applications with the latest Java flavors; SE, EE and Embedded. Following the Virtual Developer Day, we'd love to hear how you're running your rich new apps on WebLogic. But we're unashamedly biased on this blog, of course.
Java Virtual Developer Day
May 6, 9am-1pm Pacific Time
Watch tutorials from the experts to improve your expertise in Java, the world's #1 development platform. Get technical information from Java experts and ask questions during live chats. This FREE virtual event will cover:
• Java SE 8 New Features: Lambdas and more
• A technical introduction to the Java EE 7 platform
• How Java makes it easy for you to control a wide range of embedded devices
• Get the latest information about Java from the experts: Java SE 8, Java EE and Java Embedded.
• Learn about Lambdas and more!
This event is FREE, but you must register. Register NOW!
Tuesday Apr 08, 2014
By Frances Zhao on Apr 08, 2014
Oracle WebLogic Server on Oracle Database Appliance 2.9 offers a complete solution for building and deploying enterprise Java EE applications in a fully integrated system of software, servers, storage, and networking that delivers highly available database and WebLogic services. The world's most popular database, Oracle Database and the industry's best application server, WebLogic Server have been combined in this industry-unique appliance to provide high availability and the simplicity of One-Button deployment. And to top it all off, it reduces IT cost with a unique capacity-on-demand software licensing model.
Here you can download the new version of WebLogic on ODA 2.9 which
offers WebLogic templates for 11g (10.3.6), 12c (12.1.1 and 12.1.2).
The following highlighted new features are included in this release:
- Supports new X4-2 hardware with more capacity, faster processor, better networking with no price increase!
- WebLogic on ODA provisioning tool now offers multi domain and multi cluster options in the wizard-driven templates.
- New licensing options include a 'pool' of WebLogic licenses with min/max range, that can be allocated to WebLogic, Oracle Traffic Director and other Oracle Cloud Application Foudation products.
- Provides a 'silent provisioning' option.
- A new WebLogic on ODA provisioning wizard-driven template with a nicer GUI.
- Shared storage repository option.
Wednesday Mar 26, 2014
By Ruma Sanyal-Oracle on Mar 26, 2014
Therap Services is a web-based service organization that provides an integrated solution for documentation, reporting and communication needs of agencies providing support to people with developmental disabilities. It is a niche segment in the health sector. Its products and services are used by people in over 48 states in the US and by governments in at least five US states. Therap was using JBoss application server and managing it was becoming difficult. JBoss messaging proved difficult as well with out of band situations that it couldn't handle. Therap opted for WebLogic as their primary application delivery platform. Now Oracle Enterprise Manager [OEM] and JVM Diagnostics [JVMD] provide deep monitoring and visibility into the application stack. These tools have uncovered many bottlenecks in the Therap application that otherwise wouldn't have been found and fixed. "The benefits and results of Oracle solutions are huge", says Mojahedul Hoque Abul Hasanat (Masum), CTO, Therap Services. The performance relative to JBoss are order of magnitude higher, he says. Watch this video and find out more details.
- OpenWorld Double Dose: Maximum Availability in the Cloud
- Next Up: WebLogic Server Management Session from OpenWorld
- Sonatype Nexus 2.11.2 supports Oracle Maven Repository
- Calling All WebLogic Users: Please Help Us Improve WebLogic Documentation!
- OpenWorld 2014 Round 3…Highlighting Oracle Java Cloud
- Is your IT private PaaS ready? Take this 10-minute Assessment to find out
- Oracle Maven Repository - Viewing Contents in Eclipse
- Reaching 10K
- Safe Water Kenya: Follow up
- OpenWorld 2014: Next up, Coherence Strategy & Roadmap