you're going to have to provide the error message. Look in the tomcat logs and post the stack trace.
Charlie > -----Original Message----- > From: Furlan Bojan ITWET2 [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 24, 2002 4:13 AM > To: 'Tomcat Users List' > Subject: RE: Special consideration of invoking native methods > in Tomcat? > > > I may be wrong, but I believe I have set the socket for > Tomcat access to > 8080 since another web server is running on the same server. > The sockets > used by the legacy system I'm trying to access are completely > different. > > -----Original Message----- > From: Collins, Jim [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 24, 2002 10:06 AM > To: 'Tomcat Users List' > Subject: RE: Special consideration of invoking native methods > in Tomcat? > > > A possibility is Tomcat is already using the socket. > > > -----Original Message----- > > From: Furlan Bojan ITWET2 [mailto:[EMAIL PROTECTED]] > > Sent: 24 September 2002 09:01 > > To: '[EMAIL PROTECTED]' > > Subject: Special consideration of invoking native methods in Tomcat? > > > > > > I am trying to access existing legacy system in our company > > over JSP running > > on Tomcat. Using JNI, I am now able to call one of the C functions > > (something like connect to a server and select database) from > > existing API. > > The call succeeds, but it results in error during execution of that > > function. The same call in a standalone java application is always > > successful. > > As far as I know, API communicates to server over socket > > mechanism. What > > would be a difference between calling such a native function > > in standalone > > Java application and using the same in JSP? I'm new in Java > > environment, > > Tomcat and JSP, so I would appreciate any hint. > > > > Regards > > Bojan Furlan > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > PLEASE READ: The information contained in this email is confidential > and intended for the named recipient(s) only. If you are not > an intended > recipient of this email you must not copy, distribute or take any > further action in reliance on it and you should delete it and > notify the > sender immediately. Email is not a secure method of communication and > Nomura International plc cannot accept responsibility for the accuracy > or completeness of this message or any attachment(s). Please > examine this > email for virus infection, for which Nomura International plc accepts > no responsibility. If verification of this email is sought then please > request a hard copy. Unless otherwise stated any views or opinions > presented are solely those of the author and do not represent those of > Nomura International plc. This email is intended for informational > purposes only and is not a solicitation or offer to buy or sell > securities or related financial instruments. Nomura > International plc is > regulated by the Financial Services Authority and is a member of the > London Stock Exchange. > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
