[jira] [Comment Edited] (JAMES-2141) Getting an error: Error creating bean with name 'mailprocessor': Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/apache/james/services/SpoolRepository$AcceptFilter

["Arpit Srivastava (JIRA)" <se...@james.apache.org>]

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

Arpit Srivastava edited comment on JAMES-2141 at 9/10/17 6:04 AM:
------------------------------------------------------------------

Hi Tellier 

Thank you for the suggestions and leads. Just to set some context, I'd like you to know that we are doing an upgrade of the existing functionalities from James 2.3.2 to James 3.0. I did some research in the james 3.0 documentation and I looked into the code and here are some queries I'd like you to guide me on:
* One of the custom mailets is using 'Spool Repository'. As per my understanding, is Spool Repository no longer available in James 3.0? If yes, might you suggest the alternative?
* When trying to start up James 3.0, the custom mailets throwing the error are - 'Retry' mailet, 'Notification' mailet and 'LegacyRouter' mailet. For the retry mailet - it is the 'SpoolRepository' issue. However, for 'Notification' mailet and 'LegacyRouter' mailet, the error thrown is - 'Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.cisco.mail.mailets.LegacyRouterMailet]: Constructor threw exception; nested exception is java.lang.NoSuchMethodError: org.apache.james.transport.mailets.RemoteDelivery: method <init>()V not found'. Now we have identified two reasons why this might be happening for James 3.0.
Suspected causes are – 
-INIT function needs to be defined in the two mailets’ java code for instantiation. (There isn't an INIT function in 'Legacy Router' mailet but the 'Notification' mailet does have an INIT function.
	@Override
	public void init() throws MessagingException {
		super.init();
	}
This leads us to our next possible cause-
-James 3.0, maybe,_ doesn’t support custom folders _for outbound which we are trying to custom define for these two mailets – i.e-‘Legacy’ and ‘Notification’ folder. If you look at the attachment - [^mailetcontainer.xml] - you'll see that we are defining- <outgoing> file:///apps/attach/var/mail/legacy/ </outgoing> and <outgoing> file:///apps/attach/var/mail/notification/ </outgoing> (I created these folders inside var folder). Is this true? Does James 3.0 doesn't allow custom folders? (I saw in the documentation that mail persistence is different). If yes, what might be done as an alternative?

Please let me know, if you need any more info from me.

Thanks and Regards
Arpit





> Getting an error: Error creating bean with name 'mailprocessor': Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/apache/james/services/SpoolRepository$AcceptFilter
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JAMES-2141
>                 URL: https://issues.apache.org/jira/browse/JAMES-2141
>             Project: James Server
>          Issue Type: Bug
>          Components: Mailet Contributions
>    Affects Versions: 3.0.0
>         Environment: Unix Host
>            Reporter: Arpit Srivastava
>             Fix For: 3.0.0
>
>         Attachments: ErrorLog6.txt, ErrorLog8.txt, mailetcontainer.xml
>
>
> Hi 
> I am facing this error: Error creating bean with name 'mailprocessor': Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/apache/james/services/SpoolRepository$AcceptFilter
> .
> Error log is attached.
> Please suggest on what is the issue.
> Thanks
> Arpit



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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