• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 203
  • Last Modified:

Cannot open socket - Listen fails

i installed jdk2 and jsdk2.0 on win95. when i ran SERVLETRUNNER which comes with jsdk2.0 i get the following Exception

java.net.SocketException : Descriptor not a socket Listen failed.
with a stack trace printed out in Standard output

is there a problem with jvm i installed jrun and uninstalled as it too was not able to open a socket to listen.

Thanks
arun.
0
marun
Asked:
marun
  • 4
1 Solution
 
Ravindra76Commented:
Replace java.policy file

in c:\jdk2home\jre\lib\security

with



// Standard extensions get all permissions by default

grant {
      permission java.security.AllPermission;
};

Note:- c:\jdk2home is the directory where U actuallu installed JDK software
0
 
tonusCommented:
Hi,
Generally Servletrunner is trying to connect to 8080 port. If that port is occupied by some other process, servletrunner won't start. Try changing the port of the servletrunner (setup files u will get in c:/jsdk2.0/examples) and run the servletrunner

bye
0
 
Ravindra76Commented:

Hi ,

It is not port problem.

If it is so, it will give already bind exception

If U still face, some problem

run Your servlets with this command

servletrunner -d c:\Yourdir -v

wher yourdir is the directory where U are wishing to run servlets.

Otherwise U have to put your servlets in c:\jdsk\examples

because servletrunner will run servlerts in c:\jsdk\examples
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
marunAuthor Commented:
when i installed java1.1 it worked but with jdk2 its not working what may be the problem.
    its not the port problem as  said by ravindra. ravindra security is all the same in the file u mentioned i checked it up but directory is too not the problem. please suggest another way to tackle the problem

thanks
0
 
Ravindra76Commented:

try first

1.ping localhost

      If it succeeds ,

2. Type ipconfig

3. Then try

      ping ipaddress

      where ipaddress is the system ip address given in ipconfig

If both failed means something problem in Your system networking drivers.

Reinstall TCP/IP drivers
0
 
Ravindra76Commented:

I will feel very happpy if U would have been rejected my answer than giving D grade.

Ok.

Bye
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now