Hi.
If the variable that "feeds" into this log entry indeed is your LD_LIBRARY_PATH, then I bet it's being expanded somewhere else by a statement like this:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/that/additional/stuff
Check the other dot-Files (.profile, .bash_profile etc.) in the home directory of the user that your agent process starts as. You can, for example, grep them with:
# grep -H '/usr/jdk/packages/lib/sparcv9' /home/<username>
/.*
(yes, you need to specify the dot as part of the wildcard
).
Failing that, check the files in /etc, which apply to ALL users
(those do not have a dot in front, it's just /etc/profile or somesuch):
# grep -Hr '/usr/jdk/packages/lib/sparcv9' /etc
/*
Failing that, grab a drink, maybe a pizza if the server is old and slow, and fire off a search across all files on the server. It may take some minutes, but it won't do any harm :)
# find / -type f -readable -exec grep -H '/usr/jdk/packages/lib/sparcv9' {} \;
If you have no luck, you may also be able to look at the /proc file system, and there the "environ" file for the process ID of the agent (as discoverable via the ps command) to find out which environment variable the path comes from. Maybe it's not even LD_LIBRARY_PATH (but it probably is).
# cat /proc/<process_id>/environ
Hint: It's probably obvious, but the "#" indicates you should run these commands as "root" if possible, to be able to search the most files possible.
Disclaimer: Some of the parameters used (such as -H for grep) may be GNU parameters and may not work on Solaris, or you may need to use the /usr/ucb version of the utilities on Solaris to make those parameters work. I don't have a Solaris system here to check against. Similarily, I don't know if your particular server has a /proc file system at all.
Give that a try, let me know if still no dice, then we'll look further.
Best,
Carsten
p.s. I'm also just assuming you're on Solaris because of the sparcv9 path, but what I said applies to most UNIX-like OS anyhow.