java noclassdeffounderror when moving from weblogic to jboss

Question

We are moving our ftp sending from weblogic to jboss and when I try to send from the same code I get the following error. The correct libs are in jboss.

java.lang.NoClassDefFoundError: com/enterprisedt/net/puretls/i (wrong name: com/enterprisedt/net/puretls/I)

happen when we call SSLFTPClient.connect()

Answer 1

Please see https://issues.jboss.org/browse/JBVFS-170

Apparently it can be resolved by using -Djboss.vfs.forceCaseSensitive=true

- Hans (EnterpriseDT)

Answer 2

That did not affect anything and according to the bug that is only affected with JSP's. We are not calling that from a JSP we are calling it from an EJB. Any other suggestions?

Answer 3

Unfortunately this looks like an unresolved bug in Jboss, and it is not restricted to JSPs. See this report:

https://issues.jboss.org/browse/JBAS-9211

Answer 4

Thank you for finding that. I am going to attempt to unzip the jar and deploy the classes in the WEB-INF/classes directory for a work around in case anybody else is interested in this thread. I will let everybody know if it works.

Answer 5

That attempt has been unsuccessful. Just a question thought why aren't your developers following proper java naming standards? All class names are supposed to start with an uppercase letter so even though there is a jboss bug, there shouldn't be an i.class and an I.class somewhere anyways.

So your product is not compatible with JBoss version 6. That bug they claim they are fixing in JBoss version 6.1 but it looks to be quite a ways away considering the amount of bugs. Do you have any other suggestions how this could be rectified? We bought your commercial version a couple years ago but we have since expired on the support. I did try the newest version and the problem still remains.

Answer 6

That attempt has been unsuccessful. Just a question thought why aren't your developers following proper java naming standards? All class names are supposed to start with an uppercase letter so even though there is a jboss bug, there shouldn't be an i.class and an I.class somewhere anyways.

Although we do use the standard naming convention in our source-code, we run it through an obfuscator, which generates some lower-case file-names.

- Hans (EnterpriseDT)

Answer 7

We've used a different obfuscator that allows us to specify that mixed case names aren't to be used. We suspect the problem is that two classes with the same name (other than case) have been produced by the obfuscator. When one is loaded, the JBoss classloader (because it is buggy) does not load the other.

We've emailed you a link to the new jar - if this is successful we'll keep using this obfuscator for future releases.