Red Hat Training

A Red Hat training course is available for Red Hat Fuse

9.2. Error and Warn Messages

The Red Hat JBoss Fuse Plugins for JON components generate the following error and warning messages:

CuratorFabricRegistryImpl component

Note
JBoss Fuse 6.1. This component implements connections to the Zookeeper registry using Curator.
MessageDescription
WARN: Connection state changed to <connectionState>
While reading profiles from Zookeeper, the state of the connection changed to SUSPENDED or to LOST.
You can ignore this warning if no ERROR message were generated during the read operation.

FabricContainerDiscoveryComponent component

Note
JBoss Fuse 6.x. This component is used for discovering Fabrics.
MessageDescription
WARN: Unable to read JMX URL from etc/org.apache.karaf.management.cfg
A JMX URL discovery error occurred. The resource will try to use the default JMX URL, but it could end up connecting to the wrong process if the default URL is incorrect.
Fix the resource connections using the JON server console.
WARN: Container uses Fabric Zookeeper registry, using default JMX user
A Zookeeper URL was discovered, and the resource was configured using the default JMX user admin and password admin.
If these credentials are incorrect, you must change them in the connection settings using the JON server console.
WARN: Error getting JMX properties from Fabric container: <message>, using default connection properties, <error>
An error occurred while discovering JMX properties in configuration files.
If these properties differ from those in the connection settings, you must change the connection settings using the JON server console.
WARN: Looking for Zookeeper.url in data/cache/**/zookeeper.config
This warning occurs during discovery of the root container's Zookeeper URL using the zookeeper.config file.
The zookeeper URL will not be discovered if the Fabric is created after container discovery occurs. In that case, you must configure the Zookeeper URL in the connection settings, using the JON server console.
Otherwise, you can ignore this warning.
WARN: Error reading <propertiesFile>An error occurred while reading the specified properties file. Check the file's permissions.
WARN: File <propertiesFile> does not exist
The specified properties file does not exist. This could indicate a potentially corrupt installation of JBoss Fuse 6.x.
Reinstall JBoss Fuse 6.x to replace the specified missing or corrupted properties file.

FabricProfileGroupManager component

Note
FuseSource 7.x, and JBoss Fuse 6.x. This component is used for discovering fabric profiles.
MessageDescription
WARN: Disconnected from Fabric Registry
The resource was disconnected from the Zookeeper registry. The cause is either a user networking issue or the remote Zookeeper server is down or unreachable.
The component reconnects to the Zookeeper registry automatically, so you can typically ignore this warning. However, disconnects can become an issue if they happen too frequently or during profile accesses, causing network connectivity issues for Zookeeper servers.
Check your network environment. If the Zookeeper server is up, but unreachable, report the error to Red Hat Technical Support (see Note).

FabricProfileGroupsComponent component

Note
JBoss Fuse 6.x and higher. This component is used for discovering profile groups in server.log.
MessageDescription
WARN: No default property with Registry URL * specified, using defaults: <defaults>
A default registry configuration was not specified using the registry url *, so the server plugin will use the default settings.
If the default settings are satisfactory (they can be seen when adding a new registry entry for the server plugin), this error is a non issue. Otherwise, you can add a default entry for the * URI with custom settings.

FuseMBeanDiscoveryComponent component

Note
FuseSource7.x, JBoss Fuse 6.x, and ServiceMix 3.x, 4.x. This component is used for discovering Fuse MBeans.
MessageDescription
WARN: Required property <name> is missing in Bean <beanName>, ignoring Bean for resource type <resourceType>
The specified bean could not be discovered because a required property is missing.
Report the error to Red Hat Technical Support (see Note).

FuseServerComponent component

Note
FuseSource7.x, JBoss Fuse 6.x, and ServiceMix 3.x, 4.x. This component is used for connecting to Fuse servers.
MessageDescription
WARN: Failed to connect to <resourceType>[<resourceKey>]., <error message>
The specified error occurred when attempting to start the specified resource.
Verify JMX connection parameters in JON server console's Connection Settings.
ERROR: Error closing EMS connection: <error>
The specified error occurred when attempting to stop the EMS.
Verify JMX connection parameters in JON server console's Connection Settings.

FuseServerDiscoveryComponent component

Note
FuseSource7.x, JBoss Fuse 6.x, and ServiceMix 3.x, 4.x. This component is used for discovering Fuse servers.
MessageDescription
WARN: Error when trying to discover Fuse Server process [<process>] (enable DEBUG for stack trace): <error>
A resource discovery runtime exception occurred.
Enable JON agent debug logging and send log with report to Red Hat Technical Support (see Note).
ERROR: Multiple resources with the same key (<duplicateKey>) were discovered—none will be reported to the plugin container! This most likely means that there are multiple java processes running with the same value for the <resourceKeyProperty> system property specified on their command lines. Here is the list of Resources: <duplicate resource list>
Indicates a duplicate resource. This error rarely occurs.
Each server resource is required to have a unique identifier (<resourceKey>). This exception occurs when multiple running servers share the same unique identifier (<duplicateKey>). The exception message provides a list of the running servers that share the same identifier (<duplicateKey>).
Report the error to Red Hat Technical Support (see Note).
WARN: Ignoring resource <resourceName> due to error: <error message>
The specified error occurred during resource discovery. The specified resource will be ignored due to the error described in the message.
Report the error to Red Hat Technical Support (see Note).
WARN: Unable to access <directory>
An error occurred while attempting to read the specified file system.
Check user permissions on the JON agent and fix as appropriate.
WARN: Missing property <logFile> in Fuse Server configuration
Indicates a log file property is missing in the plugin configuration. This very rarely occurs.
Report the error to Red Hat Technical Support (see Note).

JBossFuseContainerDiscoveryComponent component

Note
JBoss Fuse 6.x . This component is used for discovering JBoss Fuse containers.
MessageDescription
WARN: Container uses Fabric Zookeeper registry, using default JMX user
A Zookeeper URL was discovered, and the resource was configured using the default JMX user admin and password admin.
If these credentials do not match the JON server Connection Settings, change the connection settings to match those of the monitored Fuse container.
WARN: Error getting JMX properties from Fabric container: [<message>], using default connection properties, <error>
The specified error occurred when discovering JMX properties in configuration files.
If the configuration file properties do not match the default connection properties, you must change the configuration files to match the connection defaults.
WARN: Error reading <propertiesFile>
An error occurred while attempting to read the specified properties file.
Check file permissions and fix as appropriate.
WARN: File <propertiesFile> does not exist
The specified properties file does not exist.
This indicates the possibility of a corrupted installation. Report the error to Red Hat Technical Support (see Note).
WARN: Unable to read JMX URL from etc/org.apache.karaf.management.cfg
A JMX URL discovery error occurred. The resource will try to use the default JMX URL, but it could end up connecting to the wrong process if the default URL is incorrect.
Enter the correct JMX URL in the JON server console's Connection Settings.
WARN: Failed to find start script for JBoss Fuse server with command line [<commandLine>]—defaulting 'startScripFile' plugin config prop to [<startScript>].
The shell script used to start the Fuse server could not be autodiscovered. By default, the script is set to start or start.bat.
If this default start method differs from the plugin's default configuration property, you must change the start method in the JON server Connection Settings to start/stop the Fuse server from the JON console.

JvmStatUtility component

Note
FuseSource 7.x, JBoss Fuse 6.x, and ServiceMix 3.x, 4.x. This component is used for discovering JVMs.
MessageDescription
WARN: JDK does not support jvmstat—cannot discover JVMs using Sun jvmstat API; to fix this, run the RHQ Agent on a Sun JDK.Auto discovery of jvmstat is supported on Sun JVMs only. Switch to Sun JDK.
WARN: JVM with PID [<pid>] does not support attach-on-demandThe JVM does not support attach using the jvmstat API. Check the JON agent user access permissions, and run the agent using the same user ID.
ERROR: Failed to detach from JVM [<vmid>]. <error>
The specified error occurred while attempting to detach from the specified process. This rarely occurs.
Report the error to Red Hat Technical Support (see Note).

LinkedInFabricRegistryImpl component

Note
JBoss Fuse 6.x. This component implements connections to the Zookeeper registry using the linkedin-zk library.
MessageDescription
WARN: Disconnected from Fabric Registry
Disconnected from the Zookeeper registry while reading profiles from it.
This is an issue only if ERROR messages were generated while reading the profiles. However, this warning may indicate there are other network connection issues with the Zookeeper server.