[JBoss JIRA] (JBIDE-11681) Remote System Deployment doesn't work for AS 7.1 from Windows to Linux
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-11681:
-------------------------------------
Summary: Remote System Deployment doesn't work for AS 7.1 from Windows to Linux
Key: JBIDE-11681
URL: https://issues.jboss.org/browse/JBIDE-11681
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: Remote Host Config: Linux, OpenJDK 1.6.0_23, AS 7.1.0.Final
Local Host: Windows 7 x86_64, Oracle Java 1.6.0_31-b05, JBT 3.3.0-beta3 build from trunk
Reporter: Denis Golovin
Assignee: Rob Stryker
I configure connection to linux host using SSH-only system type. After I fixed JBIDE-11283 it seems starts but there are many other problems that require time to fix:
1. No JMX connection
{code}.jboss.tools.jmx.core.JMXException: Runtime Exception contacting JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:73)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:137)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:215)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:207)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.remoting3.jmx.RemotingConnector.connect(RemotingConnector.java:155)
at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:65)
... 6 more{code}
2. Deployment is going beyond creating META-INF folder and then complains
{code}org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error
at org.eclipse.rse.internal.services.ssh.files.SftpFileService.makeSystemMessageException(SftpFileService.java:594)
at org.eclipse.rse.internal.services.ssh.files.SftpFileService.upload(SftpFileService.java:896)
at org.jboss.ide.eclipse.as.rse.core.RSERemotePublishHandler$1.run(RSERemotePublishHandler.java:63){code}
3. Stop action doesn't really stop the server and next start I get exceptions like this
{code}13:29:17,373 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Error initializing endpoint: java.net.BindException: Address already in use /0.0.0.0:8080
at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:983) [jbossweb-7.0.10.Final.jar:]
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.10.Final.jar:]
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_23]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_23]
13:29:17,385 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_23]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_23]
Caused by: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use /0.0.0.0:8080
at org.apache.catalina.connector.Connector.init(Connector.java:985)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
... 5 more
13:29:17,441 INFO [org.jboss.as.jacorb] (MSC service thread 1-6) JBAS016330: CORBA ORB Service started
13:29:17,468 WARN [jacorb.orb.iiop] (MSC service thread 1-4) could not create server socket port: 3528 host: localhost.localdomain/127.0.0.1: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method) [rt.jar:1.6.0_23]
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:353) [rt.jar:1.6.0_23]
at java.net.ServerSocket.bind(ServerSocket.java:336) [rt.jar:1.6.0_23]
at java.net.ServerSocket.<init>(ServerSocket.java:202) [rt.jar:1.6.0_23]
at org.jacorb.orb.factory.DefaultServerSocketFactory.createServerSocket(DefaultServerSocketFactory.java:49) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.iiop.IIOPListener$Acceptor.createServerSocket(IIOPListener.java:572) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.iiop.IIOPListener$Acceptor.init(IIOPListener.java:417) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.iiop.IIOPListener.configure(IIOPListener.java:163) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.etf.FactoriesBase.newInstance(FactoriesBase.java:125) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.etf.FactoriesBase.create_listener(FactoriesBase.java:74) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.BasicAdapter.configure(BasicAdapter.java:102) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.ORB.getRootPOA(ORB.java:1036) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1307) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:153) [jboss-as-jacorb-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_23]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_23]
13:29:17,476 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.jacorb.poa-service.rootpoa: org.jboss.msc.service.StartException in service jboss.jacorb.poa-service.rootpoa: org.omg.CORBA.INITIALIZE: Could not create server socket (3528): java.net.BindException: Address already in use
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:155)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_23]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_23]
Caused by: org.omg.CORBA.INITIALIZE: Could not create server socket (3528): java.net.BindException: Address already in use
at org.jacorb.orb.iiop.IIOPListener$Acceptor.createServerSocket(IIOPListener.java:580)
at org.jacorb.orb.iiop.IIOPListener$Acceptor.init(IIOPListener.java:417)
at org.jacorb.orb.iiop.IIOPListener.configure(IIOPListener.java:163)
at org.jacorb.orb.etf.FactoriesBase.newInstance(FactoriesBase.java:125)
at org.jacorb.orb.etf.FactoriesBase.create_listener(FactoriesBase.java:74)
at org.jacorb.orb.BasicAdapter.configure(BasicAdapter.java:102)
at org.jacorb.orb.ORB.getRootPOA(ORB.java:1036)
at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1307)
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:153)
... 5 more
13:29:17,583 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
13:29:17,684 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /206.169.37.222:9999
13:29:17,686 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-16) JBAS015012: Started FileSystemDeploymentService for directory /home/eskimo/Temp/as-7.1/jboss-as-7.1.0.Final/standalone/deployments
13:29:17,686 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017112: Address already in use /0.0.0.0:4447
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:110) [jboss-as-remoting-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_23]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_23]
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_23]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:137) [rt.jar:1.6.0_23]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77) [rt.jar:1.6.0_23]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:70) [rt.jar:1.6.0_23]
at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135) [xnio-api-3.0.3.GA.jar:3.0.3.GA]
at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209) [jboss-remoting-3.2.2.GA.jar:3.2.2.GA]
at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:102) [jboss-as-remoting-7.1.0.Final.jar:7.1.0.Final]
... 5 more{code}
4. Starting server first time gets
-server-config=null in command line
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12919) Keyword reporting broken
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-12919:
----------------------------------
Summary: Keyword reporting broken
Key: JBIDE-12919
URL: https://issues.jboss.org/browse/JBIDE-12919
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: usage
Affects Versions: 4.0.0.Beta1
Reporter: Radim Hopp
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 4.0.0.CR1
Attachments: keyword.png
Keyword reporting is broken.
For last week (Oct 14 - Oct 21) there is 65383 rows in keyword.
Few records are OK, but there is a lot of records with __utmv appended.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12563) Show in MBean Explorer not available when it should be
by Martin Malina (JIRA)
Martin Malina created JBIDE-12563:
-------------------------------------
Summary: Show in MBean Explorer not available when it should be
Key: JBIDE-12563
URL: https://issues.jboss.org/browse/JBIDE-12563
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 4.0.0.Alpha1
Environment: JBT 4.0.0.Alpha1 B6
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
When you start EAP 5.1.2 and then try to invoke server -> Show in -> MBean Explorer, it is grayed out and cannot be clicked. But when I open the MBean Explorer manually I can access the server's mbeans no problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-11410) Crash in Eclipse when running JBoss Server
by Muh Khairul Lukman W. (JIRA)
Muh Khairul Lukman W. created JBIDE-11410:
---------------------------------------------
Summary: Crash in Eclipse when running JBoss Server
Key: JBIDE-11410
URL: https://issues.jboss.org/browse/JBIDE-11410
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta1
Environment: JRE version: 7.0_147-b147
Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops)
Derivative: IcedTea7 2.0
Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.
Eclipse 3.7.2 64 bit
Reporter: Muh Khairul Lukman W.
Assignee: Rob Stryker
Attachments: hs_err_pid25114.log
{code}
Mar 27, 2012 2:14:48 PM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.3.GA
Mar 27, 2012 2:14:48 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.3.GA
Mar 27, 2012 2:14:48 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.2.GA
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f6542da4697, pid=25114, tid=140073270568704
#
# JRE version: 7.0_147-b147
# Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea7 2.0
# Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1
# Problematic frame:
# C [libplds4.so+0x1697] PL_HashTableLookupConst+0x17
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/rully/eclipse_jee/hs_err_pid25114.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
{code}
When i start to run JBoss server in eclipse, it start to crash and shut down.. JBoss service server won't running on my desktop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months