Hey, thanks for sharing your solution Robert. It turned out I had the same problem, and now I am good to go. This is very strange to me, since the jndi properties never changed between deployments. This was a really frustrating bug. But, thanks to you, I've got a workaround I can certainly live with.
Thanks, -- John ----- Original Message ----- From: "Robert Martin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 07, 2002 10:25 AM Subject: RE: [JBoss-user] Re: ClassCastException on redeploy of .ear > I had this exact problem, but with an ejb jar instead of an ear. I could > deploy the jar exactly once and it would work fine. After that I could > never redeploy it without it permanently breaking. The only way to fix the > problem was to shut down the server. > > After reading this message, I checked my jar and found that a > jndi.properties file I use for client-side access had sneaked into the file. > The contents of the jndi.properties were valid, but it shouldn't have been > in the jar file. After removing the jndi.properties, everything works fine. > > Question - is the behavior described above a bug or a feature that we were > accidentally misusing? It would seem to be a fairly severe vulnerability in > the server that an errant jndi.properties file in a jar file can permanently > break the server. Any insight? > > Thanks. > > Robert ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd522.html _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
