cancel
Showing results for 
Search instead for 
Did you mean: 

port issue with j2ee engine, http service provider

Former Member
0 Kudos

hi gurus,

on two of our standalone j2ee servers, the j2ee engine is up and running fine. from the mmc everything shows green including messager server.

but when i connect to the j2ee page using browser either from the client machine or on the server it never gives me an error message but the status bar keeps processing. never throws any sort of dispatcher or 500 error messages.

There were some GRC-Virsa components deployed over the weekend not sure if that had changed something.

After intial research the port information in the HTTP service provider showed 80 for http and 443 for ssl (https)so i had manually changed it to 50000 and 50001 from config tool respectively , restarted the server.

After the restart the j2ee page came up and the very second http request it goes to the loop again with no error message, whats the reason behind this sort of behavior. i have made the port changes over the whole cluster and restarted.

surprising it works only for the first time after restart, the very second http request never accepted by dispatcher/server process , no error message though.

environment, nw04s with plain j2ee, windows 2003, sql2008

please assist.

-durga

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Are there any errors in the server's default.trc at the time of the failed connection?

Regards,

Sean

Former Member
0 Kudos

thanks sean for responding, infact the issue is resolved yesterday.

Reason due to insufficient application threads and make sure the right port defined in HTTP service provider. So fixing these two things resolved the issue

Thanks,

Durga