AKAIK, idleTime should not be a problem. It is true that
ConcurrentLoginPermission() is not in our public API ( you can always
get the source code though, with only the tests you'll learn a big
deal about FtpServer) , the constructor is this:

  public ConcurrentLoginPermission(int maxConcurrentLogins,
            int maxConcurrentLoginsPerIP) {
        this.maxConcurrentLogins = maxConcurrentLogins;
        this.maxConcurrentLoginsPerIP = maxConcurrentLoginsPerIP;
    }

So in your case you should have    authorities.add(new
ConcurrentLoginPermission(8, 4)); to limit the target user to 8
connections with 4 from the same IP adress.

I still think you may need to check how many connections are actually
established! Can you provide us with a 'new log file' in DEBUG mode
reproducing your issue?




2009/4/3 Dan <[email protected]>:
> I set the concurrent logins as follows:
>
>                List<Authority> authorities = new ArrayList<Authority>();
>
>                authorities.add(new WritePermission());
>                authorities.add(new ConcurrentLoginPermission(4, 8));
>                authorities.add(new TransferRatePermission(0, 0));
>
>                setAuthorities(authorities);
>
>                setMaxIdleTime(0);
>
> Is there a problem with the setMaxIdleTime? Otherwise I assume I am setting
> the logins to be a max of 4..or 8, I am not sure since my javadocs don't
> include ConcurrentLoginPermission info!
>
> Thanks,
>
> Dan
>
> -----Original Message-----
> From: David Latorre [mailto:[email protected]]
> Sent: April-03-09 1:43 PM
> To: [email protected]
> Subject: Re: Maximum login connections: 421
>
> Hello Dan,
>
>  You also set maximum connections per user in the UserManager ... what value
> did you use in order to configure that? And when FTP Clients open several
> connections, they log you in for each of those connections ...  until we
> have an equivalent to admingui which allowed us to monitor all the
> connections you can see if DEBUG log level will help you to find out what's
> your exact problem; otherwise you can use a ftplet that gets triggered
> before "USER" command or something like that :-) And, of course, you can
> debug the server
>
>
>
>
> 2009/4/3 Dan <[email protected]>:
>> I agree, but the docs say "Maximum Logins", not Maximum Connections.
>>
>> Hopefully there are just "logins" that aren't being closed properly
>> over time, although I don't know how to find this out. There should be
>> a way to get status on all logins from the manager, I'm going to keep
> looking.
>>
>> -----Original Message-----
>> From: Steve Winter [mailto:[email protected]]
>> Sent: April-03-09 11:09 AM
>> To: [email protected]
>> Subject: Re: Maximum login connections: 421
>>
>> Hi Dan,
>>
>> I know that many ftp clients will open multiple simultaneous
>> connections to a server, so it may be that there are 4 people logged
>> in, each of them with
>> 8 connections open, which may account for this...??
>>
>> Just a random thought...
>>
>> Cheers
>> Steve
>>
>>
>> On 3 Apr 2009, at 15:05, Dan wrote:
>>
>>> I am getting:
>>>
>>> WARNING: SENT: 421 Maximum login limit has been reached.
>>>
>>> I have set the connection configuration as follows:
>>>
>>> ConnectionConfigFactory connectionConfigFactory = new
>>> ConnectionConfigFactory(); connectionConfigFactory.setMaxLogins(32);
>>>
>>> The thing is there aren't even close to 32 people logged in right
>>> now, are there known bugs with having hanging connections etc. that
>>> could cause this?
>>>
>>> Any hints to help debug this in the future?
>>>
>>> Thanks,
>>>
>>> Dan
>>>
>>
>>
>>
>>
>
>

Reply via email to