Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

java.net.SocketTimeoutException: 	at sun.nio.ch.SocketAdaptor$SocketInputStream.read(Unknown Source)	at sun.nio.ch.ChannelInputStream.read(Unknown Source)	at org.jinterop.dcom.transport.JIComTransport.receive(JIComTransport.java:152)	at rpc.DefaultConnection.receiveFragment(DefaultConnection.java:199)	at rpc.DefaultConnection.receive(DefaultConnection.java:85)	at rpc.ConnectionOrientedEndpoint.receive(ConnectionOrientedEndpoint.java:226)	at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:123)	at rpc.Stub.call(Stub.java:113)	at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:568)	at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:481)	at org.jinterop.dcom.core.JIComServer.(JIComServer.java:445)	at dk.sdu.mmmi.predict.sl4logger.driver.SL4BasicDCOMConnector.(SL4BasicDCOMConnector.java:86)	at dk.sdu.mmmi.predict.sl4logger.driver.SL4ReliableDCOMConnector.reinit(SL4ReliableDCOMConnector.java:32)	at dk.sdu.mmmi.predict.sl4logger.driver.SL4ReliableDCOMConnector.(SL4ReliableDCOMConnector.java:27)	at dk.agrotech.infogrow.setup.DetectClimateComputerSetup.(DetectClimateComputerSetup.java:51)	at dk.agrotech.infogrow.setup.LoggerConfigurationManagementThread.(LoggerConfigurationManagementThread.java:36)	at dk.sdu.mmmi.predict.sl4logger.driver.Driver.(Driver.java:77)	at dk.sdu.mmmi.predict.sl4logger.driver.Driver.createDriverWithDefaultPersistence(Driver.java:181)	at dk.sdu.mmmi.predict.sl4logger.Daemon.start(Daemon.java:55)	at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:3271)