[
https://jira.jboss.org/jira/browse/JBIDE-6024?page=com.atlassian.jira.plu...
]
henk de boer commented on JBIDE-6024:
-------------------------------------
ah, of course. The log shows the Server Startup / Shutdown from 44 hours ago and then the
one from approximately 5 hours ago, which should be the one that failed. It lists this:
info: Server Starting
warning: Could not obtain connection to any of these urls: localhost:1099 and discovery
failed with error: java.lang.ClassCastException: java.lang.Boolean
javax.naming.CommunicationException: Could not obtain connection to any of these urls:
localhost:1099 and discovery failed with error: java.lang.ClassCastException:
java.lang.Boolean [Root exception is javax.naming.CommunicationException: Failed to
connect to server localhost/127.0.0.1:1099 [Root exception is
javax.naming.ServiceUnavailableException: Failed to connect to server
localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection
refused]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.ide.eclipse.as.core.extensions.jmx.JMXSafeRunner.run(JMXSafeRunner.java:67)
at org.jboss.ide.eclipse.as.core.extensions.jmx.JMXSafeRunner.run(JMXSafeRunner.java:46)
at
org.jboss.ide.eclipse.as.core.extensions.polling.JMXPoller$PollerRunnable.run(JMXPoller.java:104)
at java.lang.Thread.run(Thread.java:613)
Caused by: javax.naming.CommunicationException: Failed to connect to server
localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException:
Failed to connect to server localhost/127.0.0.1:1099 [Root exception is
java.net.ConnectException: Connection refused]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
... 7 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection
refused]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
... 8 more
Caused by: java.net.ConnectException: Connection refused
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:433)
at java.net.Socket.connect(Socket.java:524)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
... 8 more
warning: jmx not bound
javax.naming.NameNotFoundException: jmx not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
at org.jnp.server.NamingServer.lookup(NamingServer.java:396)
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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.ide.eclipse.as.core.extensions.jmx.JMXSafeRunner.run(JMXSafeRunner.java:67)
at org.jboss.ide.eclipse.as.core.extensions.jmx.JMXSafeRunner.run(JMXSafeRunner.java:46)
at
org.jboss.ide.eclipse.as.core.extensions.polling.JMXPoller$PollerRunnable.run(JMXPoller.java:104)
at java.lang.Thread.run(Thread.java:613)
The publishing node doesn't lists any errors for that point in time, but just some ok
messages:
ok: 5 files modified in module Test
ok: 9 files modified in module myproject
ok: 44 files modified in module myproject_ejb
ok: 29 files modified in module myproject_web
ok: 1 files modified in module lib/myproject/EarContent/lib/jbosscache-core.jar
ok: 1 files modified in module lib/myproject/EarContent/lib/jgroups.jar
Test is another project I happened to have deployed (a dynamic web project, which is
normally not deployed). Suspicious is that it says 44 files were modified in
myproject_ejb, while in fact no files were actually modified. The same is true is for the
files in /lib/myproject/EarContent and for the entire Test project. I'm also not sure
where the /lib prefix comes from, but maybe this is just a naming convention?
JBoss AS adapter deploys only recently changed files and removes
everithing else
---------------------------------------------------------------------------------
Key: JBIDE-6024
URL:
https://jira.jboss.org/jira/browse/JBIDE-6024
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Environment: JBoss Tools 3.1.0.GA candidate v201003050540R-H56-GA
Reporter: Denis Golovin
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.1.1
The steps to replicate the issue are explained in this post
http://community.jboss.org/message/526847#526847.
I cannot confirm yet but it looks like problem should be replicated for any project after
couple hours of waiting.
I was able to get the same problems after I tried to change ad deploy files after 4
hours. Now it happens every time even after restoring deployment with Full Publish action
in Servers View
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira