Chapter 2. Known issues

Red Hat JBoss A-MQ's console is normally launched using the fusemq command which is fully functional. However, Red Hat JBoss A-MQ also includes a generic Apache Karaf shell that can be launched using the shell command. In the generic shell, the help command throws an exception.

We do not recommend using the generic Apache Karaf shell.

The ls console command, which is used for inspecting OSGi bundles, will throw an exception when listing the contents of some bundles.

On certain 64bit Windows platforms you need Microsoft Visual C++ 2008 Redistributable Package (x64) installed or Red Hat JBoss A-MQ will not start.

It was found that the Java hashCode() method implementation was susceptible to predictable hash collisions. A remote attacker could use this flaw to cause the Jetty HTTP server (a component of Apache Karaf used by Red Hat JBoss Fuse) to use an excessive amount of CPU time by sending an HTTP request with a large number of parameters whose names map to the same hash value. This update introduces a limit of 1000 on the number of parameters processed per request to mitigate this issue.

When this happens, click the unpin button on the Properties view tool bar to populate the Properties view with the status or properties of a newly selected process.

When this happens, you may not be able to run the project as a Local Camel Context. You can force the downloading of missing Maven dependencies by right-clicking the newly created project's root folder (not the pom.xml file) in Package Explorer/Project Explorer, and selecting Maven Update Project with the Force Update of Snapshots/Releases option enabled.

For example, switching quickly between the data format tabs of a Marshal or Unmarshal node can cause this exception.

Typically, this happens when, for example, you have a route that contains a choice node with its own internal target endpoints followed by another target endpoint outside the choice node. Instead of one flow in which messages first traverse the choice node then continue through the trailing endpoint, the route editor's Design view creates and inserts a duplicate<from/> element inside the <route/> element to generate two separate flows—one going through the choice node, and the other going directly to the trailing endpoint.

Used similarly, these EIPs also generate duplicate <from/> elements:

When you create such routes using these EIPs, and you want to retain a single flow, create the routes in Source view, not Design view, to avoid generating a duplicate <from/> element in your route.