Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / December 2005

Tip: Looking for answers? Try searching our database.

Conflicting JVMs

Thread view: 
vsingr - 29 Nov 2005 16:11 GMT
friends
has anyone encountered this error
"The procedure entry point _JVM_GetAllThreads@8 could not be located in
the dynamic link library jvm.dll". If so what is the solution to this.
I have tried pointing the right JRE in my system PATH. is there
anything else I need to do to overcome this?
Thanks
Scott Smith - 30 Nov 2005 14:07 GMT
> friends
> has anyone encountered this error
> "The procedure entry point _JVM_GetAllThreads@8 could not be located in
> the dynamic link library jvm.dll". If so what is the solution to this. I
> have tried pointing the right JRE in my system PATH. is there anything
> else I need to do to overcome this? Thanks

Man that's a weird one.  I'm inclined to say that either jvm.dll is
corrupted, missing or from a different JRE version.  If possible, I would
try reinstalling but first remove all other instances of Java first.  It's
very easy to compile in one version but accidentally run in a different
preinstalled JRE.

Signature

R. Scott Smith
Slackware on the job, at home, everywhere!

"." - 01 Dec 2005 15:13 GMT
> friends
> has anyone encountered this error
> "The procedure entry point _JVM_GetAllThreads@8 could not be located in
> the dynamic link library jvm.dll". If so what is the solution to this.
> I have tried pointing the right JRE in my system PATH. is there
> anything else I need to do to overcome this?

Changing the PATH is the right thing to do. If that does not work there
are two things to consider.

1) Did you reboot your computer? If the jvm.dll is in memory a LoadLibrary
call will use the in memory DLL and ignore the change to the PATH.
Rebooting the computer will flush the DLL from memory and switch to the
new one in your PATH.

2) Could something have overwritten the DLL? That is, you are pointing to
what you think is the correct DLL but the reality is the correct DLL was
overwritten and you might need to re-install the JDK/JRE.

Signature

Send e-mail to: darrell dot grainger at utoronto dot ca



Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.