I was thinking the same thing, but got moved onto something else before I
tested it out.  I will try that?

 

 

So a question arises from this for me?  What sorts of jvm memory numbers are
people using for axis2 deployed webservices?

 

Thanks,

 

Chris

 

  _____  

From: Vikas Gujjar [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 22, 2008 5:39 PM
To: [email protected]
Subject: Re: Transport error: 403 Error: access forbidden

 

Hi Chris,

It turned out that dev instance I was using had pretty low JVM memory
settings (much lower than the previously tuned and tested value).  Once the
settings was fixed, The error has disappeared... We took a hundred hits from
the .NET client and all is fine.

Thanks,
Vikas

On Fri, Apr 18, 2008 at 4:41 PM, Chris Richmond <[EMAIL PROTECTED]>
wrote:

Did you ever resolve it?  

 

Was your service like mine, where your service implementation actually
instantiaded an adb client to another service itself..sort of as a
passthrough service?  I'm trying to determine if that part of the
problem..although I don't know why it should be, unless Axis libraries are
very poorly implemented.

 

So how did you get yours system production ready with such low performance
threshold?

 

Thanks,


Chris

 

  _____  

From: Vikas Gujjar [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 18, 2008 12:17 PM
To: [email protected]
Subject: Re: Transport error: 403 Error: access forbidden

 

Hi Chris,

I faced this issue a short while back (rather still facing it). I
temporarily inserted a catch throwable around the web service implementation
class and discovered that one of the operation I was performing was
resulting in OutOfMemoryError after few calls from the client.

Hope this helps.

Thanks,
Vikas

On Wed, Apr 16, 2008 at 11:03 PM, Deepal Jayasinghe <[EMAIL PROTECTED]>
wrote:

hi Chris ,
Any possibility of creating test case ? if so that would be a great help to
fix the issue.
Or even send you service aar file.

Thank you!
Deepal

 


Hello all,

 
I am having a strange problem. I have built a POJO web service that is
itself an ADB client to another ws(.NET) and all works fine,  but I notice
for some reason when I use my test client make calls multiple times..and I
don't even mean load testing..but just manually call via a button click like
once a second..or even less.by 10 calls or so it throws an exception on the
server(shown below) .   I can loop calls and it will run 10 or so ok, then
start throwing this exception for several, then run a few more ok, then
throw this exception back and forth like that.  I am not using SSL, https,
or any other thing like that either , and as I said I'm using ADB.  It seems
like some sort of loading/performance issue, but I never see any spike in
CPU usage and as I said, I am doing ridiculously low call frequency.
Perhaps there is a resource issue by having an Axis2 web service that is
both a service and a client to another WS? That should work fine, but maybe
I need to take special steps?  If anyone has any ideas on this, please help
me out.

 
Thanks,

 
Chris

 
[ERROR] org.apache.axis2.AxisFault: Transport error: 403 Error: Access
Forbidden

java.lang.reflect.InvocationTargetException

       at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source)

       at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)

       at java.lang.reflect.Method.invoke(Method.java:597)

       at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:194)

       at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMes
sageReceiver.java:98)

       at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(
AbstractInOutMessageReceiver.jav

:40)

       at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageRe
ceiver.java:96)

       at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)

       at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HT
TPTransportUtils.java:275)

       at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)

       at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)

       at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

       at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:290)

       at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:206)

       at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:233)

       at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:175)

       at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128
)

       at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102
)

       at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)

       at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)

       at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

       at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http
11Protocol.java:584)

       at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)

       at java.lang.Thread.run(Thread.java:619)

 

 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 

 

Reply via email to