Greg & Anthony,
Thankyou both for the quick responses. After getting your replies I started thinking, I am not actually running SP1, I have a beta of SP2 installed [id string Build 2600.xpsp.040216-1810(Service Pack 2, v.2082)] and that could be the cause of this problem, though I'm not sure why I am not having any trouble with 2.2.0a17. I guess it could be that DNS change Noel was talking about but if that's true then there could be quite a few people with problems when SP2 makes it to release. I suppose I am stuck with a17 for a while. I can't afford the three to four days worth of work it would take to reinstall windows and I'm not even going to think about trying to uninstall it. Again thanks for the help. I hope I can return the favor some time.
Greg
Greg Pfountz wrote:
I am running James 2.2.0 final release version on Win XP PRO SP1 without any problems. I did not do anything special. I have all recommended and critical patches installed - including the ipv6 patch.
My dns configuration from config.xml is: <dnsserver> <servers> <server>68.111.1.133</server> <server>68.111.1.132</server> </servers> <autodiscover>true</autodiscover> <authoritative>false</authoritative> </dnsserver> Don't have any suggestions to offer; thought it might be helpful if you knew someone with a similar configuration as yours is working fine. -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of bigbyte Sent: Sunday, July 04, 2004 5:02 PM To: [EMAIL PROTECTED] Subject: Re: Component named "dnsserver" failed to pass through the Initialization stage.
Ok, given what Noel has told me about this problem, listed below, I have tried all the suggested fixes to this point, none of which worked. The DNS handling apparently changed somewhere between a17 (which seems to work fine) and the final release (which doesn't appear to work at all, at least in XP)
I would like to know if anyone has gotten the newest RELEASE (2.2.0) to run on XP Home/Pro with SP1. Or am I all alone with this problem? Any guidance/assistance is most appreciated.
I run into this when I run "run.bat" so I am not entirely sure all the necessary files have been created for me to run the application as a service. I suppose it is possible that the batch file is somehow using a different config file than "config.xml" but the change in the error message from:
org.apache.excalibur.containerkit.lifecycle.LifecycleException: Component named "dnsserver" failed to pass through the Initialization stage. (Reason:
java.net.UnknownHostException: fec0:0:0:ffff::1%1: fec0:0:0:ffff::1%1).
to
org.apache.excalibur.containerkit.lifecycle.LifecycleException: Component named "dnsserver" failed to pass through the Initialization stage. (Reason:
java.lang.ExceptionInInitializerError).
would suggest otherwise.
TIA, Greg
Noel J. Bergman wrote:
Try specifying your DNS servers. That may or may not help. It appears that dnsjava is throwing a RuntimeException from a static block. Really bad idea. We don't even care about their default resolver, and are about to
replace it when they throw the exception.
Ah ... that looks familar. :-) See: http://www.mail-archive.com/[EMAIL PROTECTED]/msg03078.html.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg03078.html.
Does this mean the IPv6 prevents JAMES from working in 2.2.0 (release) even with the DNS server(s) specified and the autodiscover off?
You might need to explicitly provide the IP address rather than
"localhost".
I don't have the IPv6 installed, and never run James on a Microsoft platform. The problem is the "fec0:0:0:ffff::1%1" from MS-Windows.
It works in 2.2.0a17. What changed that makes it not work now?
Different DNS handling.
--- Noel
--------------------------------------------------------------------- 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]
