Hello Simone,
Thanks for the quick reaction, this is really a useful mailing list!
Anyway, last night I -becoming more and more irritated by not being able to
solve the problem myself- simply started to do what I always do when I can't
find the source of a problem: backtrace to the last point before the
exception was thrown and then going through the code step-by-step.
This way, I found the solution to the problem: turned out there WAS an
exception being thrown in ejbActivate (my generator was using legacy code
from the BMP-generator which I forgot to erase...*bows head in shame* =)
Louis, maybe this method will help you find the cause of the problem (if you
want to debug jBoss quickly, simply look up in the server.log file where
exactly the exception is thrown -class/lineno-, open the appropriate .java
file and put a debug statement (the Log class is very useful). Then you can
put the compiled class(es) into the appropriate .jar (most classes are in
jBoss.jar and start jBoss. You can then see your 'customized' trace info.
Although I haven't found any errors in jBoss (yet ;-), this helped me to
locate errors in my own code very efficiently. It also gave me a much better
understanding of the 'inner workings' of jBoss.
Anyway, thanks for the help and hope I can return the favor sometime,
With kind regards,
Sietze
>Hey,
>please always post jboss version, OS, DB
>Anyway you're using jboss 2.0 and that exception should be related to the
>fact that there is some problem in activating your beans.
>If you're using CMP, then this is very strange (unless you throw an
>exception in ejbActivate ;).
>If BMP, check that no unexpected exceptions (NPE and the like) are thrown
>from ejbActivate.
>Would be helpful if you could post client code and ejb code
>Simon
> -----Original Message-----
> From: Sietze Dijkstra [mailto:[EMAIL PROTECTED]]
> Sent: giovedì 1 febbraio 2001 16:23
> To: [EMAIL PROTECTED]
> Subject: [jBoss-User] Weird stuff with finder results
>
>
> Hello, All
>
> I would like to post the following question to the community:
>
> I am writing some custom finder methods for CMP Entity Beans
> (which have
> been tested). Some return single objects, others return
> Collections. The
> finders returning single objects function perfectly.
>
> The problem is, when I try to access the Collections (by
> wrapping a Vector
> around them) I can see each remote object, it returns the
> correct number of
> objects and I can succesfully cast them to the remote
> interface I'm looking
> for.
>
> However, when I try to subsequently access the bean via this
> interface, it
> goes wrong, dumping the following stack trace (in the output pane):
>
> [Player] TRANSACTION ROLLBACK EXCEPTION:null; nested exception is:
> java.rmi.NoSuchObjectException
> [Player] java.rmi.NoSuchObjectException
> [Player] at
> org.jboss.ejb.plugins.EnterpriseInstanceCache.get(EnterpriseIn
> stanceCache.ja
> va:95)
> [Player] at
> org.jboss.ejb.plugins.EntityInstanceCache.get(EntityInstanceCa
> che.java:56)
> [Player] at
> org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityI
> nstanceInterce
> ptor.java:136)
> [Player] at
> org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxIntercepto
> rCMT.java:133)
> [Player] at
> org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxI
> nterceptorCMT.
> java:263)
> [Player] at
> org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT
> .java:99)
> [Player] at
> org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInter
> ceptor.java:14
> 4)
> [Player] at
> org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
> [Player] at
> org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:323)
> [Player] at
> org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(
> JRMPContainerI
> nvoker.java:163)
> [Player] at java.lang.reflect.Method.invoke(Native Method)
> [Player] at
> sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
> [Player] at sun.rmi.transport.Transport$1.run(Unknown Source)
> [Player] at java.security.AccessController.doPrivileged(Native
> Method)
> [Player] at
> sun.rmi.transport.Transport.serviceCall(Unknown Source)
> [Player] at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown
> Source)
> [Player] at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unkno
> wn Source)
> [Player] at java.lang.Thread.run(Unknown Source)
>
> Having read through Java2's documentation, I assume that the
> Container has
> found the correct records in the underlying database, translated the
> resulting ResultSet into a Collection (ArrayList?) and then
> either forgot to
> instantiate the EJBs or passivated them.
>
> Has anyone seen this before and -better yet =)- knows a solution?
>
> Thanks in advance,
>
> Sietze Dijkstra
> Centaur Media Technology
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
