Petals Starting Guide - day 1 & 2 (WSDL & Administration)

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Petals Starting Guide - day 1 & 2 (WSDL & Administration)

Mathieu Le Breton
Administrator
This post was updated on .
Any question about the day-1 or day-2 tutorial?
Post it here!

This thread might be empty for some time. But if you are here, it's because we can help.
Please start writing now. We will be more than happy to help.

I want to receive the Petals Starting Guide (for free)
Petals Link
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

Mathieu Le Breton
Administrator
Just transferring a message from a user running Petals ESB tutorial. What should I tell him ?

Dashamir wrote
Dear Mathieu,

I have not finished yet the tutorial, because I have been busy
last week, however I will try to finish it.
On the second tutorial, I could not start the web interface.
I get this error message on Tomcat Web Application Manager:

FAIL - Application at context path /petals-webconsole-ui-2.0.4 could not
be started

Since I don't have experience neither with Java nor with Tomcat,
it is a bit difficult for me to find and fix the problem.
Could you point out where I can find some help about solving
this problem?

Also, I am interested to know about how OpenESB compares to
Petals. If you could point out any comparisons between them,
this would be good. Our ESB expert insists on using OpenESB,
since he has some experience with it, it has WS-Security and
it is based on NetBeans. But I still would like to try
Petals for myself, and I hope that later I can convince people
that Petals is better than OpenESB.

Best regards,
Dashamir
Petals Link
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

Mathieu Le Breton
Administrator
== Forwarded from Dashamir ==
I am using for testing a standard Ubuntu desktop.
I have installed tomcat6 the standard way:
apt-get install tomcat6
etc.

From Tomcat Web Application Manager
(http://localhost:8080/manager/html/)
I see this Server Information:
Tomcat Version : Apache Tomcat/6.0.28
JVM Version : 1.6.0_20-b20
JVM Vendor : Sun Microsystems Inc.
OS Name : Linux
OS Version : 2.6.35-28-generic
OS Architecture : i386

I deploy the file petals-webconsole-ui-2.0.4.war
from the Web Application Manager
and when I try to 'start' this application, I get
the message: FAIL - Application at context path
/petals-webconsole-ui-2.0.4 could not be started

On the log file /var/log/tomcat6/localhost.2011-04-05.log
I see:
-----
Apr 5, 2011 6:17:45 PM org.apache.catalina.core.ApplicationContext log
INFO: HTMLManager: init: Associated with Deployer
'Catalina:type=Deployer,host=localhost'
Apr 5, 2011 6:17:45 PM org.apache.catalina.core.ApplicationContext log
INFO: HTMLManager: init: Global resources are available
Apr 5, 2011 6:17:45 PM org.apache.catalina.core.ApplicationContext log
INFO: HTMLManager: start: Starting web application at
'/petals-webconsole-ui-2.0.4'
Apr 5, 2011 6:17:45 PM org.apache.catalina.core.ApplicationContext log
INFO: HTMLManager: list: Listing contexts for virtual host 'localhost'
-----

On the log file /var/log/tomcat6/catalina.out
I see:
-----
Apr 5, 2011 6:17:45 PM org.apache.catalina.core.StandardContext
resourcesStart
SEVERE: Error starting static Resources
java.lang.IllegalArgumentException: Invalid or unreadable WAR file :
error in opening zip file
        at
org.apache.naming.resources.WARDirContext.setDocBase(WARDirContext.java:135)
        at
org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4249)
        at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4418)
        at
org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1276)
        at
org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:625)
        at
org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:136)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
        at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
        at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:636)
Apr 5, 2011 6:17:45 PM org.apache.catalina.core.StandardContext start
SEVERE: Error in resourceStart()
Apr 5, 2011 6:17:45 PM org.apache.catalina.core.StandardContext start
SEVERE: Error getConfigured
Apr 5, 2011 6:17:45 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/petals-webconsole-ui-2.0.4] startup failed due to
previous errors
Apr 5, 2011 6:17:45 PM org.apache.catalina.core.StandardContext stop
INFO: Container
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/petals-webconsole-ui-2.0.4]
has not been started
-----

Maybe it is just any stupid problem, but I am even more stupid,
so I cannot find it out.
Petals Link
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

Jérémie Doucy
This post has NOT been accepted by the mailing list yet.
Did you try to re download the war file from PEtALS web site, because this error
java.lang.IllegalArgumentException: Invalid or unreadable WAR file :
error in opening zip file
means that your war file is invalid.
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

stevec
In reply to this post by Mathieu Le Breton
Trying to follow the guide but have a couple of issues.

1/ When I try install the service assembly zips via the Webconsole I get the following error after selecting the zip file and clicking 'install':

Petals service error
Message :
Artefact content-type must be [application/zip] [application/x-zip-compressed] [application/x-sdlc]

I could see a similar error reported and fixed in a later release of the WebConsole  (2.1.SNAPSHOT) so tried deploying and using that but there are obviously other changes in that release requiring security setup so I backed out to 2.0.5 but this gives the same behaviour as the prescribed 2.0.4 version.

Regardless I went ahead and deployed the zips by dropping them in the platform install folder. Then they were visable via the Webconsole.

2/ The next step required me to install the petals-se-rmi zip via the web console - this also fails with the same error (artefact content-type must be application/zip..) so I deployed by dropping into the platform install folder. It seems to deploy and be started e.g.
  INFO 2011-05-12 13:52:22,548 [Petals.JBI-Management.InstallationServiceImpl]
    Installer of the component 'petals-se-rmi' loaded
  INFO 2011-05-12 13:52:22,611 [Petals.Container.Components.petals-se-rmi]
    INIT RMI engine
  INFO 2011-05-12 13:52:22,720 [Petals.Container.Components.petals-se-rmi]
    Starting RMI Service Engine...
  INFO 2011-05-12 13:52:22,720 [Petals.Container.Components.petals-se-rmi]
     - RMI Port : 1099
  INFO 2011-05-12 13:52:22,720 [Petals.Container.Components.petals-se-rmi]
     - Embedded : true
  INFO 2011-05-12 13:52:22,720 [Petals.Container.Components.petals-se-rmi]
     - Component Context Name : RMIComponentContext

Also on the Webconsole the rmi component is listed under Administration/Components with state of 'started', but when I go to the Test panel there is a error msg "RMI component not specified or disabled into configuration file"

I went thru the whole process again but this time with the 2.0.4 webconsole and doing all the deployments into the platform (bc-soap, then se-rmi, then a couple of service assembly zips) and then refreshed the domain on the Webconsole and voila the test panel is working? This all seems a little fragile.
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

Vincent Zurczak
Administrator
Hi Stevec,

stevec wrote
I went thru the whole process again but this time with the 2.0.4 webconsole and doing all the deployments into the platform (bc-soap, then se-rmi, then a couple of service assembly zips) and then refreshed the domain on the Webconsole and voila the test panel is working? This all seems a little fragile.
I have been through some of the problems you mentioned.
Making the console more robust and user-friendly is on our (long) TODO list.

To be honest, I don't know what is the future of the testing panel in the web console. For me, we should have an independent testing framework (relying on known bricks). We have also thought about creating a SoapUI plugin. But the decision is not mine, and I must confess the team is under a lot of pressure, working on other aspects of the bus.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

cippit_b
In reply to this post by Mathieu Le Breton
<quote author="Mathieu Le Breton">
== Forwarded from Dashamir ==

"I am using for testing a standard Ubuntu desktop."

"SEVERE: Error starting static Resources
java.lang.IllegalArgumentException: Invalid or unreadable WAR file :"

Try to launch tomcat as root, or try chmod 777 yourFile.war before the deployment
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

Mathieu Le Breton
Administrator
In reply to this post by stevec
Hi Stevec,

Problem 1/ => If you say it's a bug, then probably it is. Thanks for sharing your workaround :)

Problem 2/ => RMI needs to be enabled in the webconsole first. I fixed this on the guide very recently :
- Install Petals-SE-RMI in Petals ESB.
- Click Manage connections on the top of Webconsole page.
- Click on your server (should be localhost)
- Check petals-se-rmi component enabled and click Submit.


Cippit, thanks for the answer to the previous post !
Petals Link
spe
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

spe
I'm just starting out using Petals.  I'm on a 64bit, Windows 7 machine, using Tomcat 6.0.35.  On the second day tutorial, the startup.bat -C, I get the following error:

SEVERE 2012-01-26 13:34:59,430 [Petals.Communication.RMIConnectorImpl]
    Failed to start JMX RMI connector service
java.io.IOException: Cannot bind to URL [rmi://localhost:7700/jmxRmiConnector]: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:
        java.net.SocketTimeoutException: Read timed out]
        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:458)
        at org.ow2.petals.kernel.server.PetalsServerImpl.start(PetalsServerImpl.java:175)
        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)
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:
        java.net.SocketTimeoutException: Read timed out]
        at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:126)
        at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
        at javax.naming.InitialContext.bind(InitialContext.java:400)
        at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:625)
        at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412)
        ... 14 more
Caused by: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:
        java.net.SocketTimeoutException: Read timed out
        at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:209)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:359)
        at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
        at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:120)
        ... 18 more
Caused by: java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:129)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
        at java.io.DataInputStream.readByte(DataInputStream.java:248)
        at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:195)
        ... 21 more

Any ideas?  I'm new to Petals and ESB in general.  I appreciate the help!
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

Vincent Zurczak
Administrator
Hi,

Sorry for the delay.
Did you change values in the server.properties and topology.xml files?
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

petaleRose
In reply to this post by Mathieu Le Breton
Good morning dear administrator,

To the tutorial #1:

The "Petals_Getting_Started_5.wsdl" from the link is not working while trying to import it into petals studio version 1.3.1. The error coming out is: "You have to provide the interface name."

Can you tell me why?

Thank you.
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

Vincent Zurczak
Administrator
Hi,

petaleRose wrote
To the tutorial #1:

The "Petals_Getting_Started_5.wsdl" from the link is not working while trying to import it into petals studio version 1.3.1. The error coming out is: "You have to provide the interface name."

Can you tell me why?
This WSDL is a WSDL 2.0.
It used to be supported in previous versions of Petals Studio, but it is not anymore from Petals Studio 1.3. The reason is that depsite better features, WSDL 2.0 is not supported by many other tools in the Java world. Even Petals dropped its support for the moment.

We have to update the tutorial page about this.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

petaleRose
Tahnk you
Reply | Threaded
Open this post in threaded view
|

Petals Starting Guide - day 1-5: Tutorials for Linux also....?

petaleRose
In reply to this post by Mathieu Le Breton
Good morning  Mathieu,

i have an issue with these tutorials and i have started them from 1-3 under Windows OS; but for my thesis, i must work under Ubuntu (linux). So I need to install Petals ESB on a server having ubuntu and work with it. The configution is just so "different". If you please have a tutorial for UBUNTU-LINUX user, i will be sooo Glad to have it, in order for me to be able to go through all the tutorials.

Thank you so much.
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1-5: Tutorials for Linux also....?

Vincent Zurczak
Administrator
Hi,

Petals works on both Windows and Linux.
There are very few differences between the two when using Petals. The main difference is about the URL shapes. What's bothering you when moving to Ubuntu?
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1-5: Tutorials for Linux also....?

petaleRose
Thank you.

I just don't know where to place te .war file to get the webconsole working.

The folder structures of petals in WS and Ubuntu are not the same.

Thank you.
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1-5: Tutorials for Linux also....?

Vincent Zurczak
Administrator
Hi,

Go to your Tomcat location and install the WAR from the manager (http://localhost:8080/manager).
I think I already told you how to configure your Tomcat. That was in another reply. :)
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

infoder
In reply to this post by Mathieu Le Breton
hi,
I've probleme when i try to Install the five .ZIP Service-Assemblies your generated with Petals Studio. Could you tell me if i must do any think after this instalation, like i put it in systeme folder or other methode.
Thank's!
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

petaleRose
In reply to this post by Mathieu Le Breton
My components petals-se-rmi-1.1.1.zip and petals-bc-soap-4.0.4.zip that i've just downloaded are just not working  anymore while trying to intall it on my bus (petals-platform-3.1.1) both through the console and the copy paste in the ESB platform's /install folder. I'm using tomcat 7.1.2 on Ubuntu 11.10.

1 . petals-se-rmi-1.1.1.zip can be loaded but is on an "unknow" state. I'm getting this error while trying to "start" it:
Message :
    Server configuration already exist in the webconsole.xml
Cause :
    An internal error occured. Your request didn't complete.

    See details
    Continue

org.ow2.opensuit.core.error.NonLocalizedError: [Petals console error] Server configuration already exist in the webconsole.xml

    org.ow2.petals.tools.webconsole.uibeans.ServerFeatureUIBean.saveServer(ServerFeatureUIBean.java:118)
    org.ow2.petals.tools.webconsole.uibeans.ManagementUIBean.serverConnection(ManagementUIBean.java:392)
    org.ow2.petals.tools.webconsole.uibeans.ManagementUIBean.reconnect(ManagementUIBean.java:203)
    org.ow2.petals.tools.webconsole.uibeans.ServerUIBean.startSelectedComponents(ServerUIBean.java:219)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.lang.reflect.Method.invoke(Method.java:616)
    org.ow2.opensuit.cel.impl.tree.impl.ast.AstInvocation.invoke(AstInvocation.java:146)
    org.ow2.opensuit.cel.impl.tree.impl.ast.AstMethod.invoke(AstMethod.java:136)
    org.ow2.opensuit.cel.impl.tree.impl.ast.AstEval.invoke(AstEval.java:59)
    org.ow2.opensuit.core.expression.ExpressionUtils.invokeExpression(ExpressionUtils.java:119)
    org.ow2.opensuit.xml.base.binding.Expression.invoke(Expression.java:147)
    org.ow2.opensuit.xml.base.action.DoAndForward.invoke(DoAndForward.java:141)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.lang.reflect.Method.invoke(Method.java:616)
    org.ow2.opensuit.xml.base.Application.service(Application.java:514)
    org.ow2.opensuit.core.impl.j2ee.OpenSuitServlet.service(OpenSuitServlet.java:155)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    java.lang.Thread.run(Thread.java:679)

org.ow2.petals.tools.webconsole.util.PetalsConsoleException: Server configuration already exist in the webconsole.xml

    org.ow2.petals.tools.webconsole.business.ServerFeatureBBean.addServer(ServerFeatureBBean.java:106)
    org.ow2.petals.tools.webconsole.uibeans.ServerFeatureUIBean.saveServer(ServerFeatureUIBean.java:116)
    org.ow2.petals.tools.webconsole.uibeans.ManagementUIBean.serverConnection(ManagementUIBean.java:392)
    org.ow2.petals.tools.webconsole.uibeans.ManagementUIBean.reconnect(ManagementUIBean.java:203)
    org.ow2.petals.tools.webconsole.uibeans.ServerUIBean.startSelectedComponents(ServerUIBean.java:219)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.lang.reflect.Method.invoke(Method.java:616)
    org.ow2.opensuit.cel.impl.tree.impl.ast.AstInvocation.invoke(AstInvocation.java:146)
    org.ow2.opensuit.cel.impl.tree.impl.ast.AstMethod.invoke(AstMethod.java:136)
    org.ow2.opensuit.cel.impl.tree.impl.ast.AstEval.invoke(AstEval.java:59)
    org.ow2.opensuit.core.expression.ExpressionUtils.invokeExpression(ExpressionUtils.java:119)
    org.ow2.opensuit.xml.base.binding.Expression.invoke(Expression.java:147)
    org.ow2.opensuit.xml.base.action.DoAndForward.invoke(DoAndForward.java:141)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.lang.reflect.Method.invoke(Method.java:616)
    org.ow2.opensuit.xml.base.Application.service(Application.java:514)
    org.ow2.opensuit.core.impl.j2ee.OpenSuitServlet.service(OpenSuitServlet.java:155)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    java.lang.Thread.run(Thread.java:679)


2. The error that occurs while trying to start the petals-bc-soap-4.0.4.zip is the following:

Can't perform start action, because the component: petals-bc-soap is in the following state: Unknown


Could you please let me know what i've forgot to do here or why it is not working?


Tahnk you.
Reply | Threaded
Open this post in threaded view
|

Re: Petals Starting Guide - day 1 & 2 (WSDL & Administration)

petaleRose
It was a problem with my tomcat... I got it fixed!
12