Portal Java setup problem

Question

I have a similar problem where I have portal installed on a machine called portal.mgmt, which is on a network that users cannot access. Connection to portal.mgmt can only be made from our local network via a machine called install.mgmt. In a sense I guess it is acting like a reverse proxy or firewall.
I have run ssodatan on portal providing the install.mgmt URL and can access most of Portal pages navigating to http://install.mgmt/ except any of the servlets. Actually the only servlet I can access is the sample IsItWorking servlet.
In my java jserv.log file I am getting the following error:
java.net.SocketException: Connection reset by peer
at java.net.PlainSocketImpl.socketAvailable(Native Method)
I can only assume, from reading the Troubleshooting guide, that portal.mgmt is trying to make a separate connection to the install.mgmt box and is failing.
The network between portal.mgmt and install.mgmt is very restricted as to what can be run and what protocols and ports can be used. Is this restriction causing the problem?
I see that Jserv uses port 8007, is this port used to communicate between machines?
Are there any ports that need to be opened?
I have tried using another machine called ogg as the firewall/access server and get the following error as well.
java.net.UnknownHostException: ogg
at java.lang.Throwable.fillInStackTrace(Native Method)
Any help on this one would be very much appreciated, as I am very stuck at the minute as I have tried the Portal Security group without any success.
Regards,
Garry

Answer 1

Hi Bartosz,
We use 1.4.2  and did not test it with 1.5 yet, but we also have done the following to prevent com exception
When adding a document, such as a sales order, stock transfer document through Java Connector, there always is a COM Exception, saying that
stack overflow occurs at COM side.
It turns out to be a bug in Sun's JDK 1.3 and later. In JDK 1.3 and later, the default stack size is reduced from 1M to 256K. And the command line option -Xss<size>, which works in JDK1.2, is ignored in JDK ver. 1.3 and later. According to Sun, it will not be fixed in the future.
One way to work around is to change the default setting in java.exe with EDITBIN.EXE provided by Microsoft VC. After changing the default stack size to 1M or above, everything works well. Here is the command line to change the default stack setting:
              EDITBIN /STACK:1048576 java.exe
Before you run this tool, you should copy MSPDB60.DLL from:
C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin
to the folder where EDITBIN is. It is required by EDITBIN.
After running it, you can see the following message:
Microsoft (R) COFF Binary File Editor Version 6.00.8447
and the date of java.exe has been changed.
Note:
       If you are using some java editors, like Eclipse, it may be slightly different. Eclipse uses javaw.exe instead of java.exe. So you have to change the setting in javaw.exe accordingly.
You can find more information on Sun's developer network:
http://developer.java.sun.com/developer/bugParade/bugs/4362291.html You have to register as a developer first before you can read the article.
Regards
Ad