[pathogen]

The difference seems to have been that the ant scripts we are using in NB also wraps up all this Flex source code we have for our views and put it in the war (when it really should not).

[Riyad Kalla]

… you *sure* there isn’t some 10mb “ldap.jar” in there that you missed? 😀

When you compare the projects build paths, they look the same?

[pathogen]

LOL, nope, no 10MB LDAP jar. 😉 A far as I can see, same source path, same libs etc. The only diff I see at all is on startup, NB had a couple of jars that ME did not (see NB startup post, #6)

Specifically:
ME-
-Dcom.sun.aas.classloader.optionalOverrideableChain=webservices-rt.jar,webservices-tools.jar,commons-logging.jar,commons-launcher.jar

NB-
-Dcom.sun.aas.classloader.optionalOverrideableChain=webservices-rt.jar,webservices-tools.jar
-Dcom.sun.aas.promptForIdentity=true
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager

I’ve also noticed that ME when it starts up and deploys the app it will say by “Unknown user”. Is that normal? Thanks!

[Riyad Kalla]

Ok I feel like I am spinning off on a red-herring path here… I went back and re-read your original post… (For what seems like the 3rd time) to see if I missed something… and it actually seems that JNDI and LDAP are working fine as the communication with them is logged… the issue seems to be this last line:

javax.naming.CommunicationException: ourdirectory.acompany.com:636 [Root exception is java.net.SocketException: password can’t be null]

Implying that the connectiotn to the LDAP directory cannot be made because the password is null… then you showed when you start the server from NetBeans you get:

debug] swat.cwa: JNDI_ERROR=[LDAP: error code 48 – Inappropriate Authentication]

Which makes me thing that possibly in your NetBeans project you might have a properties file lingering some where that *is* setting the correct LDAP login credentials and when you ported the project to MyEclipse, that file got left behind possible?

I think libraries are fine… I may have jumped the gun on that library issue and ignored the fact that it looks like you are comming with the LDAP server already.

[pathogen]

Hi Rkalla,

No, there is no property file for the LDAP connection. The user inputs their user name and pswd via a login panel. This data then gets passed to an authenticate method in swat.cwa. It definitely has these values when it is handed off so no idea where this null stuff is coming from.

[Riyad Kalla]

I really wish I had a “next step”… libraries seem OK, startup seems OK… but the exception certainly looks like the credentials aren’t getting passed correctly.

So what we know so far is:
1. NB Project, NB Launch == Work
2. ME Project, ME Launch == No Work

do we know if:
3. NB Project, ME Launch == ?
4. ME Project, NB Launch == ?

I think you did #4 in your inital post, and were still seeing an error right?

[pathogen]

Hi, #3 is No Work but #4 is works. Perhaps it has something to do with the 0 KB marker file ME leaves in the autodeploy dir as compared to that generated by GF? Don’t really see how since as far as I can see there is nothing to the file but…

[Riyad Kalla]

At this point I really don’t know what is different between the ME launch and the NB launch to cause the differing results. I’m drawing a blank as far as what to look at next.

[Author]

Posts