[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-developers] Interbase-JSP-Ultradev



Hi Bruce,

> I have checked all the files and settings suggested by the group and still
> have the same error message. The tomcat.policy file has the entry for
> file:/usr/interclient exactly as stated in the email, and an entry for
> file:/home/sites/home/web with a SocketPermission set for
> localhost on port 1024.
> Should I have an entry for something other than localhost and should
> the port be 3060? /etc/services has the entry for interserver on 3060 and
> also a line for gds_db on port 3050 that says it's the Interbase Remote
> Protocol. Do I need to add something for the gds_db in the tomcat.policy
> file?

If you still use default Cobalt's scripts
(/usr/java/jakarta-tomcat/bin/cobalt_config.pl)
this script rewrite your tomcat.policy after Tomcat reloading. But you need
to reload Tomcat after changes of tomcat.policy. Without this reloading
Tomcat don't know about your changes of tomcat.policy but rewriting of
tomcat.policy drop tomcat.policy to default cobalt's status.

That you need to do while Sun changes scripts:
First and simple solution: if you don't use Tomcat for virtual hosts you
can set  AllPermissions as is shown in manual. It is very dangerous
solution, use it as the temporary solution only and wait for Sun's path.

Second and precise solution: if you use Tomcat with virtual hosts you
1. Open /usr/java/jakarta-tomcat/bin/cobalt_config.pl and comment all
lines which rewrite tomcat.policy
2. Open tomcat.policy and edit similar as below:
grant codeBase "file:/home/sites/home/web/-" {
 permission java.net.SocketPermission "localhost:1024-", "accept, listen,
connect, resolve";
 permission java.util.PropertyPermission "*", "read,write";
 permission java.lang.RuntimePermission "accessClassInPackage.sun.io";
 permission java.lang.RuntimePermission "stopThread";
 permission java.lang.RuntimePermission "modifyThread";
 permission java.lang.RuntimePermission "modifyThreadGroup";
 permission java.lang.RuntimePermission "setFactory";
 permission java.lang.RuntimePermission "createClassLoader";
 permission java.net.NetPermission "specifyStreamHandler";
 permission java.io.SerializablePermission "enableSubclassImplementation";
 permission java.io.FilePermission "/home/sites/home/-",
"read,write,delete";
};

Please note: I change RuntimePermission to my needs, correct it as need.

3. Set your JDBC URL to
jdbc:interclient://localhost/home/sites/home/test.gdb
If you want to use your host name in JDBC URL, add to tomcat.policy
following line:
 permission java.net.SocketPermission "yourhostname.com:1024-", "accept,
listen, connect, resolve";

4. Restart Tomcat: /etc/rc.d/init.d/httpd reload

5. Test your system

6. Post your report to us :-)

Best regards,
Alex

>
> ----- Original Message -----
> From: "O-S Inc. Support" <support@xxxxxxxxxxxxxxxxxxxx>
> To: <cobalt-developers@xxxxxxxxxxxxxxx>
> Sent: Monday, August 27, 2001 5:36 PM
> Subject: Re: [cobalt-developers] Interbase-JSP-Ultradev
>
>
> > Bruce,
> > Also for the record, connecting to a DB using Interclient JDBC
> driver for
> > Interbase directly from Dreamweaver UltraDev is possible, and should
> > work regardless of tomcat being installed or not.
> >
> > With that being said, you will need to give tomcat all permissions as
> > stated in an earlier post in order to use the driver from java via jsp
> > or a servlet being served by tomcat.
> >
> > If the problem occurs when you are trying to connect to the DB on your
> > server from Dreamweaver UltraDev than this has nothing to do with
> > Tomcat!!!!!!
> >
> > It will have to do with mostly with your /etc/services file as stated
> > earlier.
> >
> > Also make sure your /etc/inetd.conf file contains an uncommented entry
> like
> >
> > interserver stream tcp nowait    root /opt/interclient/bin/interserver #
> Interserver JDBC Driver for IB
> >
> > If its does not, add it, then go to /etc/rc.d/init.d and restart the
> > inetd daemon (I am not a big fan of restarts)
> > ./inet stop
> > ./inet start
> >
> > At the moment I can't seem to remember what else we did if anything when
> > we manually installed interclient to get it to work.
> >
> > We did add a few entries to host.equiv but I am not sure if that had
> > anything to do with it working.
> >
> > Otherwise let me know how it goes.
> >
> >
> > Bruce Letterle wrote:
> >
> >  > I am attempting to use Interbase and JSP via Dreamweaver Ultradev on
> > a RAQ4
> >  > with the JDK loaded and the Interbase driver that installs by default
> > with
> >  > the JDK. I setup Interbase using the instructions in the JDK manual
> > and am
> >  > using the interbase.interclient.Driver driver name and the
> >  > jdbc:interbase://www.creativewebtech.com/home/sites/home/test.gdb
> > URL. I am
> >  > getting the following error when attempting a connection from
> > Ultradev on my
> >  > PC to my remote test database:
> >  >
> >  > [interclient] Your security manager does not allow socket connections
> to
> >  > www.creativewebtech.com on interserver port.
> >  > The message of the SecurityException is 'access
> >  > denied[java.net.SocketPermission www.creativewebtech.com resolve]'
> >  > See API reference for exception
> >  > interbase.interclient.BadInstallationException
> >  >
> >  > I cannot seem to make sense of the User Manual API section and was
> hoping
> >  > someone would recognize the error and be able to point me in
> the right
> >  > direction.
> >  >
> >  > Bruce Letterle
> >  > Creative Web Technologies
> >  > eBusiness Web Services
> >  > 412-415-5217
> >  > brucelet@xxxxxxxxxxxxxxxxxxx
> >  > http://www.creativewebtech.com
> >  >
> >  > _______________________________________________
> >  > cobalt-developers mailing list
> >  > cobalt-developers@xxxxxxxxxxxxxxx
> >  > http://list.cobalt.com/mailman/listinfo/cobalt-developers
> >
> >
> > --
> > Sincerely,
> > William L. Thomson Jr.
> > Support Group
> > Obsidian-Studios Inc.
> > 439 Amber Way
> > Petaluma, Ca. 94952
> > Phone/fax 707.766.9509
> > http://www.obsidian-studios.com
> >
> > _______________________________________________
> > 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
>
>