Webservice run in Jbos 4.2.2 with jbossws 3.0.5 but not depl

[adesisp]

Hello.

We developed a webservice that is running in jboss 4.2.2GA and jboss 4.2.3GA versions.

Now we are testing jboss 5.0.0 but deployer not deploy the webservice not and no errors appears in log.

C:\DESARROLLO\jboss-5.0.0.GA\bin>run -c default -b 172.20.3.74
===============================================================================

JBoss Bootstrap Environment

JBOSS_HOME: C:\DESARROLLO\jboss-5.0.0.GA

JAVA: C:\Archivos de programa\Java\jdk1.6.0_03\bin\java

JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=360000
0 -Dsun.rmi.dgc.server.gcInterval=3600000

CLASSPATH: C:\DESARROLLO\jboss-5.0.0.GA\bin\run.jar

===============================================================================

12:13:49,608 INFO [ServerImpl] Starting JBoss (Microcontainer)...
12:13:49,608 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812042120)
12:13:49,624 INFO [ServerImpl] Bootstrap URL: null
12:13:49,624 INFO [ServerImpl] Home Dir: C:\DESARROLLO\jboss-5.0.0.GA
12:13:49,624 INFO [ServerImpl] Home URL: file:/C:/DESARROLLO/jboss-5.0.0.GA/
12:13:49,624 INFO [ServerImpl] Library URL: file:/C:/DESARROLLO/jboss-5.0.0.GA/lib/
12:13:49,624 INFO [ServerImpl] Patch URL: null
12:13:49,624 INFO [ServerImpl] Common Base URL: file:/C:/DESARROLLO/jboss-5.0.0.GA/common/
12:13:49,639 INFO [ServerImpl] Common Library URL: file:/C:/DESARROLLO/jboss-5.0.0.GA/common/lib/
12:13:49,639 INFO [ServerImpl] Server Name: default
12:13:49,639 INFO [ServerImpl] Server Base Dir: C:\DESARROLLO\jboss-5.0.0.GA\server
12:13:49,639 INFO [ServerImpl] Server Base URL: file:/C:/DESARROLLO/jboss-5.0.0.GA/server/
12:13:49,639 INFO [ServerImpl] Server Config URL: file:/C:/DESARROLLO/jboss-5.0.0.GA/server/default/conf/
12:13:49,639 INFO [ServerImpl] Server Home Dir: C:\DESARROLLO\jboss-5.0.0.GA\server\default
12:13:49,655 INFO [ServerImpl] Server Home URL: file:/C:/DESARROLLO/jboss-5.0.0.GA/server/default/
12:13:49,655 INFO [ServerImpl] Server Data Dir: C:\DESARROLLO\jboss-5.0.0.GA\server\default\data
12:13:49,655 INFO [ServerImpl] Server Library URL: file:/C:/DESARROLLO/jboss-5.0.0.GA/server/default/lib/
12:13:49,655 INFO [ServerImpl] Server Log Dir: C:\DESARROLLO\jboss-5.0.0.GA\server\default\log
12:13:49,655 INFO [ServerImpl] Server Native Dir: C:\DESARROLLO\jboss-5.0.0.GA\server\default\tmp\native
12:13:49,655 INFO [ServerImpl] Server Temp Dir: C:\DESARROLLO\jboss-5.0.0.GA\server\default\tmp
12:13:49,655 INFO [ServerImpl] Server Temp Deploy Dir: C:\DESARROLLO\jboss-5.0.0.GA\server\default\tmp\deploy
12:13:51,047 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/DESARROLLO/jboss-5.0.0.GA/server/default/conf/bootstrap.xml
12:13:51,907 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.IterableTimedVFSCache]
12:13:51,907 INFO [VFSCacheFactory] Using VFSCache [IterableTimedVFSCache{lifetime=1800, resolution=60}]
12:13:52,330 INFO [CopyMechanism] VFS temp dir: C:\DESARROLLO\jboss-5.0.0.GA\server\default\tmp
12:13:52,377 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
12:13:54,128 INFO [ServerInfo] Java version: 1.6.0_03,Sun Microsystems Inc.
12:13:54,128 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0_03-b05,Sun Microsystems Inc.
12:13:54,144 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
12:13:54,191 INFO [JMXKernel] Legacy JMX core initialized
12:13:57,569 INFO [ProfileServiceImpl] Loading profile: default from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@1
a8e53c(root=C:\DESARROLLO\jboss-5.0.0.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
12:13:57,585 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@1a8e53c(root=C:\DESARR
OLLO\jboss-5.0.0.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
12:13:57,585 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl@2445d7{key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=defau
lt,name=default]}
12:14:01,198 INFO [WebService] Using RMI server codebase: http://172.20.3.74:8083/
12:14:09,723 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
12:14:09,723 INFO [NativeServerConfig] 3.0.5.GA
12:14:23,925 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://172.20.3.74/jndi/rmi://172.20.3.74:1090/jmxconnector
12:14:24,300 INFO [MailService] Mail Service bound to java:/Mail
12:14:26,412 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messa
ges from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on
how to do this.
12:14:26,427 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
12:14:26,662 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
12:14:26,662 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
12:14:27,084 INFO [TransactionManagerService] Initializing recovery manager
12:14:27,319 INFO [TransactionManagerService] Recovery manager configured
12:14:27,319 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
12:14:27,350 INFO [TransactionManagerService] Starting transaction recovery manager
12:14:28,101 INFO [Http11Protocol] Inicializando Coyote HTTP/1.1 en puerto http-172.20.3.74-80
12:14:28,101 INFO [AjpProtocol] Inicializando Coyote AJP/1.3 en ajp-172.20.3.74-8009
12:14:28,101 INFO [StandardService] Arrancando servicio jboss.web
12:14:28,117 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.GA
12:14:28,179 INFO [Catalina] Server startup in 182 ms
12:14:28,211 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
12:14:29,102 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
12:14:29,759 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war
12:14:29,853 INFO [TomcatDeployment] deploy, ctxPath=/juddi, vfsUrl=juddi-service.sar/juddi.war
12:14:29,962 INFO [RegistryServlet] Loading jUDDI configuration.
12:14:29,978 INFO [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties
12:14:29,978 INFO [RegistryServlet] Initializing jUDDI components.
12:14:30,260 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/DESARROLLO/jboss-5.0.0.GA/server/default/deploy/jboss-local-jdbc.rar/META-
INF/ra.xml
12:14:30,306 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/DESARROLLO/jboss-5.0.0.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF
/ra.xml
12:14:30,369 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/DESARROLLO/jboss-5.0.0.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml

12:14:30,385 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/DESARROLLO/jboss-5.0.0.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xm
l
12:14:30,432 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/DESARROLLO/jboss-5.0.0.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.
xml
12:14:30,541 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
12:14:30,572 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
12:14:30,572 INFO [RAMJobStore] RAMJobStore initialized.
12:14:30,588 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.proper
ties'
12:14:30,588 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
12:14:30,588 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
12:14:31,448 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:Defaul
tDS'
12:14:32,528 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE QRTZ_JOB_DETAILS(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80) NOT NULL, DES
CRIPTION VARCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT NULL, IS_DURABLE VARCHAR(1) NOT NULL, IS_VOLATILE VARCHAR(1) NOT NULL, IS_STATEFUL VARCHAR(1) N
OT NULL, REQUESTS_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINARY NULL, PRIMARY KEY (JOB_NAME,JOB_GROUP))
12:14:32,621 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
12:14:32,637 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
12:14:32,637 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
12:14:32,637 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
12:14:32,653 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
12:14:32,653 INFO [JobStoreCMT] JobStoreCMT initialized.
12:14:32,653 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided properties instance.
12:14:32,653 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
12:14:32,668 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
12:14:32,668 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
12:14:32,668 INFO [JobStoreCMT] Recovery complete.
12:14:32,668 INFO [JobStoreCMT] Removed 0 'complete' triggers.
12:14:32,668 INFO [JobStoreCMT] Removed 0 stale fired job entries.
12:14:32,684 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
12:14:32,950 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
12:14:33,169 INFO [ConnectionFactory] Connector bisocket://172.20.3.74:4457 has leasing enabled, lease period 10000 milliseconds
12:14:33,169 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1049ddf started
12:14:33,184 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
12:14:33,184 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=Cluste
redConnectionFactory but post office is non clustered. So connection factory will *not* support failover
12:14:33,200 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=C
lusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
12:14:33,200 INFO [ConnectionFactory] Connector bisocket://172.20.3.74:4457 has leasing enabled, lease period 10000 milliseconds
12:14:33,200 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@124ed52 started
12:14:33,200 INFO [ConnectionFactory] Connector bisocket://172.20.3.74:4457 has leasing enabled, lease period 10000 milliseconds
12:14:33,216 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@7d83e6 started
12:14:33,216 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
12:14:33,388 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:Jms
XA'
12:14:33,450 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=jdbc/TelemedicinaLocalDS' to JNDI na
me 'java:jdbc/TelemedicinaLocalDS'
12:14:33,482 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
12:14:33,810 INFO [TomcatDeployment] deploy, ctxPath=/services, vfsUrl=TelemedicinaWS.war12:14:34,076 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
12:14:34,185 INFO [Http11Protocol] Arrancando Coyote HTTP/1.1 en puerto http-172.20.3.74-80
12:14:34,201 INFO [AjpProtocol] Arrancando Coyote AJP/1.3 en ajp-172.20.3.74-8009
12:14:34,217 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812042120)] Started in 44s:546ms

With AS5 we need to do something diferent that we did in 4.2.2 and 4.2.3 versions?

thanks in advance.

[jaikiran]

The logs show that your application was deployed. Were you expecting some more log messages? Also when you say WebService, do you mean Axis webservice or JBossWS.

[adesisp]

Is a jbossws webservice and log shows that is deployed, but in jboss 4.2.2 and 4.2.3 log shows that wsdl is available.

if we access to jbossws web menu, nothing appears in services deployed. So the webservice is not deployed.

[jaikiran]

Please provide more details about your application, including relevant part of the webservice code. Also please post the output of

jar -tf TelemedicinaWS.war

I haven't used JBossWS, so don't know what logs you are expecting on the console. Please post the relevant portion of logs (from JBoss-4.2.x) which shows the webservice being deployed.

While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted.

[adesisp]

thakyou very much for the reply.

jboss 4.2.2 log show next:

15:55:15,093 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
15:55:15,250 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=jdbc/TelemedicinaLocalDS' to JNDI name 'j
ava:jdbc/TelemedicinaLocalDS'
15:55:16,187 INFO [DefaultEndpointRegistry] register: jboss.ws:context=services,endpoint=wsTeleHealthRTX
15:55:16,843 INFO [TomcatDeployer] deploy, ctxPath=/services, warUrl=.../tmp/deploy/tmp2563607758009156367TelemedicinaWS-exp.war/
15:55:17,156 INFO [WebappClassLoader] validateJarFile(L:\COPSEG TMNEW\DESARROLLO\jboss-4.2.2.GA\server\default\.\tmp\deploy\tmp2563607758009156367TelemedicinaW
S-exp.war\WEB-INF\lib\javaee.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
15:55:19,156 INFO [WSDLFilePublisher] WSDL published to: file:/L:/COPSEG TMNEW/DESARROLLO/jboss-4.2.2.GA/server/default/data/wsdl/TelemedicinaWS.war/WsTeleHeal
 thRTXService3946147228382537825.wsdl

You can see that webservice is deployed, and wsdl too. And in jbossws web console it apperas as active webservice

in AS5 nothing happens. log show the war is deployed, but it don't deployed, and not appears in web console.

the output of jar -tf is

C:\Archivos de programa\Java\jdk1.6.0_11\bin>jar -tf TelemedicinaWS.war
META-INF/MANIFEST.MF
WEB-INF/classes/
WEB-INF/classes/telehealth/
WEB-INF/classes/telehealth/core/
WEB-INF/classes/telehealth/core/Meassure.class
WEB-INF/classes/telehealth/core/MeassureAM1RTX.class
WEB-INF/classes/telehealth/core/MeassureBPMRTX.class
WEB-INF/classes/telehealth/core/MeassureGLURTX.class
WEB-INF/classes/telehealth/core/MeassureOXIRTX.class
WEB-INF/classes/telehealth/core/Meassures.class
WEB-INF/classes/telehealth/core/MeassureSPRRTX.class
WEB-INF/classes/telehealth/core/MeassureWGSRTX.class
WEB-INF/classes/telehealth/core/MedidaPeso.class
WEB-INF/classes/telehealth/core/MedidaTension.class
WEB-INF/classes/telehealth/core/NivelPrioridadAlerta.class
WEB-INF/classes/telehealth/db/
WEB-INF/classes/telehealth/db/Conexion.class
WEB-INF/classes/telehealth/gestion/
WEB-INF/classes/telehealth/gestion/DispoMedida.class
WEB-INF/classes/telehealth/gestion/Dispositivo.class
WEB-INF/classes/telehealth/gestion/EstadisticaUnidades.class
WEB-INF/classes/telehealth/gestion/GateWay.class
WEB-INF/classes/telehealth/gestion/Localidad.class
WEB-INF/classes/telehealth/gestion/objDB.class
WEB-INF/classes/telehealth/gestion/Perfil.class
WEB-INF/classes/telehealth/gestion/TipoDispositivo.class
WEB-INF/classes/telehealth/gestion/UnidadDispositivo.class
WEB-INF/classes/telehealth/test/
WEB-INF/classes/telehealth/test/PruebaRTXJboss.class
WEB-INF/classes/telehealth/test/PruebaRTXSOAMain.class
WEB-INF/classes/telehealth/test/PruebaRTXSOAP.class
WEB-INF/classes/telehealth/test/pruebasConHilos.class
WEB-INF/classes/telehealth/test/pruebasWSRTX.class
WEB-INF/classes/telehealth/util/
WEB-INF/classes/telehealth/util/Constantes.class
WEB-INF/classes/telehealth/util/DBcommLog.class
WEB-INF/classes/telehealth/util/ExtensionFilter.class
WEB-INF/classes/telehealth/util/Funciones.class
WEB-INF/classes/telehealth/util/Localidad.class
WEB-INF/classes/telehealth/util/SrvLimpiarSession.class
WEB-INF/classes/telehealth/util/TeleHealth.class
WEB-INF/classes/telehealth/util/XmlTag.class
WEB-INF/classes/telehealth/ws/
WEB-INF/classes/telehealth/ws/wsTeleHealth.class
WEB-INF/classes/telehealth/ws/wsTeleHealthRTX.class
WEB-INF/classes/telehealth/ws/wsTeleHealthRTXImpl.class
WEB-INF/classes/telehealth/xml/
WEB-INF/classes/telehealth/xml/MensajeXML.class
WEB-INF/classes/telehealth/xml/MensajeXMLImpl.class
WEB-INF/classes/telehealth/xml/MensajeXMLRTX.class
WEB-INF/classes/telehealth/xml/MensajeXMLTH.class
WEB-INF/
WEB-INF/jboss-web.xml
WEB-INF/web.xml
WEB-INF/lib/javaee.jar
WEB-INF/lib/log4j-1.2.8.jar
WEB-INF/lib/commons-lang-2.1.jar
WEB-INF/lib/ojdbc14.jar

[peterj]

Remove these files from your WAR:

WEB-INF/lib/javaee.jar
WEB-INF/lib/log4j-1.2.8.jar

JBoss AS already provides them and they could be interfering with the deployment.

I checked one of my web services in 5.0.0.GA, and the WSDLFilePublisher log entry shows up.

If the above does not solve the issue, post the source code for the web service class (just the class definition, web service method definitions, and their annotations is sufficient (you can remove the method code, fields, comments), and post the web.xml and jboss-web.xml file.

[adesisp]

Thanks Peter, it works now.

In jboss422 and jboss423 the server automaticaly disable this two librarys, but AS5 don't disabled them, and then tomcat_deployer don't load the webservice.

Thanks you very much!

[peterj]

The deployers underwent a radical overhaul in 5.0. I suspect that in 4.2.x that the JBoss JARs appeared earlier in the classpath than the JARs you packaged, but in 5.0 it was the other way around.