BUILD-FAILURE: Job 'james/ApacheJames/master [master] [1309]':
Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames/job/master/1309/;>james/ApacheJames/master
[master] [1309]"
-
To unsubscribe, e-mail:
BUILD-STABLE: Job 'james/ApacheJames/master [master] [1310]':
Is back to normal.
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
mohan created JAMES-4022:
Summary: James server is getting crashed or stopped after 20 mins
or with load
Key: JAMES-4022
URL: https://issues.apache.org/jira/browse/JAMES-4022
Project: James Server
[
https://issues.apache.org/jira/browse/JAMES-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829867#comment-17829867
]
mohan commented on JAMES-4022:
--
at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_362]
Caused by:
[
https://issues.apache.org/jira/browse/JAMES-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829868#comment-17829868
]
mohan commented on JAMES-4022:
--
smtp server is running port number is 25
> James server is getting
BUILD-STABLE: Job 'james/ApacheJames/master [master] [1312]':
Is back to normal.
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[
https://issues.apache.org/jira/browse/JAMES-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829982#comment-17829982
]
Benoit Tellier commented on JAMES-4022:
---
For me, as it stands, as the server version documented in
[
https://issues.apache.org/jira/browse/JAMES-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829944#comment-17829944
]
Jean Helou commented on JAMES-4022:
---
can you provide the steps to reproduce ?
* information on the
[
https://issues.apache.org/jira/browse/JAMES-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829980#comment-17829980
]
Benoit Tellier commented on JAMES-4022:
---
Sorry to repeat it for the 50th time on this mailing list
Hello all.
The streaming approach turned out to be a terrible idea!
ChunkStream was doing massive blocking reads on the event loop.
InputStream is just not the right abstraction for non blocking reads.
Rewriting everything to support something like Flux looks
doable but requires a major
10 matches
Mail list logo