on 02-13-2008 3:36 PM
Dears,
I'm trying to run a form on WebDynpro NWCE (Java only), and I receive the following exception:
javax.xml.rpc.soap.SOAPFaultException: javax.ejb.EJBException: nested exception is: com.sap.engine.services.ts.exceptions.BaseRollbackException: SAP J2EE ENGINE | TRANSACTION SERVICE | detected a Resource Manager ERROR | TRANSACTION [SAP J2EE Engine JTA Transaction : [071ffffff93ffffff96001dffffffb1]] WAS ROLLED BACK: In prepare phase of two phase commit protocol one or more XAResource returned unspecified in the JTA1.0.1 specification prepare status! Check the Resource Manager!"
I'm new to AdobeForms and the last statement ("Check the Resource Manager!") means nothing for me. I'm actually not sure the configuration of AdobeDocumentService is correct. The configuration check succeeds (as explained in the config guide), but then - why this problem appears?
Is there some simple WebDynpro application, which uses an Adobe Form, that can be used just for configuration testing?
Thank you for your response,
Todor
1. check if you have made the changes in your EJB code after you changed the type of the data in the DB Table
2. Generated the Entities again for the changed table
3. published the EAR file which contains the changed EJB
As mentioned in my first post, the WSDL file is absolutely fine (the type of the respective attribute is 'String' and not 'boolean) so I think I adopted the EJB appropriately and published ( = deployed) it with EAR. If not I couldn't reimport the Adaptive Webservice Model with the correct attribute type, could I?
Are there more things I have to do with EJB beside deploying it with EAR that it runs correctly?
When generating the entities the Java-Files don't get the same structure as the current ones (in the head of the files) and I get even more errors.
One more thing: In the EJB there is a persistence unit mentioned but I can't find it anywhere? Perhaps I have to modify that unit too?
Thanks & regards
Kevin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems the problem is related to legacy forms only (created by an older version of ALD).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.