G Lambert

Greenhorn
+ Follow
since May 14, 2009
Merit badge: grant badges
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by G Lambert

Greetings. I know this issue is somewhat common, however nothing I've read has been able to assist me.

I'm currently migrating a Jboss application to use WAS 8 EJB 3.1. It is an older application.

I get the error "java.rmi.RemoteException: Name comp/env/jdbc not found in context "java:"." despite the datasources being set up in both the web.xml and the ibm-web.bnd.xmi files.

WEB.XML:


ibm-web.bnd.xmi (which I'm sure you know hides the reference back to "jdbc/MyDB"):


The WAS admin console has the datasource correctly setup with a green test connection and is definitely called "jdbc/ActualDS"

I execute the indirect JNDI lookup (it MUST be indirect, I cannot use "jdbc/MyDB" in the lookup string to get around the issue) ...


...but receive the error:

java.rmi.RemoteException: Name comp/env/jdbc not found in context "java:".

When I research the issue, the IBM docs tell me to do exactly what I've already done (e.g., create references in both the web.xml and binding files).

What am I missing? And yes, I know I can use annotations, it's a major refactor I might do, but it's off-topic at the moment. This was of course all working in Jboss as-is, but it used the jboss-web.xml to create the references.

Appreciate any help...
Ok, it appears I'll answer my own question as I think I've found the answer and it is NO.

http://java.sun.com/products/jndi/tutorial/ldap/models/exceptions.html

- lists all possible response codes from LDAP. Asking for anything outside this list won't be accomplished using the protocol alone (or even in conjunction, I don't know).
13 years ago
Hi,
Using strictly LDAP, is there any way to get meaningful responses back from an AD server? As in, are there ways to receive password expiration or pending expiration once a user is located in the directories? I'm using the where environment is the hashtable full of values and it does the look up. I'm beginning to believe this is too basic for my needs.

In all my tests I'm only receiving an exception and no extra data. The LDAP error 'Invalid Credentials' is the response I get for both wrong username/password as well as if it's an expired password...but I actually need a way to tell the user 'password expired.'

I was hoping I'd also receive some kind of constant I could translate to the user...can this be done with LDAP?

Thank you.
13 years ago
Ok, so I have my own answer...but the question I posed is moot because it was the wrong object to go looking inside for the answer.

Separate from searching the InitialDirContext object I ran the following code and received the 'directory from which to start searching in':


environment is the hashtable full of the attributes required to login (i.e. the same hashtable passed to the InitialDirContext for authenticating).

In my case it appears as "C=name,DC=name" etc. but obviously, the result will entirely depend upon how the LDAP tree was set up...

Anyway, I thought I'd post the result in case anyone else doesn't immediately know how to search for the 'root' directory in LDAP if they don't know it.

13 years ago
Hi all,
I'm confused. When I receive back a 'loaded' InitialDirContext object, I can do a .search() on it, and in my case it's specific to LDAP, going, ctx.search(startingDirectory, filter, ctls) and then I'll get a return that I assign to a NamingEnumeration object. Great. But using the debugger in eclipse and exploding the contents of the InitialDirContext object I cannot for the life of me find this criteria inside it, despite getting a good result. Where does this information hide?? Is it magic?? Stuff like currentDN are ""...and yet I can still get a successful .search() from the object...

I'm glad it's working I guess, but not glad that I don't understand why.

Thanks for anything that could shed light on this.
G
13 years ago
Hello all,
We are implementing LDAP and removing the old proprietary login process on one of our apps. The old way had full-featured password reset/expiration functions. For local testing I have OpenDS running and I can login. I have a simple question.

--> During authentication is it possible to detect whether or not a user's p/w is about to expire?

At first glance (3 days into this project now), it only looks as though a red light/green light takes place using the XML configuration using BASIC for the <auth-method>.

Thanks for any help.

EDIT: I see in OpenDS under cn=config there is Account Status Notification Handlers --> Error Log Handler and inside there are the password-expiring and other values. At the moment I don't know how to reach them...
13 years ago

Peter Johnson wrote:Try this. Just build the app and then from a command line run "javap -verbose" against one of your class files...



I just tried the javap -verbose and it returned this:

"Error: bad class format.\KISSettings.classThe major.minor version '49.0' is too recent for this tool to understand."

I see a similar result when I run the ant script inside eclipse that used to be used to build the ear. It states:



But please note, if I run the ant script from a cmd prompt, it builds the ear just fine...I can't even hazard a guess at this point. Is it CVS related? Is it still a compiler problem?


Have you tried installing a 1.4.2 JDK, registering it with Eclipse, and setting your project to use that JDK? (Having multiple JDKs installed is not a problem, I have 1.3.1, 1.4.1, 1.4.2, 1.5, 6 and 7 on my PC.) If it is an issue with JDK 6, then doing this should solve the problem.



All I have done is place the JDK in C:\j2sdk1.4.1_02\ and that is set to JAVA_HOME. In eclipse's Project Properties -->Java Compiler I have 'Compiler compliance level' set to 1.4...however the JRE is jre6...

Well, if you mean Windows-->Preferences and then the Java-->Compiler section, I have the compliance level also set to 1.4 there. And the box is checked next to "Add line numbers to generated class files (used by the debugger)" as well.

I think it has something to do with the JRE being 1.6 and the compliance set to 1.4, but like I said, it used to work with no problems on that setting.

I really don't want to rebuild the workspace because of this glitch, but it's starting to look that way.
Hello again,
My environment is JDK 1.4.1_02 with JRE 6 on Eclipse 3.4.

I receive the popup error window in eclipse telling me to modify my compiler settings. "Unable to install breakpoint in [projectname] due to missing line number attributes. Modify compiler options to generate line number attributes. Reason: Absent Line Number Information."

PLEASE NOTE: I have already checked the box "Add line number attributes to generated class files" in Java Compiler settings and I'm NOT using ant to build.

The interesting part: it WAS working fine. Then I had to delete the old associated EAR project. I created a new one with a stripped-down application.xml file (it doesn't describe any ejb's now) and NOW I get this error. Any ideas? =)


I was entering the arguments in the VM Argument window.

I found out the issue was a trailing white space. Thanks for the reply.
13 years ago
Hello,
I have a problem here. I'm trying to 'move' an app (jdk 1.4) that uses JBOSS 4.0 with a lot of batch files that load system properties at start up to run internal to eclipse 3.4 using the same JBOSS server.

Long story short: How does one input the values from batch files needed for the successful loading of the server into eclipse's 'internal' server? At the moment no matter what I try they are null.

When starting the server 'externally' I run a batch file that loads a range of values that populate System.properties. These are executed in the usual VM '-D' fashion, i.e. -DKISConfigFilePath=%KIS_PROPS% for example. However, when launching the server inside eclipse I thought I could use the Launch Configuration settings window to post -DKISConfigFilePath="C:\myactualpath\" inside the VM Arguments window. However, it seems to ignore the values and I still end up with a stack nullPointer when launching the server where those values should be populated.

If I'm going about this wrong I would like to know. I know this is more an eclipse question, but I am at my wit's end. Apologies.

I appreciate any help.
Regards.

13 years ago