Hi, Thanks a lot for your reply!
Yes, I have tried with the new 3.2.2-SNAPSHOT versions. I have read from one of the Nabble forums that: When Servicemix is running standalone, it runs on jetty and port number is 8192. When Servicemix is running in Geronimo, it uses Tomcat (as I am using - Geronimo 2.0.2 with Tomcat 6 (zip)) and port number is 8443. Options tried ============== 1. I modified the client.html (examples/bridge and examples/wsdl-first) and changed the URL as http://localhost:8443/bridge/ and http://localhost:8443/PersonService/ And, I got the status code as "200" that means it is able to find the component running in tomcat at port number 8443, but the response message that is coming back is some weird characters "" for both examples.While, when the servicemix is running standalone, the proper response comes back. 2. Modified the xbean.xml (for bridge and wsdl-first examples) and person.wsdl for the port number changes from 8192 to 8443). Then rebuild using maven. Still, I got status code as "200", but response is the same weird characters "". What we want to achieve ======================= We want to run Servicemix in Geronimo. Deploy the Servicemix components in Geronimo and access the components running inside Geronimo using HTTP requests (using web browser). Please help me. Thanks, Yogesh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Custine Sent: Tuesday, February 05, 2008 1:58 AM To: [email protected] Cc: SIDDHARTHA CHANDURKAR (WT01 - Computing, Storage & Software Products); Ahmadbasha Shaik (WT01 - Computing, Storage & Software Products) Subject: Re: Facing issues while deploying Apache ServiceMix 3.2.1 WAR file in Apache Geronimo 2.0.2. Responses inline below.... On Feb 4, 2008 10:47 AM, <[EMAIL PROTECTED]> wrote: > Hi Chris, > > Thanks a lot ! > > The WAR file gets deployed successfully with the following Warnings on > the console: > > << > 1. WARN [TomcatModuleBuilder] Web application . does not contain a > WEB-INF/geronimo-web.xml deployment plan. This may or may not be a > problem, depending on whether you have things like resource references > that need to be resolved. You can also give the deployer a separate > deployment plan file on the command line. I believe this is harmless because all of the resources used by ServiceMix are internal. > > > 2. WARN [EndpointRegistry] Disabled endpoint processor > 'org.apache.servicemix.jbi.framework.support.WSDL2Processor': > java.lang.NoClassDefFoundError: org/apache/woden/WSDLReader The woden jar is marked as optional in servicemix-core pom.xml so the war packaging will not include it unless it is specified explicitly. The code treats this as a warning and looks harmless, so I would ignore this. Maybe someone else has info on this warning. > 3. WARN [ClientFactory] Cound not start ClientFactory: > javax.naming.NotContextException: The intermediate context > ClientFactory does not exist > >> This is a known issue and will not cause you issues unless you need to gain access to the ClientFactory from another application on the same app server instance. > > As told by you earlier, there is no impact of first warning. Please do > correct me if I am wrong. Does Warning 2 & 3 can have any impact? > > Steps followed to deploy/install Servicemix 3.2.1 components on Apache > Geronimo 2.0.2 > ====================================================================== > == > ============== > > From the Servicemix Web Interface (WAR file) deployed on Geronimo, I > have browsed, installed and started the following components from the > "hotdeploy" folder of servicemix 3.2.1 binaries: > > 1. From the Shared Library menu - > servicemix-shared-3.2.1-installer.zip > 2. From the Components menu - servicemix-http-3.2.1-installer.zip, > servicemix-jms-3.2.1-installer.zip, servicemix-eip-3.2.1-installer.zip > and servicemix-saxon-3.2.1-installer.zip. > > Deploying the sample Servicemix example - bridge browsed, deployed and > started(from examples\bridge folder) > ====================================================================== > == > ==================================== > > 1. From the Service Assemblies menu - bridge-sa-3.2.1.zip. > > Now, when I tried to access the bridge example from the client.html > from the examples/bridge folder using URL > http://localhost:8192/bridge/, it is giving me status code - 12029 as response. > > I have searched the internet and found that either the "servicemix-http" > component or servicemix itself is not started. However, the > "servicemix-http" component gets started successfully, as shown on the > Servicemix web interface. But I am not sure how to check whether > servicemix is started or not. I think ServiceMix is starting otherwise servicemix-http would not. However I think there is still a problem with the servicemix-http or bridge-sa deployment, possibly they are running but could not open the port 8192 or something of that nature. I would check the logs for messages regarding these deployments again and post here if you find anything unusual. I am also wondering if you have tried the new 3.2.2-SNAPSHOT versions of these deployments to match the main servicemix war deployment. Thanks, Chris > > Could you please tell me how to resolve this issue? Am I accessing the > proper URL or why the servicemix is not getting started? > > Please help me. > > Thanks, > Yogesh > > Please do not print this email unless it is absolutely necessary. Spread environmental awareness. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
