Saliya,

I think this is relevant to the FORCE_HTTP_1.0 issue that we had on the 
1.7 release, and I saw he is using the HTTP/1.0 to invoke the service. 
When security is there, the message is fully built in the Rampart module 
and does not gives that error but when you remove the security, the 
message building process goes off and causes this error. I think you got 
my point...

Thanks,
Ruwan

Saliya Ekanayake wrote:
> Hi Stefan,
>
> I am looking into your problem now with your configuration. In the 
> meanwhile can you please let me know the ESB version you are using (i.e. 
> 1.7.1, SNAPSHOT, etc.)? If you are trying to remove <syn:enableSec> then 
> I will assume that the back end service does not require security.
>
> Anyway hope to get back to you with good results ;)
>
> Thanks,
> Saliya
>
> stlecho wrote:
>   
>> Hi Saliya,
>>
>> When removing the "<syn:enableSec/>" element from my proxy definition -
>> included underneath - I'm getting the "problem accessing the parser. Parser
>> already accessed!" error.
>>
>>     <syn:proxy name="FSB-Proxy-WsSecurity" transports="https http"
>> startOnLoad="true" statistics="enable" trace="enable">
>>         <syn:target endpoint="FSB-WSSecurity-Test">
>>             <syn:inSequence>
>>                 <syn:log level="full" separator=","/>
>>                 <syn:property name="FORCE_HTTP_1.0" value="true"
>> scope="axis2"/>
>>             </syn:inSequence>
>>             <syn:outSequence>
>>                 <syn:log level="full" separator=","/>
>>                 <syn:send/>
>>             </syn:outSequence>
>>         </syn:target>
>>         <syn:publishWSDL
>> uri="https://e-depottest.smals-mvm.be/fphp/3.1/ws/PersonQuery.jws?WSDL="/>
>>      <syn:enableSec/>
>>         <syn:policy key="policy-FSB" type="out"/>
>>     </syn:proxy>
>>
>> Regards, Stefan Lecho.
>>
>> Saliya Ekanayake-2 wrote:
>>   
>>     
>>> HI Stlecho,
>>>
>>> The particular exception comes when an OM tree is accessed after being 
>>> serialized and consumed. Are you using the nightly builds or a previous 
>>> version of Synapse? This was an issue in the previous versions. See 
>>> http://issues.apache.org/jira/browse/SYNAPSE-392. This is fixed in the 
>>> trunk and will be available in future releases.
>>>
>>> Btw. if you are not using HTTP 1.0 and still get this error then will 
>>> you be able to provide more information on how this happens? I mean 
>>> necessary steps to recreate it and your ESB configuration.
>>>
>>>
>>> Thanks,
>>> Saliya
>>>
>>> stlecho wrote:
>>>     
>>>       
>>>> Hi,
>>>>
>>>> Any ideas why I'm receiving an "org.apache.axis2.AxisFault: problem
>>>> accessing the parser. Parser already accessed!" error message ?
>>>>
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [I/O dispatcher 1] DEBUG
>>>> headers >> POST
>>>> https://e-depottest.smals-mvm.be/fphp/3.1/ws/PersonQuery.jws
>>>> HTTP/1.0
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [I/O dispatcher 1] DEBUG
>>>> headers >> Host: localhost:8280
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [I/O dispatcher 1] DEBUG
>>>> headers >> SOAPAction: urn://fsb.belgium.be/fphp/v3_0/findPerson
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [I/O dispatcher 1] DEBUG
>>>> headers >> Content-Type: text/xml; charset=UTF-8
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [I/O dispatcher 1] DEBUG
>>>> headers >> Content-Length: 1422
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [I/O dispatcher 1] DEBUG
>>>> headers >> Connection: Keep-Alive
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [I/O dispatcher 1] DEBUG
>>>> headers >> User-Agent: Synapse-HttpComponents-NIO
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [HttpServerWorker-1]
>>>> DEBUG
>>>> SOAPMessageFormatter start writeTo()
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [HttpServerWorker-1]
>>>> DEBUG
>>>> SOAPMessageFormatter   preserve=false
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [HttpServerWorker-1]
>>>> DEBUG
>>>> SOAPMessageFormatter   isOptimized=false
>>>> 2008-08-26 18:01:47,684 [192.168.13.175-INFOR2] [HttpServerWorker-1]
>>>> DEBUG
>>>> SOAPMessageFormatter   isDoingSWA=false
>>>> 2008-08-26 18:01:47,715 [192.168.13.175-INFOR2] [HttpServerWorker-1]
>>>> DEBUG
>>>> Utils MTOM optimized Threshold value =0
>>>> 2008-08-26 18:01:47,715 [192.168.13.175-INFOR2] [HttpServerWorker-1]
>>>> DEBUG
>>>> StAXUtils XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter
>>>> 2008-08-26 18:01:47,715 [192.168.13.175-INFOR2] [HttpServerWorker-1]
>>>> DEBUG
>>>> SOAPMessageFormatter end writeTo()
>>>> 2008-08-26 18:01:47,715 [192.168.13.175-INFOR2] [HttpServerWorker-1]
>>>> DEBUG
>>>> SSLIOSession I/O session sslclient-2 [interested ops: [r]; ready ops:
>>>> [w]][SSL handshake status: NEED_UNWRAP][0][0][0][0]: Set event [w]
>>>> 2008-08-26 18:01:47,715 [192.168.13.175-INFOR2] [HttpServerWorker-1]
>>>> ERROR
>>>> HttpCoreNIOSender IO Error while submiting request message for sending
>>>> org.apache.axis2.AxisFault: problem accessing the parser. Parser already
>>>> accessed!
>>>>    at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>>>>    at
>>>> org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83)
>>>>    at
>>>> org.apache.synapse.transport.nhttp.Axis2HttpRequest.streamMessageContents(Axis2HttpRequest.java:221)
>>>>    at
>>>> org.apache.synapse.transport.nhttp.HttpCoreNIOSender.sendAsyncRequest(HttpCoreNIOSender.java:346)
>>>>    at
>>>> org.apache.synapse.transport.nhttp.HttpCoreNIOSender.invoke(HttpCoreNIOSender.java:256)
>>>>    at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
>>>>    at
>>>> org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:190)
>>>>    at
>>>> org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:174)
>>>>    at
>>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
>>>>    at
>>>> org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:288)
>>>>    at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:57)
>>>>    at
>>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:222)
>>>>    at
>>>> org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:195)
>>>>    at
>>>> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:169)
>>>>    at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
>>>>    at
>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
>>>>    at
>>>> org.apache.synapse.transport.nhttp.ServerWorker.processPost(ServerWorker.java:253)
>>>>    at
>>>> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:194)
>>>>    at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>>>>    at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>>>>    at java.lang.Thread.run(Thread.java:595)
>>>> Caused by: javax.xml.stream.XMLStreamException: problem accessing the
>>>> parser. Parser already accessed!
>>>>    at
>>>> org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:960)
>>>>    at
>>>> org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:100)
>>>>    at
>>>> org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:68)
>>>>    at
>>>> org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:57)
>>>>    at
>>>> org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:557)
>>>>    at
>>>> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:232)
>>>>    at
>>>> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
>>>>    at
>>>> org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:471)
>>>>    at
>>>> org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79)
>>>>    ... 19 more
>>>>
>>>> Regards, Stefan Lecho.
>>>>   
>>>>       
>>>>         
>>> _______________________________________________
>>> Esb-java-user mailing list
>>> [email protected]
>>> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>>
>>>
>>>     
>>>       
>>   
>>     
>
>
> _______________________________________________
> Esb-java-user mailing list
> [email protected]
> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>   


_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Reply via email to