logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51849] LogManager and ipv6 address
Date Wed, 21 Sep 2011 06:44:47 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51849

--- Comment #8 from Varun Balakrishnan <cbvarun@yahoo.com> 2011-09-21 06:44:47 UTC ---
(In reply to comment #7)
> (In reply to comment #6)
> > FYI, here is the implementation of the method in Xerces 2.11.0:
> > 
> >     private static String expandSystemIdStrictOff(String systemId, String
> > baseSystemId)
> >         throws URI.MalformedURIException {
> > 
> >         URI systemURI = new URI(systemId, true);
> >         // If it's already an absolute one, return it
> >         if (systemURI.isAbsoluteURI()) {
> >             if (systemURI.getScheme().length() > 1) {
> >                 return systemId;
> >             }
> >             /** 
> >              * If the scheme's length is only one character,
> >              * it's likely that this was intended as a file
> >              * path. Fixing this up in expandSystemId to
> >              * maintain backwards compatibility.
> >              */
> >             throw new URI.MalformedURIException();
> >         }
> > 
> >         // If there isn't a base URI, use the working directory
> >         URI baseURI = null;
> >         if (baseSystemId == null || baseSystemId.length() == 0) {
> >             baseURI = getUserDir();
> >         }
> >         else {
> >             baseURI = new URI(baseSystemId, true);
> >             if (!baseURI.isAbsoluteURI()) {
> >                 // assume "base" is also a relative uri
> >                 baseURI.absolutize(getUserDir());
> >             }
> >         }
> > 
> >         // absolutize the system identifier using the base URI
> >         systemURI.absolutize(baseURI);
> > 
> >         // return the string rep of the new uri (an absolute one)
> >         return systemURI.toString();
> > 
> >         // if any exception is thrown, it'll get thrown to the caller.
> > 
> >     } // expandSystemIdStrictOff(String,String):String
> 
> 
> 
> 1) I downloaded Xerces 2.11.0 and added to my application classpath
> 2) What I observed was, neither the log4j initialization nor my application
> started with log4j.configuration="https://[fe80::92]:443/ucsm/log4j.xml"
> 3) Everything was fine when log4j.configuration="https://<ipv4
> address>:80/ucsm/log4j.xml"
> 
> I will debug more and let you know once I have something concrete. Thanks for
> your support.


The URL (ipv6 address part) I was trying to connect was no longer existing when
I tried with Xerces 2.11.0. I think something is working now. I do not get the
parser error for the URL but there is something wrong with the client side
logging. I will explore more.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message