Resin 4.0.21 Release
There’s no upper limit to greater stability, which was our main motivator for this release of Resin. We worked on aspects of Resin aimed to make system monitoring and management easier for developers, devops and system administrators. Improvements to the Health System includes expanding the passive monitoring tools to having pro-active health actions triggered by server conditions. Version 4.0.21 has updated and added features from PDF reports to specific Resin CLI command lines. These updates were in response to user feedback and suggestions.
Resin 4.0.21 feature updates and additions:
- Command Line Interface (CLI) – added error codes specific for authentication error, wrong argument and deployment error. Added new command for Resin boot process compatible with Mac OSX launchd. Added command-line PDF-reports with snapshot and ‘start-with-foreground’ in lieu of ‘watchdog’ commands.
- Eclipse Plugin – added GIT deployment failure error reporting and updated the download and install functionality for version specific directory installation.
- Admin Console – thread page can sort threads by stack trace.
- Health System – added triggered action for when Resin unexpectedly stops. Added action to create a concise snapshot of all JMX MBeans attributes and values. Added action to generate a sequence of reports including thread dump, heap dump, JMX dump, and PDF report.
- WebSocket – Resin’s WebSocket implementation is stream-based, supporting arbitrary length messages.
- JCache – standard API will now include compare-and-set operations.
Please continue to help us make Resin a high performance and developer friendly application server by sharing your experience and improvement suggestions.
Maryland JUG report: Reza Rahman presented talk on CDI/Seam 3
The Maryland JUG presentation on CDI/Seam 3 went extremely well. The attendees were more enthusiastic than all previous CDI JUG events. This is a great indication that CDI has grown in interest with Java developers. There were a handful of current CDI/Java EE adopters who carried the conversation beyond CDI. The discussion topic combined with the high rate of feedback and participation lead to an invitation for Reza Rahman’s return to speak again later this year about additional topics on CDI and Java EE 6. The Java Users Group (JUG) is an ideal place to learn about Java technologies from peers and leaders in the community.
Reza Rahman will present conference sessions and panel discussion at JavaOne 2011
Reza Rahman is a Senior Software Engineer and Community Outreach Advocate at Caucho® Technology focused on Resin’s EJB 3.1 Lite and CDI containers. Reza is the author of EJB 3 in Action from Manning Publishing. He is a frequent speaker at Java User Groups and conferences including TheServerSide and JavaOne. Reza was an independent member of the Java EE 6 and EJB 3.1 expert groups. He is currently a member of the Java EE 7, EJB 3.2 and JMS 2 expert groups.
At this year’s JavaOne conference Reza is scheduled to present the following sessions:
- CDI Today and Tomorrow
Panelists: David Blevins, Peter Muir, Reza Rahman, Arun Gupta and Sivakumar Thyagaranjan
Get the perspectives of leaders in the CDI ecosystem. This panel will discuss the current state of CDI ecosystem, goals, adoption, community engagement, gaps, hurdles, relationship with Java EE, and future directions.
- Patterns and Best Practices for CDI
Session speakers: Reza Rahman and Ryan Cuprak
A technical session focused on the importance of CDI and how to use CDI effectively to maximize the benefits of using a loosely coupled, type-safe, annotation-driven dependency injection solution.
- The Road to Java EE 7 – Is It All About the Cloud?
Panelists: Adam Bien, Emmanuel Bernard, Krasimir Semerdzhiev, Reza Rahman and Alexis Moussine-Pouckine
Looking ahead at the development of Java EE 7 and what’s in the way to form several JSRs in the JCP. Session topics will include the current adoption rate of Java EE 6, motivations for Java EE 7, what cloud really means for Java EE 7, modularity in the Java EE.next, better streamlined component models and status of the JCP.
- JCP and the Developer Community
Panelists: Heather VanCura, Martijin Verburg and Reza Rahman
Understanding the JCP structure and how JSRs are developed. This panel will discuss the relationship between the JCP and open source development process with emphasis on transparency and participation values. Learn how to get involved and explore upcoming changes for the JCP.
- JSR 343: What’s Coming in Java Message Service 2.0
BOF (Birds-of-a-Feather) speakers: Clebert Suconic, Reza Rahman and Nigel Deakin
Java EE 7 and the cloud be will be defined and supported by JMS 2.0 (JSR 343). It will include features to improve ease of use, mandatory API for integration with application servers, clarification on relationship with other Java EE specifications and more.
Caucho® announces new engineering positions
We are actively looking for Java Protocol and Network Software Developers. Our engineering office is based in San Francisco next to the Montgomery BART station. If you are located in the Bay Area, we can be flexible with telecommuting.
This position includes core application server development and involves active contributions to our technology and roadmap direction. As part of our team, you will be working with the latest Java web specifications such as WebSocket, Hessian and HMTP/XMPP, as well as pushing new Internet Network protocols. You will have the opportunity to influence the next generation of Java web specifications from the ground up as well as explore and test your software engineering limits.
To join our engineering or sales team, please send your cover letter, resume and sample code to email@example.com.
Resin Pro Health System Now and in the Future
Resin Pro boasts significant improvements to its already highly capable Health System. Features include condition specific triggering and post-mortem reporting. Resin provides a level of reliability and system transparency that is unparalleled in the Java EE space. Server visibility is available for single servers, up to large multi-node cloud setups. Resin can provide a snapshot of the server state when problems occur in your code or 3rd party library code. Just-In-Time profiling data and comprehensive diagnostics provide unparallel troubleshooting capability for Agile devops!
Rick Hightower presents "JCache CDI Interceptors and Spring CDI Bridge" at the SVJUG
On September 20th, Rick will present JCache CDI Interceptors and Spring CDI Bridge at the Silicon Valley Web Java User Group. Rick will discuss the work he has done with CDI and interception as part of the JCache (JSR 107) and with the Spring CDI Bridge, a Spring CDI extension.
CDI (JSR 299) is the Java standard for dependency injection (DI) and interception (AOP). Both DI and AOP are the foundation of many Java frameworks, and CDI will be the foundation of many future specifications of JSRs. Rick will provide a brief introduction to CDI and how it can be used outside of a Java EE 6 container as well as some fundamentals of CDI. It is an extremely extensible standard and can be used as a framework to build other frameworks. You can build EJB 3 or Spring as standard CDI extensions just as he did with Spring CDI Bridge.
JavaOne 2011 in San Francisco this October
JavaOne is being held at the Hilton Hotel on October 2-6, co-located with Oracle World. Caucho® is exhibiting at booth 5409. This will be a great week to meet and share Caucho’s latest developments with Resin and the Web Profile. Contact us at firstname.lastname@example.org if you will be near the Bay Area or plan to attend JavaOne to arrange for a meeting.
Stopping Resin Servers: -stop, -shutdown or -kill? By Paul Cowan
Regardless of the operating system running, Resin includes three distinct commands for the purpose of stopping the application server. In this tip of the month, Paul explains each command in detail, discusses how they differ and provides advice on the circumstances associated with the use of each command.
–stop: the -stop command is the proper way to stop Resin under normal circumstances. This command initiates a clean shutdown of the intended Resin server. In a single server configuration, the Watchdog will also stop.
–shutdown: the -shutdown command stops the Watchdog, which stops all Resin servers on the machine. It is a clean method of shutting down multiple Resin servers running from the same configuration. The difference between the -stop and -shutdown command is -stop will only bring down the intended server, whereas -shutdown will bring down all Resin servers.
-kill: the -kill command kills a single Resin server at the operating system level. The Watchdog will not restart the Resin server. It is a messy way to shutdown since clean up tasks will not have a chance to run. It is intended only for unusual cases where Resin is not responding properly to the -stop command.
Copyright (c) 1998-2011 Caucho® Technology, Inc. All rights reserved.
Caucho®, resin® and quercus® are registered trademarks of Caucho® Technology, Inc.