[JBoss JIRA] (JBIDE-13013) Deployment scanner in EAP5 works even if stopped via jmx
by Martin Malina (JIRA)
Martin Malina created JBIDE-13013:
-------------------------------------
Summary: Deployment scanner in EAP5 works even if stopped via jmx
Key: JBIDE-13013
URL: https://issues.jboss.org/browse/JBIDE-13013
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Beta2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
With JBPAPP-9973 fixed I tried this scenario from JBIDE-12643 which should now work:
{quote}
1. Add EAP 5.2.0.ER4 server
2. Create a dynamic web project (or whatever)
3. Start the server
4. Deploy your project
ASSERT project deployed
5. Remove project
ASSERT project undeployed
6. Go to MBean explorer and stop the deployer
From https://community.jboss.org/wiki/SmokeTestJBToolsServerSupport?prevContai...
12) Open MBean Viewer,
a) note that the server can now be expanded,
b) under it are mbeans. browse down to jboss.deployment -> URL ->DeploymentScanner,
c) double-click DeploymentScanner, go to "Operations" page, click "stop" in viewer, click "stop" button on the right,
d) verify operation completes successfully
7. Repeat steps 4. and 5. - this time nothing will be deployed
8. Start the deployer again - see step 6
9. Repeat steps 4. and 5. - still no deployment - FAIL
{quote}
But it doesn't work - when you stop the deployment scanner (step 6) and try to deploy your project again, it will get deployed.
I suspect that the publish operation checks if the deployment scanner is active and if it's not it will enable it again. If that's the case then this probably isn't a bug. But then we can no longer use that use case in any testing (i.e. disable deployment scanner and check that nothing can be deployed).
--
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, 4 months
[JBoss JIRA] (JBIDE-13079) edit jmx connection wizard dialog bad title
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-13079:
-----------------------------------
Summary: edit jmx connection wizard dialog bad title
Key: JBIDE-13079
URL: https://issues.jboss.org/browse/JBIDE-13079
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Alpha2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
As title says. Create default jmx connection, finish, edit the connection, wizard's title is "TEST TITLE"
--
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, 4 months
[JBoss JIRA] (JBIDE-13064) Remote server server log displays error
by Martin Malina (JIRA)
Martin Malina created JBIDE-13064:
-------------------------------------
Summary: Remote server server log displays error
Key: JBIDE-13064
URL: https://issues.jboss.org/browse/JBIDE-13064
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Beta2
Environment: JBDS 6.0.0.Beta2 B62
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
When you open the Server Log view while a remote EAP 5 server is started you get an error after a while:
'Importing Server Log' has encountered a problem.
An internal error occured during: "Importing server log"
An internal error occurred during: "Importing Server Log".
For input string: ""
--
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, 4 months
[JBoss JIRA] (JBIDE-13047) windows to linux, right-click module under server, show in file browser errors
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-13047:
-----------------------------------
Summary: windows to linux, right-click module under server, show in file browser errors
Key: JBIDE-13047
URL: https://issues.jboss.org/browse/JBIDE-13047
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Beta2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
as mentioned above, steps are:
1) in windows, jboss as 7.x server
2) in rse mode linked to remote,
3) deploy a module, publish,
4) right-click module, show in file browser,
ERROR
Ensure error log is clear and that the remote system explorer view opens properly and shows the folder.
--
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, 4 months
[JBoss JIRA] (JBIDE-13081) Focus in MBean Explorer is incorrect if clicking on an operation in opened additional DeploymentScanner
by Martin Malina (JIRA)
Martin Malina created JBIDE-13081:
-------------------------------------
Summary: Focus in MBean Explorer is incorrect if clicking on an operation in opened additional DeploymentScanner
Key: JBIDE-13081
URL: https://issues.jboss.org/browse/JBIDE-13081
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.0.0.Beta2
Environment: JBT 4.0.0.Beta2 B74
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Minor
Fix For: 4.0.0.CR1
When you have two deployment scanners in your as7.1 server and you open the additional MBean and select an operation (e.g. remove()) in the editor, the focus in the MBean Explorer should move to that operation on that mbean. Instead, it selects the same operation in the original mbean (i.e. mbean callled "default").
--
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, 4 months
[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, 4 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, 4 months