db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland <Jorgen.Lol...@Sun.COM>
Subject Re: [jira] Created: (DERBY-4257) 'Doc error' : master should be specified in slave security manager
Date Thu, 04 Jun 2009 07:27:13 GMT
Edah-Tally,

Did this solve the problem you asked about in email June 1 2009 
"Replication - startSlave hangs" to the user list? If this security 
manager issue is the root of the problem in that email, it would be 
great if you replied to your own question with the solution.

EDAH-TALLY (JIRA) wrote:
> 'Doc error' : master should be specified in slave security manager
> ------------------------------------------------------------------
> 
>                  Key: DERBY-4257
>                  URL: https://issues.apache.org/jira/browse/DERBY-4257
>              Project: Derby
>           Issue Type: Bug
>           Components: Documentation
>     Affects Versions: 10.5.1.1
>          Environment: Linux 2.6.29.2-server #1 SMP Sat May 9 22:43:24 CEST 2009 x86_64
AMD Athlon(tm) 64 X2 DualCore Processor 4200+ GNU/Linux
> 
> java version "1.6.0_06"
> Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 10.0-b22, mixed mode)
>             Reporter: EDAH-TALLY
>             Priority: Minor
> 
> 
> This concerns the Derby Server And Administration Guide.
> In the chapter 'Replication and Security', it is specified :
> 
> <>
> Add the following permission to the policy file on the slave system:
> 
>   permission java.net.SocketPermission "slaveHost", "accept,resolve";
> </>
> 
> I could have success with replication only if I use the 'masterHost' in place of 'slaveHost'
on the slaves's security policy file. It seems logical to configure the slave host to accept
any request from the master host.
> 
> May be the docs should be updated.
> 
> Thank you for considering.
> 
> 


-- 
Jørgen Løland

Mime
View raw message