[jira] [Created] (JAMES-3984) Getting ClosedChannelException during James-server-jpa-guice v3.3.0

[Pradeep (Jira)]

Pradeep created JAMES-3984:
--

 Summary: Getting ClosedChannelException during 
James-server-jpa-guice v3.3.0
 Key: JAMES-3984
 URL: https://issues.apache.org/jira/browse/JAMES-3984
 Project: James Server
  Issue Type: Bug
  Components: James Core
Affects Versions: 3.3.0
Reporter: Pradeep


Hi,

Getting ClosedChannelException during James-server-jpa-guice v3.3.0  start up 
and  "Connection closed for" continuously. Java11 is used. Kindly suggest how 
to fix this issue. 


java.nio.channels.ClosedChannelException: null
        at 
org.jboss.netty.handler.stream.ChunkedWriteHandler.discard(ChunkedWriteHandler.java:168)
        at 
org.jboss.netty.handler.stream.ChunkedWriteHandler.flush(ChunkedWriteHandler.java:192)
        at 
org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:121)
        at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
        at 
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
        at 
org.jboss.netty.handler.execution.ExecutionHandler.handleDownstream(ExecutionHandler.java:176)
        at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
        at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
        at org.jboss.netty.channel.Channels.write(Channels.java:704)
        at org.jboss.netty.channel.Channels.write(Channels.java:671)
        at 
org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:347)
        at 
org.apache.james.protocols.netty.NettyProtocolTransport.writeToClient(NettyProtocolTransport.java:104)
        at 
org.apache.james.protocols.api.AbstractProtocolTransport.writeResponseToClient(AbstractProtocolTransport.java:145)
        at 
org.apache.james.protocols.api.AbstractProtocolTransport.writeResponse(AbstractProtocolTransport.java:64)
        at 
org.apache.james.protocols.netty.BasicChannelUpstreamHandler.channelConnected(BasicChannelUpstreamHandler.java:111)
        at 
org.apache.james.smtpserver.netty.SMTPChannelUpstreamHandler.channelConnected(SMTPChannelUpstreamHandler.java:54)
        at 
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:100)

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Commented] (JAMES-3983) Admin help required in JIRA

[Pradeep (Jira)]

[ 
https://issues.apache.org/jira/browse/JAMES-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815543#comment-17815543
 ] 

Pradeep commented on JAMES-3983:


[~btellier]  can you delete 3981? I even don't see an option to delete that 
JIRA. I am ok with the deletion. 

> Admin help required in JIRA
> ---
>
> Key: JAMES-3983
> URL: https://issues.apache.org/jira/browse/JAMES-3983
> Project: James Server
>  Issue Type: Bug
>  Components: James Core
>Reporter: Pradeep
>Priority: Major
>
> Can you please delete description history in: JAMES-3981. I do not have 
> permission to do so. If history cannot be deleted, then pls delete the Jira 
> completely. IP information need to be removed from everywhere in description 
> and history. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Closed] (JAMES-3983) Admin help required in JIRA

[Benoit Tellier (Jira)]

 [ 
https://issues.apache.org/jira/browse/JAMES-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benoit Tellier closed JAMES-3983.
-
Resolution: Invalid

> Admin help required in JIRA
> ---
>
> Key: JAMES-3983
> URL: https://issues.apache.org/jira/browse/JAMES-3983
> Project: James Server
>  Issue Type: Bug
>  Components: James Core
>Reporter: Pradeep
>Priority: Major
>
> Can you please delete description history in: JAMES-3981. I do not have 
> permission to do so. If history cannot be deleted, then pls delete the Jira 
> completely. IP information need to be removed from everywhere in description 
> and history. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Commented] (JAMES-3983) Admin help required in JIRA

[Benoit Tellier (Jira)]

[ 
https://issues.apache.org/jira/browse/JAMES-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815539#comment-17815539
 ] 

Benoit Tellier commented on JAMES-3983:
---

Neither do I

According to 
https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-delete-the-history/qaq-p/2443387
 that's impossible.

I let you escalate to the INFRA team might it be needed. 
https://issues.apache.org/jira/browse/INFRA

In the meantime I close this.

Regards.

> Admin help required in JIRA
> ---
>
> Key: JAMES-3983
> URL: https://issues.apache.org/jira/browse/JAMES-3983
> Project: James Server
>  Issue Type: Bug
>  Components: James Core
>Reporter: Pradeep
>Priority: Major
>
> Can you please delete description history in: JAMES-3981. I do not have 
> permission to do so. If history cannot be deleted, then pls delete the Jira 
> completely. IP information need to be removed from everywhere in description 
> and history. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Commented] (JAMES-3983) Admin help required in JIRA

[Benoit Tellier (Jira)]

[ 
https://issues.apache.org/jira/browse/JAMES-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815536#comment-17815536
 ] 

Benoit Tellier commented on JAMES-3983:
---

Neither do i...

> Admin help required in JIRA
> ---
>
> Key: JAMES-3983
> URL: https://issues.apache.org/jira/browse/JAMES-3983
> Project: James Server
>  Issue Type: Bug
>  Components: James Core
>Reporter: Pradeep
>Priority: Major
>
> Can you please delete description history in: JAMES-3981. I do not have 
> permission to do so. If history cannot be deleted, then pls delete the Jira 
> completely. IP information need to be removed from everywhere in description 
> and history. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JAMES-3983) Admin help required in JIRA

[Pradeep (Jira)]

 [ 
https://issues.apache.org/jira/browse/JAMES-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pradeep updated JAMES-3983:
---
Description: Can you please delete description history in: JAMES-3981. I do 
not have permission to do so. If history cannot be deleted, then pls delete the 
Jira completely. IP information need to be removed from everywhere in 
description and history.   (was: Can you please delete description history in: 
JAMES-3981. I do not have permission to do so. If history cannot be deleted, 
then pls delete his Jira completely. IP information need to be removed from 
everywhere in description and history. )

> Admin help required in JIRA
> ---
>
> Key: JAMES-3983
> URL: https://issues.apache.org/jira/browse/JAMES-3983
> Project: James Server
>  Issue Type: Bug
>  Components: James Core
>Reporter: Pradeep
>Priority: Major
>
> Can you please delete description history in: JAMES-3981. I do not have 
> permission to do so. If history cannot be deleted, then pls delete the Jira 
> completely. IP information need to be removed from everywhere in description 
> and history. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Created] (JAMES-3983) Admin help required in JIRA

[Pradeep (Jira)]

Pradeep created JAMES-3983:
--

 Summary: Admin help required in JIRA
 Key: JAMES-3983
 URL: https://issues.apache.org/jira/browse/JAMES-3983
 Project: James Server
  Issue Type: Bug
  Components: James Core
Reporter: Pradeep


Can you please delete description history in: JAMES-3981. I do not have 
permission to do so. If history cannot be deleted, then pls delete his Jira 
completely. IP information need to be removed from everywhere in description 
and history. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

[jira] [Updated] (JAMES-3981) Getting ClosedChannelException during James-server-jpa-guice v3.3.0

[Pradeep (Jira)]

 [ 
https://issues.apache.org/jira/browse/JAMES-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pradeep updated JAMES-3981:
---
Description: 
Hi,

Getting ClosedChannelException during James-server-jpa-guice v3.3.0  start up 
and  "Connection closed for" continuously. Java11 is used. Kindly suggest how 
to fix this issue. 


java.nio.channels.ClosedChannelException: null
        at 
org.jboss.netty.handler.stream.ChunkedWriteHandler.discard(ChunkedWriteHandler.java:168)
        at 
org.jboss.netty.handler.stream.ChunkedWriteHandler.flush(ChunkedWriteHandler.java:192)
        at 
org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:121)
        at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
        at 
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
        at 
org.jboss.netty.handler.execution.ExecutionHandler.handleDownstream(ExecutionHandler.java:176)
        at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
        at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
        at org.jboss.netty.channel.Channels.write(Channels.java:704)
        at org.jboss.netty.channel.Channels.write(Channels.java:671)
        at 
org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:347)
        at 
org.apache.james.protocols.netty.NettyProtocolTransport.writeToClient(NettyProtocolTransport.java:104)
        at 
org.apache.james.protocols.api.AbstractProtocolTransport.writeResponseToClient(AbstractProtocolTransport.java:145)
        at 
org.apache.james.protocols.api.AbstractProtocolTransport.writeResponse(AbstractProtocolTransport.java:64)
        at 
org.apache.james.protocols.netty.BasicChannelUpstreamHandler.channelConnected(BasicChannelUpstreamHandler.java:111)
        at 
org.apache.james.smtpserver.netty.SMTPChannelUpstreamHandler.channelConnected(SMTPChannelUpstreamHandler.java:54)
        at 
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:100)

 

  was:
Hi,

Getting ClosedChannelException during James-server-jpa-guice v3.3.0  start up 
and  "Connection closed for" continuously. Java11 is used. Kindly suggest how 
to fix this issue. 

 

0:38:18.175 [INFO ] o.a.j.p.l.n.AbstractConfigurableAsyncServer - SMTP Service 
handler connection timeout is: 360
10:38:18.175 [INFO ] o.a.j.p.l.n.AbstractConfigurableAsyncServer - SMTP Service 
connection backlog is: 200
10:38:18.175 [INFO ] o.a.j.p.l.n.AbstractProtocolAsyncServer - This SMTP server 
requires authentication.
10:38:18.175 [INFO ] o.a.j.p.l.n.AbstractProtocolAsyncServer - No maximum 
message size is enforced for this server.
10:38:18.307 [INFO ] o.a.j.p.l.n.AbstractConfigurableAsyncServer - Init SMTP 
Service done
10:38:18.655 [INFO ] o.a.j.p.l.n.AbstractConfigurableAsyncServer - Init SMTP 
Service done
10:38:18.710 [INFO ] o.a.j.p.l.n.AbstractConfigurableAsyncServer - Init SMTP 
Service done
10:38:19.389 [INFO ] o.a.j.p.n.BasicChannelUpstreamHandler - Connection 
established from 169.73.162.80
10:38:19.395 [INFO ] o.a.j.p.n.BasicChannelUpstreamHandler - Connection closed 
for 169.73.162.80
10:38:19.397 [INFO ] o.a.j.p.n.BasicChannelUpstreamHandler - Unable to process 
request
java.nio.channels.ClosedChannelException: null
        at 
org.jboss.netty.handler.stream.ChunkedWriteHandler.discard(ChunkedWriteHandler.java:168)
        at 
org.jboss.netty.handler.stream.ChunkedWriteHandler.flush(ChunkedWriteHandler.java:192)
        at 
org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:121)
        at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
        at 
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
        at 
org.jboss.netty.handler.execution.ExecutionHandler.handleDownstream(ExecutionHandler.java:176)
        at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
        at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
        at org.jboss.netty.channel.Channels.write(Channels.java:704)
        at org.jboss.netty.channel.Channels.write(Channels.java:671)
        at 
org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:347)
        at 
org.apache.james.protocols.netty.NettyProtocolTransport.writeToClient(NettyProtocolTransport.java:104)
        at 
org.apache.james.protocols.api.AbstractProtocolTransport.writeResponseToClient(AbstractProtocolTransport.java:145)
        at 
org.apache.james.protocols.api.AbstractProtocolTransport.writeResponse(AbstractProtocolTransport.java:64)
        at 

Re: Vote to merge the Java 21 adoption for Apache James PR

[Eugen Stan]

Hi Quan,

+1 for Java 21 for new James distribution version.

Libraries IMO should be released with support for older versions versions.
Not every project can use the latest and greatest JVM.
And I don't think low level libraries (mime4j) will benefit a lot from 
new Java language features.


Keep in mind, you can run a library built for Java 8 on JVM 21, but not 
the other way around.


IMO I will plan a switch to Java 21 some time after Java 22 is out (3-6 
months) after some JVM version reports are published.


Eugen

La 06.02.2024 15:32, Benoit TELLIER a scris:

Hi Quan

+1 on the principle.

However I have a few remarks:

1. Please be precise on James versions:
  - Java 21 will be used by Apache James for versions 3.9.0 onward
  - Java 11 will be used by Apache James for versions 3.7.x and 3.8.x. 
No backport of the Java 21 switch is planned.


2. Votes follow a more formal procedure within the ASF, and voting rules 
shall be clearly stated (voting time, voting threshold) cf 
https://www.apache.org/foundation/voting.html

In practice:
  - I propose the wording "lazy consensus"
  - for code changes we may remind that the vote may be vetoed
  - Provide an explicit voting time range specifying starting date and 
time and ending date.

    In practice a minimum of 3 days is recommended.

Regards

Benoit

On 06/02/2024 04:36, Quan tran hong wrote:

Hi everyone,

Following the Jira ticket

and the previous mailing list discussion

regarding Java 21 adoption for James, I and Benoit put together an effort
to successfully get a green build on the Java 21 adoption PR
.

The idea is to have James migrated to Java 21 with minimal changes first,
and after that, we can leverage new Java features gradually.

Because this is a big change for James, James's community review, 
remarks,

and opinions on merging the Java 21 PR should be needed.

It would be good if the community could spend some time reviewing the PR,
or just upvote/downvote directly on this mail thread.

Thanks for reading.

Best regards,

Quan



-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org



--
Eugen Stan

+40770 941 271  / https://www.netdava.com


-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Re: Develocity

[Jean Helou]

>
> > The risk is caching a negative result coming from a flaky test. And I
> feel
> like James test suite is quite unstable.
>
> On that, maybe we can find if the Gradle extension / surefire supports
> caching only if the build (test phase for example) succeeds?
>
>
I searched the documentation again (
https://docs.gradle.com/enterprise/maven-extension/#maven_surefire_plugin_and_maven_failsafe_plugin
)
> Test results for surefire:test are stored in the Build Cache whenever the
goal succeeds. Thus, by default, only successful or skipped test results
are cached. However, if 

is set to true, test failures are cached as well.

And good news  is not used in the james build so I can´t
see a reason not to enable remote caching.

jean

Quan
>
> Vào Th 4, 7 thg 2, 2024 vào lúc 10:22 Rene Cordier 
> đã viết:
>
> > I agree caching the test suite is very tempting, it would help gain
> > so much time on the build.
> >
> > But yes the test suite is flaky unfortunately. Maybe we need extra work
> > making it more stable first, but that's not easy task ^^'
> >
> > Or maybe for remote caching on test execution, maybe we can try to
> > execute that in an other branch in parallel to master, giving us time to
> > monitor the behavior of the build, before using it for good? Requires
> > extra work, efforts and attention yes, but I hardly see how else we can
> > go safely forward on this. But somebody else has a better idea maybe? :)
> >
> > Regards,
> >
> > Rene.
> >
> > On 2/7/24 02:58, Jean Helou wrote:
> > > Thanks for trying
> > >
> > > As you can see in the output only about 10% of the tasks you ran were
> > > cached.
> > >
> > > Which explains why the gains are not so great.
> > >
> > > There are 2 good news
> > > - it is possible to configure more goals to be cached. I have an
> attempt
> > at
> > > caching scala compile (which doesn't work for now as that goal has
> rather
> > > complex input and outputs).
> > > I intend to look at build scans to cache more high CPU consuming goals
> > and
> > > to avoid running some goals entirely when possible (as per my comments
> on
> > > the PR)
> > >
> > > Where it becomes really interesting (the second good news) is that
> > surefire
> > > is supported out of the box, so if one pays the cost of running the
> > tests,
> > > every subsequent build would only run the tests for the changed
> projects
> > > and their dependencies
> > >
> > > And testing is by far the most time consuming goal in James build.
> > >
> > > Remote caching of test execution would have the most impact,
> accelerating
> > > both local and CI builds because it would allow sharing the cache
> between
> > > different machines/nodes. (Only the ci would write but everyone could
> > read
> > > if I understand correctly)
> > >
> > > The risk is caching a negative result coming from a flaky test. And I
> > feel
> > > like James test suite is quite unstable.
> > >
> > > So I'm wondering if I should go ahead with the remote build cache node
> > > request to apache INFRA or revisit that request in a few months.
> > >
> > > Jean
> > >
> > >
> > >
> > > Le mar. 6 févr. 2024 à 11:18, Quan tran hong <
> > quan.tranhong1...@gmail.com>
> > > a écrit :
> > >
> > >> Hi Jean,
> > >>
> > >> I tried your work locally and the build time is truly better.
> > >> `mvn clean install -DskipTests -Dmaven.skip.doc=true
> > >> -Dgradle.cache.local.enabled=true`
> > >>
> > >> 1st build:
> > >> [INFO] Total time:  22:18 min
> > >> [INFO] 8053 goals, 7996 executed, 57 from cache, saving at least 13s
> > >>
> > >> 2nd build:
> > >> [INFO] Total time:  15:07 min
> > >> [INFO] 8053 goals, 7296 executed, 757 from cache, saving at least 3m
> 11s
> > >>
> > >> Thank you for the initiative :-)
> > >>
> > >> Quan
> > >>
> > >> Vào Th 3, 6 thg 2, 2024 vào lúc 14:48 Jean Helou  >
> > đã
> > >> viết:
> > >>
> > >>> Hi devs,
> > >>>
> > >>> I realized this morning that I initiated the conversation on the
> wrong
> > >> list
> > >>> (server-user instead of server-dev) ...
> > >>> see the archives
> > >>> https://lists.apache.org/list.html?server-u...@james.apache.org for
> > >> Rene's
> > >>> positive answer
> > >>>
> > >>> sorry about that
> > >>>
> > >>> jean
> > >>>
> > >>> -- Forwarded message -
> > >>> From: Jean Helou 
> > >>> Date: Mon, Feb 5, 2024 at 3:52 PM
> > >>> Subject: Develocity
> > >>> To: James Users List 
> > >>>
> > >>>
> > >>> Hello fellow james devs,
> > >>>
> > >>> I'm not sure how much context to provide in the email you can read
> more
> > >> in
> > >>>
> > >>
> >
> https://issues.apache.org/jira/projects/JAMES/issues/JAMES-3978?filter=allopenissues
> > >>> TLDR; A few months ago the apache foundation announced a sponsorship
> of
> > >> the
> > >>> "gradle" company for a tool to diagnose, monitor and optimize
> builds  (
> > >>> called gradle enterprise at the time and renamed develocity since)
> > >>>
> > >>> I