{section}
{column}
h1. Introduction
Here is a list of issues you may encounter when running Petals ESB but that are not bugs. These problems may be due to a hardware configuration or to operating system restrictions.
{column}
{column:width=40%}
{panel:title=Table of contents}{toc:outline=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}
h1. General Issues
h2. Petals ESB is unreacting or freezed
*Operating system:* Windows (verified on XP and 7)
*Symptoms:*
* The Petals command line does not display anything new anymore.
* The last lines may be a normal log entry or an exception stack trace.
* JMX commands seems without effect. When you execute them (from the JConsole, from the Petals web console), there is no response.
* Other Petals scripts do not change anything. _stop.bat_ and _shutdown.bat_ do not work.
*Solutions to try:*
* Go in the Petals command line, give it the focus and type in _Enter_.
*Explanations:*
You have probably selected something in the DOS shell (e.g. the JMX URL of Petals).
This selection has blocked the underlying process (Petals). Consequently, all the requests have been waiting for the process to _come back_. By giving it the focus back (_enter_), the process is unblocked.
h2. Mime type 'text/html' installing or deploying a JBI archive
*Operating system:* All
*Symptoms:*
When installing a component or deploying services, I get the following error message:
{code}
The remote resource [http://server:port/context] is not a valid JBI archive: text/htm
{code}
*Explanations:*
If the installed archive is downloaded from Internet and it is needed to download it through a HTTP(s) proxy, perhaps have you forgotten to to configure your HTTP(s) proxy settings.
*Solution:*
Configure your HTTP(s) proxy settings editing the startup script to add your properties as JAVA_OPTS. Available properties to configure your HTTP(s) proxy are listed on the Java documentation: [Java networking and Proxies|http://download.oracle.com/javase/6/docs/technotes/guides/net/proxies.html].
{code}
if [ -z "$JAVA_OPTS" ]; then
JAVA_OPTS="-Xmx1024m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dhttp.proxyHost=proxy.company.com -Dhttp.proxyPort=8080"
fi
{code}
h2. Unable to connect to Petals ESB using JConsole or JVisualVM
*Operating system:* All
*Symptoms:*
Unable to connect to Petals ESB using JConsole or JVisualVM
*Explanations:*
Several root causes of the problem exist. See the possible causes [here|https://blogs.oracle.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole].
*Solutions:*
See the available solutions [here|https://blogs.oracle.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole].
h2. Petals is really slow
*Operating system:* All
*Symptoms:*
Deployment of new Petals artifacts is very slow, or the Petals File Transfer component is really slow.
*Explainations:*
Petals file creation and/or modification takes a lot of time compared to what it should be.
Several things can cause this kind of problem.
*Solutions:*
Check whether you have a firewall installed and if it inspects files.
If so, you should add an exception for the Petals home directory in the firewall configuration.
{excerpt-include:Known problems starting or stopping Petals ESB|nopanel=true}
{column}
h1. Introduction
Here is a list of issues you may encounter when running Petals ESB but that are not bugs. These problems may be due to a hardware configuration or to operating system restrictions.
{column}
{column:width=40%}
{panel:title=Table of contents}{toc:outline=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}
h1. General Issues
h2. Petals ESB is unreacting or freezed
*Operating system:* Windows (verified on XP and 7)
*Symptoms:*
* The Petals command line does not display anything new anymore.
* The last lines may be a normal log entry or an exception stack trace.
* JMX commands seems without effect. When you execute them (from the JConsole, from the Petals web console), there is no response.
* Other Petals scripts do not change anything. _stop.bat_ and _shutdown.bat_ do not work.
*Solutions to try:*
* Go in the Petals command line, give it the focus and type in _Enter_.
*Explanations:*
You have probably selected something in the DOS shell (e.g. the JMX URL of Petals).
This selection has blocked the underlying process (Petals). Consequently, all the requests have been waiting for the process to _come back_. By giving it the focus back (_enter_), the process is unblocked.
h2. Mime type 'text/html' installing or deploying a JBI archive
*Operating system:* All
*Symptoms:*
When installing a component or deploying services, I get the following error message:
{code}
The remote resource [http://server:port/context] is not a valid JBI archive: text/htm
{code}
*Explanations:*
If the installed archive is downloaded from Internet and it is needed to download it through a HTTP(s) proxy, perhaps have you forgotten to to configure your HTTP(s) proxy settings.
*Solution:*
Configure your HTTP(s) proxy settings editing the startup script to add your properties as JAVA_OPTS. Available properties to configure your HTTP(s) proxy are listed on the Java documentation: [Java networking and Proxies|http://download.oracle.com/javase/6/docs/technotes/guides/net/proxies.html].
{code}
if [ -z "$JAVA_OPTS" ]; then
JAVA_OPTS="-Xmx1024m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dhttp.proxyHost=proxy.company.com -Dhttp.proxyPort=8080"
fi
{code}
h2. Unable to connect to Petals ESB using JConsole or JVisualVM
*Operating system:* All
*Symptoms:*
Unable to connect to Petals ESB using JConsole or JVisualVM
*Explanations:*
Several root causes of the problem exist. See the possible causes [here|https://blogs.oracle.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole].
*Solutions:*
See the available solutions [here|https://blogs.oracle.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole].
h2. Petals is really slow
*Operating system:* All
*Symptoms:*
Deployment of new Petals artifacts is very slow, or the Petals File Transfer component is really slow.
*Explainations:*
Petals file creation and/or modification takes a lot of time compared to what it should be.
Several things can cause this kind of problem.
*Solutions:*
Check whether you have a firewall installed and if it inspects files.
If so, you should add an exception for the Petals home directory in the firewall configuration.
{excerpt-include:Known problems starting or stopping Petals ESB|nopanel=true}