JON Agent Automatic Upgrade Fails from 2.3 to 2.3.1 - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Issue

After upgrading from 2.3 to 2.3.1, the JON agent fails to upgrade because it is trying to write a file outside of the directory that it is installed in. The JON agent on our servers is installed in /opt/jboss/rhq-agent and the JON agent tries to write the upgrade jar file to /opt/jboss, rather than /opt/jboss/rhq-agent or some other valid temporary location. Is there a way to control where the installer tries to put the upgrade jar file, since we have intentionally removed the write but from /opt/jboss on our servers?

Environment

JBoss Operations Network (JON) 2.3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)