Hi Amila,
thanks for your fast response. When do you think, the fix will be released
(Axis2 1.5)?
Please could you confirm, that using a Stub and the ConfigurationContext only
one-time is a workaround, until the fix goes into production?
Regards,
Christoph
Original-Nachricht ---
Hi,
I am using Axis2 1.4 XMLBeans client stubs with shared Commons HttpClient. I
get OutOfMemory errors, if I reuse ConfigurationContext previously generated by:
configurationContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
null);
The stub instance is creat
I have created a JIRA for this issue:
https://issues.apache.org/jira/browse/AXIS2-2860
Original-Nachricht
Datum: Tue, 26 Jun 2007 11:13:39 +0200
Von: [EMAIL PROTECTED]
An: axis-user@ws.apache.org
Betreff: ADB Prefix counter never reset
> Hi,
>
> we are using current Axis2 rel
Hi,
we are using current Axis2 release with ADB binding. Each Axis stub is reused
after each call. After several calls, we have noticed, that some
namespace-prefix counters are never reseted and will increase after every loop:
will result to: after several calls with the same
stub instance.
Finally solved the problem with help of HttpClient team. Please see JIRA
comment: https://issues.apache.org/jira/browse/AXIS2-2441
Cheers,
Christoph
--
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
-
Yes, that was my suggestion, too. HttpClient could have a problem with socket
handling. But in the end, Axis2 is failing and HttpClient is the default
client.
What are your suggestions, because Axis2 is using HttpClient per default and I
think that this bug (or more exaclty HttpClient's bug) wi
Could repeat exception with a simple HelloWorld wsdl after 3800 calls in a loop
by a single thread.
Original-Nachricht
Datum: Fri, 30 Mar 2007 13:28:09 +0200
Von: [EMAIL PROTECTED]
An: axis-user@ws.apache.org
Betreff: Re: java.net.BindException
> Simply generate a Stub with yo
Simply generate a Stub with your ADB Ant Task and call it in a loop like in my
posted code fragment. I can't embedd my full code due to legal reasons.
I have used the nightly builds.
The duration until exception is < 3 minutes at my machine (windows). Tomcat is
on a different host.
Some posts w
Axis2 crashed means: Axis stub throws finally an exception after three retries
of httpclient and stops execution -> no more Axis stub calls. There is no out
of memory printed in console.
Please could you run my posted clientcode at your machine and tell me, if the
BindException is appearing th
Michele,
I could reproduce this behaviour even with a single thread inside a loop. After
4000 calls, Axis2 crashed.
By the way, how can I stop local listener? I think this might be a security
risk (if not needed).
My sample code:
ConfigurationContext configurationContext =
ConfigurationCont
Thanks for response. Your suggested solution does not work. After thousands of
calls the Bind exception appears again. Then I have to wait a little (even with
JVM restart) for next successful runs.
I think, that socket handling of HttpClient is the problem. No local server is
started.
Please co
It seems that HttpClient is the reason for the socket bind exception:
Caused by: java.net.BindException: Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.Pla
I really would appreciate if someone could ask my questions below.
Please correct me if I am wrong:
I think it would be more secure to not start a listener in client stubs due to
security reasons with default configuration.
Regards,
Christoph
Hi,
during stress test of ADB service stubs, I g
Hi,
during stress test of ADB service stubs, I got a java.net.BindException:
"Address already in use: JVM_Bind". I have already read the article at
http://wso2.org/library/165, but some things are still a bit unclear.
I just want to call a service without asynchronous receiving. Every thread g
I have tried to use the nightly build, but I am getting the following error:
java.lang.NoSuchMethodError:
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder: method
(Ljavax/xml/stream/XMLStreamReader;)V not found
at
org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.j
should have waited a little with the last email. The problem is this method:
private java.lang.String createPrefix() {
return "ns" + (int)Math.random();
}
It will always return "ns0", because Math.random return a value betwen 0.0 and
< 1. Should be fixed IMHO.
---
And another one (again with the nightly build).
During serialization the code runs into an endless loop. If have debugged until
I came to this code fragment in one of the ADB generated classes:
private java.lang.String registerPrefix(..) {
...
while (xmlWriter.getNamespaceContext().getNamespa
There is another bug concerning maxLength restriction. The following
restriction:
results in the following code:
if ( (10 < java.lang.String.valueOf(param).length()) &&
(java.lang.String.valueOf(param).length() >= 80) ) {
this.value=param
I have figured out the reason, why attributes are not generated. In WSDL the
type of the attribute is declared not inside the attribute tag itself, but in a
restriction tag under the attribute tag:
...
XMLBeans is able to generate the correct java type. ADM ignores the attribute
compl
update:
jar's are indeed a problem and especially xmlbeans version is incompatible with
our existing third party libraries.
I tried Axis2 nigthly builds in order to use ADB instead of XMLBeans. At first,
the generated classes really looked good; most attributes which were missing
with 1.1.1 had
update:
After removing all inner parts of the WSDL as suggested, I was able to generate
a Stub. Then I have removed all XMLBeans stuff and used the "real"
xmlbeans-jar. Finally, I could to sent a request against an XFire server
successfully. :-)
Hope, that other parts of Axis2 are ready for pr
Please see my answers below...
Original-Nachricht
Datum: Wed, 21 Mar 2007 17:32:26 +0530
Von: "Amila Suriarachchi" <[EMAIL PROTECTED]>
An: axis-user@ws.apache.org
Betreff: Re: Data binding questions
> On 3/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Thanks for f
Thanks for fast response. Unfortunately I cannot post the WSDL due to legal
reasons. Sorry!
Is there a way, to integrate a generated XML beans jar (and skip the generation
error)?
Original-Nachricht
Datum: Wed, 21 Mar 2007 10:09:42 +
Von: "Paul Fremantle" <[EMAIL PROTECTED
update:
Our given WSDL seems to be really challenging. With ADB, attributes are missing
in the generated classes. With XMLBeans, everything is generated fine.
Therefore I must use XMLBeans. Is there any way to use an existing xmlbeans jar
with axis2 (due to generation problem mentioned in my p
Hi,
I have some questions about data binding:
We have a rather complex wsdl, which does not work with axis 1.x WSDL2Java.
Therefore we are planning to move to a newer SOAP engine.
Our partner recommends to use XFire with XMLbeans, but I want to give Axis 2 a
try, too. If I use XMLbeans binding
Hi,
I have a question concerning thread-safety of wsdl2java generated client
stubs. These topic has been posted several times and unfortunately the
answers are as numerous, too. Some users say, that stubs are safe, because
there are synchronized code blocks inside axis code, some others say, that
26 matches
Mail list logo
