[
https://issues.apache.org/jira/browse/JAMES-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht updated JAMES-1149:
--------------------------------
Attachment: slfj4-server.patch
- Server uses apache-mailet-2.4 which has deprecated methods in MailetContext.
To not change to snapshot version I add a TODO where needed because of [1] and
used the deprecated methods instead.
- Upgrade log4j version 1.2.14 -> 1.2.16
- Removed commons-logging dependency
- Add slf4j depndencies
- Use apache-protocols version 1.4-SNAPSHOT instead 1.3
In [2] the underlaying logging framework (log4j) is hardcoded used to set the
log level. This may become a problem when changing the underlaying logging
framework (OSGI?).
Having applied all the already contributed patches (not sure if all are really
needed) I can build the project, testcases are passing.
I can start the built distribution until I get an exception [3] which is likely
to be the result of using default configuration or not enough permission as
normal unix user.
NOTE: This error [3] I could only see when starting the application not in
daemon mode (wrapper.daemonize=FALSE, bin/james script) - I couldn't find any
errors in the log files.
[1] https://issues.apache.org/jira/browse/MAILET-36
[2] org.apache.james.container.spring.provider.log.LogProviderImpl
[3] jvm 1 | INFO 16:49:23,047 | james.mailspooler |
org.apache.james.mailetcontainer.lib.JamesMailSpooler thread shutdown completed.
jvm 1 |
jvm 1 | WrapperSimpleApp: Encountered an error running main:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'smtpserver': Invocation of init method failed; nested exception is
org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:25
jvm 1 | org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'smtpserver': Invocation of init method failed; nested
exception is org.jboss.netty.channel.ChannelException: Failed to bind to:
0.0.0.0/0.0.0.0:25
jvm 1 | at
org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:133)
> Replace commons-logging with jcl-over-slf4j
> -------------------------------------------
>
> Key: JAMES-1149
> URL: https://issues.apache.org/jira/browse/JAMES-1149
> Project: JAMES Server
> Issue Type: Task
> Affects Versions: 3.0-M2
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 3.0-M3
>
> Attachments: slfj4-imap.patch, slfj4-mailbox.patch,
> slfj4-protocols.patch, slfj4-protocols_1.patch, slfj4-server.patch
>
>
> During my expirements with OSGI I noticed all the problems when using
> commons-logging which use some classloader magic. I thinkwe should use
> jcl-over-slf4j to replace it to simplify stuff in the future.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
