Re: Re: Axis on Websphere (Out of memory error)
Using Axis 2.0 is not possible because of jar file issues. What are these issues? I'm running Axis2 on Websphere 6.0 and 6.1. /Marcus On 7/12/06, Doug B <[EMAIL PROTECTED]> wrote: Are you on the latest WebSphere 5.1 fixpack? Looks like it's 5.1.1.11: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24012432 Is the OOM stack trace always in the same place? Where is it? How large is your heap? I really don't know how much memory is required for Axis to process a 20MB XML message, but I guess it could be quite large. Doug On 7/12/06, Martin Gainty <[EMAIL PROTECTED]> wrote: > Can you show us the steps you took to build the war? > Martin-- > * > This email message and any files transmitted with it contain confidential > information intended only for the person(s) to whom this email message is > addressed. If you have received this email message in error, please notify > the sender immediately by telephone or email and destroy the original > message without making a copy. Thank you. > > > > - Original Message - > From: <[EMAIL PROTECTED]> > To: > Sent: Wednesday, July 12, 2006 4:40 PM > Subject: Aw: Re: Axis on Websphere (Out of memory error) > > > > Hi, thanks for your answers: > > It is an IBM JDK and the system is running on Win 2000 Prof. > > Most of the times this error occurs after sending only one message to Axis. > > Axis 1.2 works fine on Axis but Axis 2.0 doesn't work (wsdl4j conflict). > > Tanks in advance > > - Original Nachricht > Von: Doug B <[EMAIL PROTECTED]> > An: axis-user@ws.apache.org > Datum: 12.07.2006 21:19 > Betreff: Re: Axis on Websphere (Out of memory error) > > > Do you get OOM on a single request? Or only eventually after handling > > many requests? Are you on the latest fixpacks of WebSphere? Axis > > should run fine under it as far as I know. > > > > Doug > > > > On 7/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Hello, > > > what can we do to run Axis on Websphere 5.1. > > > > > > We tried Axis 1.2 and we get out of memory errors. > > > > > > Using Axis 2.0 is not possible because of jar file issues. > > > > > > How ca we solve this problem? We receive about 20 MB of XML and our server > > = > > > has about 4 GB of mem. Heap was already increased. > > > > > > Will Axis 2.0 which should have a better memory footprint run on > > Websphere? > > > > > > > > > Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren > > > ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: > > günstig > > > und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer, > > > nur 44,85 ? inkl. DSL- und ISDN-Grundgebühr! > > > http://www.arcor.de/rd/emf-dsl-2 > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren > ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig > und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer, > nur 44,85 ? inkl. DSL- und ISDN-Grundgebühr! > http://www.arcor.de/rd/emf-dsl-2 > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Namespaces with and without security turned on
Hi, Solution for JIRA issue AXIS2-771 tested OK. Great work! Regards Marcus Ludvigson On 5/27/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: Sure ... will take a look at it. Thanks, Ruchith On 5/26/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > Seems like a bug in ns handling of DOOM. Can you please create a JIRA > issue (http://issues.apache.org/jira/browse/AXIS2). > > Ruchith, you wanna try this ? > > > > Marcus Ludvigson wrote: > > Hi, > > > > I am executing a webservice with and without security turned on. The > > result when executing the WS with security turned on is that I get > > excessive amount of namespaces ( axis2ns23, axis2ns24, axis2ns25, etc) > > compared to executing without security. I also get a > > ArrayIndexOutOfBoundsException the first time running with security but > > it works if I run it again. > > > > Who is generating all of these namespaces, and can I do something to > > avoid it? > > > > See info below. > > > > Regards, > > Marcus Ludvigson > > > > > > Result when executing without security: > > > > > xmlns="http://corp.net/ConfigManager/listAllServices";> > > > > > > > > > > > > > > > > Result when executing with security: > > > > > xmlns:axis2ns21="http://corp.net/ConfigManager/listAllServices"; > > xmlns:xenc=" http://www.w3.org/2001/04/xmlenc#"; > > xmlns:wsa="http://www.w3.org/2005/08/addressing"; xmlns:wsu=" > > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; > > xmlns="http://corp.net/ConfigManager/listAllServices"; xmlns:soapenv=" > > http://schemas.xmlsoap.org/soap/envelope/";> > > http://corp.net/ConfigManager/listAllServices"/ > > <http://corp.net/ConfigManager/listAllServices"/>> > >> xmlns:axis2ns23="http://corp.net/ConfigManager/listAllServices"/ > > <http://corp.net/ConfigManager/listAllServices"/>> > >> xmlns:axis2ns24="http://corp.net/ConfigManager/listAllServices"/ > > <http://corp.net/ConfigManager/listAllServices"/>> > > > > > > > > Relevant part from the WSDL: > > > > > targetNamespace="http://corp.net/ConfigManager/listAllServices"; > > elementFormDefault="qualified"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ArrayIndexOutOfBounds: > > > > SymbMap.index(Object) line: not available > > SymbMap.get(String) line: not available > > NameSpaceSymbTable.addMapping(String, String, Attr) line: not available > > Canonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).handleAttributesSubtree(Element, > > NameSpaceSymbTable) line: not available > > Canonicalizer20010315ExclOmitComments(CanonicalizerBase).canonicalizeSubTree(Node, > > NameSpaceSymbTable, Node) line: not available > > Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalizeSubTree(Node, > > Node) line: not available > > Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalize(XMLSignatureInput) > > line: not available > > Canonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).engineCanonicalize(XMLSignatureInput, > > String) line: not available > > TransformC14NExclusive.enginePerformTransform(XMLSignatureInput, > > OutputStream) line: not available > > Transform.performTransform(XMLSignatureInput, OutputStream) line: not > > available > > Transforms.performTransforms(XMLSignatureInput, OutputStream) line: not > > available > > Reference.getContentsAfterTransformation(XMLSignatureInput, > > OutputStream) line: not available > > Reference.dereferenceURIandPerformTransforms(OutputStream) line: not > > available > > Reference.calculateDigest() line: not available > > Reference.verify() line: not available > > SignedInfo(Manifest).verifyReferences(boolean) line: not available > > SignedInfo.verify(boolean) line: not available > > XMLSignature.checkSignatureValue(Key) line: not available > > XMLSignature.checkSignatureValue(X509Certificate) line: not available > > SignatureProcessor.verifyXMLSignature(Element, Crypto, > > X509Certificate[], Set, byte[][]) line: 264 > > SignatureProcessor.handleToken(Element, Crypto, Crypto, CallbackHandler, > > WSDocInfo, Vector, WSSConfig) line: 79 > > WSSecurityEngine.processSecurityHeader(Element, CallbackHandler, Crypto, > > Crypto) line: 269 > > WSSecurityEngine.processSecurityHeader(Document, String, > > CallbackHandler, Crypto, Crypto) line: 191 > > WSDoAllReceiver.processMessage (MessageContext) line: 180 > > WSDoAllReceiver(WSDoAllHandler).invoke(MessageContext) line: 82 > > > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL doubt
Yes, You can import and reference types or element in the schema. Below shown an example of how to import a schema under the namespace "http://corp.net/configuration"; and how to reference a element in that schema. http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="http://corp.net/ConfigManager"; xmlns:conf="http://corp.net/configuration"; name="ConfigManager" http://corp.net/ConfigManager/getConfigurations"; elementFormDefault="qualified"> http://corp.net/configuration"; schemaLocation="../schemas/config.xsd" /> Regards, Marcus Ludvigson On 5/29/06, Hariharasudhan.D Dhakshinamoorthy <[EMAIL PROTECTED]> wrote: Is there a way in axis where i can create my xsd seperately in a seperate file instead of having it in the WSDL itself ?
Re: [Axis2] Namespaces with and without security turned on
Of course, JIRA: http://issues.apache.org/jira/browse/AXIS2-771 Regards, Marcus Ludvigson On 5/26/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: Seems like a bug in ns handling of DOOM. Can you please create a JIRAissue ( http://issues.apache.org/jira/browse/AXIS2).Ruchith, you wanna try this ?Marcus Ludvigson wrote:> Hi,>> I am executing a webservice with and without security turned on. The > result when executing the WS with security turned on is that I get> excessive amount of namespaces ( axis2ns23, axis2ns24, axis2ns25, etc)> compared to executing without security. I also get a> ArrayIndexOutOfBoundsException the first time running with security but > it works if I run it again.>> Who is generating all of these namespaces, and can I do something to> avoid it?>> See info below.>> Regards,> Marcus Ludvigson >>> Result when executing without security:>> > xmlns="http://corp.net/ConfigManager/listAllServices ">> > > > > >>> Result when executing with security:>> > xmlns:axis2ns21="http://corp.net/ConfigManager/listAllServices"> xmlns:xenc=" http://www.w3.org/2001/04/xmlenc# "> xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> xmlns="http://corp.net/ConfigManager/listAllServices" xmlns:soapenv=" > http://schemas.xmlsoap.org/soap/envelope/">> http://corp.net/ConfigManager/listAllServices"/> <http://corp.net/ConfigManager/listAllServices "/>>> > xmlns:axis2ns23="http://corp.net/ConfigManager/listAllServices "/> <http://corp.net/ConfigManager/listAllServices"/>>> > xmlns:axis2ns24="http://corp.net/ConfigManager/listAllServices"/> <http://corp.net/ConfigManager/listAllServices "/>>> >>> Relevant part from the WSDL:>> > targetNamespace=" http://corp.net/ConfigManager/listAllServices"> elementFormDefault="qualified">>> > > >> > >> > > >> >>> ArrayIndexOutOfBounds:>> SymbMap.index(Object) line: not available> SymbMap.get(String) line: not available> NameSpaceSymbTable.addMapping(String, String, Attr) line: not available> Canonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).handleAttributesSubtree(Element,> NameSpaceSymbTable) line: not available > Canonicalizer20010315ExclOmitComments(CanonicalizerBase).canonicalizeSubTree(Node,> NameSpaceSymbTable, Node) line: not available> Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalizeSubTree(Node, > Node) line: not available> Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalize(XMLSignatureInput)> line: not available> Canonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).engineCanonicalize(XMLSignatureInput, > String) line: not available> TransformC14NExclusive.enginePerformTransform(XMLSignatureInput,> OutputStream) line: not available> Transform.performTransform(XMLSignatureInput, OutputStream) line: not > available> Transforms.performTransforms(XMLSignatureInput, OutputStream) line: not> available> Reference.getContentsAfterTransformation(XMLSignatureInput,> OutputStream) line: not available > Reference.dereferenceURIandPerformTransforms(OutputStream) line: not> available> Reference.calculateDigest() line: not available> Reference.verify() line: not available> SignedInfo(Manifest).verifyReferences(boolean) line: not available > SignedInfo.verify(boolean) line: not available> XMLSignature.checkSignatureValue(Key) line: not available> XMLSignature.checkSignatureValue(X509Certificate) line: not available> SignatureProcessor.verifyXMLSignature (Element, Crypto,> X509Certificate[], Set, byte[][]) line: 264> SignatureProcessor.handleToken(Element, Crypto, Crypto, CallbackHandler,> WSDocInfo, Vector, WSSConfig) line: 79> WSSecurityEngine.processSecurityHeader (Element, CallbackHandler, Crypto,> Crypto) line: 269> WSSecurityEngine.processSecurityHeader(Document, String,> CallbackHandler, Crypto, Crypto) line: 191> WSDoAllReceiver.processMessage (MessageContext) line: 180 > WSDoAllReceiver(WSDoAllHandler).invoke(MessageContext) line: 82>>
[Axis2] Namespaces with and without security turned on
Hi, I am executing a webservice with and without security turned on. The result when executing the WS with security turned on is that I get excessive amount of namespaces ( axis2ns23, axis2ns24, axis2ns25, etc) compared to executing without security. I also get a ArrayIndexOutOfBoundsException the first time running with security but it works if I run it again. Who is generating all of these namespaces, and can I do something to avoid it? See info below. Regards, Marcus Ludvigson Result when executing without security: http://corp.net/ConfigManager/listAllServices"> Result when executing with security: http://corp.net/ConfigManager/listAllServices" xmlns:xenc=" http://www.w3.org/2001/04/xmlenc#" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns="http://corp.net/ConfigManager/listAllServices" xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/"> http://corp.net/ConfigManager/listAllServices"/> http://corp.net/ConfigManager/listAllServices"/ > http://corp.net/ConfigManager/listAllServices"/ > Relevant part from the WSDL: http://corp.net/ConfigManager/listAllServices" elementFormDefault="qualified"> ArrayIndexOutOfBounds: SymbMap.index(Object) line: not availableSymbMap.get(String) line: not availableNameSpaceSymbTable.addMapping(String, String, Attr) line: not availableCanonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).handleAttributesSubtree(Element, NameSpaceSymbTable) line: not available Canonicalizer20010315ExclOmitComments(CanonicalizerBase).canonicalizeSubTree(Node, NameSpaceSymbTable, Node) line: not availableCanonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalizeSubTree(Node, Node) line: not available Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalize(XMLSignatureInput) line: not availableCanonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).engineCanonicalize(XMLSignatureInput, String) line: not available TransformC14NExclusive.enginePerformTransform(XMLSignatureInput, OutputStream) line: not availableTransform.performTransform(XMLSignatureInput, OutputStream) line: not availableTransforms.performTransforms(XMLSignatureInput, OutputStream) line: not available Reference.getContentsAfterTransformation(XMLSignatureInput, OutputStream) line: not availableReference.dereferenceURIandPerformTransforms(OutputStream) line: not availableReference.calculateDigest() line: not available Reference.verify() line: not availableSignedInfo(Manifest).verifyReferences(boolean) line: not availableSignedInfo.verify(boolean) line: not availableXMLSignature.checkSignatureValue(Key) line: not available XMLSignature.checkSignatureValue(X509Certificate) line: not availableSignatureProcessor.verifyXMLSignature(Element, Crypto, X509Certificate[], Set, byte[][]) line: 264SignatureProcessor.handleToken(Element, Crypto, Crypto, CallbackHandler, WSDocInfo, Vector, WSSConfig) line: 79 WSSecurityEngine.processSecurityHeader(Element, CallbackHandler, Crypto, Crypto) line: 269WSSecurityEngine.processSecurityHeader(Document, String, CallbackHandler, Crypto, Crypto) line: 191WSDoAllReceiver.processMessage (MessageContext) line: 180WSDoAllReceiver(WSDoAllHandler).invoke(MessageContext) line: 82
