2013 Jan 14 8:55 AM
Hi,
the scenario is that I want to get the Content of a file in the portal KM via ABAP web service call.
Everything is working fine, when the file size is less than 1 MB.
But when the file is larger or the lenght defined is smaller than the file size following error occurs:
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Header>
<To xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</To>
<Action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</Action>
<RelatesTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:92377e15-5e27-11e2-bf3a-00000084833e</RelatesTo>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>javax.ejb.EJBTransactionRolledbackException: Cannot assign resources for execution of method getContentFirstChunk for bean: sap.com/tc~kmc~bc.rf.ws~rfws~ear*xml|sap.com~tc~kmc~bc.rf.ws~wsrf~bean.jar*xml|RepositoryFrameworkBean -> com.sap.netweaver.bc.rf.ws.bean.RepositoryFrameworkBean@4abaefe7; nested exception is: com.sap.engine.services.ejb3.facades.internal.tx.ResourceUsageException: com.sap.engine.services.connector.exceptions.BaseResourceContextException: TxManager was not used correctly and TxManager.leaveLevel() was not called on all started TxManager txLevels. The problem is detected from connection management system because last entered method is "TxManager_tx_level", but exit method is "getContentFirstChunk" instead of "TxManager_tx_level".; nested exception is: javax.ejb.EJBException: Cannot assign resources for execution of method getContentFirstChunk for bean: sap.com/tc~kmc~bc.rf.ws~rfws~ear*xml|sap.com~tc~kmc~bc.rf.ws~wsrf~bean.jar*xml|RepositoryFrameworkBean -> com.sap.netweaver.bc.rf.ws.bean.RepositoryFrameworkBean@4abaefe7; nested exception is: com.sap.engine.services.ejb3.facades.internal.tx.ResourceUsageException: com.sap.engine.services.connector.exceptions.BaseResourceContextException: TxManager was not used correctly and TxManager.leaveLevel() was not called on all started TxManager txLevels. The problem is detected from connection management system because last entered method is "TxManager_tx_level", but exit method is "getContentFirstChunk" instead of "TxManager_tx_level".</faultstring>
<detail>
<yq1:com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException xmlns:yq1="http://sap-j2ee-engine/error">javax.ejb.EJBTransactionRolledbackException: Cannot assign resources for execution of method getContentFirstChunk for bean: sap.com/tc~kmc~bc.rf.ws~rfws~ear*xml|sap.com~tc~kmc~bc.rf.ws~wsrf~bean.jar*xml|RepositoryFrameworkBean -> com.sap.netweaver.bc.rf.ws.bean.RepositoryFrameworkBean@4abaefe7; nested exception is: com.sap.engine.services.ejb3.facades.internal.tx.ResourceUsageException: com.sap.engine.services.connector.exceptions.BaseResourceContextException: TxManager was not used correctly and TxManager.leaveLevel() was not called on all started TxManager txLevels. The problem is detected from connection management system because last entered method is "TxManager_tx_level", but exit method is "getContentFirstChunk" instead of "TxManager_tx_level".; nested exception is: javax.ejb.EJBException: Cannot assign resources for execution of method getContentFirstChunk for bean: sap.com/tc~kmc~bc.rf.ws~rfws~ear*xml|sap.com~tc~kmc~bc.rf.ws~wsrf~bean.jar*xml|RepositoryFrameworkBean -> com.sap.netweaver.bc.rf.ws.bean.RepositoryFrameworkBean@4abaefe7; nested exception is: com.sap.engine.services.ejb3.facades.internal.tx.ResourceUsageException: com.sap.engine.services.connector.exceptions.BaseResourceContextException: TxManager was not used correctly and TxManager.leaveLevel() was not called on all started TxManager txLevels. The problem is detected from connection management system because last entered method is "TxManager_tx_level", but exit method is "getContentFirstChunk" instead of "TxManager_tx_level".</yq1:com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Do you have any solutions?
Hi,
the scenario is that I want to get the Content of a file in the portal KM via ABAP web service call.
Everything is working fine, when the file size is less than 1 MB.
But when the file is larger or the lenght defined is smaller than the file size following error occurs:
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Header>
<To xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</To>
<Action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</Action>
<RelatesTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:92377e15-5e27-11e2-bf3a-00000084833e</RelatesTo>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>javax.ejb.EJBTransactionRolledbackException: Cannot assign resources for execution of method getContentFirstChunk for bean: sap.com/tc~kmc~bc.rf.ws~rfws~ear*xml|sap.com~tc~kmc~bc.rf.ws~wsrf~bean.jar*xml|RepositoryFrameworkBean -> com.sap.netweaver.bc.rf.ws.bean.RepositoryFrameworkBean@4abaefe7; nested exception is: com.sap.engine.services.ejb3.facades.internal.tx.ResourceUsageException: com.sap.engine.services.connector.exceptions.BaseResourceContextException: TxManager was not used correctly and TxManager.leaveLevel() was not called on all started TxManager txLevels. The problem is detected from connection management system because last entered method is "TxManager_tx_level", but exit method is "getContentFirstChunk" instead of "TxManager_tx_level".; nested exception is: javax.ejb.EJBException: Cannot assign resources for execution of method getContentFirstChunk for bean: sap.com/tc~kmc~bc.rf.ws~rfws~ear*xml|sap.com~tc~kmc~bc.rf.ws~wsrf~bean.jar*xml|RepositoryFrameworkBean -> com.sap.netweaver.bc.rf.ws.bean.RepositoryFrameworkBean@4abaefe7; nested exception is: com.sap.engine.services.ejb3.facades.internal.tx.ResourceUsageException: com.sap.engine.services.connector.exceptions.BaseResourceContextException: TxManager was not used correctly and TxManager.leaveLevel() was not called on all started TxManager txLevels. The problem is detected from connection management system because last entered method is "TxManager_tx_level", but exit method is "getContentFirstChunk" instead of "TxManager_tx_level".</faultstring>
<detail>
<yq1:com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException xmlns:yq1="http://sap-j2ee-engine/error">javax.ejb.EJBTransactionRolledbackException: Cannot assign resources for execution of method getContentFirstChunk for bean: sap.com/tc~kmc~bc.rf.ws~rfws~ear*xml|sap.com~tc~kmc~bc.rf.ws~wsrf~bean.jar*xml|RepositoryFrameworkBean -> com.sap.netweaver.bc.rf.ws.bean.RepositoryFrameworkBean@4abaefe7; nested exception is: com.sap.engine.services.ejb3.facades.internal.tx.ResourceUsageException: com.sap.engine.services.connector.exceptions.BaseResourceContextException: TxManager was not used correctly and TxManager.leaveLevel() was not called on all started TxManager txLevels. The problem is detected from connection management system because last entered method is "TxManager_tx_level", but exit method is "getContentFirstChunk" instead of "TxManager_tx_level".; nested exception is: javax.ejb.EJBException: Cannot assign resources for execution of method getContentFirstChunk for bean: sap.com/tc~kmc~bc.rf.ws~rfws~ear*xml|sap.com~tc~kmc~bc.rf.ws~wsrf~bean.jar*xml|RepositoryFrameworkBean -> com.sap.netweaver.bc.rf.ws.bean.RepositoryFrameworkBean@4abaefe7; nested exception is: com.sap.engine.services.ejb3.facades.internal.tx.ResourceUsageException: com.sap.engine.services.connector.exceptions.BaseResourceContextException: TxManager was not used correctly and TxManager.leaveLevel() was not called on all started TxManager txLevels. The problem is detected from connection management system because last entered method is "TxManager_tx_level", but exit method is "getContentFirstChunk" instead of "TxManager_tx_level".</yq1:com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Do you have any solutions?
2014 Nov 14 5:58 PM
Hi Manuel!
You should use the method getContentFirstChunk for the first 1048576 bytes. After this you should use getContentNextChunk sending the token (generated in getContentFirstChunk) and more 1048576 bytes while the parametter lastChunk return false.
Regards,
Leo
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |