EJBCLIENT-34 fails for invocations on EJB 2.x v...| JBoss.org Content Archive (Read Only)

1 2 3 Previous Next 33 Replies Latest reply on Nov 13, 2012 7:49 AM by jaikiran Go to original post Branched from an earlier discussion.

15. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 6, 2012 8:16 AM (in response to jaikiran)

the nightly builds are failing since Oct 16 --> https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/
I patch my own.
Actions
16. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jaikiran Nov 6, 2012 10:44 AM (in response to jonatan.guillen)

Jonatan Guillen wrote:

the nightly builds are failing since Oct 16 --> https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/

That's weird. Thanks for reporting, I'll see if someone knows what's going on with it.
Actions
17. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 7, 2012 2:22 AM (in response to jaikiran)

When It works I test with the last nightly build.
Actions
18. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 7, 2012 2:34 AM (in response to jonatan.guillen)

In my own JBoss modified I see a infinite log when I use the client:

08:30:09,819 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@8bb0b0 since the current EJB client context selector can't handle scoped contexts
08:30:09,821 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1bb2f11 since the current EJB client context selector can't handle scoped contexts
08:30:19,830 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@f2cb8 since the current EJB client context selector can't handle scoped contexts
08:30:19,831 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@dd7469 since the current EJB client context selector can't handle scoped contexts
08:30:29,840 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1ce3f76 since the current EJB client context selector can't handle scoped contexts
08:30:29,841 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@192a5b8 since the current EJB client context selector can't handle scoped contexts
08:30:39,850 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1506e73 since the current EJB client context selector can't handle scoped contexts
08:30:39,851 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@b7c24 since the current EJB client context selector can't handle scoped contexts
08:30:49,861 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@dce075 since the current EJB client context selector can't handle scoped contexts
08:30:49,862 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@2d5f08 since the current EJB client context selector can't handle scoped contexts
08:30:59,872 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@11e8225 since the current EJB client context selector can't handle scoped contexts
08:30:59,873 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@8b228a since the current EJB client context selector can't handle scoped contexts
08:31:09,882 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@cb669d since the current EJB client context selector can't handle scoped contexts
08:31:09,882 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1c1fcf1 since the current EJB client context selector can't handle scoped contexts
08:31:19,893 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@16bb944 since the current EJB client context selector can't handle scoped contexts
08:31:19,894 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@fdf173 since the current EJB client context selector can't handle scoped contexts
08:31:29,913 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@19ec220 since the current EJB client context selector can't handle scoped contexts
08:31:29,914 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1fa3d95 since the current EJB client context selector can't handle scoped contexts
08:31:39,934 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@79a595 since the current EJB client context selector can't handle scoped contexts
08:31:39,935 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@111c109 since the current EJB client context selector can't handle scoped contexts
08:31:49,954 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@17cb0f1 since the current EJB client context selector can't handle scoped contexts
08:31:49,954 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@12ea3d5 since the current EJB client context selector can't handle scoped contexts
08:31:59,964 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@16eb551 since the current EJB client context selector can't handle scoped contexts
08:31:59,965 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1fcebee since the current EJB client context selector can't handle scoped contexts
08:32:09,975 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@196771e since the current EJB client context selector can't handle scoped contexts
08:32:09,976 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@2f58d7 since the current EJB client context selector can't handle scoped contexts
08:32:19,985 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@c6b216 since the current EJB client context selector can't handle scoped contexts
08:32:19,987 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1780e0b since the current EJB client context selector can't handle scoped contexts
08:32:30,006 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1373ba since the current EJB client context selector can't handle scoped contexts
08:32:30,007 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@eaaa40 since the current EJB client context selector can't handle scoped contexts
08:32:40,016 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@8a3523 since the current EJB client context selector can't handle scoped contexts
08:32:40,018 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@878596 since the current EJB client context selector can't handle scoped contexts
08:32:50,026 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@198d61e since the current EJB client context selector can't handle scoped contexts
08:32:50,027 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@ad5843 since the current EJB client context selector can't handle scoped contexts
08:33:00,037 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@133ffe since the current EJB client context selector can't handle scoped contexts
08:33:00,038 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1e903 since the current EJB client context selector can't handle scoped contexts
08:33:10,058 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@4b0d4c since the current EJB client context selector can't handle scoped contexts
08:33:10,059 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@493280 since the current EJB client context selector can't handle scoped contexts
08:33:20,068 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@102bd60 since the current EJB client context selector can't handle scoped contexts
08:33:20,069 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@2dffb1 since the current EJB client context selector can't handle scoped contexts
08:33:30,079 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@b75897 since the current EJB client context selector can't handle scoped contexts
08:33:30,079 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@40df80 since the current EJB client context selector can't handle scoped contexts
08:33:40,089 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@c4821c since the current EJB client context selector can't handle scoped contexts
08:33:40,090 INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1c384c5 since the current EJB client context selector can't handle scoped contexts

This log continues forever
Actions
19. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jaikiran Nov 7, 2012 3:02 AM (in response to jonatan.guillen)

I can't say if its because of the way you created your patched version or if its an real issue. Let's wait for the nightly build job to be fixed, hopefully soon, to understand better. Or you can just build (instead of patching) the latest upstream master and see if that works.
Actions
20. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 7, 2012 3:14 AM (in response to jaikiran)

I debug the code and the repetitive log is my fault, I try to reconnect in failure.
Actions
21. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 7, 2012 3:34 AM (in response to jonatan.guillen)

I debug a little more. The log:

INFO [org.jboss.ejb.client.naming] (Thread-41) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@1c384c5 since the current EJB client context selector can't handle scoped contexts

appears when:
- The client is inside JBoss
- I do a lookup to EJB outside this Jboss (different port or diferent host)

When I do a lookup inside JBoss all works good.

---------------
---------------

When I do a lookup from a client outside JBoss to any EJB (different port or different host) all works good.
Actions
22. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jaikiran Nov 7, 2012 3:34 AM (in response to jonatan.guillen)

How exactly have you "patched" the AS7 server?
Actions
23. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 7, 2012 3:35 AM (in response to jaikiran)

I update some library in modules:
- ejb-client
- marshalling
- etc...
Actions
24. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jaikiran Nov 7, 2012 3:40 AM (in response to jonatan.guillen)

That's not enough like I said in the other thread here https://community.jboss.org/message/772708#772708
Actions
25. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 7, 2012 3:43 AM (in response to jaikiran)

Then I wait, meanwhile I try to build the master.
Actions
26. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jaikiran Nov 7, 2012 3:48 AM (in response to jonatan.guillen)

Jonatan Guillen wrote:

meanwhile I try to build the master.
If you need help with that, then this might be useful http://community.jboss.org/wiki/HackingonAS7
Actions
27. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 7, 2012 6:23 AM (in response to jaikiran)

The compilation of master fails:

[INFO] JBoss Application Server: Build Configuration ..... SUCCESS [2.606s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [0.862s]
[INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [9.585s]
[INFO] JBoss Application Server: Controller Client ....... SUCCESS [2.783s]
[INFO] JBoss Application Server: Controller Core ......... SUCCESS [20.023s]
[INFO] JBoss Application Server: Deployment Repository ... SUCCESS [1.276s]
[INFO] JBoss Application Server: Version ................. SUCCESS [0.535s]
[INFO] JBoss Application Server: Process Controller ...... SUCCESS [2.656s]
[INFO] JBoss Application Server: Platform MBean integration SUCCESS [2.601s]
[INFO] JBoss Application Server: Domain Management ....... SUCCESS [3.544s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.083s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [1.398s]
[INFO] JBoss Application Server: Embedded ................ SUCCESS [1.731s]
[INFO] JBoss Application Server: Network ................. SUCCESS [0.994s]
[INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [2.894s]
[INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [1.958s]
[INFO] JBoss Application Server: Server .................. SUCCESS [9.856s]
[INFO] JBoss Application Server: Management Client Content SUCCESS [0.980s]
[INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [1.699s]
[INFO] JBoss Application Server: Host Controller ......... SUCCESS [7.509s]
[INFO] JBoss Application Server: Core Model Test Harness and Tests SUCCESS [11.852s]
[INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [0.465s]
[INFO] JBoss Application Server: Subsystem Test Harness .. FAILURE [24.877s]
[INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
Actions
28. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jaikiran Nov 7, 2012 9:56 AM (in response to jonatan.guillen)

INFO] JBoss Application Server: Subsystem Test Harness .. FAILURE [24.877s]
Do the logs in the target/surefire-reports/ of that failing module show any details why it's failing?
Actions
29. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 7, 2012 9:59 AM (in response to jaikiran)

-------------------------------------------------------------------------------
Test set: org.jboss.as.model.test.MavenURLResourceTestCase
-------------------------------------------------------------------------------
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 21.25 sec <<< FAILURE!
testMavenGav(org.jboss.as.model.test.MavenURLResourceTestCase) Time elapsed: 21.214 sec <<< ERROR!
java.lang.RuntimeException: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.sonatype.aether:aether-api:jar:1.13.1 from/to jboss-developer (http://repository.jboss.org/nexus/content/groups/developer/): Error transferring file: Connection timed out: connect
          at org.jboss.as.model.test.ChildFirstClassLoader.createMavenGavURL(ChildFirstClassLoader.java:209)
          at org.jboss.as.model.test.MavenURLResourceTestCase.testMavenGav(MavenURLResourceTestCase.java:39)
          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:45)
          at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
          at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
          at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
          at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
          at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
          at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
          at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
          at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
          at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
          at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
          at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
          at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
          at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
          at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
          at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
          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.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
          at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
          at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
          at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
          at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.sonatype.aether:aether-api:jar:1.13.1 from/to jboss-developer (http://repository.jboss.org/nexus/content/groups/developer/): Error transferring file: Connection timed out: connect
          at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:568)
          at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:245)
          at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:222)
          at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:296)
          at org.jboss.as.model.test.ChildFirstClassLoader.createMavenGavURL(ChildFirstClassLoader.java:207)
          ... 30 more
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.sonatype.aether:aether-api:jar:1.13.1 from/to jboss-developer (http://repository.jboss.org/nexus/content/groups/developer/): Error transferring file: Connection timed out: connect
          at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1016)
          at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1004)
          at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:725)
          at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
          at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.wagon.TransferFailedException: Error transferring file: Connection timed out: connect
          at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:143)
          at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
          at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
          at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
          at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:660)
          ... 4 more
Caused by: java.net.ConnectException: Connection timed out: connect
          at java.net.PlainSocketImpl.socketConnect(Native Method)
          at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
          at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
          at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
          at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
          at java.net.Socket.connect(Socket.java:529)
          at java.net.Socket.connect(Socket.java:478)
          at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
          at sun.net.www.http.HttpClient.openServer(HttpClient.java:395)
          at sun.net.www.http.HttpClient.openServer(HttpClient.java:530)
          at sun.net.www.http.HttpClient.<init>(HttpClient.java:234)
          at sun.net.www.http.HttpClient.New(HttpClient.java:307)
          at sun.net.www.http.HttpClient.New(HttpClient.java:324)
          at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970)
          at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911)
          at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836)
          at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
          at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
          at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:115)
          ... 8 more
Actions

1 2 3 Previous Next

Go to original post