Weblogic 6.1sp2 custom exceptions being transformed to remoteexceptions

Hi,
We've recently ported our application from weblogic 6.0sp2 to weblogic 6.1sp2.
In our ejbs we throw custom exceptions in our business logic, but somehow, in
weblogic6.1sp2, these are being transformed into ejbexception/remoteexceptions.
Do you have any ideas what we may be doing wrong?
Thanks

Thanks,
we were doing that, but our custom exceptions were inheriting from RuntimeException
instead of Exception which was the cause of the problem because weblogic 6.1 is
more strict than weblogic 6.0.
Diana
Matthew Shinn <[email protected]> wrote:
Hi Diana,
Make sure your custom exceptions are declared in the throws clause of
the
home\remote\localHome\local interface methods. If they are not declared
in the
throws clause of your interface methods, they will be wrapped in RemoteExceptions
or EJBExceptions before being thrown to the client.
- Matt
Diana wrote:
Hi,
We've recently ported our application from weblogic 6.0sp2 to weblogic6.1sp2.
In our ejbs we throw custom exceptions in our business logic, but somehow,in
weblogic6.1sp2, these are being transformed into ejbexception/remoteexceptions.
Do you have any ideas what we may be doing wrong?
Thanks

Similar Messages

Help with Weblogic 6 sp1 Custom Realm !!!!

We are trying to run Weblogic 6.0 sp1 with our current environment (ejb 1.1, custom
security realm)
We can compile and deploy our ejb 1.1 beans. We wish to start with ejb1.1 and
move to ejb2.0 once we can get our custom security working.
The JDBC connection pools are fine.
Our custom security realm uses LDAP for user authentication and an Oracle table
for authorization (acls).
Earlier, I wrote to the board and received the below following instructions to
use our existing custom realm in wl 60. You can read below, but I followed these
instructions on Solaris 5.6.
1. I ensured the SunOS patches were up to date.
2. We ensured the LD_LIBRARY_PATH reflected weblogic 6 (and not 5.1). We moved
the 5.1 classes over to wl6.
3. We copied our custom realm properties file to the weblogic root and/or the
config subdirectory (tried them both).
4. We ensured the security realm class we wrote is in the classpath (we bunch
all our serverside classes in a jar file anyway).
5. Then we created a custom realm via the console – name BFXRealm and it’s
class name <package>.BFXRealm, left configuration box blank.
6. Then we created a custom caching realm BFXCachingREalm and set its basic realm
as the custom realm, BFXRealm. All of the enable caches are checked to true.
7. Then we set the default realm to the BFXCachingRealm.
Now, when we perform a query, the everyone group should be implied. We don’t
implement LDAP lookup on queries. If I try to run a query from a client, I see
the client box connecting with the server:
Last line - you can see the client box connecting to the server -
<May 30, 2001 2:20:07 PM EDT> <Info> <J2EE> <Deployed : DefaultWebApp_myserver>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <WebLogic Server started>
<May 30, 2001 2:20:07 PM EDT> <Info> <Configuration Management> <Backed up booted
configuration /opt/apps/weblogic/beasp1/wlserver6.0sp1/./config/mydomain/config.xml
at /opt/apps/weblogic/beasp1/wlserver6.0sp1/./config/mydomain/config.xml.booted>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <SSLListenThread listening
on port 7002>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <System has file
descriptor limits of - soft: '1024', hard: '1024'>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <Using effective
file descriptor limit of: '1024' open sockets/files.>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <Allocating: '3'
POSIX reader threads>
<May 30, 2001 2:20:23 PM EDT> <Info> <HTTP> <[HTTP myserver] Created log stream
/opt/apps/weblogic/beasp1/wlserver6.0sp1/config/mydomain/logs/access.log>
<May 30, 2001 2:21:50 PM EDT> <Info> <WebLogicServer> <Adding address: 152.51.164.233/152.51
The client receives the error:
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
Authentication
for user aws4270 denied in realm weblogic
It’s as if the fileRealm.properties is only being looked at. We do not
use this for our user/groups/acls in wl5.1.0 and we do not want to in wl6
For “fun”, I added a user to the fileRealm.properties file via the
console and ran a client query. It worked.
But when I tried to call an ejbCreate from the client, I received these errors
from the server:
BFXSecurityRealmException is a custom exception we have written. A query works
but a create does not - obviously cannot get to acl in database (?)
and why the ejb20 errors? We just want to start with ejb 1.1
In SeqStoreSecurityHelper.isUserAuthorized(): schema = seqStore.INTNUC, class
= bioseq, project = HIPPI, permission = create
<May 30, 2001 2:50:10 PM EDT> <Info> <EJB> <EJB Exception in method: ejbCreate:
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBean.ejbCreate(BioSequenceBean.java:1562)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanImpl.ejbCreate(BioSequenceBeanImpl.java:833)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.DBManager.create(DBManager.java:408)
at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:353)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanHomeImpl.create(BioSequenceBeanHomeImpl.java:111)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanHomeImpl_WLSkel.invoke(BioSequenceBeanHomeImpl_WLSkel.java:78)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
The client receives the error:
java.rmi.RemoteException: EJB Exception:; nested exception is:
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
o
ccurred.
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
HOW CAN WE GET THE SERVER TO BYPASS FILEREALM and use BFXREALM ???????????
Thanks,
Anne
Subject: Re: Do Custom Security Realms have to use Mbeans?
Date: 17 May 2001 06:38:23 -0800
From: "Tom Moreau" <[email protected]>
Newsgroup: weblogic.developer.interest.security
Yes this can be done. Here's how:
1) I'll assume that the classname to your custom realm is "com.yourcompany.YourCustomRealm"
2) I'll assume that your custom realm has some kind of properties file from which
it reads its configuration data. Let's call this file "YourCustomRealm.properties"
3) Copy YourCustomRealm.properties to every machine that you're running wls on
(you are probably already doing this today).
4) Make sure that com.yourcompany.YourCustomRealm is in the classpath when you
start wls (you should already be doing this today)
5) In 5.1, there used to be some utility classes that customers used for their
custom realms - something about Pools & Factories. These have been renamed in
6.0. If you're using these classes, then go to your 5.1 weblogic jar file and
pull out these classes and add them to your classpath for 6.0.
6) In the console, create a custom realm and set it's realm class name to com.yourcompany.YourCustomRealm.
Leave the configuration data section blank.
7) In the console, configure your custom realm as the alternate realm. That is,
create a caching realm and set it's basic realm to your custom realm, then set
the realm's caching realm to the caching realm you just created.
I'm pretty sure this should work for you. We did this to provide a patch that
let 6.0 users uses the LDAPRealm rewrite from 5.1.
The downside is that you don't get single point of administration - that is, you
have to make your custom realm's configuration data (YourCustomRealm.properties)
available on all the machines you're running WLS on. If you rework your custom
realm, then the configuration data gets put in the custom realm configuration
you create via the console and automatically copied to other machines for you.
- Tom

We are trying to run Weblogic 6.0 sp1 with our current environment (ejb 1.1, custom
security realm)
We can compile and deploy our ejb 1.1 beans. We wish to start with ejb1.1 and
move to ejb2.0 once we can get our custom security working.
The JDBC connection pools are fine.
Our custom security realm uses LDAP for user authentication and an Oracle table
for authorization (acls).
Earlier, I wrote to the board and received the below following instructions to
use our existing custom realm in wl 60. You can read below, but I followed these
instructions on Solaris 5.6.
1. I ensured the SunOS patches were up to date.
2. We ensured the LD_LIBRARY_PATH reflected weblogic 6 (and not 5.1). We moved
the 5.1 classes over to wl6.
3. We copied our custom realm properties file to the weblogic root and/or the
config subdirectory (tried them both).
4. We ensured the security realm class we wrote is in the classpath (we bunch
all our serverside classes in a jar file anyway).
5. Then we created a custom realm via the console – name BFXRealm and it’s
class name <package>.BFXRealm, left configuration box blank.
6. Then we created a custom caching realm BFXCachingREalm and set its basic realm
as the custom realm, BFXRealm. All of the enable caches are checked to true.
7. Then we set the default realm to the BFXCachingRealm.
Now, when we perform a query, the everyone group should be implied. We don’t
implement LDAP lookup on queries. If I try to run a query from a client, I see
the client box connecting with the server:
Last line - you can see the client box connecting to the server -
<May 30, 2001 2:20:07 PM EDT> <Info> <J2EE> <Deployed : DefaultWebApp_myserver>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <WebLogic Server started>
<May 30, 2001 2:20:07 PM EDT> <Info> <Configuration Management> <Backed up booted
configuration /opt/apps/weblogic/beasp1/wlserver6.0sp1/./config/mydomain/config.xml
at /opt/apps/weblogic/beasp1/wlserver6.0sp1/./config/mydomain/config.xml.booted>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <SSLListenThread listening
on port 7002>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <System has file
descriptor limits of - soft: '1024', hard: '1024'>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <Using effective
file descriptor limit of: '1024' open sockets/files.>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <Allocating: '3'
POSIX reader threads>
<May 30, 2001 2:20:23 PM EDT> <Info> <HTTP> <[HTTP myserver] Created log stream
/opt/apps/weblogic/beasp1/wlserver6.0sp1/config/mydomain/logs/access.log>
<May 30, 2001 2:21:50 PM EDT> <Info> <WebLogicServer> <Adding address: 152.51.164.233/152.51
The client receives the error:
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
Authentication
for user aws4270 denied in realm weblogic
It’s as if the fileRealm.properties is only being looked at. We do not
use this for our user/groups/acls in wl5.1.0 and we do not want to in wl6
For “fun”, I added a user to the fileRealm.properties file via the
console and ran a client query. It worked.
But when I tried to call an ejbCreate from the client, I received these errors
from the server:
BFXSecurityRealmException is a custom exception we have written. A query works
but a create does not - obviously cannot get to acl in database (?)
and why the ejb20 errors? We just want to start with ejb 1.1
In SeqStoreSecurityHelper.isUserAuthorized(): schema = seqStore.INTNUC, class
= bioseq, project = HIPPI, permission = create
<May 30, 2001 2:50:10 PM EDT> <Info> <EJB> <EJB Exception in method: ejbCreate:
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBean.ejbCreate(BioSequenceBean.java:1562)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanImpl.ejbCreate(BioSequenceBeanImpl.java:833)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.DBManager.create(DBManager.java:408)
at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:353)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanHomeImpl.create(BioSequenceBeanHomeImpl.java:111)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanHomeImpl_WLSkel.invoke(BioSequenceBeanHomeImpl_WLSkel.java:78)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
The client receives the error:
java.rmi.RemoteException: EJB Exception:; nested exception is:
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
o
ccurred.
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
HOW CAN WE GET THE SERVER TO BYPASS FILEREALM and use BFXREALM ???????????
Thanks,
Anne
Subject: Re: Do Custom Security Realms have to use Mbeans?
Date: 17 May 2001 06:38:23 -0800
From: "Tom Moreau" <[email protected]>
Newsgroup: weblogic.developer.interest.security
Yes this can be done. Here's how:
1) I'll assume that the classname to your custom realm is "com.yourcompany.YourCustomRealm"
2) I'll assume that your custom realm has some kind of properties file from which
it reads its configuration data. Let's call this file "YourCustomRealm.properties"
3) Copy YourCustomRealm.properties to every machine that you're running wls on
(you are probably already doing this today).
4) Make sure that com.yourcompany.YourCustomRealm is in the classpath when you
start wls (you should already be doing this today)
5) In 5.1, there used to be some utility classes that customers used for their
custom realms - something about Pools & Factories. These have been renamed in
6.0. If you're using these classes, then go to your 5.1 weblogic jar file and
pull out these classes and add them to your classpath for 6.0.
6) In the console, create a custom realm and set it's realm class name to com.yourcompany.YourCustomRealm.
Leave the configuration data section blank.
7) In the console, configure your custom realm as the alternate realm. That is,
create a caching realm and set it's basic realm to your custom realm, then set
the realm's caching realm to the caching realm you just created.
I'm pretty sure this should work for you. We did this to provide a patch that
let 6.0 users uses the LDAPRealm rewrite from 5.1.
The downside is that you don't get single point of administration - that is, you
have to make your custom realm's configuration data (YourCustomRealm.properties)
available on all the machines you're running WLS on. If you rework your custom
realm, then the configuration data gets put in the custom realm configuration
you create via the console and automatically copied to other machines for you.
- Tom

Webservices and custom exception handling

hi all,
I have one ejb method which promote as webservices.
@WebMethod
@Oneway
public void test(String arg) throws STARS21BOException{
my Custom Exception class STARS21BOException extends from EjbException and it has no-arg constructor.
but when i deploy on server i get following exception.
if i remove throws clause from method, it is working fine.
javax.xml.ws.WebServiceException: Unable to create JAXBContext
     at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:158)
     at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:87)
     at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:271)
     at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:351)
     at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:201)
     Truncated. see log file for complete stacktrace
Caused By: java.security.PrivilegedActionException: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
java.lang.StackTraceElement does not have a no-arg default constructor.
     this problem is related to the following location:
          at java.lang.StackTraceElement
          at public java.lang.StackTraceElement[] java.lang.Throwable.getStackTrace()
          at java.lang.Throwable
          at java.lang.Exception
          at public java.lang.Exception sg.com.stee.stars21.showcase.business.jaxws.STARS21BOExceptionBean.causedByException
          at sg.com.stee.stars21.showcase.business.jaxws.STARS21BOExceptionBean
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIModelImpl.java:148)
     at com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelImpl.java:87)
     at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:271)
     at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:351)
     Truncated. see log file for complete stacktrace
Caused By: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
java.lang.StackTraceElement does not have a no-arg default constructor.
     this problem is related to the following location:
          at java.lang.StackTraceElement
          at public java.lang.StackTraceElement[] java.lang.Throwable.getStackTrace()
          at java.lang.Throwable
          at java.lang.Exception
          at public java.lang.Exception sg.com.stee.stars21.showcase.business.jaxws.STARS21BOExceptionBean.causedByException
          at sg.com.stee.stars21.showcase.business.jaxws.STARS21BOExceptionBean
     at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
     at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
     at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
     Truncated. see log file for complete stacktrace
>
<Apr 23, 2010 10:51:33 AM SGT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1271991082383' for task '2'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(ejb-showcaseEJB.jar)

newt.mm wrote:
@WebMethod
@Oneway
public void test(String arg) throws STARS21BOException{
}As per method signature it is asynchronous web service however you are trying to throw soap fault. Isn't the soap fault is also a kind of response?
Do you really want your web method to be asynchronous?

Throwing MbeanException wrapping custom exception

Iam throwing a mbean exception which wraps a custom exception from mbean.
Iam invoking this mbean from wlst(python script) and Iam trying to catch this MBeanException
When i try to use the getCause method i get the following exception .
"java.rmi.UnmarshalException: Problem finding error class; nested exception is:
java.lang.ClassNotFoundException: Failed to load class oracle.webcenter.lifecycle.exception.LifecyclePortalGuidMisMatchException"
Please note that the python script is aware of the custom exception (LifecyclePortalGuidMisMatchException).
For testing purpose, to confirm this, i have also created an instance of LifecyclePortalGuidMisMatchException in python (before invoking the mbean)
The complete exception stack
java.rmi.UnmarshalException: Problem finding error class; nested exception is:
java.lang.ClassNotFoundException: Failed to load class oracle.webcenter.lifecycle.exception.LifecyclePortalGuidMisMatchException
javax.management.MBeanException
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_1035_WLStub.invoke(Unknown Source)
at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:919)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:917)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at ora_mbs$py.invoke$8(/ade/aimmanue_pt/oracle/oracle_common/common/wlst/lib/ora_mbs.py:56)
at ora_mbs$py.call_function(/ade/aimmanue_pt/oracle/oracle_common/common/wlst/lib/ora_mbs.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at LifecycleHandler$py._doScopeImport$26(/ade/aimmanue_pt/oracle/as11gr1wc/common/script_handlers/LifecycleHandler.py:892)
at LifecycleHandler$py.call_function(/ade/aimmanue_pt/oracle/as11gr1wc/common/script_handlers/LifecycleHandler.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at ExpImpHandler$py.importGroupSpaces$9(/ade/aimmanue_pt/oracle/as11gr1wc/common/script_handlers/ExpImpHandler.py:113)
at ExpImpHandler$py.call_function(/ade/aimmanue_pt/oracle/as11gr1wc/common/script_handlers/ExpImpHandler.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
Could you let me who why iam not able to get the cuase of the exception when the client is aware of the exception
Edited by: user510156 on Aug 20, 2012 6:43 AM
Edited by: user510156 on Aug 20, 2012 6:49 AM

Hi,
There is no API to provide this functionality. The reason is the XI message processing is through pipeline as you know. And this is nothing but SAP specific services. So you can not alter them as they are. For the request that you are asking, you will have to edit the pipeline step that populates the SAP:ERROR node. For this, we need to identify which service does this and then if it is possible to write a user exit, etc...So in this case, I would suggest you go with raising an OSS note.
However, can you please tell us why is this required? I can understand to send a message/mail if you get an error or something like that. But I am not able to figure out in what scenarios would you require this kind of error display.
Thanks and Regards,
Sarath.

Problems with Custom Exception Handler

Hi,
I have defined a custom exception handler for my workflow (WebLogic Platform
7).
I have a workflow variable called 'count' , which gets incremented for every
time an exception occurs.
The exception handler checks if the count is less than 3(using evaluate
condition),
if yes then it executes the action "Exit Execption Handler and retry"
else
it executes the action "Exit Execption Handler and continue"
The Workflow simply hangs, nothing on the console , the worklist from which
i call it hangs too.
Has anyone managed to use this kind of exception handling?
Thanks in advance,
Asif

bill0 wrote:
> Thanks for all the help but still no luck.
>
> The directory is d:\wSites\GBMain\html\CFMS> and I am
mapped to it as x:\CFMS.
> Most of the cfm files are in CFMS but Application.cfm is
1 directory up in
> html. I have tried misscfm.cfm in both html and CFMS but
had no luck having it
> find a non existant template referred to in a cfinclude
or a form's action
> attribute. The default ColdFusion error handler is what
shows. The missing
> template handler box says /misscfm.cfm. Misscfm.cfm is
text followed by a
> <cfabort>. We use ColdFusion MX6.1
>
> I hope that is enough information to figure what am I
missing and/or doing
> wrong.
>
>
Is the 'misscfm.cfm' file somewhere in the
'd:\wSites\GBMain\html\CFMS\'
directory. I will presume this is the 'web root' as defined
in your web
server (IIS or Apache or built-in or ???). The missing
template handler
file needs to be in the ColdFusion root. This is going to be
a
directory such as
'{drive}:\JRun4\servers\{server}\cfusion-ear\cfusion-war\misscfm.cfm'
for J2EE flavors OR '{drive}:\CFusionMX\wwwroot' for Standard
I think.
It has been a very long time since I have dealt with
Standard.
This is probably completely different from the above web
root. That is
the point I am trying to get across. ColdFusion has TWO roots
where it
will look for a CFML file. But the Missing and Sitewide
templates can
only be in the ColdFusion root listed above, they will not
work in the
web root.
HTH
Ian

What factors should be taken into account for Custom Exceptions

hi,
I just want to know that What factors should be taken into account for making Custom Exceptions.
any examples will appreciated.
regards,
vjoy

Do you want this to be checked exception? If so extend it from Exception or subclass of it. If it is unchecked exception (not forced by javac to be caught by callers), then extend it from RuntimeException or subclass of it. Exceptions are serializable objects and so have serialVersionID field. Also, to allow for exception chaining, define a constructor that accepts "cause" (http://java.sun.com/j2se/1.4.2/docs/guide/lang/chained-exceptions.html)

How to access custom exception in client side in web services?

I have an interface and implementation of a java web services. One method in it throws a custom exception indicating the error type (authrization fails, db connection lost, etc...). But in the generated proxy file, the catched exception for the correspondent method becames java.lang.Exception. I check the code and found the actual thrown exception is com.apache.soap.SOAPExcetion. In the client code, I printed out all the SOAPExcetion and related Fault messages but could not find my original custom exception info. I need this custom exception to be accessed to the client so the client knows what's wrong.

for current user, SPGroup.ContainsCurrentUser
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spgroup.containscurrentuser.aspx
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

Transformer exception while transforming BEx Web templates

Hello,
when opening the web application designer or calling a web template in the browser the error Transformer exception while transforming BEx Web templates occours. I found several hints in the forum like solving the problem with the SAP NetWeaver BI Diagnostics & SupportDesk Tool and several notes for this issue (like 937697). Unfortunately nothing works and the diagnostics tool says that everything is configured fine. The release is 701, SP4.
Has someone suggestions where to start searching the error?
Thanks a lot,
Vanessa

Hi Vanessa,
Which JAVA patch are you using?
Is it possible to download the latest patches and re-test the problem? You may find that the latest patch corrects the roblem
Regards,
Karen

Native C++ Custom Exception Not Recognized

Hi,
I'm having a problem with the native part of my code when throwing a custom exception. It is never caught when the exception is thrown in a separate class, it always falls in the generic catch(...) section. I know this problem has something to do with JNI and Java since running a C++ test program doing the same thing recognizes the exception and catches it.
My Program is something like this
Java Part:
public class RunException {
public static void main(String args[]) {
     doSomething();
}C++ Part:
class CustomException: public exception {
   public :
       exception() {};
class CatchException: public exception {
   public:
      doSomething() {
        try {
           throwException->throwException();
           throw CustomException(); //this would have been caught in catch(CustomException)
        }catch(CustomException e) {
         //never goes in here
        catch(int e) {
         //this works
        catch(...) {
        //always goes ends up here here
class ThrowException {
public:
    throwException() {
       throw CustomException(); //this ends up in catch(...)
       //throw 1 - throwing an integer would work
} I'm not sure what's causing this but I'm guessing it has something to do with loading and linking or maybe some sort of JVM security policy/behavior? Any help would be greatly appreciated.
Edited by: z3n3r on Nov 13, 2008 7:51 PM

Never seen this. Some comments on your C++:
class CustomException: public exception {
public :
exception() {};That should be CustomException() {}
}catch(CustomException e) {That should be catch (CustomException &e). Never catch exceptions by value.
throwException() {That should be throwException() throw(CustomException) {}, although good old MSVC still ignores it 15 years later ...

Weblogic 7 SP5 SQL Exceptions follow a JTA transaction timeout

I have a problem in Weblogic 7 SP5 that was not happening in SP2. I'm using the
Weblogic jDriver (weblogic.jdbc.mssqlserver4.Driver)
I have a transaction that times out due to JTA transaction timeout, and then gets
marked for rollback. For several minutes after the timeout, I get many SQL Exceptions
with bogus messages like "invalid column name" when the column name is, in fact,
correct.
Then the weblogic log file shows "Exception during rollback of transaction" (javax.transaction.SystemException:
Heuristic hazard). Next, the connection is tested on reserve, this test fails,
and the connection is refreshed. As soon as the connection is refreshed, I stop
getting SQL exceptions and everything starts working correctly again.
It seems like the transaction timeout is making the connection go bad, and somehow
other requests are using this bad connection before the transaction finishes rolling
back. What could the problem be? Some excerpts from my app log and weblogic log
are below.
com.workpoint.server.ejb.WorkPointEJBException: The transaction is no longer active
- status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 901 seconds
Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17109:68c10765ba68aaaa(12114044),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=901,seconds left=60,activeThread=Thread[WorkQueueThread[q=1, qName=ProcReleaseTaskWorkers,
id=6],5,WorkQueueGroup[id=1, name=ProcReleaseTaskWorkers]],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none,xar=weblogic.jdbc.jts.Connection@18cd616,re-Registered
= false),SCInfo[DomainManager+edwards-s1]=(state=active),properties=({weblogic.transaction.name=[EJB
com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+)]'.
No further JDBC access is allowed within this transaction.SQL Command = INSERT
INTO WP_PROCI_NODE_HIST (NODE_HIST_ID, NODE_HIST_DB, PROCI_ID, PROCI_DB, PROCI_NODE_ID,
PROCI_NODE_DB, NODE_ITERATION, NODE_STATE_ID, ROW_VERSION, LU_ID, LU_DATE) VALUES
weblogic.jdbc.mssqlserver4.TdsException: Invalid column name 'user_fname'.
[from weblogic log]
####<Jun 17, 2004 8:14:16 AM MDT> <Error> <EJB> <EDWARDS> <edwards-s1> <WorkQueueThread[q=1,
qName=ProcReleaseTaskWorkers, id=7]> <kernel identity> <> <010025> <Exception
during rollback of transaction Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17439:68c10765ba68aaaa(31878774),Status=Rolled
back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=3,seconds left=57,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=edwards-s1,xar=weblogic.jdbc.jts.Connection@15e1b7e,re-Registered
= false),SCInfo[DomainManager+edwards-s1]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+): javax.transaction.SystemException:
Heuristic hazard: (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAException:
I/O exception while talking to the server, java.io.EOFException))
####<Jun 17, 2004 8:14:17 AM MDT> <Warning> <JDBC> <EDWARDS> <edwards-s1> <ExecuteThread:
'8' for queue: 'default'> <kernel identity> <> <001094> <A connection from pool
"sp_connection_pool" was tested during reserve with the SQL "select 1" and failed:
weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server,
java.io.EOFException
...[stack trace omitted]...
This connection will now be refreshed.>

Brad Swanson wrote:
According to BEA's documentation, the jDriver is deprecated (no longer supported)
in WLS 7 SP5. Not sure when they stopped supporting it, but sometime after SP2,
apparently. Our solution, unfortunately, was to stay with SP2. Using the newer,
supported JDBC driver would presumably fix the problem, but we didn't have time
to do a full regression test with a different driver.Hi, no. The jDriver is deprecated, not unsupported. For WLS releases that contain
the jDriver it will be supported for as long as we support the WLS release!
Deprecation just means that we may choose to not supply that driver in any future
release, and will not support it in that or any subsequent release.
Practically, much depends on which jDriver you're using. In decreasing order
of practical support we have: The weblogic.jdbc.oci.Driver to Oracle: We do actively
continue to fix bugs in it. The weblogic.jdbc.mssqlserver4.Driver: Very unlikely that
we will fix any new problem with it. The weblogic.jdbc.ifmx.Driver: Even less
likely that we will do anything with it...
I hope that makes it better for you.
Joe

Custom exceptions and carrying forward stack trace

Hi, I have a question on exception handling.
I have written an application which has several custom exceptions. When an exception occurs, sometimes I throw it and then when its caught, wrapping it in another exception like so:
} catch (Exception e){
throw new CollectionFailedException(this.getName() + " could not get collection", e);
This works fine, but when I output the stacktrace, it only goes as far as the new exception, making things more difficult to debug. Is there any way of incrementing the stack trace using the first exception?
Many thanks for any help offered!
Marc

Marc, this is expected behaviour. When you throw a new exception, the stacktrace starts off at the new one. A really nice explanation and sample code for creating new Exceptions and extending the Exception class is located at:
http://www.javaworld.com/javaworld/jw-09-2001/jw-0914-exceptions.html
Good luck, fstream

Raise custom exception

Hi experts,
I have synchronous scenario and in response inbound message I have Fault type ft_my_error_message.
My question is: how I can raise my custom exception ft_my_error_message in mapping.
I would like to send some information in my custom exception and catch it in ABAP proxy. With
throw new StreamTransformationException("my message");
I’m losing response message and in ABAP proxy I don’t know is my custom error occurred or something else.
Thanks
Vedran

Hi Vedran
Based on the discussion above, it looks like the JDBC call returns the error on the RESPONSE message and do not have a FAULT message type, is that right? Also, you mentioned ABAP proxy, so I'm guessing your scenario is synchronous Proxy to JDBC.
If the JDBC call does not have a FAULT message, AFAIK I don't think you can map this back to the Proxy fault message.
An alternative approach would be to map back the JDBC response to the Proxy response, and handle this in the ABAP proxy.
In the proxy coding, you can check for the values in the response for an indicator of the error. If an error happens, you can raise an exception there. You can check out the link below on how to raise fault messages in the proxy.
https://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
If you use the application log, or have access to error information from a BAPI return table, you can also use these directly to complete the fault message. In this case, you only need to call the methodCL_PROXY_FAULT=>RAISE of the proxy runtime to trigger the error:
CALL METHOD cl_proxy_fault=>raise
EXPORTING
   exception_class_name   = <Name of Exception Class>
   application_log_handle = < Application Log: Handle of a Protocol>
   bapireturn_tab         = < Table with BAPI Return Information>.
The exception class name would be the proxy generated class based on the custom fault type that you declared for the proxy service interface.
Once the exception is raised in the ABAP proxy, you will see this as an "Application Error" in SXMB_MONI of your ECC system.
Rgds
Eng Swee

How to use customized exception

Hi all,
I have a problem using struts-action-mappings.
I have a method for update in my app module, and i'm using that method with data action.
In that method, I have to throw my customized exception to user if there is error. I just don't know how to catch the exception and display it in page.
I've read about struts page flow diagram elements and know there are Exceptions and Global Exceptions. But i still don't know how to use them.
What i want to know is can I relate my custom exception with Exceptions/Global Exceptions in struts diagram? And if so, can anybody show me an example for it?
Thanks

1.Create a method GET_ACTORS using RH_GET_ACTORS,
2.Create a container element 'Actors' type string with multiline.
3.Create Task, where you can call the Method GET_ACTORS and pass the Container values of 'Actors' from Method->Task->Workflow
4.Create a Step type before creating the Step mail and include the previous Task.
5.Now you can create the step Mail. Give the Recipient Type as 'Expression'-> Select the Container Element 'Actors' from WF container
But remember the values should be Passed from the task to Workflow in Binding correctly.
Regards,
Sriyash

Raising Custom Exceptions in RMI

hi all,
i have a problem. i have an RMI server that makes use of some classes. in those classes, i am raising exceptions.
problem is that the first time that those classes are called, the correct custom exception is raised.
all the following times, i receive a java.util.EmptyStackException, and looking at the log file that i write, it seems that the call never reaches the inteded class.
All the custom exceptions that i use extends the java.lang.Exception class
can anyone explain me why i got this weird behaviour??
thanx in advance and regards
marco

What was the resolution to this. I am getting an EmptyStackException running a application with 50 threads. I get this exception in one thread and recover OK. I get the exception in another thread and the whole process hangs! Any thoughts?

Mapping custom faults to custom exceptions

Hello all,
I defined a web service that could thow for some operations custom faults. These custom faults were manually defined in the WSDL file of the web service. I sent some request messages to the web service and I received the result and everything seems to be fine.
I automatically generated the Java stub/client, but it seems that the client doesn't receive custom exceptions for the corresponding custom faults defined in the WSDL file. I would like that, in the Java client, for the custom faults defined in the WSDL for the operations exposed, the client to receive corresponding custom exceptions. I work with JDev 9.0.5, OC4J 10g 9.0.4. release. Is this possible in that release? I knew that there were limitations regarding JAX-RPC in that release... If not, will this be available in 10.1.3 release?
As an additional info, I tried to generate the Java client stub with AXIS WSDL2Java tool. Also, I received a generic exception for the custom faults, due to the fact that for the custom exceptions (from code generated by axis tools) to work, you need axis both on client and the server.
Many thanks in advance!
Regards,
Marinel

Hi,
I'm uncertain about 9.0.4/10.1.2 (I will investigate further), but 10.1.3 supports fault to exception and exception to fault mappings.

Weblogic 6.1sp2 custom exceptions being transformed to remoteexceptions

Similar Messages

Maybe you are looking for