March | 2017 | Caucho

Caucho at Devoxx - for the developers!

Q1 has been filled with activity at Caucho!

Developer Sean Wiley is on the road presenting at key events including Devoxx US. We continue to collect valuable feedback from Resin users and look forward to the next release, Resin 4.0.51. We encourage you to report any issues with reproducible behavior to bugs.caucho.com website, or by reaching out directly to us at presales@caucho.com.

Newsletter at a Glance:

Caucho presents Baratine @ Devoxx 2017, March 21-23 in San Jose
Caucho presents webinar with Elastic Beam
Caucho presents @ San Diego JUG
Resin High Availability Settings (Part 2)

Caucho Presenting Baratine @ Devoxx 2017

Join Caucho Engineer Sean Wiley for a “Tools in Action” presentation on server side Java. Sean will be presenting on operational service views using Caucho’s MicroService Platform Baratine (link to www.baratine.io)

Sean’s presentation will provide details into how MicroServices can improve high volume web services, making bottlenecks a thing of the past. The talk will integrate these services with current architecture, allowing developers to use platforms they are familiar with for next generation applications.

If you’d like to meet up with Sean for a coffee or beer during Devoxx, contact him at wiley@caucho.com

Devoxx conferences in Europe are famous for being vendor neutral community events, organized by developers, for developers. The events are always highly intellectual, geeky and fulfilling conversations with some of the best speakers and attendees in the industry.

Caucho/Elastic Beam Webinar

Ouch!!! We saw that Gartner estimates that downtime costs are >$300,000/hr with variation based on industry vertical and other factors. So we partnered with Elastic Beam to build a robust web application server environment that delivers performance, security and minimizes costly downtime.

Our webinar focused on simplifying and securing application infrastructures with example deployments. We also touched on the following questions:

• What is causing availability issues with today’s Java EE application servers?

• What are the critical requirements to consider when building robust web-scale infrastructure?

• How do you build highly available web infrastructure with a software only approach to avoid significant costs?

• What types of hacker attacks do you need to worry about?

• How to secure your applications against malicious activity?

• How to track API usage and detect abnormal behavior?

To learn more, please reach out to us at presales@caucho.com.

San Diego JUG

We gave a talk at the San Diego Java Users Group on high availability of the Resin Application Server. The talk was well received and we were glad to share with the San Diego developer community details to improve their application deployments.

Check out the abstract: Uptimes, scalability, clustering and performance monitoring are all important aspects of running a successful Java Web Application. This talk will focus on real world examples of features and advanced configurations deployed in the Resin Application Server to achieve success in the aforementioned aspects. Features and examples covered will reveal how users of the Resin Application Server are achieving 99.99% uptime with their enterprise deployments.

Details and presentation slides are online at http://www.sdjug.org/meetings.

High Availability Part II - How does the Web Tier find the App Tier

Following up on Part I presented in January's newsletter, here is Part II. As always, we value your feedback so take a look and feel free to send your comments to wiley@caucho.com.

The Web Tier hosts the load balancer, which is configured in resin.xml with the following:

New Picture (1)

Note that resin:LoadBalance has a cluster parameter which will be used to find servers that serve that cluster (Tier). In the case above the cluster is called 'app'.

New Picture (2)

Web Tier resolves servers in the App Tier using resin.properties. Resin.properties configuration file must have a correct app_serversproperty which lists static App Tier servers. Once the Web Tier can find core servers of the App Tier it can resolve the dynamic servers using the cluster state that is communicated by the App Tier to Web Tier.

Deploying Web Applications

Web Applications should be deployed into App Tier using Resin deploy command. Once deployed into one of the three founding members of the cluster (the first three static servers defined in app_servers) application is replicated to the rest of the static and dynamic servers in the cluster. Deploying a foo.war application will look as so:

New Picture (3) 2

New Picture (4)

Configuring user name and password

Username and password are configured in resin.properties with admin_user and admin_password properties.

For production deployment the password must be generated with Resin's password command as so:

New Picture (5)

Lines admin_user and admin_password can be copied into resin.properties replacing the commented out admin_user and admin_password properties

For testing the password can be specified in plain text as so:

New Picture (6)

Cluster Security: Cluster Key

Cluster Key is used as a security token which allows participants in Resin Cluster Resin Servers to communicate. Cluster key should be specified in resin.properties as so:

New Picture (7)

Extended – New Years gift to optimize your configuration!

Contact Caucho engineer Sean Wiley at wiley@caucho.com or (858) 456-0300 to set up a complimentary review of your deployment, including learning about new Resin features and tips to optimize your configuration.

Download Resin