[JBossWS] - Web service parameters are always null
by ppollard
I have a web service running on JBoss 4.2.1.GA. I have two different clients consuming the service. The 1st client is Remedy, a 3rd party service management application. Using tcpmon, I captured the SOAP document coming across. Here it is:
POST /remedyAbstractService/remedyAbstractService_1_0 HTTP/1.0
| Content-Type: text/xml; charset=utf-8
| Accept: application/soap+xml, application/dime, multipart/related, text/*
| User-Agent: Axis/1.1
| Host: phpoll0905:8666
| Cache-Control: no-cache
| Pragma: no-cache
| SOAPAction: ""
| Content-Length: 1065
|
| <?xml version="1.0" encoding="UTF-8"?>
| <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
| <soapenv:Body><sendTicketRequestToPartner xmlns="http://MY_COMPANY.com/remedyAbstractService_1_0/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
| <remedyUserID>MY_USER</remedyUserID>
| <remedyPassword>MY_PASS</remedyPassword>
| <remedyTransactionCode>60</remedyTransactionCode>
| <remedyTPSID>00000002600</remedyTPSID>
| <remedyTicketNumber>ATS01994267</remedyTicketNumber>
| <partner>Initech</partne>
| <partnerTicketNumber>ats11111</partnerTicketNumber>
| <technicalNotes>2/19/2007 4:58:28 PM
| 2/19/2007 4:50:33 PM asdfasdfasdfasdf 2/17/2006 3:15:24 PM iswebsvc tech notes
| </technicalNotes>
| <closedCode>my closed code</closedCode>
| <resolvedBy>guy who fixed it</resolvedBy>
| <solution>my solution</solution>
| </sendTicketRequestToPartner> </soapenv:Body>
| </soapenv:Envelope>
With this request, all of the parameters of the web service are null. The client calls the web service successfully, but the parms are always null, even though values are being specified for each field, as you can see in the document above.
I've also created a standard .NET client to consume the same service. When running it, the values from the client do reach the web service. The request SOAP document looks like this:
| POST /remedyAbstractService/remedyAbstractService_1_0 HTTP/1.1
| User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407)
| Content-Type: text/xml; charset=utf-8
| SOAPAction: ""
| Content-Length: 1014
| Expect: 100-continue
| Connection: Keep-Alive
| Host: phpoll0905:8666
|
| <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><sendTicketRequestToPartner xmlns="http://MY_COMPANY.com/remedyAbstractService_1_0/types"><remedyUserID xmlns="">MY_USER</remedyUserID><remedyPassword xmlns="">MY_PASS</remedyPassword><remedyTransactionCode xmlns="">60</remedyTransactionCode><remedyTPSID xmlns="">00000002600</remedyTPSID><remedyTicketNumber xmlns="">ATS01994267</remedyTicketNumber><partner xmlns="">Initech</partner><partnerTicketNumber xmlns="">ats11111</partnerTicketNumber><technicalNotes xmlns="">2/19/2007 4:58:28 PM 2/19/2007 4:50:33 PM asdfasdfasdfasdf 2/17/2006 3:15:24 PM iswebsvc tech notes</technicalNotes><closedCode xmlns="">my closed code</closedCode><resolvedBy xmlns="">guy who fixed it</resolvedBy><solution xmlns="">my solution</solution></sendTicketRequestToPartner></soap:Body></soap:Envelope>
Why does the 2nd document work, yet the 1st one does not?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092615#4092615
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092615
17 years, 1 month
[JBossWS] - Client side memory leak?
by m0hmad
Hello,
I've got EJBs that operates in proxy mode. They just pass thru requests parameters to JBossWS Client implementation and redirect responses back.
All WS artifacts, service and endpoints have been generated with wsconsume tool. Soap endpoints are exposed like:
public class SoapServicesFactory {
|
| static private Content contentSoap; // the SOAP client
|
| static public synchronized ContentSoap getContentSoap() {
| if (null == contentSoap)
| contentSoap = new Content();
| return contentSoap.getContentSoap();
| }
| }
The endpoint released right after first remote method invoked, no storing or caching etc being performed.
The problem is, ALL artifacts retrieved from WSs as responses will never released by Garbage Collector and sooner or later there Java heap Space criticall error will be.
Utilizing profiler I can see that artifacts retained by instances of several classes:
- org.jboss.ws.core.soap.ObjectContent
- org.jboss.ws.coreEndpointInvocation
- java.lang.Object
Changing endpoint exposing to:
return (new MobileContent()).getMobileContentSoap();
removes the memory leakage but the service works too slowly cos instantiation of Soap Service is too expensive procedure.
Can anybody help me with this issue?
Looking forward for any response.
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092530#4092530
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092530
17 years, 1 month
[JBossWS] - Upgrade to JBossWS 2 - Failed to find META-INF/jboss-service
by panagiotis.kammas
Pls help...
I have downloaded JBoss 4.2 GA which starts ok.
Then i tried to upgrade the iJBossWS to 2.0GA, which seemed ok
<<<---Log upgrading JBossWS------
C:\genesis\dev\jbossws-native-2.0.0.GA>ant deploy-jboss50
Buildfile: build.xml
prepare:
undeploy-jboss50:
[delete] Deleting 8 files from C:\genesis\dev\jboss-4.2.0.GA\bin
[delete] Deleting 9 files from C:\genesis\dev\jboss-4.2.0.GA\client
[delete] Deleting 3 files from C:\genesis\dev\jboss-4.2.0.GA\server\default\l
ib
[delete] Deleting directory C:\genesis\dev\jboss-4.2.0.GA\server\default\depl
oy\jbossws.sar
deploy-jboss50-endorsed:
deploy-jboss50:
[unzip] Expanding: C:\genesis\dev\jbossws-native-2.0.0.GA\lib\jbossws-core-s
cripts.zip into C:\genesis\dev\jboss-4.2.0.GA\bin
[copy] Copying 14 files to C:\genesis\dev\jboss-4.2.0.GA\client
[copy] Copying 2 files to C:\genesis\dev\jboss-4.2.0.GA\lib
[copy] Copying 4 files to C:\genesis\dev\jboss-4.2.0.GA\server\default\lib
[mkdir] Created dir: C:\genesis\dev\jboss-4.2.0.GA\server\default\deployers\
jbossws.deployer
[unzip] Expanding: C:\genesis\dev\jbossws-native-2.0.0.GA\lib\jbossws-native
50-deployer.zip into C:\genesis\dev\jboss-4.2.0.GA\server\default\deployers\jbos
sws.deployer
[mkdir] Created dir: C:\genesis\dev\jboss-4.2.0.GA\server\default\deploy\jbo
ssws.sar
[unjar] Expanding: C:\genesis\dev\jbossws-native-2.0.0.GA\lib\jbossws-native
50.sar into C:\genesis\dev\jboss-4.2.0.GA\server\default\deploy\jbossws.sar
[mkdir] Created dir: C:\genesis\dev\jboss-4.2.0.GA\server\default\deploy\jud
di-service.sar
[unzip] Expanding: C:\genesis\dev\jbossws-native-2.0.0.GA\lib\juddi-service.
sar into C:\genesis\dev\jboss-4.2.0.GA\server\default\deploy\juddi-service.sar
[unzip] Expanding: C:\genesis\dev\jbossws-native-2.0.0.GA\lib\jbossws-spi-sc
ripts.zip into C:\genesis\dev\jboss-4.2.0.GA\bin
[copy] Copying 1 file to C:\genesis\dev\jboss-4.2.0.GA\client
[copy] Copying 1 file to C:\genesis\dev\jboss-4.2.0.GA\server\default\lib
BUILD SUCCESSFUL
Total time: 2 seconds
---Log upgrading JBossWS------>>>
The above has been tried with jdk 1.6.0 and jdk 1.5.0 with the same results
Then when i try to start JBoss (again with both JDKs) i get the following exception on startup (Failed to find META-INF/jboss-service.xml for archive jbossws.sar). Can you please help? There is no such file in this path. How can i overcome this problem?
<<<----Exception during startup---
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\genesis\dev\jboss-4.2.0.GA
JAVA: C:\genesis\dev\jdk1.5.0-b64\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli
ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: C:\genesis\dev\jdk1.5.0-b64\lib\tools.jar;C:\genesis\dev\jboss-4.2.
0.GA\bin\run.jar
===============================================================================
22:29:42,781 INFO [Server] Starting JBoss (MX MicroKernel)...
22:29:42,781 INFO [Server] Release ID: JBoss [Trinity] 4.2.0.GA (build: SVNTag=
JBoss_4_2_0_GA date=200705111440)
22:29:42,781 INFO [Server] Home Dir: C:\genesis\dev\jboss-4.2.0.GA
22:29:42,781 INFO [Server] Home URL: file:/C:/genesis/dev/jboss-4.2.0.GA/
22:29:42,781 INFO [Server] Patch URL: null
22:29:42,781 INFO [Server] Server Name: default
22:29:42,781 INFO [Server] Server Home Dir: C:\genesis\dev\jboss-4.2.0.GA\serve
r\default
22:29:42,781 INFO [Server] Server Home URL: file:/C:/genesis/dev/jboss-4.2.0.GA
/server/default/
22:29:42,781 INFO [Server] Server Log Dir: C:\genesis\dev\jboss-4.2.0.GA\server
\default\log
22:29:42,781 INFO [Server] Server Temp Dir: C:\genesis\dev\jboss-4.2.0.GA\serve
r\default\tmp
22:29:42,781 INFO [Server] Root Deployment Filename: jboss-service.xml
22:29:43,171 INFO [ServerInfo] Java version: 1.5.0,Sun Microsystems Inc.
22:29:43,171 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0-b64,Su
n Microsystems Inc.
22:29:43,171 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
22:29:44,171 INFO [Server] Core system initialized
22:29:48,484 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
/
22:29:48,484 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:jboss-log4j.xml
22:29:49,640 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
version) - JBoss Inc.
22:29:49,640 INFO [TransactionManagerService] Setting up property manager MBean
and JMX layer
22:29:50,015 INFO [TransactionManagerService] Starting recovery manager
22:29:50,359 INFO [TransactionManagerService] Recovery manager started
22:29:50,359 INFO [TransactionManagerService] Binding TransactionManager JNDI R
eference
22:29:57,593 INFO [EJB3Deployer] Starting java:comp multiplexer
22:29:59,031 ERROR [MainDeployer] Could not initialise deployment: file:/C:/gene
sis/dev/jboss-4.2.0.GA/server/default/deploy/jbossws.sar/
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.
xml for archive jbossws.sar
at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:616)
at org.jboss.deployment.SARDeployer.init(SARDeployer.java:181)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
22:30:03,031 INFO [AprLifecycleListener] The Apache Tomcat Native library which
allows optimal performance in production environments was not found on the java
.library.path: C:\genesis\dev\jdk1.5.0-b64\bin;.;D:\WINDOWS\System32;D:\WINDOWS;
%ANT_HOME%\bin;C:\genesis\dev\jdk1.6.0\bin;D:\WINDOWS\system32;D:\WINDOWS;D:\WIN
DOWS\System32\Wbem;D:\Program Files\Microsoft SQL Server\80\Tools\BINN;D:\Progra
m Files\QuickTime\QTSystem\;C:\genesis\dev\jdk1.5.0-b64\bin;C:\dev\appfuse\Tools
\apache-ant-1.6.5\bin;
22:30:04,671 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0
.1-8080
22:30:04,671 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80
09
22:30:04,671 INFO [Catalina] Initialization processed in 2133 ms
22:30:04,671 INFO [StandardService] Starting service jboss.web
22:30:04,671 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.GA
22:30:04,828 INFO [Catalina] Server startup in 154 ms
22:30:04,968 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w
eb.deployer/ROOT.war/
22:30:06,765 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
http-invoker.sar/invoker.war/
22:30:07,343 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../
deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
22:30:07,562 INFO [TomcatDeployer] deploy, ctxPath=/juddi, warUrl=.../deploy/ju
ddi-service.sar/juddi.war/
22:30:08,000 INFO [RegistryServlet] Loading jUDDI configuration.
22:30:08,000 INFO [RegistryServlet] Resources loaded from: /WEB-INF/juddi.prope
rties
22:30:08,000 INFO [RegistryServlet] Initializing jUDDI components.
22:30:09,734 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep
loy/management/console-mgr.sar/web-console.war/
22:30:10,937 INFO [MailService] Mail Service bound to java:/Mail
22:30:11,437 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-local-jdbc.rar
22:30:11,484 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-xa-jdbc.rar
22:30:11,656 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-local-jdbc.rar
22:30:12,015 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-xa-jdbc.rar
22:30:12,125 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jms/jms-ra.rar
22:30:12,187 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/quartz-ra.rar
22:30:12,218 INFO [QuartzResourceAdapter] start quartz!!!
22:30:12,296 INFO [SimpleThreadPool] Job execution threads will use class loade
r of thread: main
22:30:12,328 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
22:30:12,328 INFO [RAMJobStore] RAMJobStore initialized.
22:30:12,328 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule
r' initialized from default resource file in Quartz package: 'quartz.properties'
22:30:12,328 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
22:30:12,328 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
22:30:13,140 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
22:30:13,453 INFO [A] Bound to JNDI name: queue/A
22:30:13,453 INFO [B] Bound to JNDI name: queue/B
22:30:13,500 INFO [C] Bound to JNDI name: queue/C
22:30:13,515 INFO [D] Bound to JNDI name: queue/D
22:30:13,515 INFO [ex] Bound to JNDI name: queue/ex
22:30:13,531 INFO [testTopic] Bound to JNDI name: topic/testTopic
22:30:13,531 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
22:30:13,546 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
22:30:13,546 INFO [testQueue] Bound to JNDI name: queue/testQueue
22:30:13,593 INFO [UILServerILService] JBossMQ UIL service available at : /127.
0.0.1:8093
22:30:13,640 INFO [DLQ] Bound to JNDI name: queue/DLQ
22:30:14,375 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
22:30:14,484 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
loy/jmx-console.war/
22:30:14,968 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@658782f0 { url=file:/C:/genesis/dev/jboss-4.
2.0.GA/server/default/deploy/jbossws.sar/ }
deployer: org.jboss.deployment.SARDeployer@164dbd5
status: null
state: FAILED
watch: file:/C:/genesis/dev/jboss-4.2.0.GA/server/default/deploy/jbossws.sar/M
ETA-INF/jboss-service.xml
altDD: null
lastDeployed: 1191785399031
lastModified: 1191785272140
mbeans:
22:30:15,281 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
080
22:30:15,312 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
22:30:15,343 INFO [Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBos
s_4_2_0_GA date=200705111440)] Started in 32s:562ms
----Exception during startup--->>>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092349#4092349
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092349
17 years, 1 month