Error building CXF from source (trunk checkout) [64 Bit Vista]

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

Error building CXF from source (trunk checkout) [64 Bit Vista]

Jim Talbut
Hi,

When I try to build CXF from source I get this:
[INFO] Preparing pmd:check
[INFO] [pmd:pmd {execution: pmd}]
[INFO] [pmd:check {execution: validate}]
[INFO]
[INFO] [cxf-xml2fastinfoset:xml2fastinfoset {execution: xml2fastinfoset}]
[INFO] [cxf-xjc:xsdtojava {execution: generate-sources}]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The filename, directory name, or volume label syntax is incorrect

[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The filename,
directory name, or volume label syntax is incorrect
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
         at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
         at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
         at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: The filename,
directory name, or volume label syntax is incorrect
         at
org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJavaMojo.java:229)
         at
org.apache.cxf.maven_plugin.XSDToJavaMojo.execute(XSDToJavaMojo.java:38)
         at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
         at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
         ... 17 more
Caused by: java.io.IOException: The filename, directory name, or volume
label syntax is incorrect
         at java.io.WinNTFileSystem.createFileExclusively(Native Method)
         at java.io.File.createNewFile(File.java:883)
         at
org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJavaMojo.java:220)
         ... 20 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 50 seconds
[INFO] Finished at: Thu Jun 24 20:59:07 BST 2010
[INFO] Final Memory: 120M/502M
[INFO]
------------------------------------------------------------------------

Useful version details:
C:\Work\cxf>mvn -v
Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
Java version: 1.6.0_14
Java home: C:\Program Files\Java\jdk1.6.0_14\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
C:\Work\cxf>echo %MAVEN_OPTS%
-Xms512m -Xmx512m -XX:PermSize=512m -XX:MaxPermSize=512m

Noone else seems to be hitting this, so I'm guess it's something stupid
in my setup, can anyone point me in the right direction?

Thanks

Jim
Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Glen Mazza
Administrator
What are you entering at the command line to build CXF from source?  Build instructions are here: http://cxf.apache.org/building.html .

Glen

Jim Talbut wrote
Hi,

When I try to build CXF from source I get this:
[INFO] Preparing pmd:check
[INFO] [pmd:pmd {execution: pmd}]
[INFO] [pmd:check {execution: validate}]
[INFO]
[INFO] [cxf-xml2fastinfoset:xml2fastinfoset {execution: xml2fastinfoset}]
[INFO] [cxf-xjc:xsdtojava {execution: generate-sources}]
[INFO]
Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Daniel Kulp
Administrator
In reply to this post by Jim Talbut

Probably my fault.   Most of us aren't using Windows anymore which would
explain why it affected you and not us.  I just committed a fix and deployed a
new snapshot.    Thus, you should be able to build now if you run with the -U
-cpu to update the snapshot.

Dan


On Thursday 24 June 2010 4:06:17 pm Jim Talbut wrote:

> Hi,
>
> When I try to build CXF from source I get this:
> [INFO] Preparing pmd:check
> [INFO] [pmd:pmd {execution: pmd}]
> [INFO] [pmd:check {execution: validate}]
> [INFO]
> [INFO] [cxf-xml2fastinfoset:xml2fastinfoset {execution: xml2fastinfoset}]
> [INFO] [cxf-xjc:xsdtojava {execution: generate-sources}]
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The filename, directory name, or volume label syntax is incorrect
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The filename,
> directory name, or volume label syntax is incorrect
>          at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif
> ecycleExecutor.java:719) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycl
> e(DefaultLifecycleExecutor.java:556) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife
> cycleExecutor.java:535) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai
> lures(DefaultLifecycleExecutor.java:387) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Def
> aultLifecycleExecutor.java:348) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl
> eExecutor.java:180) at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>          at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>          at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
> 9) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
> l.java:25) at java.lang.reflect.Method.invoke(Method.java:597)
>          at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>          at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>          at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>          at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: The filename,
> directory name, or volume label syntax is incorrect
>          at
> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJava
> Mojo.java:229) at
> org.apache.cxf.maven_plugin.XSDToJavaMojo.execute(XSDToJavaMojo.java:38)
>          at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag
> er.java:490) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif
> ecycleExecutor.java:694) ... 17 more
> Caused by: java.io.IOException: The filename, directory name, or volume
> label syntax is incorrect
>          at java.io.WinNTFileSystem.createFileExclusively(Native Method)
>          at java.io.File.createNewFile(File.java:883)
>          at
> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJava
> Mojo.java:220) ... 20 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 50 seconds
> [INFO] Finished at: Thu Jun 24 20:59:07 BST 2010
> [INFO] Final Memory: 120M/502M
> [INFO]
> ------------------------------------------------------------------------
>
> Useful version details:
> C:\Work\cxf>mvn -v
> Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
> Java version: 1.6.0_14
> Java home: C:\Program Files\Java\jdk1.6.0_14\jre
> Default locale: en_GB, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> C:\Work\cxf>echo %MAVEN_OPTS%
> -Xms512m -Xmx512m -XX:PermSize=512m -XX:MaxPermSize=512m
>
> Noone else seems to be hitting this, so I'm guess it's something stupid
> in my setup, can anyone point me in the right direction?
>
> Thanks
>
> Jim

--
Daniel Kulp
[hidden email]
http://dankulp.com/blog
Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Jim Talbut
Ah, thanks, that's much better.
But a full "mvn clean install" is consistently failing on this test:
<testcase time="2.054"
classname="org.apache.cxf.systest.dispatch.DispatchClientServerTest"
name="testTimeout">
<failure message="java.net.SocketTimeoutException"
type="java.lang.AssertionError">java.lang.AssertionError:
java.net.SocketTimeoutException
     at org.junit.Assert.fail(Assert.java:91)
     at org.junit.Assert.assertTrue(Assert.java:43)
     at
org.apache.cxf.systest.dispatch.DispatchClientServerTest.testTimeout(DispatchClientServerTest.java:165)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)

I haven't investigated further yet, if this isn't known to anyone I'll
have a look to see if I can work out what's going on.

Jim


On 25/06/2010 03:52, Daniel Kulp wrote:

> Probably my fault.   Most of us aren't using Windows anymore which would
> explain why it affected you and not us.  I just committed a fix and deployed a
> new snapshot.    Thus, you should be able to build now if you run with the -U
> -cpu to update the snapshot.
>
> Dan
>
>
> On Thursday 24 June 2010 4:06:17 pm Jim Talbut wrote:
>    
>> Hi,
>>
>> When I try to build CXF from source I get this:
>> [INFO] Preparing pmd:check
>> [INFO] [pmd:pmd {execution: pmd}]
>> [INFO] [pmd:check {execution: validate}]
>> [INFO]
>> [INFO] [cxf-xml2fastinfoset:xml2fastinfoset {execution: xml2fastinfoset}]
>> [INFO] [cxf-xjc:xsdtojava {execution: generate-sources}]
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] The filename, directory name, or volume label syntax is incorrect
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: The filename,
>> directory name, or volume label syntax is incorrect
>>           at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif
>> ecycleExecutor.java:719) at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycl
>> e(DefaultLifecycleExecutor.java:556) at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife
>> cycleExecutor.java:535) at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai
>> lures(DefaultLifecycleExecutor.java:387) at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Def
>> aultLifecycleExecutor.java:348) at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl
>> eExecutor.java:180) at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at
>> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>           at
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>>           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>           at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
>> 9) at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
>> l.java:25) at java.lang.reflect.Method.invoke(Method.java:597)
>>           at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>           at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>           at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>           at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> Caused by: org.apache.maven.plugin.MojoExecutionException: The filename,
>> directory name, or volume label syntax is incorrect
>>           at
>> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJava
>> Mojo.java:229) at
>> org.apache.cxf.maven_plugin.XSDToJavaMojo.execute(XSDToJavaMojo.java:38)
>>           at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag
>> er.java:490) at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif
>> ecycleExecutor.java:694) ... 17 more
>> Caused by: java.io.IOException: The filename, directory name, or volume
>> label syntax is incorrect
>>           at java.io.WinNTFileSystem.createFileExclusively(Native Method)
>>           at java.io.File.createNewFile(File.java:883)
>>           at
>> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJava
>> Mojo.java:220) ... 20 more
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 50 seconds
>> [INFO] Finished at: Thu Jun 24 20:59:07 BST 2010
>> [INFO] Final Memory: 120M/502M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> Useful version details:
>> C:\Work\cxf>mvn -v
>> Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
>> Java version: 1.6.0_14
>> Java home: C:\Program Files\Java\jdk1.6.0_14\jre
>> Default locale: en_GB, platform encoding: Cp1252
>> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
>> C:\Work\cxf>echo %MAVEN_OPTS%
>> -Xms512m -Xmx512m -XX:PermSize=512m -XX:MaxPermSize=512m
>>
>> Noone else seems to be hitting this, so I'm guess it's something stupid
>> in my setup, can anyone point me in the right direction?
>>
>> Thanks
>>
>> Jim
>>      
>    

Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Daniel Kulp
Administrator
On Friday 25 June 2010 8:46:56 am Jim Talbut wrote:

> Ah, thanks, that's much better.
> But a full "mvn clean install" is consistently failing on this test:
> <testcase time="2.054"
> classname="org.apache.cxf.systest.dispatch.DispatchClientServerTest"
> name="testTimeout">
> <failure message="java.net.SocketTimeoutException"
> type="java.lang.AssertionError">java.lang.AssertionError:
> java.net.SocketTimeoutException
>      at org.junit.Assert.fail(Assert.java:91)
>      at org.junit.Assert.assertTrue(Assert.java:43)
>      at
> org.apache.cxf.systest.dispatch.DispatchClientServerTest.testTimeout(Dispat
> chClientServerTest.java:165) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
> 9) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
> l.java:25) at java.lang.reflect.Method.invoke(Method.java:597)
>
> I haven't investigated further yet, if this isn't known to anyone I'll
> have a look to see if I can work out what's going on.

If you find something, let me know.   Hudson was fine the last build and I
haven't seen that test fail lately so I'm not sure what would be going on.

Dan



>
> Jim
>
> On 25/06/2010 03:52, Daniel Kulp wrote:
> > Probably my fault.   Most of us aren't using Windows anymore which would
> > explain why it affected you and not us.  I just committed a fix and
> > deployed a new snapshot.    Thus, you should be able to build now if you
> > run with the -U -cpu to update the snapshot.
> >
> > Dan
> >
> > On Thursday 24 June 2010 4:06:17 pm Jim Talbut wrote:
> >> Hi,
> >>
> >> When I try to build CXF from source I get this:
> >> [INFO] Preparing pmd:check
> >> [INFO] [pmd:pmd {execution: pmd}]
> >> [INFO] [pmd:check {execution: validate}]
> >> [INFO]
> >> [INFO] [cxf-xml2fastinfoset:xml2fastinfoset {execution:
> >> xml2fastinfoset}] [INFO] [cxf-xjc:xsdtojava {execution:
> >> generate-sources}]
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] The filename, directory name, or volume label syntax is incorrect
> >>
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Trace
> >> org.apache.maven.lifecycle.LifecycleExecutionException: The filename,
> >> directory name, or volume label syntax is incorrect
> >>
> >>           at
> >>
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
> >> Lif ecycleExecutor.java:719) at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
> >> ycl e(DefaultLifecycleExecutor.java:556) at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
> >> ife cycleExecutor.java:535) at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> >> Fai lures(DefaultLifecycleExecutor.java:387) at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> >> Def aultLifecycleExecutor.java:348) at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
> >> ycl eExecutor.java:180) at
> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at
> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at
> >> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >>
> >>           at
> >>
> >> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> >>
> >>           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>           at
> >>
> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> >> a:3 9) at
> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> >> Imp l.java:25) at java.lang.reflect.Method.invoke(Method.java:597)
> >>
> >>           at
> >>
> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >>
> >>           at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >>           at
> >>
> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >>
> >>           at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >>
> >> Caused by: org.apache.maven.plugin.MojoExecutionException: The filename,
> >> directory name, or volume label syntax is incorrect
> >>
> >>           at
> >>
> >> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJ
> >> ava Mojo.java:229) at
> >> org.apache.cxf.maven_plugin.XSDToJavaMojo.execute(XSDToJavaMojo.java:38)
> >>
> >>           at
> >>
> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
> >> nag er.java:490) at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
> >> Lif ecycleExecutor.java:694) ... 17 more
> >> Caused by: java.io.IOException: The filename, directory name, or volume
> >> label syntax is incorrect
> >>
> >>           at java.io.WinNTFileSystem.createFileExclusively(Native
> >>           Method) at java.io.File.createNewFile(File.java:883)
> >>           at
> >>
> >> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJ
> >> ava Mojo.java:220) ... 20 more
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Total time: 50 seconds
> >> [INFO] Finished at: Thu Jun 24 20:59:07 BST 2010
> >> [INFO] Final Memory: 120M/502M
> >> [INFO]
> >> ------------------------------------------------------------------------
> >>
> >> Useful version details:
> >> C:\Work\cxf>mvn -v
> >> Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
> >> Java version: 1.6.0_14
> >> Java home: C:\Program Files\Java\jdk1.6.0_14\jre
> >> Default locale: en_GB, platform encoding: Cp1252
> >> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> >> C:\Work\cxf>echo %MAVEN_OPTS%
> >> -Xms512m -Xmx512m -XX:PermSize=512m -XX:MaxPermSize=512m
> >>
> >> Noone else seems to be hitting this, so I'm guess it's something stupid
> >> in my setup, can anyone point me in the right direction?
> >>
> >> Thanks
> >>
> >> Jim

--
Daniel Kulp
[hidden email]
http://dankulp.com/blog
Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Jim Talbut
The problem is that the timeout in the test is too low, so this fixes it:
Index:
src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
===================================================================
---
src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
(revision 959071)
+++
src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
(working copy)
@@ -149,7 +149,7 @@

          DispatchImpl dispImpl = (DispatchImpl)disp;
          HTTPConduit cond = (HTTPConduit)dispImpl.getClient().getConduit();
-        cond.getClient().setConnectionTimeout(500);
+        cond.getClient().setConnectionTimeout(5000);

          InputStream is =
getClass().getResourceAsStream("resources/GreetMeDocLiteralReq.xml");
          SOAPMessage soapReqMsg =
MessageFactory.newInstance().createMessage(null, is);

/Now/ the question is why does it take more than 0.5s to fail to connect
to a local endpoint
(http://localhost:4986/SOAPDispatchService/SoapDispatchPort) on my PC?
I'm still looking into that.

Jim


On 25/06/2010 17:47, Daniel Kulp wrote:

> On Friday 25 June 2010 8:46:56 am Jim Talbut wrote:
>    
>> Ah, thanks, that's much better.
>> But a full "mvn clean install" is consistently failing on this test:
>> <testcase time="2.054"
>> classname="org.apache.cxf.systest.dispatch.DispatchClientServerTest"
>> name="testTimeout">
>> <failure message="java.net.SocketTimeoutException"
>> type="java.lang.AssertionError">java.lang.AssertionError:
>> java.net.SocketTimeoutException
>>       at org.junit.Assert.fail(Assert.java:91)
>>       at org.junit.Assert.assertTrue(Assert.java:43)
>>       at
>> org.apache.cxf.systest.dispatch.DispatchClientServerTest.testTimeout(Dispat
>> chClientServerTest.java:165) at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
>> 9) at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
>> l.java:25) at java.lang.reflect.Method.invoke(Method.java:597)
>>
>> I haven't investigated further yet, if this isn't known to anyone I'll
>> have a look to see if I can work out what's going on.
>>      
> If you find something, let me know.   Hudson was fine the last build and I
> haven't seen that test fail lately so I'm not sure what would be going on.
>
> Dan
>
>
>
>    
>> Jim
>>
>> On 25/06/2010 03:52, Daniel Kulp wrote:
>>      
>>> Probably my fault.   Most of us aren't using Windows anymore which would
>>> explain why it affected you and not us.  I just committed a fix and
>>> deployed a new snapshot.    Thus, you should be able to build now if you
>>> run with the -U -cpu to update the snapshot.
>>>
>>> Dan
>>>
>>> On Thursday 24 June 2010 4:06:17 pm Jim Talbut wrote:
>>>        
>>>> Hi,
>>>>
>>>> When I try to build CXF from source I get this:
>>>> [INFO] Preparing pmd:check
>>>> [INFO] [pmd:pmd {execution: pmd}]
>>>> [INFO] [pmd:check {execution: validate}]
>>>> [INFO]
>>>> [INFO] [cxf-xml2fastinfoset:xml2fastinfoset {execution:
>>>> xml2fastinfoset}] [INFO] [cxf-xjc:xsdtojava {execution:
>>>> generate-sources}]
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] BUILD ERROR
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] The filename, directory name, or volume label syntax is incorrect
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Trace
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: The filename,
>>>> directory name, or volume label syntax is incorrect
>>>>
>>>>            at
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
>>>> Lif ecycleExecutor.java:719) at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
>>>> ycl e(DefaultLifecycleExecutor.java:556) at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
>>>> ife cycleExecutor.java:535) at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
>>>> Fai lures(DefaultLifecycleExecutor.java:387) at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>>>> Def aultLifecycleExecutor.java:348) at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
>>>> ycl eExecutor.java:180) at
>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at
>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at
>>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>>>
>>>>            at
>>>>
>>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>>>>
>>>>            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>            at
>>>>
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
>>>> a:3 9) at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
>>>> Imp l.java:25) at java.lang.reflect.Method.invoke(Method.java:597)
>>>>
>>>>            at
>>>>
>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>
>>>>            at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>            at
>>>>
>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>
>>>>            at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>
>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: The filename,
>>>> directory name, or volume label syntax is incorrect
>>>>
>>>>            at
>>>>
>>>> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJ
>>>> ava Mojo.java:229) at
>>>> org.apache.cxf.maven_plugin.XSDToJavaMojo.execute(XSDToJavaMojo.java:38)
>>>>
>>>>            at
>>>>
>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
>>>> nag er.java:490) at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
>>>> Lif ecycleExecutor.java:694) ... 17 more
>>>> Caused by: java.io.IOException: The filename, directory name, or volume
>>>> label syntax is incorrect
>>>>
>>>>            at java.io.WinNTFileSystem.createFileExclusively(Native
>>>>            Method) at java.io.File.createNewFile(File.java:883)
>>>>            at
>>>>
>>>> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDToJ
>>>> ava Mojo.java:220) ... 20 more
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Total time: 50 seconds
>>>> [INFO] Finished at: Thu Jun 24 20:59:07 BST 2010
>>>> [INFO] Final Memory: 120M/502M
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>> Useful version details:
>>>> C:\Work\cxf>mvn -v
>>>> Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
>>>> Java version: 1.6.0_14
>>>> Java home: C:\Program Files\Java\jdk1.6.0_14\jre
>>>> Default locale: en_GB, platform encoding: Cp1252
>>>> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
>>>> C:\Work\cxf>echo %MAVEN_OPTS%
>>>> -Xms512m -Xmx512m -XX:PermSize=512m -XX:MaxPermSize=512m
>>>>
>>>> Noone else seems to be hitting this, so I'm guess it's something stupid
>>>> in my setup, can anyone point me in the right direction?
>>>>
>>>> Thanks
>>>>
>>>> Jim
>>>>          
>    

Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Daniel Kulp
Administrator
On Wednesday 30 June 2010 1:59:27 am Jim Talbut wrote:

> The problem is that the timeout in the test is too low, so this fixes it:
> Index:
> src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
> ===================================================================
> ---
> src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
> (revision 959071)
> +++
> src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
> (working copy)
> @@ -149,7 +149,7 @@
>
>           DispatchImpl dispImpl = (DispatchImpl)disp;
>           HTTPConduit cond =
> (HTTPConduit)dispImpl.getClient().getConduit(); -      
> cond.getClient().setConnectionTimeout(500);
> +        cond.getClient().setConnectionTimeout(5000);
>
>           InputStream is =
> getClass().getResourceAsStream("resources/GreetMeDocLiteralReq.xml");
>           SOAPMessage soapReqMsg =
> MessageFactory.newInstance().createMessage(null, is);
>
> /Now/ the question is why does it take more than 0.5s to fail to connect
> to a local endpoint
> (http://localhost:4986/SOAPDispatchService/SoapDispatchPort) on my PC?
> I'm still looking into that.


Well, no.   The test ISN'T supposed to connect to the endpoint.   It's
supposed to test the failure condition where there isn't anything running on
that port.    That's why the timeout is so low as it's SUPPOSED to timeout.  
Thus, if the test is failing, it's either successfully connecting to something
or the thrown fault is wrong.

Can you try keeping it at 500, but then put a System.gc() and/or a
Thread.yield() or something before it to see if it just needs a little extra
time.   The TestUtil.getPortNumber("fake-port") gets a "unique" port number by
allocating a server socket, getting the port number, then immediately closing
it.   Maybe it's taking a little extra time to close that port.    Also, try
doing a printStackTrace on the caught exception prior to the assert.   I'd
like to know the trace where the SocketTimeoutException is coming from.    
According to javadocs, we SHOULD be getting the ConnectException, not the
SocketTimeoutException.    


Dan




>
> Jim
>
> On 25/06/2010 17:47, Daniel Kulp wrote:
> > On Friday 25 June 2010 8:46:56 am Jim Talbut wrote:
> >> Ah, thanks, that's much better.
> >> But a full "mvn clean install" is consistently failing on this test:
> >> <testcase time="2.054"
> >> classname="org.apache.cxf.systest.dispatch.DispatchClientServerTest"
> >> name="testTimeout">
> >> <failure message="java.net.SocketTimeoutException"
> >> type="java.lang.AssertionError">java.lang.AssertionError:
> >> java.net.SocketTimeoutException
> >>
> >>       at org.junit.Assert.fail(Assert.java:91)
> >>       at org.junit.Assert.assertTrue(Assert.java:43)
> >>       at
> >>
> >> org.apache.cxf.systest.dispatch.DispatchClientServerTest.testTimeout(Dis
> >> pat chClientServerTest.java:165) at
> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> >> a:3 9) at
> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> >> Imp l.java:25) at java.lang.reflect.Method.invoke(Method.java:597)
> >>
> >> I haven't investigated further yet, if this isn't known to anyone I'll
> >> have a look to see if I can work out what's going on.
> >
> > If you find something, let me know.   Hudson was fine the last build and
> > I haven't seen that test fail lately so I'm not sure what would be going
> > on.
> >
> > Dan
> >
> >> Jim
> >>
> >> On 25/06/2010 03:52, Daniel Kulp wrote:
> >>> Probably my fault.   Most of us aren't using Windows anymore which
> >>> would explain why it affected you and not us.  I just committed a fix
> >>> and deployed a new snapshot.    Thus, you should be able to build now
> >>> if you run with the -U -cpu to update the snapshot.
> >>>
> >>> Dan
> >>>
> >>> On Thursday 24 June 2010 4:06:17 pm Jim Talbut wrote:
> >>>> Hi,
> >>>>
> >>>> When I try to build CXF from source I get this:
> >>>> [INFO] Preparing pmd:check
> >>>> [INFO] [pmd:pmd {execution: pmd}]
> >>>> [INFO] [pmd:check {execution: validate}]
> >>>> [INFO]
> >>>> [INFO] [cxf-xml2fastinfoset:xml2fastinfoset {execution:
> >>>> xml2fastinfoset}] [INFO] [cxf-xjc:xsdtojava {execution:
> >>>> generate-sources}]
> >>>> [INFO]
> >>>> ----------------------------------------------------------------------
> >>>> -- [ERROR] BUILD ERROR
> >>>> [INFO]
> >>>> ----------------------------------------------------------------------
> >>>> -- [INFO] The filename, directory name, or volume label syntax is
> >>>> incorrect
> >>>>
> >>>> [INFO]
> >>>> ----------------------------------------------------------------------
> >>>> -- [INFO] Trace
> >>>> org.apache.maven.lifecycle.LifecycleExecutionException: The filename,
> >>>> directory name, or volume label syntax is incorrect
> >>>>
> >>>>            at
> >>>>
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau
> >>>> lt Lif ecycleExecutor.java:719) at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif
> >>>> ec ycl e(DefaultLifecycleExecutor.java:556) at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul
> >>>> tL ife cycleExecutor.java:535) at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
> >>>> le Fai lures(DefaultLifecycleExecutor.java:387) at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
> >>>> s( Def aultLifecycleExecutor.java:348) at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
> >>>> ec ycl eExecutor.java:180) at
> >>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at
> >>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at
> >>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >>>>
> >>>>            at
> >>>>
> >>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60
> >>>> )
> >>>>
> >>>>            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >>>>            Method) at
> >>>>
> >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> >>>> av a:3 9) at
> >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> >>>> or Imp l.java:25) at java.lang.reflect.Method.invoke(Method.java:597)
> >>>>
> >>>>            at
> >>>>
> >>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >>>>
> >>>>            at
> >>>>            org.codehaus.classworlds.Launcher.launch(Launcher.java:255
> >>>>            ) at
> >>>>
> >>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >>>>
> >>>>            at
> >>>>            org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >>>>
> >>>> Caused by: org.apache.maven.plugin.MojoExecutionException: The
> >>>> filename, directory name, or volume label syntax is incorrect
> >>>>
> >>>>            at
> >>>>
> >>>> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDT
> >>>> oJ ava Mojo.java:229) at
> >>>> org.apache.cxf.maven_plugin.XSDToJavaMojo.execute(XSDToJavaMojo.java:3
> >>>> 8)
> >>>>
> >>>>            at
> >>>>
> >>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin
> >>>> Ma nag er.java:490) at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau
> >>>> lt Lif ecycleExecutor.java:694) ... 17 more
> >>>> Caused by: java.io.IOException: The filename, directory name, or
> >>>> volume label syntax is incorrect
> >>>>
> >>>>            at java.io.WinNTFileSystem.createFileExclusively(Native
> >>>>            Method) at java.io.File.createNewFile(File.java:883)
> >>>>            at
> >>>>
> >>>> org.apache.cxf.maven_plugin.AbstractXSDToJavaMojo.execute(AbstractXSDT
> >>>> oJ ava Mojo.java:220) ... 20 more
> >>>> [INFO]
> >>>> ----------------------------------------------------------------------
> >>>> -- [INFO] Total time: 50 seconds
> >>>> [INFO] Finished at: Thu Jun 24 20:59:07 BST 2010
> >>>> [INFO] Final Memory: 120M/502M
> >>>> [INFO]
> >>>> ----------------------------------------------------------------------
> >>>> --
> >>>>
> >>>> Useful version details:
> >>>> C:\Work\cxf>mvn -v
> >>>> Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
> >>>> Java version: 1.6.0_14
> >>>> Java home: C:\Program Files\Java\jdk1.6.0_14\jre
> >>>> Default locale: en_GB, platform encoding: Cp1252
> >>>> OS name: "windows vista" version: "6.0" arch: "amd64" Family:
> >>>> "windows" C:\Work\cxf>echo %MAVEN_OPTS%
> >>>> -Xms512m -Xmx512m -XX:PermSize=512m -XX:MaxPermSize=512m
> >>>>
> >>>> Noone else seems to be hitting this, so I'm guess it's something
> >>>> stupid in my setup, can anyone point me in the right direction?
> >>>>
> >>>> Thanks
> >>>>
> >>>> Jim

--
Daniel Kulp
[hidden email]
http://dankulp.com/blog
Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Jim Talbut
On 30/06/2010 17:55, Daniel Kulp wrote:

> On Wednesday 30 June 2010 1:59:27 am Jim Talbut wrote:
>    
>> The problem is that the timeout in the test is too low, so this fixes it:
>> Index:
>> src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
>> ===================================================================
>> ---
>> src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
>> (revision 959071)
>> +++
>> src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
>> (working copy)
>> @@ -149,7 +149,7 @@
>>
>>            DispatchImpl dispImpl = (DispatchImpl)disp;
>>            HTTPConduit cond =
>> (HTTPConduit)dispImpl.getClient().getConduit(); -
>> cond.getClient().setConnectionTimeout(500);
>> +        cond.getClient().setConnectionTimeout(5000);
>>
>>            InputStream is =
>> getClass().getResourceAsStream("resources/GreetMeDocLiteralReq.xml");
>>            SOAPMessage soapReqMsg =
>> MessageFactory.newInstance().createMessage(null, is);
>>
>> /Now/ the question is why does it take more than 0.5s to fail to connect
>> to a local endpoint
>> (http://localhost:4986/SOAPDispatchService/SoapDispatchPort) on my PC?
>> I'm still looking into that.
>>      
>
> Well, no.   The test ISN'T supposed to connect to the endpoint.   It's
> supposed to test the failure condition where there isn't anything running on
> that port.    That's why the timeout is so low as it's SUPPOSED to timeout.
>    
I can tell that :)
> Thus, if the test is failing, it's either successfully connecting to something
> or the thrown fault is wrong.
>    
In which case it would appear that the thrown fault is wrong, but why
not on your hudson builds?

> Can you try keeping it at 500, but then put a System.gc() and/or a
> Thread.yield() or something before it to see if it just needs a little extra
> time.
I went for:
         System.gc();
         Thread.sleep(1000);
         System.gc();
I also tried changing the port to one that I simply know isn't in use,
in each the result is the same:
java.lang.AssertionError: java.net.SocketTimeoutException


> The TestUtil.getPortNumber("fake-port") gets a "unique" port number by
> allocating a server socket, getting the port number, then immediately closing
> it.   Maybe it's taking a little extra time to close that port.    Also, try
> doing a printStackTrace on the caught exception prior to the assert.   I'd
> like to know the trace where the SocketTimeoutException is coming from.
> According to javadocs, we SHOULD be getting the ConnectException, not the
> SocketTimeoutException.
Not sure I concur with your interpretation of the javadoc, both
http://java.sun.com/javase/6/docs/api/java/net/Socket.html#connect%28java.net.SocketAddress%29 
and
http://java.sun.com/javase/6/docs/api/java/net/URLConnection.html#connect%28%29 
say that a SocketTimeoutException is returned if the timeout expires
whilst connecting.

The stack trace is:
Running org.apache.cxf.systest.dispatch.DispatchClientServerTest
javax.xml.ws.WebServiceException: Could not send Message.
         at
org.apache.cxf.jaxws.DispatchImpl.mapException(DispatchImpl.java:243)
         at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:335)
         at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:217)
         at
org.apache.cxf.systest.dispatch.DispatchClientServerTest.testTimeout(DispatchClientServerTest.java:163)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
         at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
         at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
         at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
         at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
         at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
         at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
         at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
         at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
         at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
         at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
         at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
         at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
         at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
         at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
         at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
         at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
         at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
         at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:140)
         at org.apache.maven.surefire.Surefire.run(Surefire.java:109)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
         at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017)
Caused by: java.net.SocketTimeoutException: SocketTimeoutException
invoking http://localhost:1534/SOAPDispatchService/SoapDispatchPort: 
connect timed out
         at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1973)
         at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1958)
         at
org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:47)
         at
org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:188)
         at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
         at
org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:640)
         at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
         at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:244)
         at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:487)
         at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
         at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
         at
org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:300)
         at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:328)
         ... 32 more
Caused by: java.net.SocketTimeoutException: connect timed out
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
         at java.net.Socket.connect(Socket.java:529)
         at sun.net.NetworkClient.doConnect(NetworkClient.java:158)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
         at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
         at sun.net.www.http.HttpClient.<init>(HttpClient.java:233)
         at sun.net.www.http.HttpClient.New(HttpClient.java:306)
         at sun.net.www.http.HttpClient.New(HttpClient.java:323)
         at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:860)
         at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:801)
         at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:726)
         at
sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:904)
         at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleHeadersTrustCaching(HTTPConduit.java:1869)
         at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.onFirstWrite(HTTPConduit.java:1821)
         at
org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:42)
         at
org.apache.cxf.io.AbstractThresholdOutputStream.write(AbstractThresholdOutputStream.java:69)
         at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1889)
         ... 43 more

The interesting thing, found after a bit of experimentation at work
today, is that trying to connect to a nonexistant localhost port on a
Windows box takes ~1s to fail, but on either Linux or MacOS it fails
immediately.
So on Linux and MacOS you get a ConnectException because it has failed
to connect, but on Windows it times out instead.

Jim
Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Daniel Kulp
Administrator
On Wednesday 30 June 2010 2:33:18 pm Jim Talbut wrote:
> On 30/06/2010 17:55, Daniel Kulp wrote:
> > Thus, if the test is failing, it's either successfully connecting to
> > something or the thrown fault is wrong.
>
> In which case it would appear that the thrown fault is wrong, but why
> not on your hudson builds?

Hudson is running on Linux so your linux experiments you list below apply.  
:-)

> I also tried changing the port to one that I simply know isn't in use,
> in each the result is the same:
> java.lang.AssertionError: java.net.SocketTimeoutException

Interesting.

> > The TestUtil.getPortNumber("fake-port") gets a "unique" port number by
> > allocating a server socket, getting the port number, then immediately
> > closing it.   Maybe it's taking a little extra time to close that port.
> >   Also, try doing a printStackTrace on the caught exception prior to the
> > assert.   I'd like to know the trace where the SocketTimeoutException is
> > coming from. According to javadocs, we SHOULD be getting the
> > ConnectException, not the SocketTimeoutException.
>
> Not sure I concur with your interpretation of the javadoc, both
> http://java.sun.com/javase/6/docs/api/java/net/Socket.html#connect%28java.n
> et.SocketAddress%29 and
> <a href="http://java.sun.com/javase/6/docs/api/java/net/URLConnection.html#connect%2">http://java.sun.com/javase/6/docs/api/java/net/URLConnection.html#connect%2
> 8%29 say that a SocketTimeoutException is returned if the timeout expires
> whilst connecting.

Well, I was looking at the javadoc for the ConnectException that says:

 * Signals that an error occurred while attempting to connect a
 * socket to a remote address and port.  Typically, the connection
 * was refused remotely (e.g., no process is listening on the
 * remote address/port).

But I see where you are coming from as well.   Nice to have things nice an
consistent.  :-)

.......
 
> The interesting thing, found after a bit of experimentation at work
> today, is that trying to connect to a nonexistant localhost port on a
> Windows box takes ~1s to fail, but on either Linux or MacOS it fails
> immediately.
> So on Linux and MacOS you get a ConnectException because it has failed
> to connect, but on Windows it times out instead.

OK.  So I guess the fix is to update the test to increase the timeout to 2
secs or so and also catch and allow the SocketTimeoutException.  Want to
contribute a patch?  (since you can test it on Windows and I cannot)  :-)


--
Daniel Kulp
[hidden email]
http://dankulp.com/blog
Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Jim Talbut
On 30/06/2010 20:01, Daniel Kulp wrote:
> OK.  So I guess the fix is to update the test to increase the timeout to 2
> secs or so and also catch and allow the SocketTimeoutException.  Want to
> contribute a patch?  (since you can test it on Windows and I cannot)  :-
Why do both?
Just checking for both exception types should work on all platforms:
Index:
src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
===================================================================
---
src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
(revision 959071)
+++
src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
(working copy)
@@ -162,8 +162,9 @@
              fail("should not be a SOAPFaultException");
          } catch (WebServiceException ex) {
              //expected
-            assertTrue(ex.getCause().getClass().getName(),
-                       ex.getCause() instanceof java.net.ConnectException);
+            assertTrue(ex.getCause().getClass().getName(),
+                       ex.getCause() instanceof java.net.ConnectException
+                       || ex.getCause() instanceof
java.net.SocketTimeoutException);
          }

      }

Got to go for a bike ride now, I'll file a Jira and put the patch on
that tomorrow morning.

Jim
Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Jim Talbut
Jira filed and patch submitted: https://issues.apache.org/jira/browse/CXF-2865

The patch just permits both classes of exception, if there is a reason  
to increase the timeout too just let me know and I'll do another  
little patch.

Thanks

Jim

Quoting Jim Talbut <[hidden email]>:

> On 30/06/2010 20:01, Daniel Kulp wrote:
>> OK.  So I guess the fix is to update the test to increase the timeout to 2
>> secs or so and also catch and allow the SocketTimeoutException.  Want to
>> contribute a patch?  (since you can test it on Windows and I cannot)  :-
> Why do both?
> Just checking for both exception types should work on all platforms:
> Index:  
> src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java
> ===================================================================
> ---  
> src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java  
> (revision 959071)
> +++  
> src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java  
> (working copy)
> @@ -162,8 +162,9 @@
>              fail("should not be a SOAPFaultException");
>          } catch (WebServiceException ex) {
>              //expected
> -            assertTrue(ex.getCause().getClass().getName(),
> -                       ex.getCause() instanceof java.net.ConnectException);
> +            assertTrue(ex.getCause().getClass().getName(),
> +                       ex.getCause() instanceof java.net.ConnectException
> +                       || ex.getCause() instanceof  
> java.net.SocketTimeoutException);
>          }
>
>      }
>
> Got to go for a bike ride now, I'll file a Jira and put the patch on  
> that tomorrow morning.
>
> Jim
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Reply | Threaded
Open this post in threaded view
|

Re: Error building CXF from source (trunk checkout) [64 Bit Vista]

Daniel  Kulp
Administrator
On Thursday 01 July 2010 3:41:59 am Jim Talbut wrote:
> Jira filed and patch submitted:
> https://issues.apache.org/jira/browse/CXF-2865
>
> The patch just permits both classes of exception, if there is a reason
> to increase the timeout too just let me know and I'll do another
> little patch.

Finally got around to applying this.   Been a busy couple weeks.   :-(

Thanks!
Dan


>
> Thanks
>
> Jim
>
> Quoting Jim Talbut <[hidden email]>:
> > On 30/06/2010 20:01, Daniel Kulp wrote:
> >> OK.  So I guess the fix is to update the test to increase the timeout to
> >> 2 secs or so and also catch and allow the SocketTimeoutException.  Want
> >> to contribute a patch?  (since you can test it on Windows and I cannot)
> >>  :-
> >
> > Why do both?
> > Just checking for both exception types should work on all platforms:
> > Index:
> > src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.ja
> > va ===================================================================
> > ---
> > src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.ja
> > va (revision 959071)
> > +++
> > src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.ja
> > va (working copy)
> > @@ -162,8 +162,9 @@
> >
> >              fail("should not be a SOAPFaultException");
> >          
> >          } catch (WebServiceException ex) {
> >          
> >              //expected
> >
> > -            assertTrue(ex.getCause().getClass().getName(),
> > -                       ex.getCause() instanceof
> > java.net.ConnectException); +          
> > assertTrue(ex.getCause().getClass().getName(),
> > +                       ex.getCause() instanceof
> > java.net.ConnectException +                       || ex.getCause()
> > instanceof
> > java.net.SocketTimeoutException);
> >
> >          }
> >      
> >      }
> >
> > Got to go for a bike ride now, I'll file a Jira and put the patch on
> > that tomorrow morning.
> >
> > Jim
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.

--
Daniel Kulp
[hidden email]
http://dankulp.com/blog