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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to