[Javaemailserver-user] Version 2.8.2 not starting up - authentication problem

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi,

I've been using JES 1.6.1 for some time, but now that I have a new
laptop with Windows 7 and java 7, I decided to upgrade JES as well, to
2.8.2.

I've translated my mail.conf settings into the corresponding mail.xml
values and added my users in users.conf.

I've fixed mail.bat to point to the correct JRE and the correct
installation directory for JES.

Now, when I run mail.bat, I get the following exception:

2014-06-23 16:33:49,817 - [main] ConfigurationManager - There was an
error loading the schema

org.xml.sax.SAXParseException; schema_reference.4: Failed to read schema
document 'http://javaemailserver.sourceforge.ne

t/schema/mail_2_8.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element o

f the document is not <xsd:schema>.

        at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXPar
seException(Unknown Source)

        at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unknow
n Source)

        at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unk
nown Source)

        at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unk
nown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportS
chemaErr(Unknown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportS
chemaError(Unknown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSche
maDocument1(Unknown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSche
maDocument(Unknown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSc
hema(Unknown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(Un
known Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(U
nknown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(U
nknown Source)

        at
com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newS
chema(Unknown Source)

        at javax.xml.validation.SchemaFactory.newSchema(Unknown Source)

        at javax.xml.validation.SchemaFactory.newSchema(Unknown Source)

        at
com.ericdaugherty.mail.server.configuration.ConfigurationManager$1.run(C
onfigurationManager.java:1344)

        at
com.ericdaugherty.mail.server.configuration.ConfigurationManager$1.run(C
onfigurationManager.java:1340)

        at java.security.AccessController.doPrivileged(Native Method)

        at
com.ericdaugherty.mail.server.configuration.ConfigurationManager.getXMLS
chema(ConfigurationManager.java:1339)

        at
com.ericdaugherty.mail.server.configuration.ConfigurationManager.init(Co
nfigurationManager.java:334)

        at
com.ericdaugherty.mail.server.configuration.ConfigurationManager.initial
ize(ConfigurationManager.java:279)

        at com.ericdaugherty.mail.server.Mail.init(Mail.java:181)

        at com.ericdaugherty.mail.server.Mail.instantiate(Mail.java:343)

        at com.ericdaugherty.mail.server.Mail.main(Mail.java:472)

Caused by: java.io.IOException: Server returned HTTP response code: 401
for URL: http://javaemailserver.sourceforge.net/

schema/mail_2_8.xsd

        at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
Source)

        at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEnt
ity(Unknown Source)

        at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocV
ersion(Unknown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.pars
e(Unknown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.pars
e(Unknown Source)

        at
com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaDOMParser.parse(Un
known Source)

        ... 17 more

The application failed to initialize.

java.lang.RuntimeException: There was an error loading the schema

        at
com.ericdaugherty.mail.server.configuration.ConfigurationManager.getXMLS
chema(ConfigurationManager.java:1364)

        at
com.ericdaugherty.mail.server.configuration.ConfigurationManager.init(Co
nfigurationManager.java:334)

        at
com.ericdaugherty.mail.server.configuration.ConfigurationManager.initial
ize(ConfigurationManager.java:279)

        at com.ericdaugherty.mail.server.Mail.init(Mail.java:181)

        at com.ericdaugherty.mail.server.Mail.instantiate(Mail.java:343)

        at com.ericdaugherty.mail.server.Mail.main(Mail.java:472)

C:\Program Files\jes 2.8.2\bin>

It looks like JES is not able to get to the schema file on the Internet,
probably because we have a proxy server here that we have to go through.
I never had this problem with 1.6.1.

I'm guessing my options are:

1.       Go back to 1.6.1 (I'm just using it for testing an app that
sends out e-mail notifications, anyway)

2.       Find where the schema document location is specified and edit
it to file://some_path_on_my_laptop/mail_2_8.xsd
<file:///\\some_path_on_my_laptop\mail_2_8.xsd>  and copy the schema
file there.

3.       Configure 2.8.2 to authenticate at our proxy server.

Can anyone help me with either option 2 or option 3?

I'm thinking the simplest thing is just to go back to 1.6.1.

Thanks,

Rebeccah

______________________________________________________________________
The contents of this message, together with any attachments, are intended only for the use of the person(s) to which they are addressed and may contain confidential and/or privileged information. Further, any medical information herein is confidential and protected by law. It is unlawful for unauthorized persons to use, review, copy, disclose, or disseminate confidential medical information. If you are not the intended recipient, immediately advise the sender and delete this message and any attachments. Any distribution, or copying of this message, or any attachment, is prohibited.