Memory leak woes
Hi All, I have attached couple of small test programs. I am trying to reuse svc_client and I can't figure out the cause of memory leaks in the loop. Any insight will be greatly appreciated. I am using AXIS2/C 1.4.0 on Win32 with Visual Studio 2003 Thank you, Hatim --- Confidentiality Notice: This electronic mail transmission is confidential, may be privileged and should be read or retained only by the intended recipient. If you have received this transmission in error, please immediately notify the sender and delete it from your system. axis_leak1.c Description: axis_leak1.c axiom_leak1.c Description: axiom_leak1.c - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One service multiple access points
Hello World wrote: On Thu, Jun 26, 2008 at 5:25 PM, Supun Kamburugamuva [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Anis, Have you looked at the Math client and Service in the samples directory? Yes. But from what I have understood the math service is just one service with many operations (which quite common). I.e single handler, one URL, one set of operations. What I want is single handler but MULTIPLE URLs and thus MULTIPLE operation sets (i.e multiple WSDL files) If you are talking about the sg_math service, than that one is indeed, multiple interfaces, but it is also multiple handlers (it is a bunch of separate services) PS. I don't want clients to have anything to do with what's going on at the server side. The clients don't see that the interfaces are implemented by the same .so object. All they see is standard services . Looks like you are talking about service aggregation. Either you can write a wrapper service, to direct retests to relevant services, or you could get another third party mediator to do the proxying. Samisa... Regards, No virus found in this incoming message. Checked by AVG. Version: 8.0.101 / Virus Database: 270.4.1/1521 - Release Date: 6/26/2008 11:20 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 1.3 to Axis2 1.4
Thank you for your answer I did a mistake in the lib name ... But now I have another error, is there an incompatibility between Axis2 1.4 and Tomcat 6.0.16 ? The error : Impossible to call remote service with url. Caused by: org.apache.axis2.AxisFault: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/produits/Tomcat%206.0/webapps/axis2/WEB-INF/lib/jaxb-impl-2.1.6.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/) Thank you sumedha rubasinghe a écrit : Hi, Do you have XmlSchema-1.4.2.jar in your classpath? /sumedha On Thu, Jun 26, 2008 at 5:46 PM, Fabien Couvert [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all, I try to upgrade Axis2 to 1.4 version but I get this exception when I try to createConfigurationContextFromFileSystem : Exception in thread main java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/resolver/URIResolver at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184) Anyone have an idea please ? - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: java.lang.NullPointerException AbstractDispatcher.invoke
Thanks. It is working. Which build will this be part of ? Mohan -- View this message in context: http://www.nabble.com/java.lang.NullPointerException-AbstractDispatcher.invoke-tp18070227p18148961.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 1.3 to Axis2 1.4
Should be an issue with the JDK you are using not with Tomcat. What is your JDK version? Thanks, Keith. On Fri, Jun 27, 2008 at 12:02 PM, Fabien Couvert [EMAIL PROTECTED] wrote: Thank you for your answer I did a mistake in the lib name ... But now I have another error, is there an incompatibility between Axis2 1.4 and Tomcat 6.0.16 ? The error : Impossible to call remote service with url. Caused by: org.apache.axis2.AxisFault: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/produits/Tomcat%206.0/webapps/axis2/WEB-INF/lib/jaxb-impl-2.1.6.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/) Thank you sumedha rubasinghe a écrit : Hi, Do you have XmlSchema-1.4.2.jar in your classpath? /sumedha On Thu, Jun 26, 2008 at 5:46 PM, Fabien Couvert [EMAIL PROTECTED]mailto: [EMAIL PROTECTED] wrote: Hi all, I try to upgrade Axis2 to 1.4 version but I get this exception when I try to createConfigurationContextFromFileSystem : Exception in thread main java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/resolver/URIResolver at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184) Anyone have an idea please ? - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Re: Axis2 1.3 to Axis2 1.4
I use Jdk1.5.0-14 Did you think that is the problem ? keith chapman a écrit : Should be an issue with the JDK you are using not with Tomcat. What is your JDK version? Thanks, Keith. On Fri, Jun 27, 2008 at 12:02 PM, Fabien Couvert [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thank you for your answer I did a mistake in the lib name ... But now I have another error, is there an incompatibility between Axis2 1.4 and Tomcat 6.0.16 ? The error : Impossible to call remote service with url. Caused by: org.apache.axis2.AxisFault: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/produits/Tomcat%206.0/webapps/axis2/WEB-INF/lib/jaxb-impl-2.1.6.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/) Thank you sumedha rubasinghe a écrit : Hi, Do you have XmlSchema-1.4.2.jar in your classpath? /sumedha On Thu, Jun 26, 2008 at 5:46 PM, Fabien Couvert [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all, I try to upgrade Axis2 to 1.4 version but I get this exception when I try to createConfigurationContextFromFileSystem : Exception in thread main java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/resolver/URIResolver at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184) Anyone have an idea please ? - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Relying on Http error codes with AXIS
Hi, REST-based styles and the SOAP web service differ. Our client relies on the Http transport error codes to find out if the SOAP/Http request has reached or not. There are two styles being mixed here. Does anyone have an opinion about this ? Can the Http 200 come to the client even if the SOAP/Http request has not been processed by the Axis engine but the http layer has processed it successfully. The protocols are different here ? Thanks, Mohan -- View this message in context: http://www.nabble.com/Relying-on-Http-error-codes-with-AXIS-tp18150103p18150103.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Rampart/Rahas problems
So I've essentially taken Rampart sample6 and split it across three machines with my own web service instead of SimpleService. Here's what happens: 1) client makes Mex request to Service : Service responds. 2) Client makes token request to STS - STS responds 3) Client attempts to make the actual call the Service. Service then responds with axisFault: Missing wsse:Security header in request The server logs show something different: ERROR org.apache.ws.security.components.crypto.CryptoFactory - Unable to instantiate (1): org.apache.ws.security.components.crypto.Merlin java.lang.reflect.InvocationTargetException So, I checked and made sure I had BouncyCastle jar in lib directory. I check that security provider is updated (though I haven't a clue why i'm doing this). And, now, I've run out of things to check. i'd appreciate any help. Thanks, --tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 1.3 to Axis2 1.4
Well... then how about your system classpath? Open up a new command window and check what jars are in your classpath. /sumedha rubasinghe a écrit : Hi, I tested axis2-1.4 war with java version 1.5.0_14 Tomcat 6.0.16 .o It works fine. So this must be due to an additional jar file in your system classpath. Try printing contents of classpath variable just before tomcat starts. axis2.war contains jaxb-api-2.1.jar file. There must be an older version of the same jar file in your classpath, which gets loaded before 2.1 jar. /sumedha On Fri, Jun 27, 2008 at 1:21 PM, Fabien Couvert [EMAIL PROTECTED]mailto: [EMAIL PROTECTED] wrote: I use Jdk1.5.0-14 Did you think that is the problem ? keith chapman a écrit : Should be an issue with the JDK you are using not with Tomcat. What is your JDK version? Thanks, Keith. On Fri, Jun 27, 2008 at 12:02 PM, Fabien Couvert [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thank you for your answer I did a mistake in the lib name ... But now I have another error, is there an incompatibility between Axis2 1.4 and Tomcat 6.0.16 ? The error : Impossible to call remote service with url. Caused by: org.apache.axis2.AxisFault: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/produits/Tomcat%206.0/webapps/axis2/WEB-INF/lib/jaxb-impl-2.1.6.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/) Thank you sumedha rubasinghe a écrit : Hi, Do you have XmlSchema-1.4.2.jar in your classpath? /sumedha On Thu, Jun 26, 2008 at 5:46 PM, Fabien Couvert [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all, I try to upgrade Axis2 to 1.4 version but I get this exception when I try to createConfigurationContextFromFileSystem : Exception in thread main java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/resolver/URIResolver at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184) Anyone have an idea please ? - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] --Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]