[Design of JBoss Wiki] - Re: Installation of JBoss Wiki
by margotmedia
Sorry!
With mvn install in wiki-common directory I get a BUILD ERROR Invalid argument. With mvn -e install I get
| org.apache.maven.lifecycle.LifecycleExecutionException: Invalid argument
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
| ultLifecycleExecutor.java:584)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
| fecycle(DefaultLifecycleExecutor.java:500)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
| ltLifecycleExecutor.java:479)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
| dleFailures(DefaultLifecycleExecutor.java:331)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
| ts(DefaultLifecycleExecutor.java:292)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
| fecycleExecutor.java:142)
| at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
| at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
| at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
| java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.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: Invalid argument
| at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo
| .java:166)
| at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
| nManager.java:453)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
| ultLifecycleExecutor.java:559)
| ... 16 more
| Caused by: org.apache.maven.shared.filtering.MavenFilteringException: Invalid ar
| gument
| at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(Def
| aultMavenFileFilter.java:96)
| at org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filt
| erResources(DefaultMavenResourcesFiltering.java:293)
| at org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo
| .java:162)
| ... 18 more
| Caused by: java.io.IOException: Invalid argument
| at java.io.WinNTFileSystem.canonicalize0(Native Method)
| at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:396)
| at java.io.File.getCanonicalPath(File.java:559)
| at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:959)
| at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:2051)
| at org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(Def
| aultMavenFileFilter.java:91)
| ... 20 more
|
I need this installation instruction badly ;-)
I think I help you to find all the failures anyone can make ;-)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216938#4216938
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216938
17 years
[Design of Messaging on JBoss (Messaging/JBoss)] - Remoting Issue when writing failover test
by gaohoward
I already asked Ron's help, but in case someone has direct experience with this, please give me some hint. Thanks.
I'm writing a JBM test and got an issue with Remoting, need your help. The test is to force the client side failover to happen when the JMS connection and server node are good. To do this, I directly called JBM's client failover handler method, which is
FailoverCommandCenter.failureDetected(Throwable reason, FailureDetector source, JMSRemotingConnection remotingConnection)
Inside this method, the will disconnect the 'remotingConnection' and create a new one. The http transport is used. The JMSRemotingConnection is a wrapper of Remoting's Client object. The steps are
1. starting two jboss nodes 0 and 1
2. create a connection on node 1
3. call failureDetected() method to failover
4. expect the connection failed over to node 0
However in step 3, I failed to create a new connection to node 0. The exception is 'Read timed out', stack trace:
@CallbackPoller:10[@1415056] 17:50:21,639 ERROR [Client] 22222222222222222 error:
org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Read timed out.
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:369)
at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:147)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:133)
at org.jboss.remoting.Client.invoke(Client.java:1644)
at org.jboss.remoting.Client.invoke(Client.java:554)
at org.jboss.remoting.Client.getCallbacks(Client.java:1175)
at org.jboss.remoting.callback.CallbackPoller.run(CallbackPoller.java:190)
at org.jboss.remoting.callback.CallbackPoller$BlockingPollerThread.run(CallbackPoller.java:338)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:681)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:626)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:957)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:294)
... 7 more
I'm using remoting 2.2.2.SP11 with some added log my myself. The exact location where timed out happens is at HTTPClientInvoker.useHttpURLConnection():
if (sendingData)
{
....
responseCode = conn.getResponseCode(); //this gets timed out!!!
......
Another thing is if in step 3 I kill node 1 instead of calling failureDetected() directly, I got the expected failover. (I think the only differece is that in this case the caller thread of failureDetected() is from remoting (connectionValidator)).
I have no idea where did I do wrong?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216899#4216899
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216899
17 years