[
https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi...
]
Brian Fitzpatrick commented on JBIDE-16066:
-------------------------------------------
Can definitely duplicate the bug on Windows 7 with JBDS 7.1.1.GA.
I'm open to suggestions on how to diagnose this [~maxandersen]. It appears it's
coming from the runtime during deployment, but that's way beyond me at this point. Who
should I talk to? [~rob.stryker]?
See the following in the console:
{code}
17:06:28,286 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
17:06:28,510 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
17:06:28,745 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.1.0.GA
(AS 7.2.0.Final-redhat-8) starting
17:06:30,547 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.7.GA-redhat-1
17:06:30,549 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating
http management service using socket-binding (management-http)
17:06:30,571 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version
3.0.7.GA-redhat-1
17:06:30,758 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version
3.2.16.GA-redhat-1
17:06:30,849 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171:
Activating Security Subsystem
17:06:30,849 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29)
JBAS010280: Activating Infinispan subsystem.
17:06:30,859 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800:
Activating Naming Subsystem
17:06:30,864 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46)
JBAS015537: Activating WebServices Extension
17:06:30,950 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605:
Activated the following JSF Implementations: [main, 1.2]
17:06:31,603 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread
Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
17:06:31,605 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408:
Starting JCA Subsystem (IronJacamar 1.0.17.Final-redhat-1)
17:06:31,750 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current
PicketBox version=4.0.17.Final-redhat-1
17:06:31,893 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052:
Starting JBoss Web Services - Stack CXF Server 4.1.3.Final-redhat-3
17:06:31,896 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting
Naming Service
17:06:32,081 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400:
Bound mail session [java:jboss/mail/Default]
17:06:32,556 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003001: Coyote
HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080
17:06:32,562 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003000: Coyote
HTTP/1.1 starting on: http-localhost/127.0.0.1:8080
17:06:32,614 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread
1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
17:06:33,567 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4)
JBAS015012: Started FileSystemDeploymentService for directory
C:\Runtimes4\jboss-eap-6.1\standalone\deployments
17:06:33,593 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening
on 127.0.0.1:4447
17:06:33,601 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening
on 127.0.0.1:9999
17:06:33,919 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management
interface listening on
http://127.0.0.1:9990/management
17:06:33,919 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on
http://127.0.0.1:9990
17:06:33,919 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA
(AS 7.2.0.Final-redhat-8) started in 9019ms - Started 123 of 177 services (53 services are
passive or on-demand)
17:11:23,732 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads -
2) JBAS015003: Found jbide16066.ear in deployment directory. To trigger deployment create
a file called jbide16066.ear.dodeploy
17:11:23,753 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "jbide16066.ear" (runtime-name:
"jbide16066.ear")
17:11:23,784 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876:
Starting deployment of "null" (runtime-name: "dweb.war")
17:11:24,011 WARN [org.jboss.as.ee] (MSC service thread 1-3) JBAS011006: Not installing
optional component org.example.newwsdlfile.impl.NewWSDLFileImpl due to exception:
java.lang.ClassNotFoundException: org.example.newwsdlfile.impl.NewWSDLFileImpl from
[Module "deployment.jbide16066.ear.dweb.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196)
[jboss-modules.jar:1.2.0.Final-redhat-1]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444)
[jboss-modules.jar:1.2.0.Final-redhat-1]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432)
[jboss-modules.jar:1.2.0.Final-redhat-1]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:399)
[jboss-modules.jar:1.2.0.Final-redhat-1]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374)
[jboss-modules.jar:1.2.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119)
[jboss-modules.jar:1.2.0.Final-redhat-1]
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_24]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_24]
at
org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54)
at
org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:78)
[jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]
17:11:24,079 INFO [org.jboss.web] (ServerService Thread Pool -- 49) JBAS018210: Register
web context: /dweb
17:11:24,218 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559:
Deployed "jbide16066.ear" (runtime-name : "jbide16066.ear")
{code}
Top-Down WS deployment isn't successful when selecting Start/Test
service in Web Service dialog
-----------------------------------------------------------------------------------------------
Key: JBIDE-16066
URL:
https://issues.jboss.org/browse/JBIDE-16066
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.1.CR1
Environment: JBDS 7.1.0 CR1, EAP-6.1
Reporter: Radoslav RĂ¡bara
Assignee: Brian Fitzpatrick
Fix For: 4.2.0.CR2
Attachments: topDownServer.log
Deployment isn't successful when Top-Down web service is created with slider level
selected to "Start service" or "Test service". Project is deployed to
the server but the service endpoint isn't added so the service is not accessible.
It works with other slider levels and all levels works when the server isn't started
before the web service is created.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)