RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies
Ok, I was able to finally test this. It works great! Thanks for all the help. -Original Message- From: VanKooten, Derek [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 3:32 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies I wont be able to try it out till Monday when I get back to work. I'll try it out then. Thanks. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 3:01 PM To: axis-user@ws.apache.org Subject: Re: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Nevermind. Fixed. Please pick up a nightly in another hour or so. On 9/15/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Please log a bug report in JIRA. thanks, dims On 9/15/06, VanKooten, Derek [EMAIL PROTECTED] wrote: Ok, its working in websphere 6 now with this build. I'm able to call my service again. Thanks! :) Btw, I was also finally able to get the eager inintialization to work as well. Seems like the actual method signature to use for the init or startup methods were not the same as what I read in the forums or in the JIRA. When I implemented the Service interface and used those methods it worked correctly. public void startUp(ConfigurationContext configurationContext, AxisService axisService); public void init(ServiceContext serviceContext); and I had to put the load-on-startup parameter into the services.xml. parameter name=load-on-startup locked=falsetrue/parameter I am now getting another error when I try http://localhost:9080/PersonalizationEngine/services/PersonalizationServ ices?wsdl I get this: Error page exception The server cannot use the error page specified for your application to handle the Original Exception printed below. Please see the Error Page Exception below for a description of the problem with the specified error page. Original Exception: Error Message: String index out of range: 14 Error Code: 500 Target Servlet: AxisServlet Error Stack: java.lang.StringIndexOutOfBoundsException: String index out of range: 14 at java.lang.String.substring(String.java(Compiled Code)) at org.apache.axis2.transport.http.ListingAgent.extractHostAndPort(ListingA gent.java:126) at org.apache.axis2.transport.http.ListingAgent.processListService(ListingA gent.java:166) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:165) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.ja va:1282) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrap per.java:673) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheS ervletWrapper.java:89) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:187 8) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:8 4) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscriminatio n(HttpInboundLink.java:472) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformatio n(HttpInboundLink.java:411) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpIC LReadCallback.java:101) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueMa nager.java:566) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager. java:619) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager. java:952) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager .java:1039) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1462) Error Page Exception: Error Message: SRVE0199E: OutputStream already obtained Error Code: 0 Target Servlet: null Error Stack: java.lang.IllegalStateException: SRVE0199E: OutputStream already obtained at com.ibm.ws.webcontainer.srt.SRTServletResponse.getWriter(SRTServletRespo nse.java:467) at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:170) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:1 63) at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:2 17) at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspF actoryImpl.java:149) at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryIm pl.java:117) at com.ibm._jsp._error500._jspService(_error500.java:79) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88
RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies
I'll try it today. I've got to completely rebuild my Rational development environment first. Just found a stupid issue with Rational and a 259 character limit with windows. Why oh why must ibm think it's a good idea to make directory structures with such long names Sheesh. So, its going to take me 4-5 hours before I can get to it. Thanks. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 12:15 AM To: axis-user@ws.apache.org; Charak, Vikas; VanKooten, Derek Subject: Re: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Vikas, Derek, Please try the nightly build in a couple of hours. I checked in fixes to get it working under websphere 6.1 thanks, dims On 9/14/06, VanKooten, Derek [EMAIL PROTECTED] wrote: I also just got done rolling back to the 1.0 version of axis, and all of my services are working fine now too. I am running the same version numbers of websphere and jdk as well. Would love to be able to use the eager initialization stuff that's supposed to be in the nightly builds, but alas, doesn't seem to work for me. I can switch back to the nightly version if you need me to test something. -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:23 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Websphere6.1 with JDK 1.4.2. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:19 PM To: axis-user@ws.apache.org Subject: Re: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Which version of websphere? jdk? On 9/14/06, Charak, Vikas [EMAIL PROTECTED] wrote: .aar format works fine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:07 PM To: axis-user@ws.apache.org Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies So you have the release version of Axis2 deployed to WebSphere and it works with the version service in aar format or is it unpacked? Dave -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 10:41 AM To: axis-user@ws.apache.org Subject: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Okay! Atlast I was able to invoke the version service on websphere. Issue is it works with Axis2 release1.0 but not with any of the nightly builds. Possible bug in nightilies. -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 9:56 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: NoSuchMethodError while deploying aar file on WebSphere Hi Dave/ Dims, I tried almost everything still same issue. REST version works but not SOAP version. I will write a separate email to Axis2 Designers for assistance. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 1:35 PM To: axis-user@ws.apache.org Subject: Re: NoSuchMethodError while deploying aar file on WebSphere Derek, Did you set the soap action to getMemoryStatus? try that, the alternative is to specify the method name in the EPR itself like you did for REST. thanks, dims On 9/13/06, VanKooten, Derek [EMAIL PROTECTED] wrote: I seem to be having the same problem. I wrote a service that worked fine on the 1.0 release. I then read that the nightly builds had a eager initialization feature. So, I tried getting a nightly build and using the same aar file from before. I get the error Sep 13, 2006 11:20:52 AM org.apache.axis2.engine.AxisEngine receiveFault INFO: Received Error Message with id urn:uuid:9EF9037ADD59CB7B7D11581608519631 org.apache.axis2.AxisFault: Service not found operation terminated !! at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:298) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:539 ) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:473 ) at com.bealls.services.personalization.PersonalizationService.main(Personal izationService.java:53) I have tried replacing the wsdl4j.jar in lib of webshpere 6.0 with the one that comes with axis2 nightly build. I have created a shared lib, added it to the class loader for the app server, and set the class loader to have Parent Last The class path for my
RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies
I'm reinstalling Rational because there is a 259 limit on the length of paths in windows, and the default install directory is c:\program files\ibm\RAD\sdp\6.0. So, when I am evaluating IBM's version of webservices, IBM creates these ungodly long paths under its install directory and hits that windows limit. So, this reinstall isnt because of AXIS2 its because of a stupid thing IBM did with their RATIONAL product. So, I'm reinstalling RAD under a directory of c:\rad6 instead and saving some space hoping to be able to continue evaluating IBM's web services at the same time evaluating AXIS2. BTW, I really like AXIS2 better so far. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 9:28 AM To: axis-user@ws.apache.org Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies WAIT! That's not it! You don't need to rebuild you env! I had the same issue. Deploy Axis2, then use the axis 2 manager interface to deploy your service. Dave -Original Message- From: VanKooten, Derek [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 8:20 AM To: axis-user@ws.apache.org Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies I'll try it today. I've got to completely rebuild my Rational development environment first. Just found a stupid issue with Rational and a 259 character limit with windows. Why oh why must ibm think it's a good idea to make directory structures with such long names Sheesh. So, its going to take me 4-5 hours before I can get to it. Thanks. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 12:15 AM To: axis-user@ws.apache.org; Charak, Vikas; VanKooten, Derek Subject: Re: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Vikas, Derek, Please try the nightly build in a couple of hours. I checked in fixes to get it working under websphere 6.1 thanks, dims On 9/14/06, VanKooten, Derek [EMAIL PROTECTED] wrote: I also just got done rolling back to the 1.0 version of axis, and all of my services are working fine now too. I am running the same version numbers of websphere and jdk as well. Would love to be able to use the eager initialization stuff that's supposed to be in the nightly builds, but alas, doesn't seem to work for me. I can switch back to the nightly version if you need me to test something. -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:23 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Websphere6.1 with JDK 1.4.2. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:19 PM To: axis-user@ws.apache.org Subject: Re: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Which version of websphere? jdk? On 9/14/06, Charak, Vikas [EMAIL PROTECTED] wrote: .aar format works fine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:07 PM To: axis-user@ws.apache.org Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies So you have the release version of Axis2 deployed to WebSphere and it works with the version service in aar format or is it unpacked? Dave -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 10:41 AM To: axis-user@ws.apache.org Subject: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Okay! Atlast I was able to invoke the version service on websphere. Issue is it works with Axis2 release1.0 but not with any of the nightly builds. Possible bug in nightilies. -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 9:56 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: NoSuchMethodError while deploying aar file on WebSphere Hi Dave/ Dims, I tried almost everything still same issue. REST version works but not SOAP version. I will write a separate email to Axis2 Designers for assistance. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 1:35 PM To: axis-user@ws.apache.org Subject: Re: NoSuchMethodError while deploying aar file on WebSphere Derek, Did you set the soap action to getMemoryStatus? try that, the alternative is to specify the method name in the EPR itself like you did for REST. thanks, dims On 9/13/06, VanKooten, Derek [EMAIL PROTECTED] wrote: I seem
RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies
) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformatio n(HttpInboundLink.java:411) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpIC LReadCallback.java:101) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueMa nager.java:566) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager. java:619) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager. java:952) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager .java:1039) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1462) -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 12:15 AM To: axis-user@ws.apache.org; Charak, Vikas; VanKooten, Derek Subject: Re: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Vikas, Derek, Please try the nightly build in a couple of hours. I checked in fixes to get it working under websphere 6.1 thanks, dims On 9/14/06, VanKooten, Derek [EMAIL PROTECTED] wrote: I also just got done rolling back to the 1.0 version of axis, and all of my services are working fine now too. I am running the same version numbers of websphere and jdk as well. Would love to be able to use the eager initialization stuff that's supposed to be in the nightly builds, but alas, doesn't seem to work for me. I can switch back to the nightly version if you need me to test something. -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:23 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Websphere6.1 with JDK 1.4.2. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:19 PM To: axis-user@ws.apache.org Subject: Re: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Which version of websphere? jdk? On 9/14/06, Charak, Vikas [EMAIL PROTECTED] wrote: .aar format works fine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:07 PM To: axis-user@ws.apache.org Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies So you have the release version of Axis2 deployed to WebSphere and it works with the version service in aar format or is it unpacked? Dave -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 10:41 AM To: axis-user@ws.apache.org Subject: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Okay! Atlast I was able to invoke the version service on websphere. Issue is it works with Axis2 release1.0 but not with any of the nightly builds. Possible bug in nightilies. -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 9:56 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: NoSuchMethodError while deploying aar file on WebSphere Hi Dave/ Dims, I tried almost everything still same issue. REST version works but not SOAP version. I will write a separate email to Axis2 Designers for assistance. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 1:35 PM To: axis-user@ws.apache.org Subject: Re: NoSuchMethodError while deploying aar file on WebSphere Derek, Did you set the soap action to getMemoryStatus? try that, the alternative is to specify the method name in the EPR itself like you did for REST. thanks, dims On 9/13/06, VanKooten, Derek [EMAIL PROTECTED] wrote: I seem to be having the same problem. I wrote a service that worked fine on the 1.0 release. I then read that the nightly builds had a eager initialization feature. So, I tried getting a nightly build and using the same aar file from before. I get the error Sep 13, 2006 11:20:52 AM org.apache.axis2.engine.AxisEngine receiveFault INFO: Received Error Message with id urn:uuid:9EF9037ADD59CB7B7D11581608519631 org.apache.axis2.AxisFault: Service not found operation terminated !! at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:298) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:539 ) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:473 ) at com.bealls.services.personalization.PersonalizationService.main(Personal izationService.java:53) I have tried replacing
RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies
I wont be able to try it out till Monday when I get back to work. I'll try it out then. Thanks. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 3:01 PM To: axis-user@ws.apache.org Subject: Re: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Nevermind. Fixed. Please pick up a nightly in another hour or so. On 9/15/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Please log a bug report in JIRA. thanks, dims On 9/15/06, VanKooten, Derek [EMAIL PROTECTED] wrote: Ok, its working in websphere 6 now with this build. I'm able to call my service again. Thanks! :) Btw, I was also finally able to get the eager inintialization to work as well. Seems like the actual method signature to use for the init or startup methods were not the same as what I read in the forums or in the JIRA. When I implemented the Service interface and used those methods it worked correctly. public void startUp(ConfigurationContext configurationContext, AxisService axisService); public void init(ServiceContext serviceContext); and I had to put the load-on-startup parameter into the services.xml. parameter name=load-on-startup locked=falsetrue/parameter I am now getting another error when I try http://localhost:9080/PersonalizationEngine/services/PersonalizationServ ices?wsdl I get this: Error page exception The server cannot use the error page specified for your application to handle the Original Exception printed below. Please see the Error Page Exception below for a description of the problem with the specified error page. Original Exception: Error Message: String index out of range: 14 Error Code: 500 Target Servlet: AxisServlet Error Stack: java.lang.StringIndexOutOfBoundsException: String index out of range: 14 at java.lang.String.substring(String.java(Compiled Code)) at org.apache.axis2.transport.http.ListingAgent.extractHostAndPort(ListingA gent.java:126) at org.apache.axis2.transport.http.ListingAgent.processListService(ListingA gent.java:166) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:165) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.ja va:1282) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrap per.java:673) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheS ervletWrapper.java:89) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:187 8) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:8 4) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscriminatio n(HttpInboundLink.java:472) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformatio n(HttpInboundLink.java:411) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpIC LReadCallback.java:101) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueMa nager.java:566) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager. java:619) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager. java:952) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager .java:1039) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1462) Error Page Exception: Error Message: SRVE0199E: OutputStream already obtained Error Code: 0 Target Servlet: null Error Stack: java.lang.IllegalStateException: SRVE0199E: OutputStream already obtained at com.ibm.ws.webcontainer.srt.SRTServletResponse.getWriter(SRTServletRespo nse.java:467) at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:170) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:1 63) at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:2 17) at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspF actoryImpl.java:149) at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryIm pl.java:117) at com.ibm._jsp._error500._jspService(_error500.java:79) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.ja va:1282) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrap per.java:673) at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(G
RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies
I also just got done rolling back to the 1.0 version of axis, and all of my services are working fine now too. I am running the same version numbers of websphere and jdk as well. Would love to be able to use the eager initialization stuff that's supposed to be in the nightly builds, but alas, doesn't seem to work for me. I can switch back to the nightly version if you need me to test something. -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:23 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Websphere6.1 with JDK 1.4.2. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:19 PM To: axis-user@ws.apache.org Subject: Re: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Which version of websphere? jdk? On 9/14/06, Charak, Vikas [EMAIL PROTECTED] wrote: .aar format works fine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 12:07 PM To: axis-user@ws.apache.org Subject: RE: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies So you have the release version of Axis2 deployed to WebSphere and it works with the version service in aar format or is it unpacked? Dave -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 10:41 AM To: axis-user@ws.apache.org Subject: [AXIS2] Calling SOAP version on WebSphere works with Release1; Possible bug in nightilies Okay! Atlast I was able to invoke the version service on websphere. Issue is it works with Axis2 release1.0 but not with any of the nightly builds. Possible bug in nightilies. -Original Message- From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Thursday, September 14, 2006 9:56 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: NoSuchMethodError while deploying aar file on WebSphere Hi Dave/ Dims, I tried almost everything still same issue. REST version works but not SOAP version. I will write a separate email to Axis2 Designers for assistance. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 1:35 PM To: axis-user@ws.apache.org Subject: Re: NoSuchMethodError while deploying aar file on WebSphere Derek, Did you set the soap action to getMemoryStatus? try that, the alternative is to specify the method name in the EPR itself like you did for REST. thanks, dims On 9/13/06, VanKooten, Derek [EMAIL PROTECTED] wrote: I seem to be having the same problem. I wrote a service that worked fine on the 1.0 release. I then read that the nightly builds had a eager initialization feature. So, I tried getting a nightly build and using the same aar file from before. I get the error Sep 13, 2006 11:20:52 AM org.apache.axis2.engine.AxisEngine receiveFault INFO: Received Error Message with id urn:uuid:9EF9037ADD59CB7B7D11581608519631 org.apache.axis2.AxisFault: Service not found operation terminated !! at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:298) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:539 ) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:473 ) at com.bealls.services.personalization.PersonalizationService.main(Personal izationService.java:53) I have tried replacing the wsdl4j.jar in lib of webshpere 6.0 with the one that comes with axis2 nightly build. I have created a shared lib, added it to the class loader for the app server, and set the class loader to have Parent Last The class path for my shared lib is: C:\Projects\axis2\WEB-INF\lib\activation-1.1.jar;C:\Projects\axis2\WEB-I NF\lib\annogen-0.1.0.jar;C:\Projects\axis2\WEB-INF\lib\axiom-api-SNAPSHO T.jar;C:\Projects\axis2\WEB-INF\lib\axiom-dom-SNAPSHOT.jar;C:\Projects\a xis2\WEB-INF\lib\axiom-impl-SNAPSHOT.jar;C:\Projects\axis2\WEB-INF\lib\a xis2-adb-codegen-SNAPSHOT.jar;C:\Projects\axis2\WEB-INF\lib\axis2-adb-SN APSHOT.jar;C:\Projects\axis2\WEB-INF\lib\axis2-codegen-SNAPSHOT.jar;C:\P rojects\axis2\WEB-INF\lib\axis2-java2wsdl-SNAPSHOT.jar;C:\Projects\axis2 \WEB-INF\lib\axis2-jaxbri-SNAPSHOT.jar;C:\Projects\axis2\WEB-INF\lib\axi s2-jibx-SNAPSHOT.jar;C:\Projects\axis2\WEB-INF\lib\axis2-kernel-SNAPSHOT .jar;C:\Projects\axis2\WEB-INF\lib\axis2-soapmonitor-SNAPSHOT.jar;C:\Pro jects\axis2\WEB-INF\lib\axis2-xmlbeans-SNAPSHOT.jar;C:\Projects\axis2\WE B-INF\lib\backport-util-concurrent-2.1.jar;C:\Projects\axis2\WEB-INF\lib \commons-codec-1.3.jar;C:\Projects\axis2\WEB-INF\lib\commons
