Blog

Transaction Memory Values Explained

One of the metrics gathered by FusionReactor during the execution of a transaction (request) is the memory usage of the transaction. This is displayed on the Main tab in the transaction details page. Since FusionReactor 6 we have added the Transaction Allocated Memory value to these details. All of these numbers can be a little confusing so below we have explained what all the memory values mean.

Explaining FusionReactor Transaction/Request Memory Values

The first few numbers are quite straight forward. These are simply a snap shot of the JVM state at either the start of the transaction (for transactions that are still running), or at the end of the transaction (for transactions that are finished).

Used Memory

This is the amount of memory that is currently used by the JVM, shown as both a absolute byte value and as a percentage of the maximum memory.

Max Memory

This is the maximum amount of memory that the JVM is allowed to use. This can be defined using the -Xmx Java argument.

Total Free Memory

This is the actual amount of memory that is not used by the JVM, this includes memory that has been allocated but not used yet. i.e. this is max memory minus used memory.

Allocated Memory

This is the current amount of memory that has been allocated by the JVM.

Free Memory

This is the amount of memory that has not been allocated by JVM. i.e. max memory minus allocated memory.

Transaction Allocated Memory

This value needs some deeper explanation in order to avoid confusion. This number is the total number of bytes that have been allocated during the life time of the transaction. Every time an object is created a portion of the JVM memory is used to hold this object, of course in java the garbage collector (GC) will automatically free any memory that is no longer needed.

This means that you can the reuse the same memory space again. So if we run the bit of code below, we will allocate memory space the string 10 times. Resulting in the transaction allocated memory value being 10 times the size of the single string.

for(int i = 0; i < 10; i++)
{

String str = “this is a string”;

}

This would mean that even if you have a max heap of 8 gigabyte the transaction allocated memory value can exceed this value. This would indicate that JVM is allocating and then freeing lots of object. If we look at the image below you can see that a single transaction can allocate more than the maximum heap, as long as it does not do it all in one go.

Transaction Memory Vales 2

2015 Wrap-Up – hello FR6 and Happy Birthday FusionReactor !

What a year 2015 has been – I just wanted to share some of the highlights we’ve achieved :

1. We launched FusionReactor 6 – with loads of new features – some significant performance improvements as well as the new ULTIMATE Edition with the Production Debugger
2. We applied for our first ever patent – which was actually for the Production Debugger
3. Sold our 25,000’th FusionReactor license
4. FusionReactor was 10 YEARS OLD in December 2015
5. Rolled out FusionReactor CLOUD Beta – which is currently hosting over 1000 server instances !
6. Sponsored a number of events, including dev.Objective(); Into The Box in Minneapolis, CFCAMP in Munich, Germany, Velocity in New York & the Adobe ColdFusion Summit in Las Vegas
7. Launched the new FusionReactor website – https://www.fusion-reactor.com
8. Introduced a FusionReactor Developer Edition (will post a separate article on this)
9. Launched FeeFo independent review service for FR – see Customer Reviews for the current score https://www.fusion-reactor.com/customer-reviews/
10. Look out 2016 – with the planned launch of FusionReactor CLOUD + lots of new goodies planned for FusionReactor – it’s going to be VERY BUSY

Finally, as the end of the year rapidly approaches I would like to take this opportunity to wish you all the very best for the holiday season and good health, happiness and success for 2016.

Best Wishes,

David Tattersall

CEO Intergral – makers of FusionReactor Application Performance Monitor

Announcing FusionReactor 6 – the wait is over !

After approximately 10 years of engineering, 100 meetings, 1,000 pizzas and 10,000 cups of coffee we’re now ready with FusionReactor 6 – it’s taken a while – but it’s worth it and FR6 is by far the best, fastest and most feature rich version of FusionReactor ever launched. Oh – and as everything seems to be the power of 10 – FusionReactor is also exactly 10 years old this month 🙂

What’s different…? Well, FR6 includes tons of new features and improvements, but one feature really stands out – which is the Production Debugger available in the new ULTIMATE Edition of FusionReactor. We’ve always believed that monitoring is really a means to an end. The end goal is about your company being able to deliver your service, such that your customers are satisfied and your business makes money. So your applications need to be free of defects and always ON. Unfortunately, all software has defects, but we believe that the measure of a great monitor, is the speed at which the monitor can highlight and direct you to the defect, so that you can actually get it fixed and restore service.

FusionReactor has always been about giving you accurate, real-time insight into what’s happening on your server/application right now and the Production Debugger available in the ULTIMATE Edition takes that goal to a whole new level.

How to get FusionReactor Ultimate Edition

FusionReactor ULTIMATE can be purchased separately and it’s also possible to upgrade from either Standard or Enterprise Editions. Please contact sales for more details.

Here are some of the highlights which FR6 has to offer:

  • Memory Usage metrics
  • Application Filter view
  • Application Session Tracking
  • Enhanced Garbage Collection Analysis
  • SQL Query Planner (Explain)
  • ColdFusion Extended Metrics visualized
  • On the fly code de-compilation
  • Improved Notification Center
  • Improved Java Frameworks – Spring, Struts
  • Support for Fusion SaaS (CLOUD) – note Fusion SaaS will be released separately to FR6

The whole team is very proud of what we’ve achieved with FusionReactor 6 and we very much hope that you enjoy using it and that it continues to be your first choice tool to monitor, detect issues and protect your applications and servers.

David Tattersall
CEO Intergral – makers of FusionReactor, FusionAnalytics and FusionDebug

FusionReactor 6 sneak peek – Re-writing the definition of what Application Performance Monitoring is all about!

APM tools have emerged as a category to help businesses address issues when applications break or systems are slow. Unfortunately, even though many of those tools measure metrics and provide some insight into what’s going on, they don’t do anything to minimize downtime and really accelerate time to fix. To be honest, traditional APM tools simply don’t do enough.
FusionReactor 6 takes a different approach – we not only provide the basics and core APM expectations that every user has for server monitoring, FusionReactor 6 introduces the unique and patented capability that allows you to do real-time Production Debugging, a game changer in accelerating the time needed to IDENTIFY and FIX issues – PLUS FR’s unique Crash Protection, which will alert you and guard your servers against crashes, so you can take action BEFORE systems go down – resulting in high application and server resilience, improved quality, less downtime and happier customers !
FusionReactor 6 is breaking the mold of traditional APM tools and will enable you keep your production systems online longer and with better results.

Here are some of the highlights which you can you expect with FR6:

  • Production Debugging / Alerting
  • Enhanced Crash Protection / Scripting
  • System Monitor – extensive metrics
  • Daily + Service Level Reports + weekly, monthly summaries
  • Enhanced Stack Trace Analysis (Trace Assist)
  • Memory Usage metrics
  • Application Filter view
  • Application Session Tracking
  • Enhanced Garbage Collection Analysis
  • SQL Query Planner (Explain)
  • ColdFusion Extended Metrics visualized
  • On the fly code de-compilation
  • Improved Notification Center
  • Improved Support for Java Frameworks
  • Support for Fusion SaaS (CLOUD) – note Fusion SaaS will be released separately to FR6

Production Debugging/Alerting

Did you ever hear someone say, “We can’t reproduce that problem, it ONLY ever happens in production” – well, with the introduction of FR6’s new Production Debugging (PD) capability, this will become a thing of the past.
Production Debug gives you all the control you need to simply and securely interact with your production environment as issues unfold. The insight it provides will revolutionize how you identify problems.   Unlike a typical debugger, you can setup conditional breakpoints and be alerted by email when they fire.   The email will contain a link to the debug session, as well as stack trace and variable details at the instant the break point fired.   It has NEVER been easier and faster to get to the root of issues.

Production Debug

The Production Debug feature will only be available in the new FusionReactor Ultimate Edition.

Key features include:

  • Interactive debugger within FusionReactor’s interface
  • Conditional breakpoint (BP) and break on exception handling – allowing full control of debug sessions in your production environment
  • Usual debug features e.g. alter variable, step into, out etc.
  • Email breakpoint notification – when a breakpoint fires, FusionReactor will hold the thread and send you a link to the debugger at that point. Restricting this to a single thread ensures that your production environment is not impacted by the Production Debugger
  • Time controlled handling mechanism, allowing you to easily control how your production system handles break points / exceptions / debug sessions
  • Exception Alert Email – including Stack trace + Stack context – will enable rapid identification of issues
  • Visual indication (in the FR banner) that a Production Debug trigger has occurred
    Bug Notification

System Monitor

Over the years, customers have often asked for other system related metrics which were usually only available in more traditional system monitoring tools. We have now extended FR6 to include a wide range of new metrics and system specific information. Access to this information is via the System Resources icon in the main FusionReactor interface.

The new metrics being tracked, include:

  • System Environment details
  • Java Environment details
  • Currently logged in users
  • Network Details
  • Memory Swap Information
  • System Console Access
  • Running processes page; showing:
    • CPU usage
    • Memory usage
    • File descriptors
    • Threads
  • Process details page; showing:
    • Memory details
    • Environment variables
    • Modules
    • Process arguments
  • Disk IO / Per disk
  • Network IO / Per network adaptor
  • Disk Usage & capacity – broken down per disk
  • CPU usage per core
  • CPU usage break down (nice/wait/system/user)

System Metrics

Another important feature is the ability to set disk space thresholds, so now FusionReactor can alert you when disk space reaches a defined limit.

New FusionReactor Reports

Daily Reports

Feedback to the original FR Daily Report was really positive and we wanted to build on that with our new Daily Report, which adds additional information and draws your attention to potential issues and/or improvements in performance and stability. The new layout includes both previous values, and targets for those values. We think that this will allow for a better overview of how your server is doing on a day to day basis.

We have also added some more statistics to the report including number of sessions and number of 404 errors. In addition to these metrics we have added a breakdown of the recorded outage, with estimated start and end dates and times, durations and the reason for the outage. We also now have a breakdown of all response codes for the reported period, with average runtime, count and its percentage out of all requests.

Along with the Service Level report, we are introducing a Weekly report, which will produce a summary of your server for the week, as well as a monthly report, which will produce a summary of the calendar month.

ColdFusion Metrics Page

FR5 already collected a number of specific ColdFusion metrics. Till now, these were stored in various log files and were only available visually via FusionAnalytics. FR6 has 2 new screens available which break down the CF metrics and display them in graphical form. Some of the metrics shown, include : Active Sessions, # of current sessions, Template Requests, Web Service requests, App Scope Size, hit counts (breakdown of hits per request type) etc.

ColdFusion Metrics

SQL – Query Plan (Explain)

Since SQL is declarative language, there are typically a large number of alternative ways to execute a given query. These alternatives can provide widely varying performance. JDBC is typically one of the main areas which we find at the root of application related performance issues.

FusionReactor 6 has the capability to attach an SQL Query Plan to the given JDBC transaction in the event that the SQL statement execution is longer than a given time. This is made available on the transaction details page. This feature will provide database users and administrators the capability to manually examine the plans produced by the optimizer to spot potential performance issues. FusionReactor will run the query plan immediately after the actual query is executed.

FusionReactor 6 Query Plan

Session Tracking and Visualization per Application

In the stateless HTTP web world, Session’s play an important role for maintaining client state. Sessions are generally used to store user data – which can quickly eat up memory if not kept in check. Sessions are tracked (and identified) using a session ID. FR6 is now tracking and visualizing sessions. All created, destroyed and active sessions are tracked per application.

Session Planning

Northern Virginia ColdFusion Users Group FusionReactor Product Suite Presentation (Recorded November 2014)

Using FusionReactor, FusionAnalytics, and FusionDebug to Solve CF Server and Coding Challenges (Recorded November 2014)

Using FusionReactor, FusionAnalytics, and FusionDebug to Solve CF Server and Coding Challenges Presented to the Northern Virginia ColdFusion Users Group, Presented by Charlie Arehart (Recorded November, 2014)

In this 90 minute talk, veteran CFer Charlie Arehart will introduce and demonstrate the “Fusion tools”, FusionReactor (FR), FusionAnalytics (FA), and FusionDebug (FD). If you’re not familiar with the tools, or are not aware of how they have evolved, you’ll come to appreciate how they can quickly and easily help you solve server or coding challenges.

About the Northern Virginia ColdFusion Users Group

Northern Virginia ColdFusion Users Group meets (at a minimum) once per month.

Their aim is to provide opportunities for ColdFusion and Actionscript developers to meet and network with one another as well as opportunities to engage in presentations and learning to help sharpen your ColdFusion development skills.

They are an active group and always welcome new members. If you live or work (or can otherwise get to) Fairfax, VA then they would love to have you come out.

Relevant Links

Charlie Arehart: http://www.carehart.org/
Northern Virginia ColdFusion Users Group: http://www.meetup.com/nvcfug/

All about FusionReactor’s Daily Reports


Something you will hear over and over when looking at the APM space, is reports. Every APM solution has reports, and FusionReactor is no different.

With the release of FusionReactor 5.0.0, we included the Daily Report, which is a summary report which is sent as an email to the configured address(s) at the given time.  This plugin is very simple to use and just like other features in FusionReactor will work without a restart.   The idea behind this report is that it can be used to provide users with a quick indication of server health without having to check the instance directly via the FR interface.

Background

A quick overview of what the daily report consists of before we get started in making it work for us.

You can see from the image that the daily report contains a break down of the up time, web request activity and the core resource usage. The report is intended to quickly put over the basic state of your server over the last 24 hours; and in my opinion does it quite well.

Uptime is measured as a percentage of that day that the server was online, effectively it is (1 day – downtime / 1day) * 100.

 

Daily Report Screenshot

Setup

I feel that the best thing about this feature is that there is very little to do, as is often the case when setting up FusionReactor. All you need to do to receive this report is to enter the mail server settings within the FusionReactor -> Settings page. I will not go through all the settings as for the most part they are fairly simple. There are also a few other things in this email settings which can be helpful to know. For any further help please refer to the docs here.

From Address

The “From Address” is actually not needed to send an email, and is usually just used as a method to identify the sender. What i like to do for the FusionReactor instances is to use this to indicate the instance/server that the email has come from. So for instance i have the current released version of FusionReactor running on the testfr server. I can then use the email address release@ testfr.com, so now i can apply filters to the email account that this mail is sent to, allowing to be have different folders in the mail client for the different instances/server.

Using this approach means i can just look at the new mails per folder to know it there is any missing.

Host Name

This field is quite often overlooked. As FusionReactor’s internal web server, and discovered host name, is usually hidden from the outside world. The links in the email will not work unless you are inside the correct network. This field allows you to specify the host name and port that should be used in the links in the email. This has no affect on the email server used or and functionality, it is simply a way to set the host name that this instance of FusionReactor is available on.

As you can see from this example you can also include port numbers.

Send Test Email

This last part of the form is quite useful, if not a little annoying in its implementation. Basically this little button will send a test mail using the entered settings, unfortunately you do need to save the settings prior to clicking this button. This hopefully will be fixed in FR 6.

If you have set up the email settings for your mail server correctly the you will receive an email report from FusionReactor at 00:05 (server time). If you want to change the time the report is sent or the recipients read on.

Advanced Settings

There are a few more settings that can be changed if you want to have the email sent at a different time, or have the report sent to recipients other than those in the default mail settings for the instance. These settings are available in plugin configuration screen, go to FusionReactor -> Plugins -> Active Plugins. Then click on the Configuration button for the FusionReactor Daily Report Plugin, there are not many plugins on this page so should be easy to find.

Firstly, send time. If you want the report to be sent at another time, simply change the “Report Time” field to the time that you want the report sent. Note: this time should be in 24hour format. You should also be aware that this time also indicates the time that the report takes as the end of the day. So if you change the time to be 12:00, the report will be for the time from 12:00 – 12:00.

Next we have recipients, this is fairly straight forward. A comma separated list of email address that the email should be sent to, these recipients are only used for this report. Also note that a blank field indicates that it will use the To Address in the FusionReactor -> Settings page.

No need for the Daily Report?

If you do not want to receive reports from FusionReactor then you can either remove the settings in FusionReactor -> Settings (which will prevent all emails from FusionReactor), or you can disable the plugin from the plugin configuration.

FR6 Reporting Sneak Peak

We received lots of positive feedback to the Daily Report in FusionReactor and we decided to further extend the reporting in the upcoming FusionReactor 6 release.  FR6 will include an improved new Daily Report, as well as a brand new Service Level Report.   Here is a sneak peak of some of the features you can expect.

  • Session activity
  • Improved source details
  • 404 count
  • Outage details Start – end times
  • Durations
  • Reason
  • HTTP response code break down
  • Trend indicators
  • Improved configurations
  • Daily AND weekly summaries !
Preview of FR6 Daily Reports

Getting custom instrumentation and metrics using FusionReactor: Examples with ColdFusion


FusionReactor will simply work out-of-the-box to give you masses of metric data and insight into requests, transactions, queries and resources without adding any additional code to your application.   However, if you want to get even more insight into specific areas of your application, then it’s easy to customize FusionReactor.   This level of customization will enable you to instrument specific parts of your code that FusionReactor (normally) does not track e.g. you can track method calls, web service calls – anything you like.   All this can be achieved by simply adding a few lines of code to instruct FusionReactor to track metrics, add properties to transactions or even create new child transactions around parts of your code.

In this post I will show you how to instrument your ColdFusion code to:

  • Create graphed series
  • Add properties to transactions
  • Create new Transactions

Creating a Graphed Series

The first step in creating a tracked series in FusionReactor is to create an instance of the FusionReactor API, playfully named FRAPI. This requires the use of the ColdFusion createObject call, see below.

Create FRAPI object
<cfset frapiObj = createObject("java", "com.intergral.fusionreactor.api.FRAPI")>
<cfset frapi = frapiObj.getInstance()>

From here all we need do is call the method on the frapi variable to post the metric, see below.

 

Post Float value
<cfset frapi.postNumericAggregateMetricFloat("/series/name", 10.0)>
 As ColdFusion can have some problems with distinguishing float and long primitive values there is also a method that takes a long, see below.
Post long value
 <cfset frapi.postNumericAggregateMetricLong("/series/name", 10)>
 Now both of these methods will take the value and post it to the given series name, in the event that that series does not exist it will be created automatically. These two methods will also create the standard numeric aggregates that are available in FusionReactor (1 Hour, 1 Day and 1 Week), if you do not want this much data from the series then you can use the alternative methods to post data without creating the aggregates.
Non Aggregated metrics
<cfset frapi.postNumericMetricLong("/series/name", 10)>
<cfset frapi.postNumericMetricFloat("/series/name", 10.0)>

The first call to post will create the series and aggregates, so if you first call is to postNumericAggregateMetric.. then the series will have the aggregates.  Similarly if you create the series using the postNumeric. then the series will not have the aggregates, even if a later post is to postNumericAggregate.

 

A Simple Example

Simulate Revenue being generated via sales and display the revenue in a graph within FusionReactor.

<cfloop from=1 to=120 index="j">
   <cfscript>
   frapi.postNumericAggregateMetric("/Revenue", RandRange(100,300));
   Thread.sleep(JavaCast("long",1000));
   </cfscript>
   <cfflush>
</cfloop>

Once you have posted the values to FRAPI you can see the graphs in FusionReactor on the Custom Metrics page. (Metrics -> Custom Metrics) and will be able to access the /Revenue values from the drop down menu.

FRAPI customization in FusionReactor

 

Add Properties to a Transaction

FusionReactor will automatically track lots of ColdFusion metrics, one of the most important is Web Requests. Along with tracking requests, FusionReactor is able to attach properties to requests so you can better diagnose problems later on. To attach a property to a transaction using ColdFusion see the code snippet below.

 

Adding properties to WebRequest
<cfset transaction = frapi.getActiveTransaction()>
<cfset transaction.setProperty("/property/name","StringValue")>

The setProperty method is effectively a map put, and is able to take any object as a value. However the FusionReactor UI is only able to display the value as a string, so it is a good idea to ensure the result of the toString method of the given object is a user friendly string.

It is even possible to use the FusionReactor as a kind of private session store, that is only available for the life time of that request. So similar as above, but by using the getActiveMasterTransaction you can always get the top level transaction on this request. The difference between getActiveMasterTransaction and getActiveTransaction is explained in the next section. With this top level transaction you can put and get properties from it just like a session, but this is only available for this request.

 

Get property from Transaction
<cfset transaction = frapi.getActiveMasterTransaction()>
<cfset prop = transaction.getProperty("/property/name")>

If you do put properties into the request it is important to remember that FusionReactor will keep these requests in memory for some time, depending on settings, so it is NOT ADVISABLE to put large objects into the request properties !

 

Creating new Transactions

As mentioned above, FusionReactor will automatically create many transactions to track WebRequests, JDBC requests, CFHTTP among many more.  Let’s imagine you have a function or section of code that you want to track the performance of.   Using FusionReactor you can wrap this section of code is a custom transaction to visualize the performance inside FusionReactor.   Doing this is very simple, image we have the below CFFunction code.

 

Example CFFunction
<cffunction name="newRandomNumber" access="public" returnType="string" output="false">
<cfset rndObj = createObject("java", "java.util.Random")>
<cfset rnd = rndObj.init()>
<cfset area = rnd.nextInt(99999)>
<cfreturn area>
</cffunction>
 So from this example if we want to track all calls to this function all we need to is add a create and end transaction call.
Instrumented CFFunction
<cffunction name="newRandomNumber" access="public" returnType="string" output="false">
  <cfset frapiObj = createObject("java","com.intergral.fusionreactor.api.FRAPI")>
  <cfset frapi = frapiObj.getInstance()>
  <cfset trans = frapi.createTransaction("newRandomNumber")>
  <cfset rndObj = createObject("java", "java.util.Random")>
  <cfset rnd = rndObj.init()>
  <cfset area = rnd.nextInt(99999)>
  <cfset trans.close()>
  <cfreturn area>
</cffunction>

This code will now create a transaction with the flavour “newRandomNumber”, which will be added as a child transaction to the web request and visible in the FusionReactor UI. Alternatively there is a createTrackedTransaction method that will do the same as the createTransaction but will also create a periodic sampler that will produce a activity and duration graph for the given transaction flavour.

Summary

These three features of FRAPI are a small select sample of the functions available, and offer some unique and powerful options to developers that are looking for ways to track performance and debug code. There are many other methods available via the FRAPI interface many of which are helpful for both tracking performance and debugging errors. For more information on the available methods please review the Java docs.

Keeping it real – excluding the effect of long running requests in FusionReactor



Something that comes up when speaking to FusionReactor customers is the need to handle long running requests.  In FusionReactor as with many APM solutions there is a continuous running aggregate of the average run-time of the web requests.

Unfortunately if you have a single request that has to run for a long time it can cause this number to become skewed; essentially the average run-time of requests can end up being longer than it really is just because of this one request e.g. often a maintenance job run by the system admins, which is not so important when you are interested in real user experience.

Scenario 1 – Excluding a single long running request which is skewing performance metrics

Details

Let us assume you have a running web application, in this instance running on a tomcat server.  Now let’s assume that you have a request that is run via this application as some routine job.   This job typically runs over a minute and has a negative affect on the average run-time of your server.    We would like this request to be ignored by FusionReactor and not included in the metrics calculated, but every other request should continue to be tracked.

Goal

The goal is to eliminate this request from the metrics, and get a better picture of what the overall performance of the server is.

Using this example URL for the job: /JTA/performance/jdbc/jdbc30secondrating.jsp

Steps

FusionReactor has this feature right out of the box, FR has the ability to restrict requests from almost every feature that it offers.  There are a few different ways to go about adding this restriction, the simplest (but not always possible solution) is to simply click the ‘Stop Tracking’ button, next to the request you want to ignore, on the Request -> Activity screen.   This has the disadvantage of requiring the request to be running before it can be removed from the statistics. It also will not affect any statistics that have already been calculated from this request. This approach will only affect that single request, and as such is of limited usefulness when applying it to a routine job.   I mention it here as it is useful when running a job manually that you do not want to be tracked.

The better approach is to simply enter the request details prior to it entering the system.

  1. Go to FusionReactor -> Restrictions
  2. Enter the details of the request that you want to ignore from metrics. (help with settings)

We have some options here, if the request always comes from the same host, we can also add the host name check to the restrictions, this means FusionReactor will only ignore the request if it comes from the matching host name.

Another approach, which is quite a neat feature, is to filter the request based on the query parameters. So if this job is in fact the same end point as some other request, but contains specific query parameters, then we can filter on those, and we can actually add an extra query parameter to the request when it is the job.

For example, if we have the endpoint /JTA/performance/report.jsp, but this request by itself is part of the usual use model of the application. We can actually alter the request to be /JTA/performance/report.jsp?__fr_ignore=true, this should not have any effect on your request, unless you happen to use the query parameter __fr_ignore; which seems unlikely.   So now by changing the “Request” field of the restriction form to include this parameter, and set the “Parameter” field to “Check”, you can make FusionReactor ignore this request when the parameter __fr_ignore=true is sent, and continue to track it when it is not.

I should point out at this point that if you use the “Exact Match” strategy then you will also have to include any other parameters that are part of the request.   Another alternative is to use the “Regular Expression” strategy, covered later.

So now that the restriction is configured, clicking save will add this restriction, visible below the form, in real time, and any new request that match this pattern will be ignored from FusionReactor.

long_req_blog_1

Outcome – we’re keeping it real 🙂

At this point FusionReactor will now be ignoring the request that you have added to the restrictions, and will no longer be included it in the metrics for the server.    This will hopefully improve the rating of the server among your peers as it will now seem that by magic the server is performing better.

 

Scenario 2 – Using regex to exclude multiple tasks affecting your server performance rating

Similar to the previous scenario, but this time we have a whole sub section of the application that is only used by the system administrators to affect changes on the database, or perform clean up tasks.

Details

Lets us imagine that we have a number of administrative tasks, such as account merge, account removal etc.  These are not performed that often, but never the less do take some time.   These requests can then affect the overall statistics of the server, making it seem busier or less efficient than it actually is.

Goal

The goal here is to identify these administrative tasks and remove them from the request tracking.   We can identify these requests as they have the string /system/admin/ in the URL.   This being the root of all the system administrator tasks that we want to ignore.    Once approach would be to enter all the URLs one by one in the same way we did above.  The disadvantage is that if new jobs would be entered, we would need to remember to include the individual URL.  A much better approach is to use the “Regular Expression” strategy to ignore all the requests by using a single rule.

Steps

The way to add this rule is basically the same as the single rule, we went through above. The only real difference here is the use of the “Regular Expression” strategy and the Request actually being the regex and not the URL as it was above.

  1. Again we go to FusionReactor -> Restrictions
  2. Now we set the “Match Strategy” to “Regular Expression”
  3. Enter the regex .*/system/admin/.* into the “Request” field
  4. now simply save the form

You will immediately see the restriction enter the list below the form, and FusionReactor will immediately start ignoring any new request that contain the pattern /system/admin/.

Outcome

We have now, in these very simple steps, removed all system administrator request from being tracked into the FusionReactor statistics for your application.   You will now get a much clearer view of how your application is really performing.

long_req_blog_2

Additional

Regex, or Regular Expressions, are a very powerful tool for any language. However just like many, many things in programming the implementation of regex can vary from language to language.  FusionReactor uses the Java regex engine.    Plenty of documentation on the Java regex exists, here are a few links: FR quick list, Oracle Docs, online Java regex evaluator

How to keep your application / server responding when you’re running out of memory – FusionReactor Survival Strategy


FusionReactor has many great features one of the most overlooked and possibly one of the most powerful is EnGuard Crash Protection (CP).   This feature is able to alert you as well as prevent your servers from falling over by limiting the load based on a variety of criteria.

In this post I will walk you through how to setup the various settings for CP and the benefits of using these features.

Scenario – Application Server is running low on memory

Let us imagine the situation where, for whatever reason, the application server that you are running on is consistently running out of memory. By using FusionReactor’s Crash Protection features we can be alerted to the situation and take steps to keep the system / application operational.   Of course you will be investigating the cause of the memory issue, but in the mean time FusionReactor can buy you the time to ensure that service levels are maintained and you have minimized impact to your customers/business.   By using the FusionReactor’s “WebRequest Memory Protection” feature, you can limit the traffic on your server by either queuing or rejecting requests based on the current JVM memory usage.   FusionReactor can also invoke system garbage collections if we exceed the threshold values, to help reduce the over all memory usage of the application.

Goal

In this situation the goal is to reduce the concurrent requests running on the application when the memory usage exceeds a specific value. What we want to do is make FusionReactor queue requests when the memory usage exceeds 80% for more that 15 seconds.

Steps

Our first action here is to enable the Crash Protection features. This does not require a restart and will take effect immediately.

  • Go to Protection -> Settings
  • Click on “WebRequest Memory Protection”
    1. Change the “WebRequest Memory Protection Threshold” to 80%
    2. Change the “Minimum condition Duration” to 15
    3. Change the “Memory Protection Strategy” to “Queue and Email Notification” or “Queue”
    4. Enable “Automatic Garbage Collection Trigger”
  • Click “Save FusionReactor Settings”
  • CP Blog

If you are using the “Queue and Email Notifications” you will need to enable email notifications under Protection -> Settings -> Email Settings, you will also need valid Email settings in the FusionReactor -> Settings -> Email Settings page.

Results

When the system is setup correctly you will begin to see FusionReactor start queuing requests as they come in. These requests will be queued for 60 seconds, (configurable in the protection settings), before they timeout.    This request queue is nicely displayed in the Request -> Activity screen, clearly showing the time in the queue and the time until the request is rejected.    The request will be served as normal if the memory usage falls below 80% before the request times out.

The requests that are rejected based on the queue timeout, are tracked into a separate screen, Requests -> Rejections, and a summary is available on the WebMetrics page. Additionally the garbage collection metrics are tracked on the Resources -> Garbage Collection page (from FusionReactor 5 and later)

So hopefully at this stage you will have saved your system from collapsing from an out of memory error, kept the server running and bought yourself more time to diagnose the initial cause of the memory issues on the system.     FusionReactor saves the day (AGAIN !).

Advanced Option

In addition to the setting described above the following options are available to improve the effectiveness of FusionReactor Crash Protection.

Garbage Collection

When using the memory protection settings feature, you might have noticed the “Automatic Garbage Collection Trigger”. This feature is a very useful tool if you are experiencing memory issues on your application server. By using this setting you can configure FusionReactor to perform a garbage collection (GC) when the request starts.  As you may be aware performing a garbage collection can be an expensive operation, as such, FusionReactor comes with a rate limiting option. The “Minimum Garbage Collection Interval” setting allows you to set the minimum time that must elapse before FusionReactor will invoke another garbage collection.

EULA V3 – FusionReactor 6

INTERGRAL SOFTWARE END USER LICENSE AGREEMENT (“EULA”)

THE FOLLOWING EULA APPLIES TO FUSIONREACTOR VERSION 6 AND ITS MINOR/MICRO UPDATES ONLY

IMPORTANT: CAREFULLY READ THE FOLLOWING LICENSE AGREEMENT. THIS END USER LICENSE AGREEMENT (“EULA”) IS A LEGAL AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR, IF PURCHASED OR OTHERWISE ACQUIRED BY OR FOR AN ENTITY, AN ENTITY) AND INTERGRAL. YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS AGREEMENT BY SELECTING THE “ACCEPT” OPTION OR DOWNLOADING THE SOFTWARE OR BY INSTALLING, USING, OR COPYING THE SOFTWARE. IF YOU DO NOT AGREE TO BE BOUND BY THESE TERMS THEN DO NOT INSTALL, COPY, DOWNLOAD OR OTHERWISE USE THE SOFTWARE. THIS EULA SHALL APPLY ONLY TO THE SOFTWARE SUPPLIED BY INTERGRAL HEREWITH REGARDLESS OF WHETHER OTHER SOFTWARE IS REFERRED TO OR DESCRIBED HEREIN.

Definitions

“INTERGRAL” means INTERGRAL Information Solutions GmbH and its licensors, if any.

“Developer Version” means a version or edition of the Software to be used only for design, development and evaluation purposes.

“Free Version” means a version or edition of the Software that may have limited features, and may stop operating after a given amount of time.

“Trial Version” means a version or edition of the Software to be used only for review, demonstration and evaluation purposes. The Trial Version may have limited features, and may stop operating after a given amount of time.

“Full Version” means a version or edition of the Software that is not a Developer Version nor a Trial Version of the Software nor a Free Version of the Software.

“Accessible Code” means source code that is unprotected and accessible.

“Protected Code” means any source code that is protected against access by INTERGRAL or a third party and is not accessible under this EULA.

“Fees” mean all fees and expenses payable by the Licensee to INTERGRAL in acquiring the Software and as applicable any Subscription or User Licenses.

“Software” means only the INTERGRAL software and third party software programs, in each case, supplied by INTERGRAL together with this EULA, including its Accessible Code and Protected Code and any corresponding documentation, online or electronic documentation, printed materials, and associated media. Any updates to such Software that you are entitled to receive and that have been provided to you by INTERGRAL shall also mean Software for purposes of this Agreement.

License Grant
The Software is subject to the terms and conditions of this Agreement. INTERGRAL hereby grants, and you accept, the right and license to install and use the Software provided that you do not use, copy, or install the Software on more than the number of computers permitted by license, or permit the use, copying, or installation by more users on more computers than the number permitted by the license.

You may make one copy of the Software in machine-readable form solely for backup purposes. You must reproduce on any such copy all copyright notices and any other proprietary legends on the original copy of the Software.

The Software is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. INTERGRAL reserves all intellectual property rights, including copyrights and trademark rights. Your license rights under this EULA are non-exclusive.

License Restrictions

Restrictions on Use
Other than as expressly set forth above, you may not make or distribute copies of the Software, or electronically transfer the Software from one computer to another or over a network.

You may not decompile, “reverse-engineer”, disassemble, or otherwise attempt to derive the source code for the Software.

You may not use the database portion of the Software in connection with any software other than the Software.

You shall not (A) in the aggregate, install or use more than one copy of the Trial Version of the Software, (B) download the Trial Version of the Software under more than one username, (C) alter the contents of a hard drive or computer system to enable the use of the Trial Version of the Software for an aggregate period in excess of the trial period for one license to such Trial Version, (D) disclose the results of software performance benchmarks obtained using the Trial Version to any third party without INTERGRAL’s prior written consent, (E) use the Trial Version for any application deployment or ultimate production purpose, or (F) use the Trial Version of the Software for a purpose other than the sole purpose of determining whether to purchase a license to a Full Version or a Developer Version of the software; provided, however, notwithstanding the foregoing, you are strictly prohibited from installing or using the Trial Version of the Software for any commercial training purpose.

You shall not use the Developer Version for any application deployment in a live or stand-by production environment or staging environment, in each case, including, without limitation, in any environment accessed by application end- users, including, but not limited to, servers, workstations, kiosks, and mobile computers. You shall not use the Software to develop any application having the same primary function as the Software.

Subject to the terms and conditions of this Agreement you must at all times ensure that the Software is not used for rental, timesharing, subscription service, hosting, outsourcing, or as part of a service or consulting practice to a third-party, without first obtaining the express written consent of INTERGRAL.

Restrictions on Alteration
You may not alter, merge, adapt, translate or modify the Software or create any derivative work of the Software or its accompanying documentation. Derivative works include but are not limited to translations. You may not alter any files or libraries in any portion of the Software. You may not reproduce the database portion or create any tables or reports relating to the database portion.

Restrictions on Copying
You may not copy any part of the Software except to the extent that licensed use inherently demands the creation of a temporary copy stored in computer memory and not permanently affixed on storage medium. You may make one archival copy which must be stored on a medium other than a computer hard drive.

Restrictions on Transfer
Without first obtaining the express written consent of INTERGRAL, you may not assign your rights and obligations under this Agreement, or redistribute, encumber, sell, rent, lease, sublicense, or otherwise transfer your rights to the Software. You may not sell or transfer any Software purchased under a volume discount. You may not sell or transfer any Trial Version or Free Version of the Software.

Permitted Fixes
Notwithstanding anything else in this EULA but subject to the terms and conditions contained herein, the Licensee is permitted to modify the Accessible Code in the Software to develop bug fixes, customizations or additional features solely for their internal purposes of using the Software.

Upgrades
If this copy of the Software is an upgrade from an earlier version of the Software, it is provided to you on a license exchange basis. You agree by your installation and use of this copy of the Software to voluntarily terminate your EULA with respect to such prior license to the Software and that you will not continue to install or use such prior license of the Software or transfer it to another person or entity.

Ownership
The foregoing grants of rights give you limited license to use the Software. Except as expressly provided in this Agreement, INTERGRAL remain the owner of all right, title and interest in the Software. All rights not specifically granted in this EULA are reserved by INTERGRAL.

Fees
The Licensee must pay all Fees by their due date. Failure to pay Fees by the due date will result in the immediate termination of the licenses granted under this EULA.

You are responsible for reviewing the Software’s website for changes in the fees, including, but not limited to, subscription fees and payment terms.

TERMINATION
Without prejudice to any other rights and in addition to any other termination rights in this EULA, INTERGRAL may terminate this EULA if the Licensee fails to comply with the terms and conditions of this EULA. Immediately upon termination of a license granted under this EULA, the Licensee must at its own cost remove all copies of the Software including all Accessible Code from its computer systems and provide INTERGRAL with written certification that it has destroyed all copies of the Software including all Accessible Code in its possession, custody or control.

LIMITED WARRANTY AND DISCLAIMER
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN THE JURISDICTION IN WHICH THE SOFTWARE IS PROVIDED, INTERGRAL PROVIDES THE SOFTWARE AS IS AND WITH ALL FAULTS, AND EXCEPT OTHERWISE EXPRESSLY CONTAINED IN THE EULA, HEREBY DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED OR STATUTORY.

INTERGRAL MAKES NO WARRANTY THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS OR OPERATE UNDER YOUR SPECIFIC CONDITIONS OF USE. INTERGRAL MAKES NO WARRANTY THAT OPERATION OF THE SOFTWARE WILL BE SECURE, ERROR FREE, OR FREE FROM INTERRUPTION. YOU MUST DETERMINE WHETHER THE SOFTWARE SUFFICIENTLY MEETS YOUR REQUIREMENTS FOR SECURITY AND UNINTERRUPTABILITY. YOU BEAR SOLE RESPONSIBILITY AND ALL LIABILITY FOR ANY LOSS INCURRED DUE TO FAILURE OF THE SOFTWARE TO MEET YOUR REQUIREMENTS. INTERGRAL WILL NOT, UNDER ANY CIRCUMSTANCES, BE RESPONSIBLE OR LIABLE FOR THE LOSS OF DATA ON ANY COMPUTER OR INFORMATION STORAGE DEVICE. INTERGRAL DISCLAIM ALL OTHER WARRANTIES AND REPRESENTATIONS, WHETHER EXPRESS, IMPLIED, OR OTHERWISE, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE IS NOT DESIGNED, INTENDED OR LICENSED FOR USE IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL- SAFE CONTROLS, INCLUDING WITHOUT LIMITATION, THE DESIGN, CONSTRUCTION, MAINTENANCE OR OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, AND LIFE SUPPORT OR WEAPONS SYSTEMS. INTERGRAL SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR SUCH PURPOSES.

INTERGRAL PROVIDES NO REMEDIES OR WARRANTIES, WHETHER EXPRESS OR IMPLIED, FOR THE TRIAL VERSION AND THE FREE VERSION OF THE SOFTWARE. THE TRIAL VERSION AND THE FREE VERSION OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITH ALL FAULTS AND HEREBY DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED OR STATUTORY.

UNLESS OTHERWISE EXPLICITLY AGREED TO IN WRITING BY INTERGRAL, INTERGRAL MAKES NO OTHER WARRANTIES, EXPRESS OR IMPLIED, IN FACT OR IN LAW, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OTHER THAN AS SET FORTH IN THIS AGREEMENT OR IN THE LIMITED WARRANTY DOCUMENTS PROVIDED WITH THE SOFTWARE.

IF APPLICABLE LAW REQUIRES ANY WARRANTIES WITH RESPECT TO THE SOFTWARE, ALL SUCH WARRANTIES ARE LIMITED IN DURATION TO THIRTY (30) DAYS FROM THE DATE OF DELIVERY.

NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY INTERGRAL, ITS DEALERS, DISTRIBUTORS, AGENTS OR EMPLOYEES SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF ANY WARRANTY PROVIDED HEREIN.

LIMITED REMEDY
YOUR REMEDY FOR A BREACH OF THIS AGREEMENT OR OF ANY WARRANTY INCLUDED IN THIS AGREEMENT IS THE CORRECTION OR REPLACEMENT OF THE SOFTWARE. SELECTION OF WHETHER TO CORRECT OR REPLACE SHALL BE SOLELY AT THE DISCRETION OF INTERGRAL. INTERGRAL RESERVES THE RIGHT TO SUBSTITUTE A FUNCTIONALLY EQUIVALENT COPY OF THE SOFTWARE AS A REPLACEMENT. IF INTERGRAL IS UNABLE TO PROVIDE A REPLACEMENT OR SUBSTITUTE SOFTWARE OR CORRECTIONS TO THE SOFTWARE, YOUR SOLE ALTERNATE REMEDY SHALL BE A REFUND OF THE PURCHASE PRICE FOR THE SOFTWARE EXCLUSIVE OF ANY COSTS FOR SHIPPING AND HANDLING.

ANY CLAIM MUST BE MADE WITHIN THE APPLICABLE WARRANTY PERIOD. ALL WARRANTIES COVER ONLY DEFECTS ARISING UNDER NORMAL USE AND DO NOT INCLUDE MALFUNCTIONS OR FAILURE RESULTING FROM MISUSE, ABUSE, NEGLECT, ALTERATION, MISAPPLICATION, PROBLEMS WITH DATA NETWORKS, PROBLEMS WITH ELECTRICAL POWER, ACTS OF NATURE, UNUSUAL TEMPERATURES OR HUMIDITY, IMPROPER INSTALLATION, DAMAGE TO MEDIA OR DAMAGE DETERMINED BY INTERGRAL TO HAVE BEEN CAUSED BY YOU. ALL LIMITED WARRANTIES ON THE SOFTWARE ARE GRANTED ONLY TO YOU AND ARE NON- TRANSFERABLE.

YOU AGREE TO INDEMNIFY AND HOLD INTERGRAL HARMLESS FROM ALL CLAIMS, JUDGMENTS, LIABILITIES, EXPENSES, OR COSTS ARISING FROM YOUR BREACH OF THIS AGREEMENT AND/OR ACTS OR OMISSIONS. THIS REMEDY IS THE SOLE AND EXCLUSIVE REMEDY AVAILABLE TO YOU FOR BREACH OF EXPRESS OR IMPLIED WARRANTIES WITH RESPECT TO THE SOFTWARE AND RELATED DOCUMENTATION.

LIMITATION OF LIABILITY
UNDER NO CIRCUMSTANCES SHALL INTERGRAL, ITS DIRECTORS, OFFICERS, EMPLOYEES AND AGENTS BE LIABLE TO YOU OR ANY OTHER PARTY FOR INDIRECT, CONSEQUENTIAL, SPECIAL, INCIDENTAL, PUNITIVE, OR EXEMPLARY DAMAGES OF ANY KIND (INCLUDING LOST REVENUES OR PROFITS OR LOSS OF BUSINESS) RESULTING FROM THIS AGREEMENT, OR FROM THE FURNISHING, PERFORMANCE, INSTALLATION, OR USE OF THE SOFTWARE, WHETHER DUE TO A BREACH OF CONTRACT, BREACH OF WARRANTY, OR THE NEGLIGENCE OF INTERGRAL OR ANY OTHER PARTY, EVEN IF INTERGRAL IS ADVISED BEFOREHAND OF THE POSSIBILITY OF SUCH DAMAGES. TO THE EXTENT THAT THE APPLICABLE JURISDICTION LIMITS INTERGRAL’S ABILITY TO DISCLAIM ANY IMPLIED WARRANTIES, THIS DISCLAIMER SHALL BE EFFECTIVE TO THE MAXIMUM EXTENT PERMITTED. INTERGRAL’S LIABILITY UNDER THIS AGREEMENT WILL NOT, IN ANY EVENT, EXCEED THE LICENSE FEES YOU PAID FOR THE SOFTWARE, IF ANY.

Indemnification
To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless INTERGRAL, its directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys fees) arising out of or accruing from (a) your use of the Software, (b) any application you develop on the Software that infringes any copyright, trademark, trade secret, trade dress, patent or other intellectual property right of any person or defames any person or violates their rights of publicity or privacy, and (c) any non- compliance by you with this License Agreement.

Confidentiality
The Software contains trade secrets and proprietary know-how that belong to INTERGRAL and it is being made available to you in strict confidence. ANY USE OR DISCLOSURE OF THE SOFTWARE, OR OF ITS ALGORITHMS, PROTOCOLS OR INTERFACES, OTHER THAN IN STRICT ACCORDANCE WITH THIS LICENSE AGREEMENT, MAY BE ACTIONABLE AS A VIOLATION OF OUR TRADE SECRET RIGHTS.

Publicity Rights
Licensee grants INTERGRAL the right to include Licensee as a customer in Software promotional material. Licensee can deny INTERGRAL this right at any time by submitting a written request via email to SALES@INTERGRAL.COM, requesting to be excluded from Software promotional material. Requests made after purchasing may take thirty (30) calendar days to process.

Use of Decompiler
The Software includes decompiling functionality (“Decompiler”) that enables reproducing source code from the original binary code. You hereby acknowledge that the binary code and source code may be protected by copyright, trademark and other other laws which may prohibit you from decompiling them and/or using Decompiler. Before using Decompiler, you should make sure that the decompilation is not prohibited by any applicable license agreement of the application and/or original binary code (except to the extent that you may be expressly permitted under applicable law) or that you have obtained permission to decompile the code from the copyright owner. Using Decompiler is entirely optional. INTERGRAL does neither encourage nor condone the use of the Decompiler and disclaims any liability for your use of Decompiler in violation of applicable laws.

Use of Debugger
The Software includes debugging functionality (“Debugger”) that enables debugging programs that may contain binary code, source code and intellectual property protected by copyright, trademark, patent and other other laws which may prohibit you from debugging them and/or using Debugger. Before using Debugger, you should make sure that debugging is not prohibited by any applicable license agreement of the program and/or original binary code (except to the extent that you may be expressly permitted under applicable law), or by other protecting laws, or that you have obtained permission to debug the program from all legal protection owner(s). Using Debugger is entirely optional. INTERGRAL does neither encourage nor condone the use of the Debugger and disclaims any liability for your use of Debugger in violation of applicable laws.

Third Party Software
Any software provided along with the Software that is associated with a separate license agreement is licensed to you under the terms of that license agreement. This license does not apply to those portions of the Software. Copies of these third party licenses are included in all copies of the Software. By accepting this EULA, you are also accepting the additional terms.

RESTRICTIONS
United States: If the Software is acquired by the Licensee in the United States, the Licensee acknowledges: (a) the Software is subject to U.S. export jurisdiction and agrees to comply with all applicable international and national laws that apply to the Software, including the U.S. Export Administration Regulations, as well as end-user, end- use, and destination restrictions issued by U.S. and other governments and notwithstanding the above; and (b) the provisions of the USA Uniform Computer Information Transaction Act do not apply to this EULA.

General: The export of the Software from the country of original purchase may be subject to control or restriction by applicable local law. Licensee is solely responsible for determining the existence and application of any such law to any proposed export and for obtaining any needed authorization. Licensee agrees not to export the Software from any country in violation of applicable legal restrictions on such export.

Governing Law, Jurisdiction and Costs
This EULA is governed by the laws of Baden-Wuerttemberg, Germany without regard to Baden-Wuerttemberg’s conflict or choice of law provisions. Exclusive jurisdiction and place of performance is Boeblingen, Germany, as long as permitted by applicable law. The United Nations Convention for the International Sale of Goods shall not apply.

Changes to the License Agreement
INTERGRAL may make changes to the License Agreement as it distributes new versions of the Software. When these changes are made, INTERGRAL will make a new version of the License Agreement available on the website where the Software is made available.

Entire Agreement and Severability
This EULA is the entire agreement between INTERGRAL and you, and supersedes all prior or contemporaneous agreements or understandings, whether oral or written any other communications or advertising with respect to the Software; this EULA may be modified only by written agreement signed by authorized representatives of both you and INTERGRAL. No INTERGRAL dealer or agent is authorized to make any amendment to this EULA.

If any provision of this EULA shall be held to be invalid or unenforceable, the remainder of this EULA shall remain in full force and effect. All rights not expressly granted in this agreement are retained by INTERGRAL. To the extent any express or implied restrictions are not permitted by applicable laws, these express or implied restrictions shall remain in force and effect to the maximum extent permitted by such applicable laws. The failure or delay of INTERGRAL to exercise any of its rights under this EULA or upon any breach of this EULA shall not be deemed a waiver of those rights or of the breach. You agree that any varying or additional terms contained in any purchase order or other written notification or document issued by you in relation to the Software licensed hereunder shall be of no effect.

INTERGRAL and other trademarks contained in the Software are trademarks or registered trademarks of INTERGRAL Information Solutions GmbH. Third party trademarks, trade names, product names and logos may be the trademarks or registered trademarks of their respective owners. You may not remove or alter any trademark, trade names, product names, logo, copyright or other proprietary notices, legends, symbols or labels in the Software. This EULA does not authorize you to use INTERGRAL’s or its licensors’ names or any of their respective trademarks.