Known Problems

Version 3 by Christophe DENEUX
on May 02, 2011 12:05.

<< Changes from 2 to 3

compared with

Version 4 by Christophe DENEUX
on Jun 29, 2011 17:57.

Changes from 4 to 5 >>

Key

This line was removed.

This word was removed. This word was added.

This line was added.

Changes (4)

View Page History

...

Here is a list of issues you may encounter with Petals ESB but that are not bugs.
These problems may be due to a hardware configuration or to operating system restrictions.

h1. Petals 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_.

\\
*Explainations:*
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.

h1. 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/html
{code}
*Explainations:*
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}

h1. Unable to start Petals: "Cannot bind to URL \[rmi://xx.yy.zz.tt:7700/jmxRmiConnector\]"

*Operating system:* All

*Symptoms:*

# You have configured your topology with several Petals nodes declared as slave,
# Your Petals node declared as master starts correctly,
# You try to start your Petals slave for the first time with this distributed topology,
# You get the following error message:
{code}
[Petals.Communication.RMIConnectorImpl]-SEVERE 2011-06-29 17:44:27,449 Failed to start JMX RMI connector service
java.io.IOException: Cannot bind to URL [rmi://10.10.124.57:7700/jmxRmiConnector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /10.10.124.47 is non-local host]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417)
at org.ow2.petals.communication.jmx.rmi.RMIConnector.start(RMIConnector.java:148)
at org.ow2.petals.communication.jmx.rmi.RMIConnector.startFc(RMIConnector.java)
at org.objectweb.fractal.julia.generated.Cbd2013d7_0.setFcContentState(BasicControllerMixin.java:8128)
at org.objectweb.fractal.julia.generated.Cbd2013d7_0.setFcStarted(BasicControllerMixin.java:8068)
at org.objectweb.fractal.julia.generated.C18c4c884_0.setFcStarted(INTERFACE[LifeCycleCoordinator])
at org.objectweb.fractal.julia.generated.C4eddf8e0_0.startFc$$0(BasicControllerMixin.java:4097)
at org.objectweb.fractal.julia.generated.C4eddf8e0_0.startFc(BasicControllerMixin.java:5095)
at org.objectweb.fractal.julia.generated.C18c4c884_0.startFc(INTERFACE[LifeCycleCoordinator])
at org.ow2.petals.kernel.server.FractalHelper.startComponent(FractalHelper.java:354)
at org.ow2.petals.kernel.server.PetalsServerImpl.startPetalsComposite(PetalsServerImpl.java:459)
at org.ow2.petals.kernel.server.PetalsServerImpl.start(PetalsServerImpl.java:176)
at org.ow2.petals.launcher.AbstractLauncher.start(AbstractLauncher.java:190)
at org.ow2.petals.launcher.AbstractLauncher.launch(AbstractLauncher.java:147)
at org.ow2.petals.distribution.platform.Main.main(Main.java:42)
{code}

*Solutions/Explanations:*

You have missed to configure the Petals container name in your $PETALS_HOME/conf/server.properties. The default Petals container name '0' is used and it is associated to Petals ESB master node that is configured in your topology with a diferrent IP adress that is not local to your Petals slave node.

h1. Unable to connect to Petals ESB using JConsole or JVisualVM

*Operating system:* All\\

*Symptom:* Unable to connect to Petals ESB using JConsole or JVisualVM

...

*Explanations:* Several root causes of the problem exist. See possible root causes here: [http://blogs.sun.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole]

*Solutions:* See solutions available here: [http://blogs.sun.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole]

Wiki

Helpful links

Known Problems

Changes (4)