You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by c0...@gmail.com on 2008/02/05 08:31:20 UTC
NoSuchMethodError: org.apache.mailet.MailetContext.getSMTPHostAddresses...
Hello,
I have a question regarding what could be causing the following
exception located in the mailet-*.log:
05/02/08 00:49:16 INFO James.Mailet: RemoteDelivery: Exception caught
in RemoteDelivery.run()
java.lang.NoSuchMethodError:
org.apache.mailet.MailetContext.getSMTPHostAddresses(Ljava/lang/String;)Ljava/util/Iterator;
at org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDelivery.java:442)
at org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:1111)
at java.lang.Thread.run(Thread.java:595)
We are only encountering this exception when running James 2.3.0 on
Solaris 10 using java 1.5.0_13. We are attempting to run it in a zone
if that makes any difference. We notice this message around 800 times
per second in the log files. We have run this same build successfully
on Mac OS X 10.4 and 10.5, as well as Ubuntu 7.10. I've confirmed
that the zone has full outbound DNS access, and external network
connectivity. Any thoughts, or additional information needed to help?
Thank you,
c0ns0ul
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: NoSuchMethodError: org.apache.mailet.MailetContext.getSMTPHostAddresses...
Posted by Stefano Bagnara <ap...@bago.org>.
c0ns0ul@gmail.com ha scritto:
> Stefano,
>
> I removed both jars and restarted. Once I sent a message to the
> system the problem surfaced again:
>
> java.lang.NoSuchMethodError:
> org.apache.mailet.MailetContext.getSMTPHostAddresses(Ljava/lang/String;)Ljava/util/Iterator;
> at org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDelivery.java:442)
> at org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:1111)
> at java.lang.Thread.run(Thread.java:595)
99% the problem is in the jars in your classpath.
Stop james, remove the work folder (it contains the wrong jars too),
make sure your james-2.3.0/apps/james/SAR-INF/lib/ and
james-2.3.0/apps/james/SAR-INF/classes are empty (unless you added some
custom mailet/resource).
what is james-2.3.0/bin/SAR-INF/ ? in bin you should not have a SAR-INF
folder at all.
> We've currently identified two patches that we will be applying:
> http://sunsolve.sun.com/search/document.do?assetkey=1-21-118668-15-1
> http://sunsolve.sun.com/search/document.do?assetkey=1-21-118669-15-1
I doubt the patches will fix this issue. But everything is possible.
> I've included a list of all of the jars located in our james
> installation and their locations here: http://pastie.caboo.se/148028
>
> I noticed that there are the following jars in
> james-2.3.0/bin/SAR-INF/lib/, mailet-2.3.jar, and mailet-api-2.3.jar.
> I removed both 3.0 and 2.3 version of the jars, restarted and
> attempted to send a message with the same outcome.
there should not be a james-2.3.0/bin/SAR-INF folder at all. There is
no such folder in our distribution.
you should have a james-2.3.0/apps/james.sar file, look inside this file
(this is a ZIP), it should contains the mailet-2.3.jar and
mailet-api-2.3.jar. James will uncompress them in the work folder at
startup and will include them in the classpath. They should be the only
mailet jars in your classpath.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: NoSuchMethodError: org.apache.mailet.MailetContext.getSMTPHostAddresses...
Posted by c0...@gmail.com.
Stefano,
I removed both jars and restarted. Once I sent a message to the
system the problem surfaced again:
java.lang.NoSuchMethodError:
org.apache.mailet.MailetContext.getSMTPHostAddresses(Ljava/lang/String;)Ljava/util/Iterator;
at org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDelivery.java:442)
at org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:1111)
at java.lang.Thread.run(Thread.java:595)
We've currently identified two patches that we will be applying:
http://sunsolve.sun.com/search/document.do?assetkey=1-21-118668-15-1
http://sunsolve.sun.com/search/document.do?assetkey=1-21-118669-15-1
I've included a list of all of the jars located in our james
installation and their locations here: http://pastie.caboo.se/148028
I noticed that there are the following jars in
james-2.3.0/bin/SAR-INF/lib/, mailet-2.3.jar, and mailet-api-2.3.jar.
I removed both 3.0 and 2.3 version of the jars, restarted and
attempted to send a message with the same outcome.
We will apply the sun patches and retest.
On Feb 5, 2008 8:37 AM, Stefano Bagnara <ap...@bago.org> wrote:
> Remove mailet-api-3.0.jar and mailet-3.0.jar and restart.
>
> I don't know why you have mailet jars in your
> /zfs/james-2.3.0/bin/SAR-INF/lib/. That lib folder is for custom
> dependencies. The mailet jars are already contained in the sar file and
> automatically extracted by james at startup.
>
> Stefano
>
> c0ns0ul@gmail.com ha scritto:
>
> > Thank you Bernd & Stefano for your prompt replies. I have deployed
> > this james instance into a new zone that has never had james in it
> > before. I have run the find command from the / of the zone, and it is
> > as follows:
> >
> > inmail1[/]# find / -name mailet*.jar -ls
> > 1358 7 -rw-r--r-- 1 root root 6609 Feb 5 00:48
> > /zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-api-3.0.jar
> > 1355 11 -rw-r--r-- 1 root root 10299 Feb 5 00:48
> > /zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-2.3.jar
> > 1357 7 -rw-r--r-- 1 root root 6646 Feb 5 00:48
> > /zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-api-2.3.jar
> > 1356 13 -rw-r--r-- 1 root root 12335 Feb 5 00:48
> > /zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-3.0.jar
> > 390 8 -rw-r--r-- 1 501 501 6675 Jan 3 22:28
> > /zfs/james-2.3.0/bin/SAR-INF/lib/mailet-api-2.3.jar
> > 388 11 -rw-r--r-- 1 501 501 10475 Jan 3 22:28
> > /zfs/james-2.3.0/bin/SAR-INF/lib/mailet-2.3.jar
> > 391 7 -rw-r--r-- 1 501 501 6609 Jan 3 22:28
> > /zfs/james-2.3.0/bin/SAR-INF/lib/mailet-api-3.0.jar
> > 389 13 -rw-r--r-- 1 501 501 12335 Jan 3 22:28
> > /zfs/james-2.3.0/bin/SAR-INF/lib/mailet-3.0.jar
> >
> > We're using IPv4:
> > inmail1[/]# ifconfig -a
> > lo0:3: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> > mtu 8232 index 1
> > inet 127.0.0.1 netmask ff000000
> > bge0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
> > inet 192.168.18.222 netmask ffffff00 broadcast 192.168.18.255
> >
> > I will begin looking at the possibility that this could be caused by a
> > bug in the JVM shipped with Solaris 10. Is there anything else that I
> > could check from the James perspective?
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: NoSuchMethodError: org.apache.mailet.MailetContext.getSMTPHostAddresses...
Posted by Stefano Bagnara <ap...@bago.org>.
Remove mailet-api-3.0.jar and mailet-3.0.jar and restart.
I don't know why you have mailet jars in your
/zfs/james-2.3.0/bin/SAR-INF/lib/. That lib folder is for custom
dependencies. The mailet jars are already contained in the sar file and
automatically extracted by james at startup.
Stefano
c0ns0ul@gmail.com ha scritto:
> Thank you Bernd & Stefano for your prompt replies. I have deployed
> this james instance into a new zone that has never had james in it
> before. I have run the find command from the / of the zone, and it is
> as follows:
>
> inmail1[/]# find / -name mailet*.jar -ls
> 1358 7 -rw-r--r-- 1 root root 6609 Feb 5 00:48
> /zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-api-3.0.jar
> 1355 11 -rw-r--r-- 1 root root 10299 Feb 5 00:48
> /zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-2.3.jar
> 1357 7 -rw-r--r-- 1 root root 6646 Feb 5 00:48
> /zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-api-2.3.jar
> 1356 13 -rw-r--r-- 1 root root 12335 Feb 5 00:48
> /zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-3.0.jar
> 390 8 -rw-r--r-- 1 501 501 6675 Jan 3 22:28
> /zfs/james-2.3.0/bin/SAR-INF/lib/mailet-api-2.3.jar
> 388 11 -rw-r--r-- 1 501 501 10475 Jan 3 22:28
> /zfs/james-2.3.0/bin/SAR-INF/lib/mailet-2.3.jar
> 391 7 -rw-r--r-- 1 501 501 6609 Jan 3 22:28
> /zfs/james-2.3.0/bin/SAR-INF/lib/mailet-api-3.0.jar
> 389 13 -rw-r--r-- 1 501 501 12335 Jan 3 22:28
> /zfs/james-2.3.0/bin/SAR-INF/lib/mailet-3.0.jar
>
> We're using IPv4:
> inmail1[/]# ifconfig -a
> lo0:3: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
> mtu 8232 index 1
> inet 127.0.0.1 netmask ff000000
> bge0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
> inet 192.168.18.222 netmask ffffff00 broadcast 192.168.18.255
>
> I will begin looking at the possibility that this could be caused by a
> bug in the JVM shipped with Solaris 10. Is there anything else that I
> could check from the James perspective?
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: NoSuchMethodError: org.apache.mailet.MailetContext.getSMTPHostAddresses...
Posted by c0...@gmail.com.
Thank you Bernd & Stefano for your prompt replies. I have deployed
this james instance into a new zone that has never had james in it
before. I have run the find command from the / of the zone, and it is
as follows:
inmail1[/]# find / -name mailet*.jar -ls
1358 7 -rw-r--r-- 1 root root 6609 Feb 5 00:48
/zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-api-3.0.jar
1355 11 -rw-r--r-- 1 root root 10299 Feb 5 00:48
/zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-2.3.jar
1357 7 -rw-r--r-- 1 root root 6646 Feb 5 00:48
/zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-api-2.3.jar
1356 13 -rw-r--r-- 1 root root 12335 Feb 5 00:48
/zfs/james-2.3.0/work/ourProduct-james-1202194121076/SAR-INF/lib/mailet-3.0.jar
390 8 -rw-r--r-- 1 501 501 6675 Jan 3 22:28
/zfs/james-2.3.0/bin/SAR-INF/lib/mailet-api-2.3.jar
388 11 -rw-r--r-- 1 501 501 10475 Jan 3 22:28
/zfs/james-2.3.0/bin/SAR-INF/lib/mailet-2.3.jar
391 7 -rw-r--r-- 1 501 501 6609 Jan 3 22:28
/zfs/james-2.3.0/bin/SAR-INF/lib/mailet-api-3.0.jar
389 13 -rw-r--r-- 1 501 501 12335 Jan 3 22:28
/zfs/james-2.3.0/bin/SAR-INF/lib/mailet-3.0.jar
We're using IPv4:
inmail1[/]# ifconfig -a
lo0:3: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.18.222 netmask ffffff00 broadcast 192.168.18.255
I will begin looking at the possibility that this could be caused by a
bug in the JVM shipped with Solaris 10. Is there anything else that I
could check from the James perspective?
Thank you,
c0ns0ul
On Feb 5, 2008 4:31 AM, Stefano Bagnara <ap...@bago.org> wrote:
> Bernd Fondermann ha scritto:
> > Another hint: Please double check that your classpath is cleared from
> > left-over jars of any kind.
> > Maybe try to re-deploy in a clean environment.
> >
> > Errors like this often occur on binding errors (wrong/outdated jar on
> > the classpath).
> >
> > Bernd
>
> you have been faster! ;-)
>
> Stefano
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: NoSuchMethodError: org.apache.mailet.MailetContext.getSMTPHostAddresses...
Posted by Stefano Bagnara <ap...@bago.org>.
Bernd Fondermann ha scritto:
> Another hint: Please double check that your classpath is cleared from
> left-over jars of any kind.
> Maybe try to re-deploy in a clean environment.
>
> Errors like this often occur on binding errors (wrong/outdated jar on
> the classpath).
>
> Bernd
you have been faster! ;-)
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: NoSuchMethodError: org.apache.mailet.MailetContext.getSMTPHostAddresses...
Posted by Bernd Fondermann <be...@googlemail.com>.
On Feb 5, 2008 8:31 AM, <c0...@gmail.com> wrote:
> Hello,
>
> I have a question regarding what could be causing the following
> exception located in the mailet-*.log:
>
> 05/02/08 00:49:16 INFO James.Mailet: RemoteDelivery: Exception caught
> in RemoteDelivery.run()
> java.lang.NoSuchMethodError:
> org.apache.mailet.MailetContext.getSMTPHostAddresses(Ljava/lang/String;)Ljava/util/Iterator;
> at org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDelivery.java:442)
> at org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:1111)
> at java.lang.Thread.run(Thread.java:595)
>
>
> We are only encountering this exception when running James 2.3.0 on
> Solaris 10 using java 1.5.0_13. We are attempting to run it in a zone
> if that makes any difference. We notice this message around 800 times
> per second in the log files. We have run this same build successfully
> on Mac OS X 10.4 and 10.5, as well as Ubuntu 7.10. I've confirmed
> that the zone has full outbound DNS access, and external network
> connectivity. Any thoughts, or additional information needed to help?
Another hint: Please double check that your classpath is cleared from
left-over jars of any kind.
Maybe try to re-deploy in a clean environment.
Errors like this often occur on binding errors (wrong/outdated jar on
the classpath).
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: NoSuchMethodError: org.apache.mailet.MailetContext.getSMTPHostAddresses...
Posted by Bernd Fondermann <be...@googlemail.com>.
On Feb 5, 2008 8:31 AM, <c0...@gmail.com> wrote:
> Hello,
>
> I have a question regarding what could be causing the following
> exception located in the mailet-*.log:
>
> 05/02/08 00:49:16 INFO James.Mailet: RemoteDelivery: Exception caught
> in RemoteDelivery.run()
> java.lang.NoSuchMethodError:
> org.apache.mailet.MailetContext.getSMTPHostAddresses(Ljava/lang/String;)Ljava/util/Iterator;
> at org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDelivery.java:442)
> at org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:1111)
> at java.lang.Thread.run(Thread.java:595)
>
>
> We are only encountering this exception when running James 2.3.0 on
> Solaris 10 using java 1.5.0_13. We are attempting to run it in a zone
> if that makes any difference. We notice this message around 800 times
> per second in the log files. We have run this same build successfully
> on Mac OS X 10.4 and 10.5, as well as Ubuntu 7.10. I've confirmed
> that the zone has full outbound DNS access, and external network
> connectivity. Any thoughts, or additional information needed to help?
What about IPv6 vs. IPv4 usage?
As you nailed it down to that particular platform and setup, have you
already check for JVM-specific bugreports at sun?
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: NoSuchMethodError: org.apache.mailet.MailetContext.getSMTPHostAddresses...
Posted by Stefano Bagnara <ap...@bago.org>.
IMHO a NoSuchMethodError on a james class is not related to OS or JVM,
but to is something related to the mailet versions.
The method getSMTPHostAddresses has been introduced to mailet in james
2.2.0. This means the mailet.jar included with previous versions (e.g:
james 2.1) did not include this method.
Please check your system and make sure you don't have any outdated
mailet*.jar in your classpath.
A first check:
find / -name mailet\*\.jar
Stefano
c0ns0ul@gmail.com ha scritto:
> Hello,
>
> I have a question regarding what could be causing the following
> exception located in the mailet-*.log:
>
> 05/02/08 00:49:16 INFO James.Mailet: RemoteDelivery: Exception caught
> in RemoteDelivery.run()
> java.lang.NoSuchMethodError:
> org.apache.mailet.MailetContext.getSMTPHostAddresses(Ljava/lang/String;)Ljava/util/Iterator;
> at org.apache.james.transport.mailets.RemoteDelivery.deliver(RemoteDelivery.java:442)
> at org.apache.james.transport.mailets.RemoteDelivery.run(RemoteDelivery.java:1111)
> at java.lang.Thread.run(Thread.java:595)
>
>
> We are only encountering this exception when running James 2.3.0 on
> Solaris 10 using java 1.5.0_13. We are attempting to run it in a zone
> if that makes any difference. We notice this message around 800 times
> per second in the log files. We have run this same build successfully
> on Mac OS X 10.4 and 10.5, as well as Ubuntu 7.10. I've confirmed
> that the zone has full outbound DNS access, and external network
> connectivity. Any thoughts, or additional information needed to help?
>
> Thank you,
>
> c0ns0ul
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org