Skip to Main Content
Forums

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

How to log stack trace of EJB exception cause

We need to log stack trace of exception we are getting from EJB call. We are trying to log it with slf4j with log4j backend:

EJBException ee; LOG.error("EJB exception details: ", ee.getCausedByException());

but this logs only exception type (NullPointerException) without stacktrace. What may be the problem with stacktrace? I tried -XX:-OmitStackTraceInFastThrow even though I don't know if it's valid parameter for our IBM J9 VM, but it didn't help. Our weblogic is in version 12c.

Comments

John Stegeman

Unique constraints automatically create (or "capture," if one already exists) an index, so just create the constraint - no need for a separate index. The underlying index may be unique or not, depending upon whether the constraint is deferrable. So, you can make the error go away by not creating the index in the first place

Having said that, it looks like you've discovered a situation where Oracle gets confused, and filing an SR with Oracle could either get that issue resolved or explained as to why it's not an issue.

John

1 person found this helpful
Solomon Yakobson
Answer

First of all you have show_orders in index and show_order in constraint. I'll assume it is a typo. Secondly, when you create constraint without specifying reinforcing index Oracle looks for existing index on same set of columns in ASCending order. If such index doesn't exists (and that's your case since one of your index columns is in DESCending order), Oracle tries to create one with same name as the constraint. That's why you get ORA-00955: name is already used by an existing object. In general, you can explicitly specify index name to force Oracle using existing index. But it will not help you. If you issue

alter table orders add constraint orders_year_show_uq unique(year, show_orders) using index orders_year_show_uq;

You'll get ORA-14196: Specified index cannot be used to enforce the constraint.

Anyway, Oracle doesn't support using DESC indexes for PK/UK.

SY.

Marked as Answer by Giovanni_66 · Sep 27 2020
Giovanni_66

Ok, thank you for your answer.

1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jul 2 2013
Added on Jun 4 2013
#12c, #application-servers, #ejb, #exception, #java, #oracle-application-server-general
0 comments
598 views