You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by GitBox <gi...@apache.org> on 2022/12/23 12:14:08 UTC
[GitHub] [mina-sshd] zmrush opened a new issue, #302: requestNewKeysExchange may cause KeyExchangeMessageHandler into dead lock,cpu 100%
zmrush opened a new issue, #302:
URL: https://github.com/apache/mina-sshd/issues/302
### Version
2.9.1
### Bug description
i observed in cases， the write packet thread is always running and in the interval i saw "equestNewKeysExchange(ClientSessionImpl[root@/47.104.92.124:22]) Initiating key re-exchange
method:o.a.s.c.s.ClientSessionImpl(AbstractSession.java:2404) " in log
### Actual behavior
after i saw log "equestNewKeysExchange(ClientSessionImpl[root@/47.104.92.124:22]) Initiating key re-exchange
method:o.a.s.c.s.ClientSessionImpl(AbstractSession.java:2404)",the write packet thread is soar to 100%,not stopped
### Expected behavior
i expect when the connection is closed the cpu is down,and the thread is stopped
### Relevant log output
```Shell
equestNewKeysExchange(ClientSessionImpl[root@/47.104.92.124:22]) Initiating key re-exchange
method:o.a.s.c.s.ClientSessionImpl(AbstractSession.java:2404)
```
### Other information
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org
[GitHub] [mina-sshd] tomaswolf commented on issue #302: requestNewKeysExchange may cause KeyExchangeMessageHandler into dead lock,cpu 100%
Posted by GitBox <gi...@apache.org>.
tomaswolf commented on issue #302:
URL: https://github.com/apache/mina-sshd/issues/302#issuecomment-1364179109
Not enough information. Please provide full jstack traces as text file. If you have some code that can reproduce the behavior reliably that would also be helpful.
With just the information given, I don't see how one could even begin to investigate.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org
[GitHub] [mina-sshd] tomaswolf closed issue #302: requestNewKeysExchange may cause KeyExchangeMessageHandler into dead lock,cpu 100%
Posted by GitBox <gi...@apache.org>.
tomaswolf closed issue #302: requestNewKeysExchange may cause KeyExchangeMessageHandler into dead lock,cpu 100%
URL: https://github.com/apache/mina-sshd/issues/302
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org
[GitHub] [mina-sshd] zmrush commented on issue #302: requestNewKeysExchange may cause KeyExchangeMessageHandler into dead lock,cpu 100%
Posted by GitBox <gi...@apache.org>.
zmrush commented on issue #302:
URL: https://github.com/apache/mina-sshd/issues/302#issuecomment-1364450488
it happens occasionally,not always.i guess that when we write packet, the thread is in requestNewKeysExchange,so kexDone not fulfilled and the thread goes into "block = kexFlushedFuture;" and unfortunately, the connection is done,so the kexDone never done, and it goes into infinite loop
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org
[GitHub] [mina-sshd] zmrush commented on issue #302: requestNewKeysExchange may cause KeyExchangeMessageHandler into dead lock,cpu 100%
Posted by GitBox <gi...@apache.org>.
zmrush commented on issue #302:
URL: https://github.com/apache/mina-sshd/issues/302#issuecomment-1364450878
> Not enough information. Please provide full jstack traces as text file. If you have some code that can reproduce the behavior reliably that would also be helpful.
>
> With just the information given, I don't see how one could even begin to investigate.
i cannot paste all the jstack traces,because it may explode some information about my company, but it goes into infinite loop.you can see below two images,it goes in the "for;;" not ends
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org
[GitHub] [mina-sshd] quequan commented on issue #302: requestNewKeysExchange may cause KeyExchangeMessageHandler into dead lock,cpu 100%
Posted by "quequan (via GitHub)" <gi...@apache.org>.
quequan commented on issue #302:
URL: https://github.com/apache/mina-sshd/issues/302#issuecomment-1491504323
we have faced same problem : KeyExchangeMessageHandler.writeOrEnqueue is running forever ,cpu usage is 100% . can you release a new version and publish to repo?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org
[GitHub] [mina-sshd] zmrush commented on issue #302: requestNewKeysExchange may cause KeyExchangeMessageHandler into dead lock,cpu 100%
Posted by GitBox <gi...@apache.org>.
zmrush commented on issue #302:
URL: https://github.com/apache/mina-sshd/issues/302#issuecomment-1363931090
![Uploading 76694429-AB75-4229-A733-7A51F5776628.png…]()
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org
[GitHub] [mina-sshd] tomaswolf commented on issue #302: requestNewKeysExchange may cause KeyExchangeMessageHandler into dead lock,cpu 100%
Posted by GitBox <gi...@apache.org>.
tomaswolf commented on issue #302:
URL: https://github.com/apache/mina-sshd/issues/302#issuecomment-1376388012
@zmrush can you give #308 a try? I think that should avoid this endless loop.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org