EJB module Error Observed ::?

[Former Member]

Hi @,

In my custom adaptor module I am getting the following error ::

Attempt to process file failed with com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.

PLease suggest why this error is coming ?

Regards

[Former Member]

Hi Beyong,

Check your method "Process"...It indicates exception is raised in methid "Process"...

Also you can changeyour exception part by..

catch (Exception e) {

ModuleException me = new ModuleException(e);

throw me; :

Otherwise you can debug the exact location by :

For this you would need to carry out certain steps which are :

1. In NWDS , create a new file in the META-INF folder of Enterprise Project. The name of the file should be log-configuration.xml.Paste the following content in this file

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE log-configuration SYSTEM "log-configuration.dtd">

<log-configuration>

<log-formatters>

<!-- This formatter produces human readable messages. -->

<log-formatter

name="trc"

pattern="%26d %150l [%t] %10s: %m"

type="TraceFormatter"/>

</log-formatters>

<log-destinations>

<!-- Destination for Trace Information of this sample -->

<log-destination

count="5"

effective-severity="DEBUG"

limit="2000000"

name="sample.trc"

pattern="./log/applications/sample/default.trc"

type="FileLog">

<formatter-ref

name="trc"/>

</log-destination>

</log-destinations>

<log-controllers>

<!-- Trace Location sample -->

<log-controller

effective-severity="DEBUG"

name="sample">

<associated-destinations>

<destination-ref

association-type="LOG"

name="sample.trc"/>

</associated-destinations>

</log-controller>

<!-- Logging Category: none, use the default XILog -->

</log-controllers>

</log-configuration>

2. In your process method, add following statement

AuditMessageKey auditMKey =

new AuditMessageKey(message.getMessageId(), AuditDirection.INBOUND);

Audit.addAuditLogEntry(

auditMKey,

AuditLogStatus.SUCCESS,

"CustomModule :: process method started");

This would send the statement "CustomModule :: process method started" to the Audit Log of XI server and you would be in a position to see upto which step your code is executing sucessfully. Audit log can be viewed at

http://<host>:<port>/MessagingSystem/monitor/monitor.jsp. you need to know the message ID for your transaction in this case.

Hope this wull help you.

Nilesh

[Former Member]

Hi,

did you check thist thread ?

Francesco

[Former Member]

you can try printing the stacktrace to System.err which will go to the defaultTrace file of J2EE engine and from there you can find out the root cause. The exepction you've specified is a wrapper exception and hence doesnt tell you the root cause.