WARNING Message in Websphere 5.1.1.3 Whenever Axis2 Server Receive a Request
I used axis2.war (version 1.1.1) in Websphere 5.1.1.3. Everything works fine, but I saw following WARNING message in SystemOut.log whenever axis2 server receive a request (even invoking Version Service). [7/30/07 17:51:04:813 MDT] 23bd6a2f TraceNLS u No message text associated with key WARNING:.Cannot.set.header..Response.already.committed. in bundle com.ibm.ejs.resources.seriousMessages [7/30/07 17:51:04:813 MDT] 23bd6a2f SRTServletRes W WARNING: Cannot set header. Response already committed. Even though the server function correctly, this message is taking a lot of log space. Anyone know how to get rid of this message? Thanks Bryan >>> The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Importing a external schema in WSDL
I had the same issue. But this issue looks like only related to the new release (1.1.1 and 1.2), and if you use release 1.1, everything seems to work fine, except that it cannot generate wsdl, but the service works fine though >>> dharmendra3 <[EMAIL PROTECTED]> 6/14/2007 8:50 AM >>> Iam using Axis2 1.1.1 and OS is windows XP. We are creating our own war file. Its actually some WarBasedConfigurator which is not able to locate the .xsd file. Did you try with the wsdl ans xsd that I have sent. Do I need to make any changes to them. Ineed to resolve it asap. Amila Suriarachchi wrote: > > what is the axis2 version and the OS you use? I generated the code with > full > path and it worked fine. > and it sets the paths in saved wsdl and schema files as well. > > On 6/11/07, dharmendra3 <[EMAIL PROTECTED]> wrote: >> >> >> i have attached the xsd and the wsdl files. >> >> >> >> Amila Suriarachchi wrote: >> > >> > can you send your wsdl and your xsd files? >> > >> > On 6/7/07, dharmendra3 <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> When I try to import a schema with relative url,wsdl2ava is working >> fine >> >> but >> >> deployment is causing the problem saying that its not able to find the >> >> xsd >> >> file (It looks for xsd file from the domain root). >> >> >> >> If I use absolute url (schemalocation) wsdl2java is failing. >> >> >> >> >> >> Is this a bug with the wsdl4j,how can I resolve this. >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/-AXIS2---Importing-a-external-schema-in-WSDL-tf3884021.html#a11008452 >> >> >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> > -- >> > Amila Suriarachchi, >> > WSO2 Inc. >> > >> > >> http://www.nabble.com/file/p11062282/transporter.xsd transporter.xsd >> http://www.nabble.com/file/p11062282/PoetManagementService.wsdl >> PoetManagementService.wsdl >> -- >> View this message in context: >> http://www.nabble.com/-AXIS2---Importing-a-external-schema-in-WSDL-tf3884021.html#a11062282 >> >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Amila Suriarachchi, > WSO2 Inc. > > -- View this message in context: http://www.nabble.com/-AXIS2---Importing-a-external-schema-in-WSDL-tf3884021.html#a11121505 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] >>> The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem when using a different web context for Axis2 war
Chad, Thank you very much for your helps. The settings solved the problem! It really doesn't matter if the wsdl is shown in admin page or not for us, as long as the services are working. Bryan >>> The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem when using a different web context for Axis2 war
There is no error from either out nor err log. The problem I think is because the context root is not generated correctly in the wsdl. Here is the segment of wsdl that is generated by axis2 in websphere. Even though I deployed in /test/axis2, it only shows /test as address location. Also, when I go the validation page, the "Examining Version Service" gives the following error. It doesn't matter what endpoint I gave (/test or /test/axis2), the client cannot connect to the Version service. /test gives 404 error, and /test/axis2 gives 500 error (Service not found operation terminated !!) Thanks Bryan http://dadev.fb.com:80/test/services/Version"/> http://dadev.fb.com:80/test/services/Version"/> http://dadev.fb.com:80/test/rest/Version"/> There was a problem in Axis2 version service , may be the service not available or some thing has gone wrong. But this does not mean system is not working ! Try to upload some other service and check to see whether it is working. >>> The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem when using a different web context for Axis2 war
Chad, It looks like we will not move to 6.1 very soon. Could you tell me more specific why it is not running in WAS 5.1, and are there any work around for this in WAS 5.1? Thanks Bryan >>> The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem when using a different web context for Axis2 war
Thanks for the information, we will try it in 6.1 Bryan > I don't believe WAS 5.1.x supports context roots such as this > "/test/axis2". We are using WAS 6.1 and haven't had a problem changing the > context root with Axis2. Although you do have to change class loading > settings within WAS 6.1 after you deploy the war. > > Chad > > On 6/11/07, Bryan Chen <[EMAIL PROTECTED]> wrote: > > >> Did you get it working in Websphere with the context root as axis2? Also >> what version of WAS are you using? > > >> => Yes, it is working in Websphere with context root as axis2, and we use >> WAS 5.1.1.3. >>> The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem when using a different web context for Axis2 war
Did you get it working in Websphere with the context root as axis2? Also what version of WAS are you using? => Yes, it is working in Websphere with context root as axis2, and we use WAS 5.1.1.3. Thanks Bryan >>> The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem when using a different web context for Axis2 war
Hi, Does any one try to deploy Axis2 war file under Websphere (or any other containers) with a different root context. E.g. the default (or working) root context usually is /xxx, and I tried to deploy under /test/xxx, but it looks like this doesn't work. Any suggestions? Thanks Bryan >>> The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
