> -----Original Message----- > From: Schouten, Andreas > Sent: 03 January 2002 18:25 > To: 'Vinodh Lakshminarayan' > Subject: RE: [JBoss-user] Runtime Exceptions in Session Bean > > Hello, > > if a runtime exception occurs, the comtainer has to remove the bean > instance. The 'FileNotFoundException' is irritating. The container can't > find the instance, because it's removed and asumes, that the bean was > passivated, but it isn't. > You need to catch the runtime exceptions and throw a non runtime, i. e. a > remote if it is a remote client, exception. The the beans instance should > not be removed. > Andreas > > -----Original Message----- > From: Vinodh Lakshminarayan [SMTP:[EMAIL PROTECTED]] > Sent: 03 January 2002 11:14 > To: [EMAIL PROTECTED] > Subject: [JBoss-user] Runtime Exceptions in Session Bean > > Hello everyone > > I have a peculiar case here.I have a stateful session bean which > basically talks to an Oracle database .The methods in the bean take care > of insert,update and deletion of rows and they throw a lot of runtime > exceptions.The problem is when there is a run time exception thrown the > exception is not propogated to the client but instead is caught by the > container.The server then tries to passivate the bean.An further calls to > this bean results in "FileNotFoundException : Could not activate the > bean". Any help is appreciated. > > I am using JBoss-2..4.0_Tomcat-3.2.2 bundle.( I have also tried the > NoPassivation in jboss.xml but is of no use.It is still passivated when > any runtime exception is thrown.) > > > > _____ > > Do You Yahoo!? > Send your FREE holiday greetings online at Yahoo! Greetings > <http://rd.yahoo.com/mail_us/tag/?http://greetings.yahoo.com/>. _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
