[cobalt-developers] unsubscribe me, please

["Brunnengräber, Stefan" <Stefan.Brunnengraeber@xxxxxxxxx>]

Mit freundlichen Gruessen  /  Best regards

Dipl.-Ing. (FH) Stefan Brunnengräber
Multimedia / Internet / Intranet

----------------------------------------------------------------------------
---
Voith Turbo GmbH & Co. KG, Straße
Technische Dokumentation - antd
Alexanderstr. 2
89522 Heidenheim, Germany

Tel.:    		+49 7321 37 4397
Fax:     		+49 7321 37 8714397
E-Mail:  	Stefan.Brunnengraeber@xxxxxxxxx
----------------------------------------------------------------------------
---

> -----Ursprüngliche Nachricht-----
> Von:	Paul Rosenthal [SMTP:paul.rosenthal@xxxxxxxxxxxxxxxxx]
> Gesendet am:	30. November 2001 14:28
> An:	cobalt-developers@xxxxxxxxxxxxxxx
> Betreff:	Re: Re: [cobalt-developers] tomcat.policy.custom &
> permission for external hosts
> 
> Thanks for explaining how to use tomcat.policy.custom
> 
> Your advice on not needing the codebase etc did the trick.
> 
> However, the actual line
> 
> permission java.net.SocketPermission "*:1521", "listen,connect,resolve";
> 
> still did not work, but
> 
> permission java.security.AllPermission;
> 
> did.  I don't know why, perhaps database connections need more permissions
> than the java.net.SocketPermission alone.
> 
> Thanks for your help.
> 
> Regards
> 
> Paul Rosenthal
> 
> ----- Original Message -----
> From: <travis@xxxxxxxxxxxxxxxx>
> To: <cobalt-developers@xxxxxxxxxxxxxxx>
> Sent: Thursday, November 29, 2001 3:36 PM
> Subject: RE: Re: [cobalt-developers] tomcat.policy.custom & permission for
> external hosts
> 
> 
> > I don't think you need the grantcodeBase etc for the custom files, as
> the
> cobalt script creates that for you, all you need is the actual permission
> lines...
> >
> > like all you should have in the file is:
> >
> > permission java.net.SocketPermission "*:1521", "listen,connect,resolve";
> >
> > Travis
> >
> > ---- Original Message ----
> > From: Paul Rosenthal <paul.rosenthal@xxxxxxxxxxxxxxxxx>
> > Sent: 2001-11-29 03:37:33.0
> > To: cobalt-developers@xxxxxxxxxxxxxxx
> > Subject: Re: [cobalt-developers] tomcat.policy.custom & permission for
> external hosts
> >
> > Thanks for the tip.  However, I am still struggling with the rest of the
> > code that it needs.
> >
> > I have created a tomcat.policy.custom file that contains:
> >
> >
> > grant codeBase "file:${tomcat.home}/lib/-" {
> >  permission java.net.SocketPermission "*:1521",
> "listen,connect,resolve";
> > };
> > grant codeBase "file:/home/sites/-"
> >
> >  permission java.net.SocketPermission "*:1521",
> "listen,connect,resolve";
> > };
> >
> >
> > It is the rest of the grant command that I also need help on.
> >
> > The above code (and all sorts of variations that I have tried) just
> crashes
> > Tomcat and Apache.
> >
> > Do you know the complete text to put into the tomcat.policy.custom file?
> >
> >
> >
> > ----- Original Message -----
> > From: "alpo" <alpo@xxxxxxxxxxxxxxxxxx>
> > To: <cobalt-developers@xxxxxxxxxxxxxxx>
> > Sent: Thursday, November 29, 2001 12:57 AM
> > Subject: RE: [cobalt-developers] tomcat.policy.custom & permission for
> > external hosts
> >
> >
> > > Hi,
> > >
> > > You need the following:
> > > permission java.net.SocketPermission
> "<putRequiredDomainNameHere>:1521",
> > > "listen,connect,resolve";
> > >
> > > or
> > > permission java.net.SocketPermission "*:1521",
> "listen,connect,resolve";
> > > for all hosts.
> > >
> > > Regards,
> > > Alexander Povargo
> > > YourNewHosting.com
> > > alpo@xxxxxxxxxxxxxxxxxx
> > > http://www.yournewhosting.com
> > > ICQ 25639843
> > >
> > >
> > > > -----Original Message-----
> > > > From: cobalt-developers-admin@xxxxxxxxxxxxxxx
> > > [mailto:cobalt-developers-
> > > > admin@xxxxxxxxxxxxxxx] On Behalf Of Paul Rosenthal
> > > > Sent: Thursday, November 29, 2001 4:05 AM
> > > > To: cobalt-developers@xxxxxxxxxxxxxxx
> > > > Subject: [cobalt-developers] tomcat.policy.custom & permission for
> > > > external hosts
> > > >
> > > > We are porting a working servlet/jsp application from JRun on NT4 to
> > > > Tomcat
> > > > on a Raq4.
> > > >
> > > > This application needs to connect to an Oracle database on another
> > > server.
> > > > This database is up and running perfectly fine and is contactable.
> > > >
> > > > We have copied over the classes12.zip file which contains the JDBC
> > > drivers
> > > > we have successfully been using so far.  We have renamed them
> > > > classes12.jar
> > > > and put them in /usr/java/jakarta-tomcat/lib which we believe to be
> > > the
> > > > right place for them, and believe that they are being picked up and
> > > > detected.
> > > >
> > > > On the Tomcat platform, when we try to run the application, it ends
> > > with
> > > > the
> > > > error, perhaps not surprisingly:
> > > >
> > > > Null pointer exception (no database
> > > > connection)java.security.AccessControlException: access denied
> > > > (java.net.SocketPermission IP address:1521 connect,resolve)
> > > >
> > > > [1521 is the Oracle port]
> > > >
> > > > I gather we have to modify the tomact.policy file, and on a Raq4,
> this
> > > is
> > > > done by creating a tomcat.policy.custom file.
> > > >
> > > > My question is, what is the exact code I need to enter into this
> file
> > > to
> > > > allow Tomcat to "see out" to the remote server, to allow our
> > > application
> > > > to
> > > > connect to the database?
> > > >
> > > > Either for a specific site on the Raq4, or for all sites?
> > > >
> > > > I have tried a few things by looking at other examples, but all to
> no
> > > > avail.
> > > >
> > > > Any help from either anyone who has actually connected to an Oracle
> > > > database, or anyone who just knows how to connect to a remote
> database
> > > on
> > > > another machine, would be greatly appreciated.
> > > >
> > > > Regards
> > > >
> > > > Paul Rosenthal
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > cobalt-developers mailing list
> > > > cobalt-developers@xxxxxxxxxxxxxxx
> > > > http://list.cobalt.com/mailman/listinfo/cobalt-developers
> > >
> > >
> > > _______________________________________________
> > > cobalt-developers mailing list
> > > cobalt-developers@xxxxxxxxxxxxxxx
> > > http://list.cobalt.com/mailman/listinfo/cobalt-developers
> >
> > _______________________________________________
> > cobalt-developers mailing list
> > cobalt-developers@xxxxxxxxxxxxxxx
> > http://list.cobalt.com/mailman/listinfo/cobalt-developers
> >
> >
> > _______________________________________________
> > cobalt-developers mailing list
> > cobalt-developers@xxxxxxxxxxxxxxx
> > http://list.cobalt.com/mailman/listinfo/cobalt-developers
> 
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers