Le 03/03/2018 à 21:15, Jonathan Valliere a écrit :
> Emmanuel,
>
> IMHO ConnectorTest, from a quick glance, suffers from some pretty bad
> concurrency problems in how it waits on the handler and manipulates the
> buffer independent of whatever the IoProcessor is doing. I would expect it
> to fa
Le 03/03/2018 à 22:54, Christoph John a écrit :
> BTW, is there a reason why **/Abstract* and **/*RegressionTest* are
> excluded fromthe surefire plugin? This leads to some tests not executed,
> in my case specifically the tests for AbstractIoService.
Those excludes have been present since almos
Hi Guys,
thanks to Jonathan and Christopher work, some big issues have been fixed
in the 2.0 branch. I will start to cut a release today.
Keep tuned !
--
Emmanuel Lecharny
Symas.com
directory.apache.org
Hi,
Here is the list of fixed issues :
Bugs :
--
[DIRMINA-844] - Http Proxy Authentication failed to complete (see
description for exact point of failure)
[DIRMINA-1002] - Mina IoHandlerEvents missing inputClosed enum item.
[DIRMINA-1051] - The MD5withRSA cipher is not anymore
Hi guys,
I just ran Sonarqube analysis on the current 2.0.17 branch, and there
are a few things we might want to fix.
Please have a look at
https://sonarcloud.io/project/issues?id=org.apache.mina%3Amina-parent%3A2&resolved=false
Thanks !
--
Emmanuel Lecharny
Symas.com
directory.apache.org
Le 06/03/2018 à 18:20, Jonathan Valliere a écrit :
> So many warnings… 😨
Yes...
There are a few puzzling ones, like the synchronized( buf ) where buf is
a parameter...
I think we should focus on blockers and critical level issues atm.
--
Emmanuel Lecharny
Symas.com
directory.apache.org
Le 11/03/2018 à 08:41, Jonathan Valliere a écrit :
> Isn’t this a committee vote? Unless I read it wrong all votes are limited
> to committee members. Shouldn’t this be posted on the pmc mailing list?
We do vote release in the open. Every one - including users - can vote.
Only PMC members hav
11/03/2018 à 07:23, Emmanuel Lecharny a écrit :
> Hi guys,
>
> please don't forget to spend 5 minutes to review and vote this release !
>
> Many thanks !
>
> On Tue, Mar 6, 2018 at 3:09 PM, Emmanuel Lécharny
> wrote:
>
>> Hi,
>>
>&
t;> interface contract
>> [DIRMINA-1076] - Leaking NioProcessors/NioSocketConnectors hanging
>> in call to dispose
>> [DIRMINA-1077] - Threads hanging in dispose() on SSLHandshakeException
>>
>> Improvement :
>> -
>>
>> [DIRMINA-1061] -
Hi guys,
I have registred MINA on the SonarQube server we have at Apache. The
result can be seen here :
https://builds.apache.org/analysis/component_measures/?id=MINA
It gets generated every time a build is launched, ie, when a commit is
pushed.
--
Emmanuel Lecharny
Symas.com
directory.apache
t;> Improvement :
>> -
>>
>> [DIRMINA-1061] - When AbstractPollingIoProcessor read nothing, free
>> the temporary buffer should be better
>>
>> Task :
>> --
>>
>> [DIRMINA-1058] - Add the missing Javadoc
>>
>> We recommend all users to upgrade to this release. We consider this a
>> stable and production ready release.
>>
>>
>> The Apache MINA PMC
>>
>>
>> Thanks !
>>
>>
>>
>> --
>> Regards,
>> Cordialement,
>> Emmanuel Lécharny
>> www.iktek.com
--
Emmanuel Lecharny
Symas.com
directory.apache.org
Hi Lyor,
Le 18/03/2018 à 19:26, Lyor Goldstein a écrit :
> Looks interesting is there a guide as to how to register a project (I was
> thinking about SSHD...)
I have created the config for SSHD.
The result can be found here:
https://builds.apache.org/analysis/overview?id=MINA_SSHD
Now, the bui
Le 19/03/2018 à 18:20, Lyor Goldstein a écrit :
> Thanks a lot Emmanuel...
>
> As far as the build failure it is strange indeed as it passes on both my
> Windows and Linux machines. However, since it states:
>
> [INFO] Rat check: Summary over all files. Unapproved: 2
>
> it means that the offe
Sorry, this was supposed to be sent on priv...@mina.apache.org...
Le 20/03/2018 à 19:12, Lyor Goldstein a écrit :
> +1
>
> I fully agree that " Guillaume is a very nice and talended
> person " and thank him for volunteering...
>
>>> Vote Guillaume Nodet as the new MINA chairman :
>
>>> [ ] +1
Hi,
Le 20/03/2018 à 21:47, Markus Rathgeb a écrit :
> Hi,
>
> has this been the wrong mailing list?
Nope.
> I know there exist also "users" and "ftpserver-users", but isn't it more or
> less a developer question and so should be sent to the "dev" list?
That's correct.
The thing is that we lac
Hi guys,
as a follow up of a discussion we have had with Jonathan, I would like
to suggest we add the 'secured()' event in the IoHandler. Th idea is to
make it simpler for MINA users to be informed when teh TLS handshake has
been completed.
Currently, one need to add the USE_NOTIFICATION attribut
Le 05/04/2018 à 14:18, Jonathan Valliere a écrit :
> I am concerned that it is bad precedent to add handler methods based on
> specific filters. The purpose of the filter system is that each filter has
> no direct knowledge of what is before or after it. Maybe there could be a
> generic “event”
Le 05/04/2018 à 15:42, Jonathan Valliere a écrit :
> Yes, its different in that it may act like a buffer, in some phases, but
> doesn’t necessarily break the pattern of filter use. What your FilterChain
> needs is fire(index) options so the SSL can fire writes relative to itself,
> in response t
self,
> in response to a read, without having to choke down the whole chain with
> special exceptions via flags in setAttributes. Make a lot of the design
> easier. IMHO, I think the biggest problem is the design of SSL filter and
> the limitations of the Filter API.
>
> On Thu,
Le 09/04/2018 à 17:17, Jonathan Valliere a écrit :
> I’d be interested in the diff. Why not propagate the sent down the chain
> instead of just to the handler?
I do propagate the event down teh chain. Ultimately, the IoHandler is
responsible for handling it.
I have attached the diff, nit sure
stead of just to the handler? I have a generic event system that I use
> to notify users fo server events, like pending shutdown or app reloads.
>
> On Sun, Apr 8, 2018 at 11:56 AM, Emmanuel Lécharny
> wrote:
>
>> Ok, I have some kind of 'elegant' soution that is
Sent to the dev list, where it belongs...
Message transféré
Subject: Re: Adding a secured() event in the IoHandler
To: Emmanuel Lécharny
If nextFilter.fire is called within messageReceived then it will send the
event to SSL Filter + 1; if nextFilter.fire is called within
Hi guys,
I'd like to ask your opinion about what we should do with the FtpServer
project.
There is little activity around it, and in the last 3 years, I was the
only one committig patches and code to the source base.
OTOH, I know this project is being used, as we have bug reports
periodically.
Hi guys,
I'd like to ask your opinion about what we should do with the FtpServer
project.
There is little activity around it, and in the last 3 years, I was the
only one committig patches and code to the source base.
OTOH, I know this project is being used, as we have bug reports
periodically.
Hi guys,
I'd like to ask your opinion about what we should do with the FtpServer
project.
There is little activity around it, and in the last 3 years, I was the
only one committig patches and code to the source base.
OTOH, I know this project is being used, as we have bug reports
periodically.
Le 19/04/2018 à 18:29, Jonathan Valliere a écrit :
> I’m guessing that the expected behavior is to disconnect from idle
> sessions?
I think so.
--
Emmanuel Lecharny
Symas.com
directory.apache.org
pEpkey.asc
Description: application/pgp-keys
Hi guys,
I'll be MIA for the coming week, starting tomorrow morning. I will left
my computer at home during these vacations, so don't expect any code to
be committed in the following days.
I'll have my phone though, so I will check the mail from time to time,
don't worry :-)
--
Emmanuel Lechar
have for other events, and rename
> 'fire' to 'event'.
>
> Thanks !
>
> On Fri, Apr 13, 2018 at 6:25 PM, Emmanuel Lécharny
> wrote:
>
>> Sent to the dev list, where it belongs...
>>
>>
>> ---- Message transféré
>>
Le 01/05/2018 à 19:05, Jonathan Valliere a écrit :
> Yes
Cool.
Change pushed.
--
Emmanuel Lecharny
Symas.com
directory.apache.org
pEpkey.asc
Description: application/pgp-keys
Hi,
Le 21/05/2018 à 15:36, rexxar a écrit :
> hi pete:
> I still come across the same IoBuffer "mark" problem with mina2.0.16 。
Do you have a piece of code demonstrating the problem you have ?
--
Emmanuel Lecharny
Symas.com
directory.apache.org
pEpkey.asc
Description: application/pg
Hi,
the IoBuffer.getHexDump() method does not copy the IoBuffer, and will
move the position while dumping the content.
It's clearly not the smartes utility function, as you can imagine...
Anyway, you have to copy the buffer (duplicate() function) you want to
dump before dumping it, to avoid any
Le 22/05/2018 à 11:17, rexxar a écrit :
> Hi,Emmanuel
>
>Thank you very much for your Explanation and Suggest。But I still have
> doubts about this ：
>
> the IoBuffer.getHexDump() method do move the position while dumping the
> content，but it
>
> recover it finally。It seems no other thread
Le 22/05/2018 à 14:02, Jonathan Valliere a écrit :
> Duplicating the buffer most likely temporarily moves the position also. If
> you submit a buffer to be written, don’t do anything with it until after it
> it written.
ByteBuffer.duplicate() - which is called by IoBuffer.duplicate() -
creates
Le 22/05/2018 à 15:09, Jonathan Valliere a écrit :
> Right, but the caveat is that the duplicate buffer shares the same memory
> space.
Correct. As soon as you don't change the internal byte [], you are fine
though. Dumping a duplicate should thenalways be fine.
Calling duplicate then changi
Le 22/05/2018 à 16:04, Jonathan Valliere a écrit :
> Just made the commit so getHexDump() is now perfectly safe without having
> to create a duplicate.
Thanks for that !
One more thing : the IoBufferHexDumper class is package protected, which
is probably a bit limiting. It might be worthful to
Le 22/05/2018 à 18:37, Jonathan Valliere a écrit :
> I don’t think there is any benefit of having it public. It’s only useable
> with IoBuffer and it’s built in to IoBuffer. Unless someone added more
> functions to it which aren’t present in IoBuffer such as hex ranges then
> might as well leave
Le 22/05/2018 à 19:31, Jonathan Valliere a écrit :
> Or you could add IoBuffer#getHexDump(start, end)?
Clearly an option.
That would raise the question : do we need an helper class then ?
--
Emmanuel Lecharny
Symas.com
directory.apache.org
pEpkey.asc
Description: application/pgp-keys
Hi,
we currently are using Google Analytics on MINA web site. I'm not sure
many of us is looking at the results (I have access to the results, but
I must admit I haven't looked at it for years).
In a GDPR compliance context, I think it's probably better to get rid of
GA. It's just a matter of rem
Le 23/05/2018 à 23:13, Jeff MAURY a écrit :
> By default GA will automatically change settings to be gdpr compliant
I do'nt want to take any risk, and we don't really use it anyway.
If you want to get some stats about MINA downloads, Nexus provides them.
--
Emmanuel Lecharny
Symas.com
direct
Got some errors :
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]
AsyncAuthInteractiveTest>AsyncAuthTestBase.testAsyncAuthSucceededAfterTimeout:121->Assert.assertTrue:41->Assert.fail:88
Unexpected failure Session.connect: java.io.IOException: End of IO
Stream Read
[ERROR]
AsyncAuthInteractiveTes
Hi !
I'm calling for a vote of Apache MINA 2.0.18 release. There is nothing
critical in it, no big bug fixes, just a few annoying ones. Although
there is some important addition: The IoHandler interface now expose a
new method :
void event(IoSession session, FilterEvent event) throws Exception;
Le 29/05/2018 à 16:15, Jonathan Valliere a écrit :
> Just me or does it feel like we’re cutting releases more often than usual?
There is no defined timeframe for releases. A usual moto at The ASF is
'release early, release often' [1]
FTR, MINA has been released 4 times (2.0.10, 2.0.11, 2.0.12
Le 01/06/2018 à 00:31, Guillaume Nodet a écrit :
> But if the community want to pursue the 2.0.0 release as it is, that's fine
> with me, I can restart a vote quickly, as I haven't deleted the staging
> repository or tag yet.
Regardless to the cancelation reasons, do you have any insight on th
Le 01/06/2018 à 08:10, Guillaume Nodet a écrit :
> Not really.
>
> Could you try running only those tests ?
> Maybe raising the log level to DEBUG in
> sshd-core/src/test/resources/log4j.properties,
> running:
> mvn clean test -Dtest=AsyncAuth\*Test
> and gist the content of the sshd-core/targ
Le 01/06/2018 à 09:10, Guillaume Nodet a écrit :
> Cool, that gives a lot of information. The problems seems to come from the
> following exception:
> java.lang.IllegalArgumentException: RSA modulus has a small prime factor
>
> I'll investigate the possible causes.
Looking at BC code at
https
>
>> On May 29, 2018, at 7:48 AM, Emmanuel Lécharny wrote:
>>
>> Hi !
>>
>> I'm calling for a vote of Apache MINA 2.0.18 release. There is nothing
>> critical in it, no big bug fixes, just a few annoying ones. Although
>> there is some important ad
... FAILURE
[04:24 min]
> I can't figure why BC would generate a modulus that would be rejected later
> :-(
>
>
> 2018-06-01 9:44 GMT+02:00 Emmanuel Lécharny :
>
>>
>>
>> Le 01/06/2018 à 09:10, Guillaume Nodet a écrit :
>>> Cool, that gi
MINA PMC
Thanks !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
pEpkey.asc
Description: application/pgp-keys
Hi guys,
I have made a mistake when I cut the latest release (MINA 2.0.18), which
breaks the API - actually, two errors -.
The first one was to inject a new event in the IoHandler, expecting
users to extend IoHandlerAdapter instead of implementing IoHandler
The second one was related to the remo
Le 07/06/2018 à 20:41, Jonathan Valliere a écrit :
> Would it make sense to rename the 3.0 branch to FUTURE or something that
> doesn’t involve a numerical version number?
Sure. It's a bit annoying to have blocked a version number for years...
--
Emmanuel Lecharny
Symas.com
directory.apache.
Hi !
I'm calling for a vote of Apache MINA 2.0.19 release.
This is a fix for the previous release (2.0.18) which broke the API by
mistake.
Two changes have been rolled back :
- the 'event' message has been removed from the IoHandler interface
- the SESSION_SECURED/SESSION_UNSECURED message are
Le 11/06/2018 à 11:18, Christoph John a écrit :
> Hi Emmanuel,
>
> just a short question: I can compile against 2.0.18 without problems and
> the tests run fine. So is it safe to use that version then? In our
> project we extend AbstractIoHandler.
So it's safe.
2.0.19 fixed the API regressions
Hi guys,
I'm closing the vote, with 4 binding +1 and one non-binding +1
Binding votes :
Guillaume
Jeff
Lyor
and me
Non-binding votes :
Elijah
I will push tha packages and update the web site.
Thanks !
--
Emmanuel Lecharny
Symas.com
directory.apache.org
pEpkey.asc
Description: applicati
I'd like to have the following test ran with -Djavax.net.debug=all
option set :
org.apache.camel.component.xmpp.XmppMultiUserChatTest.testXmppChat
There is clearly some SSL weirdness going on...
java.lang.RuntimeException: Could not connect to XMPP server:
localhost:5222/null
Caused by: org.jives
tion attack?
javax.net.ssl.SSLException: Inbound closed before receiving peer's
close_notify: possible truncation attack?
...
Could it be a problem in Camel ?
>
> Le mer. 20 juin 2018 à 17:22, Emmanuel Lécharny a
> écrit :
>
>> I'd like to have the following test ran w
Le 20/06/2018 à 18:09, Lyor Goldstein a écrit :
> I believe CAMEL can simply choose to use mina-core 2.0.18
2.0.17.
There is an API regression in 2.0.18 which has been solved in 2.0.19.
--
Emmanuel Lecharny
Symas.com
directory.apache.org
Le 20/06/2018 à 19:00, Guillaume Nodet a écrit :
> So I've enabled debug logging which helps a bit.
> https://gist.github.com/gnodet/04b08b1d19caa67359f352522774a70d
>
> I suspect a concurrent access to the byte buffer because the exception
> should be thrown from the HeapByteBuffer#checkIndex
Le 21/06/2018 à 12:42, Guillaume Nodet a écrit :
> So I can't explain exactly why, but the problem comes from the removal of
> the following variable:
>
> https://github.com/apache/mina/commit/60cb619b6f0a940e7a6b18c060158270c227255b#diff-e3418ff2f83464c155b780cdbfb9e4aaL754
Hmmm...
public f
Le 21/06/2018 à 18:30, Guillaume Nodet a écrit :
> Sorry, my link does not work.
> I pinned it down to the removal of the SslHandler#handshakeStatus variable.
Ok, that makes more sense :-)
Can you test a 2.0.19 with this change reverted ?
I can easily cut a 2.0.20 fast. (makes me think that m
Hi Guillaume,
I have reverted the change. Can you give it a try ? If it's ok, I can
cut a release right away.
Thanks !
--
Emmanuel Lecharny
Symas.com
directory.apache.org
pEpkey.asc
Description: application/pgp-keys
Le 22/06/2018 à 14:01, Jonathan Valliere a écrit :
> At what point is the SSL going to be redesigned and anyone using it will be
> forced to update their code?
Sadly, we have thousands of peope using MINA as it is.
Mina 3.0 was an effort we started a few years ago to redesign this piece
of code
Le 23/06/2018 à 01:40, Guillaume Nodet a écrit :
> Sorry, I've been on meetings the whole week. I'll give it a try on monday.
Hi Guillaume,
any update ?
Thanks !
--
Emmanuel Lecharny
Symas.com
directory.apache.org
pEpkey.asc
Description: application/pgp-keys
Le 29/06/2018 à 13:10, Guillaume Nodet a écrit :
> Sorry for the delay.
> I gave it another try and unfortunately, the problem persists with my local
> build of 2.20-SNAPSHOT.
Ah, crap :/
> I'll try to find a fix next week.
Okiedo. What is surprizing is that I fixed the change you pointed, so
Le 06/07/2018 à 16:29, Jonathan Valliere a écrit :
> Any objections to setting up a 2.X branch which serves as the master then
> create the explicit numerical branches when releases are done? The 2.0
> used to be the master but now there is 2.1. Just looking to make it easier
> to understand.
Le 06/07/2018 à 23:15, Jonathan Valliere a écrit :
> There are no 2.1 releases are there?
No, there are none. There is a branch I created, but no release so far.
Maybe 3.0 should be reserved for some
> incompatible refactor.
3.0 does exist, and we have releases for it, but it's currently sle
Le 16/07/2018 à 01:47, Reijhanniel Jearl Campos a écrit :
> Hi!
>
> I was recently working on a test that involves setting up an embedded XMPP
> server with Vysper, and Smack[1]. I encountered an issue[2] and posted on
> the Smack forum, and a developer pointed out that it might be a server
> is
Le 14/08/2018 à 19:54, Lyor Goldstein a écrit :
> While going over the MINA SSHD code in order to try and break it down
> further to smaller modules, I encountered quite a few utility classes that
> duplicate (exactly or closely) code that already exists in other very
> popular "3rd party" librar
Hi guys,
the new release policy requires that we remove MD5 signature from the
www.apache.org/dist repository for our projects :
" -- for past releases :
-- you are not required to change anything ;
-- it would be nice if you fixed your dist area ;
-- start with : clea
Sorry for the delay, I will take some time tonite or tomorrow to vote
this release !
Le 17/09/2018 à 10:35, Guillaume Nodet a écrit :
> I've staged a candidate release for Mina SSHD 2.1.0 at
> https://repository.apache.org/content/repositories/orgapachemina-1038/
>
> This release contains the fo
Compiled the package, compiled from source, check the N&L files.
Weird enough, everything works fine with source grabbed from the git
repo, but the package consistently fails with those errors :
...
[ERROR] Tests run: 6, Failures: 2, Errors: 4, Skipped: 0, Time elapsed:
0.476 s <<< FAILURE! - in
Le 27/09/2018 à 15:07, Lyor Goldstein a écrit :
> Hi Emmanuel,
>
>>> I just used the link Guillaume provided
> https://repository.apache.org/content/repositories/orgapachemina-1038/
>
> The link contains only binaries -
Nope, it also contains a source package :
https://repository.apache.org/
Just for the record :
"Every ASF release MUST contain one or more source packages, which MUST
be sufficient for a user to build and test the release provided they
have access to the appropriate platform and tools."
(http://www.apache.org/legal/release-policy.html#source-packages)
Le 29/09/2018 à
Le 30/09/2018 à 16:21, Lyor Goldstein a écrit :
>>> Also Github is own by a private company, we should not depend on them, they
> can easily shutdown their service, or stopping offering it for
> free.
>
> Very good point - however, why shouldn't Apache run its own GIT repository
> (which it act
Le 30/09/2018 à 20:37, Guillaume Nodet a écrit :
> #2 is not an option imho. Given the amount of work that would be needed to
> manually re-package and re-sign the distributions artifacts, i'd go for #1
> if this is considered a blocker.
As soon as we know why it fails when we try to build fro
Le 01/10/2018 à 09:10, Lyor Goldstein a écrit :
>>> Lyor, would you mind writing the release annoucement ? I'll publish the
>>> artifacts
> this morning, so we can send it later today.
>
> Sure - I'll send it to your private mail for proof-reading and any
> last-minute modifications you see f
Le 03/10/2018 à 16:25, Mondain a écrit :
> I was looking into an issue reported in our use of UDP sessions in Mina
> 2.0.19. The IoSession.getScheduledWriteMessages() seemed to give very odd
> and varying results when more than one session existed. It seems that the
> scheduledWriteMessages stat
Sounds good to me.
I think we should reboot the Vysper and FtpServer move to attic
discussion...
Le 09/10/2018 à 09:14, Guillaume Nodet a écrit :
> Below is the draft board report we need to submit for the next board
> meeting in a week.
> If you have anything to add / modify, let me know, else I
Le 09/10/2018 à 14:49, Jonathan Valliere a écrit :
> I was willing to be the default maintainer for FtpServer.
That works :-)
Vysper seems a bit of a lost case, IMHO..
--
Emmanuel Lecharny
Symas.com
directory.apache.org
pEpkey.asc
Description: application/pgp-keys
Thanks, Jonathan,
Le 11/10/2018 à 18:07, Jonathan Valliere a écrit :
> I was having a conversation with a colleague last week about the cost of
> automatic casting due to the use of generics in java; so, I decided to
> write a benchmark. Since everyone wants their networking code to run as
> fast
Le 11/10/2018 à 19:03, Jonathan Valliere a écrit :
> One explaination I came up was that Java is performing a full upcast when
> encountering the generic-based interface. Unchecked and checked genetics
> perform identically.
Here is the bytecode for the strictMethod() :
0: aload_0
1: invokev
Hi Lyor,
a few hints, onsidering I haven't reviewed the code...
Le 19/10/2018 à 07:00, Lyor Goldstein a écrit :
> Here is the issue in a nutshell - a client might open an SSH tunnel, send
> some data and close (normally) its side of the tunnel before the channel to
> the other side has been succe
Hi !
sure, feel free to do so ! We haven't tested it with Java > 8, so that
would clearly help.
Thanks !
On 02/12/2018 18:43, Sina Kashipazha wrote:
Dear Community members
I'm graduated CS student with computer network and operating system experience.
I want to help open source community
On 18/01/2019 23:22, Jonathan Valliere wrote:
I suggest creating the 2.X branch and continue that as the master for all 2
releases. Tag everything else.
we have a 2.0 branch that is the working branch for 2.0 x releases, and
a 2.1.0 branch for the next iteration (that plus a trunk that is f
Thanks for the headsup !
All the site has been updated.
On 06/02/2019 00:19, Jonathan Valliere wrote:
We need to update all the website pages to point to gitbox. All of the
projects continue to list git-wip-us.apache.org
On Sat, Jan 12, 2019 at 6:10 AM Lyor Goldstein
wrote:
The reposit
On 08/02/2019 15:22, Jonathan Valliere wrote:
You mean that you want to pass messages from one thread to another?
Or from one session to another one ?
On Fri, Feb 8, 2019 at 9:02 AM Kevin Kal wrote:
Dear Sir/Madam,
I've been trying to find out how to send loopback messages on a IoSes
On 08/02/2019 15:22, Jonathan Valliere wrote:
You mean that you want to pass messages from one thread to another?
Or from one session to another one ?
On Fri, Feb 8, 2019 at 9:02 AM Kevin Kal wrote:
Dear Sir/Madam,
I've been trying to find out how to send loopback messages on a IoSess
I still don't get it.
Your IoHandler will be called everytime an event occurs (message
received, message written, session created/closed/idling, exception).
You have the opportunity to execute some action at this moment.
Beside that, I don't see a use case. I'm probably missing something...
erstand that It would be a deferred action that could only happen after
the IO processor is done? Maybe you could explain the reason why you want
to do this?
On Thu, Feb 14, 2019 at 10:40 AM Emmanuel Lécharny <
elecharny@
>
wrote:
I still don't get it.
Your IoHandler will be called
On 14/02/2019 17:42, Jonathan Valliere wrote:
On a side note, this is the developers mailing list. We're filling the
inboxes of other developers that probably don't want to be a part of this
conversation. We should move it to the us...@mina.apache.org mailing list.
True.
Although I sugges
On 14/02/2019 17:28, kevintjuh93 wrote:
Yes, I am aware that's what happens. And in these cases I can make it execute
at the end of a messageReceived. But my case is that I do something from a
non io-processor thread, but what it does needs to be synced with the
io-processor.
Ok, now that mak
Hi guys,
I finally found a bit of time to prepare the MINA 2.0.20 release. I'm
currently cleaning up the site, (cf DIRMINA-1089), and there are *many*
broken links (161 this morning). Most of them are related to links to
the dist directory, which does not contain any of the old versions
pack
On 20/02/2019 14:14, Jonathan Valliere wrote:
Is there some automated release process or is it entirely manual?
I use a link checker, then I fix it manually. There are 1423 links, out
of which 161 were broken when I started cleaning them up. I'm down to
87, but many are false positive (I'm
Hi guys,
for some unknown reasons, I can't find any trace of the SSHD 1.3.0 and
1.4.0 packages and signatures in https://archive.apache.org/dist/mina/sshd/
The 'old versions' download pages yet list those versions as available
(http://mina.apache.org/downloads-sshd.html)
ATM, I have marked
Hi guys,
yesterday evening, I cut a MINA 2.0.20 release (vote to come). Then I
tested it with Ftpserver (all is good), and SSHD. I get some test failures :
[INFO]
[ERROR] Errors:
[ERROR] PortForwardingTest.testLocalForwarding:467->createSession:802 »
JSch java.net
[ERROR] PortForwardin
Hi !
I'm calling for a vote of Apache MINA 2.0.20 release.
It's a bug fix release. Here are the list of bugs that have been fixed :
DIRMINA-1092: Removed a spurious printstacktrace
DIRMINA-1098: handshakeStatus variable has been wrongly made global
DIRMINA-1088: the OrderedThreadPool implementa
same name with 2
different versions :/ ).
Thanks !
On 21/02/2019 12:06, Emmanuel Lécharny wrote:
Hi !
I'm calling for a vote of Apache MINA 2.0.20 release.
It's a bug fix release. Here are the list of bugs that have been fixed :
DIRMINA-1092: Removed a spurious printsta
Hi guys,
after having cut MINA 2.0.20, I tried to cut MINA 2.1.0 (which is just
MINA 2.0.20 with a slight API change). Sadly, I can't have the package
moved to Nexus.
I'm trying to figure out what's wrong, but there is nothing obvious. It
should work, the pom.xml hasn't change that much...
Hi !
I'm calling for a vote of Apache MINA 2.1.0 release.
It's a branched version diverging from Apache MINA 2.0.17, with some
difference in the API. Otherwise, every changes made in 2.0.18/19/20
have been ported to this version.
The API change is that the IoFilter interface now propagates a
On 05/03/2019 01:25, Jonathan Valliere wrote:
I just checked git, looks like 2.1.0 was updated with changes through
2.0.20. Is this correct?
correct
Is the plan to maintain 2.0.X separate from
2.1.X and just port the changes?
Yep.
On 05/03/2019 14:19, Jonathan Valliere wrote:
What in 2.1.X is not compatible with products build around 2.0.X?
The difference lies in the API change in IoFilter interface (which
should not impact your code), and in the IoHandler interface, where the
addition of the event() method has been
801 - 900 of 1053 matches
Mail list logo
