Hi, 

the ouput of ssh -v splic...@clucene.git.sourceforge.net is:


OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug1: Connecting to clucene.git.sourceforge.net [216.34.181.91] port 22.
debug1: Connection established.
debug1: identity file /c/Users/splichal/.ssh/identity type -1
debug1: identity file /c/Users/splichal/.ssh/id_rsa type 1
debug1: identity file /c/Users/splichal/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_5.2
debug1: match: OpenSSH_5.2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.6
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'clucene.git.sourceforge.net' is known and matches the RSA host 
key.
debug1: Found key in /c/Users/splichal/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /c/Users/splichal/.ssh/identity
debug1: Offering public key: /c/Users/splichal/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
fatal: What do you think I am? A shell?
debug1: channel 0: free: client-session, nchannels 1
Connection to clucene.git.sourceforge.net closed.
debug1: Transferred: stdin 0, stdout 0, stderr 51 bytes in 1.0 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 49.5
debug1: Exit status 128

Jiri

-----Original Message-----
From: Veit Jahns [mailto:nuncupa...@googlemail.com] 
Sent: Tuesday, September 07, 2010 12:27 PM
To: clucene-developers@lists.sourceforge.net
Subject: Re: [CLucene-dev] Span Queries have been ported

2010/9/7 Šplíchal Jiří <splic...@tovek.cz>:
> Yes, me and Borek wanted to merge our branches so I pushed all my changes - 
> and forgot
> not to push this one. I removed it again in my local repository but 
> unfortunately I am not able to push the change
> to the original repository - I always got the message "fatal: The remote end 
> hung up unexpectedly". I don't know what
> to do.
> But I could pull your changes.

A firewall/proxy issue, maybe? What do you get, if you execute:

ssh -v <your sf login>@clucene.git.sourceforge.net

> But back to the additional decRef:
> - I tried to investigate it further and the situation is the following:
> If the SegmentReader gets closed via close() then decRef() method is called 
> where the Norms are also decRefed and the
> close flag is being set - this happens in the close() method.
> If you just delete a SegmentReader than the doClose() method is called and 
> the Norms are not touched - so memory leaks
> arise. So I added the decRef() calls to the destructor, called only if the 
> closed false is false.
> But when the SegmentReader is used as a child merger of MultiSegmentReader 
> and you call close() on the MultiSegmentReader,
> then the child SegmentReaders are just decRefed (which leads to doClose() 
> call) but the closed flag remains false.
>
> I tried to find the right position for setting the closed flag to true (in 
> the doClose() method?) but I did not finish
> the fix yet. The simplest solution is ofcourse not to forget to call the 
> close() method on the SegmentReader before
> deleting it.

Would be the best at the moment. Ben wrote once [1] that is a reason
for the current behaviour. Another solution will be to use a
smart/shared pointer here, so manually handling a reference counter
isn't needed anymore. But this is a task I still have to complete.

Veit

[1] http://comments.gmane.org/gmane.comp.jakarta.lucene.clucene.devel/2505

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers

Reply via email to