I created a different folder var/mail/outgoing2
and modified one of the mailets to use that folder
<outgoing>file://var/mail/outgoing2/ </outgoing>
Since that change I have not been able restart James.
I reverted back the change and James will still not start
I had been running James as a service. I am now trying to running
it from the console. The only message printed on the console is
James 2.2.0 I don't see the usual output re: SMTP,NNTP etc.
All the logs re: mailets, spoolmanager etc. don't show any errors
I also don't see any issues in phoenix.log
At one point I did get the following error
James 2.2.0
JVM exiting abnormally. Shutting down Phoenix.
org.apache.excalibur.containerkit.lifecycle.LifecycleException: Component named
"spoolmanager" failed to pass through the Initialization stage. (Reason: java.la
ng.OutOfMemoryError).
at org.apache.excalibur.containerkit.lifecycle.LifecycleHelper.fail(Life
cycleHelper.java:289)
at org.apache.excalibur.containerkit.lifecycle.LifecycleHelper.startup(L
ifecycleHelper.java:159)
at org.apache.avalon.phoenix.components.application.DefaultApplication.s
tartup(DefaultApplication.java:480)
at org.apache.avalon.phoenix.components.application.DefaultApplication.d
oRunPhase(DefaultApplication.java:428)
at org.apache.avalon.phoenix.components.application.DefaultApplication.r
unPhase(DefaultApplication.java:364)
at org.apache.avalon.phoenix.components.application.DefaultApplication.s
tart(DefaultApplication.java:138)
at org.apache.avalon.framework.container.ContainerUtil.start(ContainerUt
il.java:251)
at org.apache.avalon.phoenix.components.kernel.DefaultKernel.startup(Def
aultKernel.java:178)
at org.apache.avalon.phoenix.components.kernel.DefaultKernel.addApplicat
ion(DefaultKernel.java:254)
at org.apache.avalon.phoenix.components.deployer.DefaultDeployer.deploy(
DefaultDeployer.java:353)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.deployF
ile(DefaultEmbeddor.java:498)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.deployF
ile(DefaultEmbeddor.java:491)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.deployF
iles(DefaultEmbeddor.java:476)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.deployD
efaultApplications(DefaultEmbeddor.java:466)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.execute
(DefaultEmbeddor.java:224)
at org.apache.avalon.phoenix.frontends.CLIMain.run(CLIMain.java:158)
at org.apache.avalon.phoenix.frontends.CLIMain.execute(CLIMain.java:144)
at org.apache.avalon.phoenix.frontends.CLIMain.main(CLIMain.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.avalon.phoenix.launcher.Main.startup(Main.java:94)
at org.apache.avalon.phoenix.launcher.Main.main(Main.java:46)
Caused by: java.lang.OutOfMemoryError
There was an uncaught exception:
Quoting Stefano Bagnara <[EMAIL PROTECTED]>:
> Shal Jain wrote:
> > No I haven't
> > The following
> > <outgoing> db://maildb/spool/outgoing </outgoing>
> > is the same in both cases. I didn't think that would make a difference
> > I'd appreciate an explanation
>
>
> Here is how a RemoteDelivery works:
>
> When James start RemoteDelivery create a number of delivery threads.
> The threads simply wait for new messages appearing in its outgoing spool
> and send them. The delivery threads are specific to the RemoteDelivery
> that create them.
>
> When the spoolmanager got a new message for the remote delivery it call
> the service() method of the RemoteDelivery.
>
> RemoteDelivery will eventually split the mail in multiple parts (if no
> gateway is specified and the message recipients are from different
> domains) and store each copy in the outgoing spool.
>
> So you understand that the bridge between a RemoteDelivery mailet and
> its delivery threads IS the *outgoing spool*. If you share the outgoing
> then you don't know what delivery thread will send what mail.
>
> So add an
> <outgoing> db://maildb/spool/outgoing2 </outgoing>
> To one of the remote delivery mailets.
>
> Stefano
>
> PS: we should add a comment in the default configuration to remember
> this to new users.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
