Problem with SvnKit - 1.77

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem with SvnKit - 1.77

Fabrizio Giudici
Hello.

I couldn't follow the discussion about a couple of SVN-related Hudson bugs for some weeks, but I saw that they were closed thanks to the use of SvnKit.

But with 1.77 now all my builds fail with:

At revision 420
FATAL: Provider org.apache.xalan.transformer.TransformerImpl could not be instantiated: java.lang.NullPointerException
javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.transformer.TransformerImpl could not be instantiated: java.lang.NullPointerException
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:109)
at hudson.scm.SubversionSCM.createTransformerHandler(SubversionSCM.java:189)
at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:143)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:236)
at hudson.model.AbstractProject.checkout(AbstractProject.java:266)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:136)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:103)
at hudson.model.Run.run(Run.java:533)
at hudson.model.Build.run(Build.java:203)
at hudson.model.Executor.run(Executor.java:61)


Could it be some problem with my Tomcat configuration? Do other experience the same? Thanks.


-- 
Fabrizio Giudici, Ph.D. - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
[hidden email] - mobile: +39 348.150.6941


Reply | Threaded
Open this post in threaded view
|

Re: Problem with SvnKit - 1.77

Kohsuke Kawaguchi-2

This is actually a known issue in Tomcat, and so Hudson has code to work
around this problem by overriding the default transformer setting.

>         // Tomcat breaks XSLT with JDK 5.0 and onward. Check if that's the case, and if so,
>         // try to correct it
>         try {
>             TransformerFactory.newInstance();
>             // if this works we are all happy
>         } catch (TransformerFactoryConfigurationError x) {
>             // no it didn't.
>             Logger logger = Logger.getLogger(WebAppMain.class.getName());
>
>             logger.log(Level.WARNING, "XSLT not configured correctly. Hudson will try to fix this. See http://issues.apache.org/bugzilla/show_bug.cgi?id=40895 for more details",x);
>             System.setProperty(TransformerFactory.class.getName(),"com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl");
>             try {
>                 TransformerFactory.newInstance();
>                 logger.info("XSLT is set to the JAXP RI in JRE");
>             } catch(TransformerFactoryConfigurationError y) {
>                 logger.log(Level.SEVERE, "Failed to correct the problem.");
>             }
>         }
Can you check your log to see if you saw one of those messages logged
here? Also see http://issues.apache.org/bugzilla/show_bug.cgi?id=40895


Fabrizio Giudici wrote:

> Hello.
>
> I couldn't follow the discussion about a couple of SVN-related Hudson  
> bugs for some weeks, but I saw that they were closed thanks to the  
> use of SvnKit.
>
> But with 1.77 now all my builds fail with:
>
> Updating https://mistral.dev.java.net/svn/mistral/trunk/src
> At revision 420
> FATAL: Provider org.apache.xalan.transformer.TransformerImpl could  
> not be instantiated: java.lang.NullPointerException
> javax.xml.transform.TransformerFactoryConfigurationError: Provider  
> org.apache.xalan.transformer.TransformerImpl could not be  
> instantiated: java.lang.NullPointerException
> at javax.xml.transform.TransformerFactory.newInstance
> (TransformerFactory.java:109)
> at hudson.scm.SubversionSCM.createTransformerHandler
> (SubversionSCM.java:189)
> at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:143)
> at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:236)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:266)
> at hudson.model.AbstractBuild$AbstractRunner.checkout
> (AbstractBuild.java:136)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:
> 103)
> at hudson.model.Run.run(Run.java:533)
> at hudson.model.Build.run(Build.java:203)
> at hudson.model.Executor.run(Executor.java:61)
>
>
> Could it be some problem with my Tomcat configuration? Do other  
> experience the same? Thanks.
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Problem with SvnKit - 1.77

Fabrizio Giudici

On Jan 31, 2007, at 20:19 , Kohsuke Kawaguchi wrote:

>
> This is actually a known issue in Tomcat, and so Hudson has code to  
> work around this problem by overriding the default transformer  
> setting.
>
>>         // Tomcat breaks XSLT with JDK 5.0 and onward. Check if  
>> that's the case, and if so,
>>         // try to correct it
>>         try {
>>             TransformerFactory.newInstance();
>>             // if this works we are all happy
>>         } catch (TransformerFactoryConfigurationError x) {
>>             // no it didn't.
>>             Logger logger = Logger.getLogger
>> (WebAppMain.class.getName());
>>             logger.log(Level.WARNING, "XSLT not configured  
>> correctly. Hudson will try to fix this. See http://
>> issues.apache.org/bugzilla/show_bug.cgi?id=40895 for more  
>> details",x);
>>             System.setProperty(TransformerFactory.class.getName
>> (),"com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryIm
>> pl");
>>             try {
>>                 TransformerFactory.newInstance();
>>                 logger.info("XSLT is set to the JAXP RI in JRE");
>>             } catch(TransformerFactoryConfigurationError y) {
>>                 logger.log(Level.SEVERE, "Failed to correct the  
>> problem.");
>>             }
>>         }
>
> Can you check your log to see if you saw one of those messages  
> logged here? Also see http://issues.apache.org/bugzilla/ 
> show_bug.cgi?id=40895

Well, in the meantime I say that I've upgraded my Tomcat from 5.5.12  
to 5.5.20 and cleaned up the installation. The problem is still here  
anyway.
I don't see any of those log lines, and I have a INFO level of  
logging (in facts I see stuff such as

Jan 31, 2007 9:26:10 PM hudson.triggers.SCMTrigger$Runner runPolling
INFO: Polling SCM changes of Pleiades




>
>
> Fabrizio Giudici wrote:
>> Hello.
>> I couldn't follow the discussion about a couple of SVN-related  
>> Hudson  bugs for some weeks, but I saw that they were closed  
>> thanks to the  use of SvnKit.
>> But with 1.77 now all my builds fail with:
>> Updating https://mistral.dev.java.net/svn/mistral/trunk/src
>> At revision 420
>> FATAL: Provider org.apache.xalan.transformer.TransformerImpl  
>> could  not be instantiated: java.lang.NullPointerException
>> javax.xml.transform.TransformerFactoryConfigurationError:  
>> Provider  org.apache.xalan.transformer.TransformerImpl could not  
>> be  instantiated: java.lang.NullPointerException
>> at javax.xml.transform.TransformerFactory.newInstance  
>> (TransformerFactory.java:109)
>> at hudson.scm.SubversionSCM.createTransformerHandler  
>> (SubversionSCM.java:189)
>> at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:143)
>> at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:236)
>> at hudson.model.AbstractProject.checkout(AbstractProject.java:266)
>> at hudson.model.AbstractBuild$AbstractRunner.checkout  
>> (AbstractBuild.java:136)
>> at hudson.model.AbstractBuild$AbstractRunner.run
>> (AbstractBuild.java: 103)
>> at hudson.model.Run.run(Run.java:533)
>> at hudson.model.Build.run(Build.java:203)
>> at hudson.model.Executor.run(Executor.java:61)
>> Could it be some problem with my Tomcat configuration? Do other  
>> experience the same? Thanks.
>
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]

--
Fabrizio Giudici, Ph.D. - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
[hidden email] - mobile: +39 348.150.6941


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Problem with SvnKit - 1.77

Kohsuke Kawaguchi-2
Fabrizio Giudici wrote:

> On Jan 31, 2007, at 20:19 , Kohsuke Kawaguchi wrote:
>
>>
>> This is actually a known issue in Tomcat, and so Hudson has code to  
>> work around this problem by overriding the default transformer  
>> setting.
>>
>>>         // Tomcat breaks XSLT with JDK 5.0 and onward. Check if  
>>> that's the case, and if so,
>>>         // try to correct it
>>>         try {
>>>             TransformerFactory.newInstance();
>>>             // if this works we are all happy
>>>         } catch (TransformerFactoryConfigurationError x) {
>>>             // no it didn't.
>>>             Logger logger = Logger.getLogger
>>> (WebAppMain.class.getName());
>>>             logger.log(Level.WARNING, "XSLT not configured  
>>> correctly. Hudson will try to fix this. See http://
>>> issues.apache.org/bugzilla/show_bug.cgi?id=40895 for more  
>>> details",x);
>>>             System.setProperty(TransformerFactory.class.getName
>>> (),"com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryIm
>>> pl");
>>>             try {
>>>                 TransformerFactory.newInstance();
>>>                 logger.info("XSLT is set to the JAXP RI in JRE");
>>>             } catch(TransformerFactoryConfigurationError y) {
>>>                 logger.log(Level.SEVERE, "Failed to correct the  
>>> problem.");
>>>             }
>>>         }
>>
>> Can you check your log to see if you saw one of those messages  
>> logged here? Also see http://issues.apache.org/bugzilla/ 
>> show_bug.cgi?id=40895
>
> Well, in the meantime I say that I've upgraded my Tomcat from 5.5.12  
> to 5.5.20 and cleaned up the installation. The problem is still here  
> anyway.
> I don't see any of those log lines, and I have a INFO level of  
> logging (in facts I see stuff such as
>
> Jan 31, 2007 9:26:10 PM hudson.triggers.SCMTrigger$Runner runPolling
> INFO: Polling SCM changes of Pleiades
Hmm. Maybe I should start bundling a XSLT implementation that's known to
work...

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Problem with SvnKit - 1.77

Fabrizio Giudici
>>>
>>> Can you check your log to see if you saw one of those messages  
>>> logged here? Also see http://issues.apache.org/bugzilla/ 
>>> show_bug.cgi?id=40895
>> Well, in the meantime I say that I've upgraded my Tomcat from  
>> 5.5.12  to 5.5.20 and cleaned up the installation. The problem is  
>> still here  anyway.
>> I don't see any of those log lines, and I have a INFO level of  
>> logging (in facts I see stuff such as
>> Jan 31, 2007 9:26:10 PM hudson.triggers.SCMTrigger$Runner runPolling
>> INFO: Polling SCM changes of Pleiades
>
> Hmm. Maybe I should start bundling a XSLT implementation that's  
> known to work...

Well, tonight it worked. I don't know why, as I'm pretty sure of the  
error yesterday, and I didn't anything to fix it.
In the meantime I installed another webapp, which has some scripts  
that could have changed some configuration in tomcat.
Indeed I'm not sure - there's a chance that I did something wrong  
yesterday.

In any case, now it works.

--
Fabrizio Giudici, Ph.D. - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
[hidden email] - mobile: +39 348.150.6941


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Problem with SvnKit - 1.77

Kohsuke Kawaguchi-2
Fabrizio Giudici wrote:
> Well, tonight it worked. I don't know why, as I'm pretty sure of the  
> error yesterday, and I didn't anything to fix it.
> In the meantime I installed another webapp, which has some scripts  
> that could have changed some configuration in tomcat.
> Indeed I'm not sure - there's a chance that I did something wrong  
> yesterday.
>
> In any case, now it works.

You know, machines have feelings too ;-)

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment