Nevermind my 2nd question below... After much head scratching and cursing at Microsoft
for not keeping things simple to understand,
;-) I now have James up and running on Windows2000... FWIW - The config.xml file is
also getting to be a bit complex and is easy to
make mistakes in when trying to upgrade James..
My observations made in points 1 and 3 below still remain... Someone might want to
clean these issues up???
Marc...
----- Original Message -----
From: "Marc Chamberlin" <[EMAIL PROTECTED]>
To: "james-user" <[EMAIL PROTECTED]>
Sent: Saturday, November 23, 2002 6:31 PM
Subject: james-2.1a1-cvs and Win2000
> Well OK, I may have tried to bite off more than I can chew here.... I am trying to
>upgrade my server from running on Win98 to
> Win2000 and I thought I would grab the latest version of James and try a port it to
>Win2000 as well. Not going well, and I admit I
> am unfamiliar with Win2000 also...
>
> 1. First let me report what I think may be an installation problem with the release
>candidate of James and will be interested in
> hearing feedback on this as well. I have a bunch of mailets and jar files to support
>them and I stashed these in my James/lib
> directory. But I had a heck of a time trying to figure out why James was crashing
>after I ported all my config.xml code over! I
> finally was able to track the problem down to what is apparently a misconfiguration
>??? of the places where some of the needed jar
> files were being placed. I found them in James/work/James-1038102691318/SAR-INF/lib
>and when I copied all these jar files over to
> the James/lib directory it made James a lot happier and it now "appears" to be
>coming up OK.
>
> This was a tough problem to track down as the stack walkbacks one gets are very
>misleading. SO I might suggest that before you
> release the next version of James this configuration ought to be cleaned up, or at
>least well documented! (and IMHO that is a
> horrible name for a directory that James is placing these jar file in!!! I refer to
>James-1038102691318.) ;-)
>
> 2. Even though James is appearing to come up OK now, it is still not functioning OK.
>I tried to telnet to port 4555 and the telnet
> session hangs and eventually times out without succeeding. When I bring up a mail
>client to try and receive mail, I get a popup
> dialog asking me to enter my user id and password. I am using SMTP authorization,
>but it is not accepting the user id or password
> even though I know them to be correct. Telneting to the POP3 port on 110, or the
>SMTP port on 25 also fails to make a connection.
Of
> note, I do use MySQL for a database for James, and I think it is working OK... I am
>able to connect to it from across my LAN using
> dbVisualizer and it responds as expected. Am I facing some Win2000 issues here that
>I don't understand? Any help would be much
> appreciated, and I will continue to poke around at it...
>
> 3. One last item of note... I noticed that when I close James down (BTW much much
>cleaner now!) I am getting a stack walkback in
the
> phoenix.log file which I include below....
>
>
> Marc Chamberlin
>
>
>
> INFO 2002-11-23 17:51:30.287 [Phoenix ] (): Logger started
> WARN 2002-11-23 17:51:30.347 [Phoenix ] (): Phoenix was not started by the daemon
>thus it will not be possible to restart the
JVM
> via the Management interface.
> INFO 2002-11-23 17:51:31.318 [Phoenix.] (): Installing Sar located at
> file:/F:/james/jakarta-james-2.1a1/james-2.1a1-cvs/apps/james.sar.
> WARN 2002-11-23 17:51:31.459 [Phoenix.] (): The file SAR-INF/config.xml can not
>be extracted from the Sar
> "file:/F:/james/jakarta-james-2.1a1/james-2.1a1-cvs/apps/james.sar" into directory
> F:\james\jakarta-james-2.1a1\james-2.1a1-cvs\apps\james\SAR-INF\config.xml because
>there is a file in the way.
> INFO 2002-11-23 17:51:31.569 [Phoenix.] (): No policy specified in server.xml,
>giving full permissions to ServerApplication.
> INFO 2002-11-23 17:51:31.929 [Phoenix.] (): Verifying that the name specified for
>Blocks and BlockListeners are valid.
> INFO 2002-11-23 17:51:31.939 [Phoenix.] (): Verifying that the name specified for
>Blocks and BlockListeners are unique.
> INFO 2002-11-23 17:51:31.939 [Phoenix.] (): Verifying that the specified
>Dependencies are valid according to BlockInfo.
> INFO 2002-11-23 17:51:31.939 [Phoenix.] (): Verifying that the dependencies of
>Blocks are valid with respect to other Blocks.
> INFO 2002-11-23 17:51:31.939 [Phoenix.] (): Verifying that there are no circular
>dependencies between Blocks.
> INFO 2002-11-23 17:51:31.939 [Phoenix.] (): Verifying that the specified Blocks
>have valid types.
> INFO 2002-11-23 17:51:31.999 [Phoenix.] (): Verifying that the specified
>BlockListeners have valid types.
> INFO 2002-11-23 17:51:32.090 [Phoenix.] (): 17 Blocks to process for phase
>"startup". Order of processing = [dnsserver,
> objectstorage, database-connections, mailstore, users-store, thread-manager,
>connections, sockets, scheduler, James, spoolmanager,
> remotemanager, pop3server, smtpserver, nntp-repository, nntpserver, fetchpop].
> INFO 2002-11-23 18:20:13.695 [Phoenix.] (): 17 Blocks to process for phase
>"shutdown". Order of processing = [spoolmanager,
> remotemanager, pop3server, smtpserver, fetchpop, James, dnsserver, nntpserver,
>nntp-repository, mailstore, users-store,
> objectstorage, connections, sockets, scheduler, database-connections,
>thread-manager].
> WARN 2002-11-23 18:20:14.346 [Phoenix.] (): Error deleting Work Directory
> "F:\james\jakarta-james-2.1a1\james-2.1a1-cvs\work\james-1038102691318". (Reason:
>File
>
>F:\james\jakarta-james-2.1a1\james-2.1a1-cvs\work\james-1038102691318\SAR-INF\lib\mm.mysql-2.0.14.jar
> unable to be deleted.)
> java.io.IOException: File
>F:\james\jakarta-james-2.1a1\james-2.1a1-cvs\work\james-1038102691318\SAR-INF\lib\mm.mysql-2.0.14.jar
> unable to be deleted.
> at org.apache.avalon.excalibur.io.FileUtil.forceDelete(FileUtil.java:638)
> at org.apache.avalon.excalibur.io.FileUtil.cleanDirectory(FileUtil.java:806)
> at org.apache.avalon.excalibur.io.FileUtil.deleteDirectory(FileUtil.java:762)
> at org.apache.avalon.excalibur.io.FileUtil.forceDelete(FileUtil.java:630)
> at org.apache.avalon.excalibur.io.FileUtil.cleanDirectory(FileUtil.java:806)
> at org.apache.avalon.excalibur.io.FileUtil.deleteDirectory(FileUtil.java:762)
> at org.apache.avalon.excalibur.io.FileUtil.forceDelete(FileUtil.java:630)
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>