[JBossWS] - Jboss ActiveBPEL deployment error
by j_gohel
Hello,
I am using Jboss 4.0.2.
I have created and placed ActiveBPEL.ear file in server/default/deploy folder which will invoking my webservices.
I am getting following deployment error when accessing Deployed Processes on BpelAdmin screen (http://localhost:8080/BpelAdmin):
17:52:45,763 INFO [STDOUT] Jul 2, 2008 5:52:45 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logError
| SEVERE: Unable to deploy: file:/D:/jboss-4.0.2/server/default/bpr/AeEngineAdmin.wsr
Following is the console log for reference:
===============================================================================
| . STARTING THE JBOSS...
| .
| JBoss Bootstrap Environment
| .
| JBOSS_HOME: D:\jboss-4.0.2\bin\\..
| .
| JAVA: C:\j2sdk1.4.2_13\bin\java
| .
| JAVA_OPTS: -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=5555,server=y,suspend=n -Dpro
| gram.name=run_emvolve.bat -Xms768m -Xmx1024m -Dconfig.installDir=D:/servers/config/etc -Dpx.sc.cache=D:\servers\scoreca
| rd -Djava.security.policy=D:/jboss-4.0.2/server/default/conf/server.policy -Dbpr.home=D:\jboss-4.0.2\server\default -Dws
| .port=8080
| .
| CLASSPATH: C:\j2sdk1.4.2_13\lib\tools.jar;D:\jboss-4.0.2\bin\\run.jar;D:/servers/config/etc;emvolve4.x.zip
| .
| ===============================================================================
| .
| 17:51:51,794 INFO [Server] Starting JBoss (MX MicroKernel)...
| 17:51:51,794 INFO [Server] Release ID: JBoss [Zion] 4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)
| 17:51:51,794 INFO [Server] Home Dir: D:\jboss-4.0.2
| 17:51:51,794 INFO [Server] Home URL: file:/D:/jboss-4.0.2/
| 17:51:51,794 INFO [Server] Library URL: file:/D:/jboss-4.0.2/lib/
| 17:51:51,794 INFO [Server] Patch URL: null
| 17:51:51,794 INFO [Server] Server Name: default
| 17:51:51,794 INFO [Server] Server Home Dir: D:\jboss-4.0.2\server\default
| 17:51:51,794 INFO [Server] Server Home URL: file:/D:/jboss-4.0.2/server/default/
| 17:51:51,794 INFO [Server] Server Data Dir: D:\jboss-4.0.2\server\default\data
| 17:51:51,794 INFO [Server] Server Temp Dir: D:\jboss-4.0.2\server\default\tmp
| 17:51:51,810 INFO [Server] Server Config URL: file:/D:/jboss-4.0.2/server/default/conf/
| 17:51:51,810 INFO [Server] Server Library URL: file:/D:/jboss-4.0.2/server/default/lib/
| 17:51:51,810 INFO [Server] Root Deployment Filename: jboss-service.xml
| 17:51:51,810 INFO [Server] Starting General Purpose Architecture (GPA)...
| 17:51:52,263 INFO [ServerInfo] Java version: 1.4.2_13,Sun Microsystems Inc.
| 17:51:52,263 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_13-b06,Sun Microsystems Inc.
| 17:51:52,263 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
| 17:51:53,232 INFO [Server] Core system initialized
| 17:52:04,341 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
| 17:52:04,482 INFO [WebService] Using RMI server codebase: http://rte-2256094b625:8083/
| 17:52:04,763 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0,
| Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
| 17:52:09,154 INFO [Embedded] Catalina naming disabled
| 17:52:09,951 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
| 17:52:09,951 INFO [Catalina] Initialization processed in 672 ms
| 17:52:09,951 INFO [StandardService] Starting service jboss.web
| 17:52:09,966 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.9
| 17:52:10,044 INFO [StandardHost] XML validation disabled
| 17:52:10,091 INFO [Catalina] Server startup in 140 ms
| 17:52:10,326 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/D:/jboss-4.0.2/server/default/deploy/http-inv
| oker.sar/invoker.war/
| 17:52:11,935 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/D:/jboss-4.0.2/server/default/deploy/jbossweb-tomcat
| 55.sar/ROOT.war/
| 17:52:12,294 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/D:/jboss-4.0.2/server/default/deploy/j
| ms/jbossmq-httpil.sar/jbossmq-httpil.war/
| 17:52:15,498 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/D:/jboss-4.0.2/server/default/deploy/mana
| gement/console-mgr.sar/web-console.war/
| 17:52:16,763 INFO [MailService] Mail Service bound to java:/Mail
| 17:52:17,654 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/jboss-4.0.2/server/de
| fault/deploy/jboss-ha-local-jdbc.rar
| 17:52:17,857 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/jboss-4.0.2/server/de
| fault/deploy/jboss-ha-xa-jdbc.rar
| 17:52:18,029 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/jboss-4.0.2/server/de
| fault/deploy/jboss-local-jdbc.rar
| 17:52:18,216 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/jboss-4.0.2/server/de
| fault/deploy/jboss-xa-jdbc.rar
| 17:52:18,373 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/jboss-4.0.2/server/de
| fault/deploy/jms/jms-ra.rar
| 17:52:18,529 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/jboss-4.0.2/server/de
| fault/deploy/mail-ra.rar
| 17:52:19,435 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
| .jca:name=jdbc/DataSource,service=DataSourceBinding to JNDI name 'java:jdbc/DataSource'
| 17:52:19,498 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
| .jca:name=emvolveds,service=DataSourceBinding to JNDI name 'java:emvolveds'
| 17:52:19,544 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
| .jca:name=recruitmentds,service=DataSourceBinding to JNDI name 'recruitmentds'
| 17:52:19,576 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
| .jca:name=configurationsds,service=DataSourceBinding to JNDI name 'configurationsds'
| 17:52:19,654 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
| .jca:name=appraisalmanagerds,service=DataSourceBinding to JNDI name 'appraisalmanagerds'
| 17:52:19,685 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
| .jca:name=insightds,service=DataSourceBinding to JNDI name 'insightds'
| 17:52:21,123 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
| .jca:name=DefaultDS,service=DataSourceBinding to JNDI name 'java:DefaultDS'
| 17:52:21,732 INFO [p4mix_Determination] Bound to JNDI name: topic/p4mix_Determination
| 17:52:21,732 INFO [userManagementTopic] Bound to JNDI name: topic/userManagementTopic
| 17:52:21,732 INFO [importExportResultTopic] Bound to JNDI name: topic/importExportResultTopic
| 17:52:21,763 INFO [importExportControlQueue] Bound to JNDI name: queue/importExportControlQueue
| 17:52:21,779 INFO [A] Bound to JNDI name: queue/A
| 17:52:21,779 INFO [B] Bound to JNDI name: queue/B
| 17:52:21,779 INFO [C] Bound to JNDI name: queue/C
| 17:52:21,779 INFO [D] Bound to JNDI name: queue/D
| 17:52:21,794 INFO [ex] Bound to JNDI name: queue/ex
| 17:52:21,841 INFO [testTopic] Bound to JNDI name: topic/testTopic
| 17:52:21,841 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
| 17:52:21,841 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
| 17:52:21,857 INFO [testQueue] Bound to JNDI name: queue/testQueue
| 17:52:21,982 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
| 17:52:22,091 INFO [DLQ] Bound to JNDI name: queue/DLQ
| 17:52:22,435 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManager
| 'jboss.jca:name=JmsXA,service=ConnectionFactoryBinding to JNDI name 'java:JmsXA'
| 17:52:22,607 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
| .jca:name=jdbc/LiferayPool,service=DataSourceBinding to JNDI name 'java:jdbc/LiferayPool'
| 17:52:22,794 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss
| .jca:name=ReactorDS,service=DataSourceBinding to JNDI name 'java:ReactorDS'
| 17:52:22,873 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/D:/jboss-4.0.2/server/default/deploy/jmx-
| console.war/
| 17:52:23,279 INFO [EARDeployer] Init J2EE application: file:/D:/jboss-4.0.2/server/default/deploy/ActiveBPEL.ear
| 17:52:24,732 INFO [TomcatDeployer] deploy, ctxPath=/BpelAdmin, warUrl=file:/D:/jboss-4.0.2/server/default/tmp/deploy/tm
| p47518ActiveBPEL.ear-contents/BpelAdmin-exp.war/
| 17:52:25,091 INFO [TomcatDeployer] deploy, ctxPath=/BpelAdminHelp, warUrl=file:/D:/jboss-4.0.2/server/default/tmp/deplo
| y/tmp47518ActiveBPEL.ear-contents/BpelAdminHelp-exp.war/
| 17:52:25,341 INFO [TomcatDeployer] deploy, ctxPath=/active-bpel, warUrl=file:/D:/jboss-4.0.2/server/default/tmp/deploy/
| tmp47518ActiveBPEL.ear-contents/active-bpel-exp.war/
| 17:52:27,623 INFO [STDOUT] Jul 2, 2008 5:52:27 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet initAxisServer
|
| INFO: Initialized Axis Server
| 17:52:27,685 INFO [STDOUT] Jul 2, 2008 5:52:27 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet init
| INFO: Active BPEL startup
| 17:52:27,732 INFO [STDOUT] Jul 2, 2008 5:52:27 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logInfo
| INFO: Loaded config file from D:\jboss-4.0.2\server\default\bpr\aeEngineConfig.xml
| 17:52:30,638 INFO [STDOUT] Jul 2, 2008 5:52:30 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logInfo
| INFO: ********** Persistent Configuration Initialized
| 17:52:30,794 INFO [EARDeployer] Started J2EE application: file:/D:/jboss-4.0.2/server/default/deploy/ActiveBPEL.ear
| 17:52:30,982 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
| 17:52:31,248 INFO [JkMain] Jk running ID=0 time=0/110 config=null
| 17:52:31,279 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)] Started in 39s:
| 469ms
| 17:52:45,732 INFO [STDOUT] Jul 2, 2008 5:52:45 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logInfo
| INFO: [AeEngineAdmin.wsr] Starting WebServices deployment.
| 17:52:45,732 INFO [STDOUT] Jul 2, 2008 5:52:45 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logInfo
| INFO: [AeEngineAdmin.wsr] Deploying META-INF\service.wsdd
| 17:52:45,763 INFO [STDOUT] Jul 2, 2008 5:52:45 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logError
| SEVERE: Unable to deploy: file:/D:/jboss-4.0.2/server/default/bpr/AeEngineAdmin.wsr
| 17:52:45,857 INFO [STDOUT] Jul 2, 2008 5:52:45 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logInfo
| INFO: [appraisal.wsr] Starting WebServices deployment.
| 17:52:45,857 INFO [STDOUT] Jul 2, 2008 5:52:45 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logInfo
| INFO: [appraisal.wsr] Deploying service.wsdd
| 17:52:45,982 INFO [STDOUT] Jul 2, 2008 5:52:45 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logInfo
| INFO: [appraisal.wsr] Finished WebServices deployment.
| 17:52:46,076 INFO [STDOUT] Jul 2, 2008 5:52:46 PM org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger
| logInfo
| INFO: ********** Persistent Configuration Started
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162049#4162049
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162049
17 years, 9 months
[JBoss Portal] - WARN [LoadContexts] fail-safe cleanup
by Subemontes
Hi. wanna know if this warning is a dangerous one.
Here's the Code.14:40:01,602 WARN [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@1749a
| 5d<rs=org.hsqldb.jdbc.jdbcResultSet@129df0e>
| 14:40:01,664 WARN [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@42755
| 8<rs=org.hsqldb.jdbc.jdbcResultSet@1bc00fb>
| 14:40:01,711 WARN [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@13778
| bc<rs=org.hsqldb.jdbc.jdbcResultSet@1e2d7ab>
| 14:40:01,774 WARN [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@1ee63
| 4f<rs=org.hsqldb.jdbc.jdbcResultSet@42d317>
|
It shows in console each time a user click on any link of the main portal Web (the /portal one).
Seems that is "related" to the DB, but, in what aspect ?
Thanks for the help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162044#4162044
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162044
17 years, 9 months
[JCA/JBoss] - JCA concurrent acces to ManagedConnection problem
by pierre.brico
Hello,
I'm using jBoss 4.2.2GA with jdk 1.5.0_12.
For my transactional monitor (a Tuxedo clone but a little faster :-)), I'm developing a JCA connector based on JCA specifications 1.0. Until now, everything was working fine until I tried to add XA functionality.
When jBoss is under stress, it seems that ManagedConnections can be used concurrently by 2 (or more) separated threads. As my implementation of ManagedConnection isn't thread-safe, I have troubles.
Is it normal that a ManagedConnection can be used by several threads ? I thought the pooling mechanism was built to avoid such cases.
I give you my trace just in case of I'm wrong in interpreting it. I add the thread id to the log4j pattern to known from which thread the message is coming from. As you can see, the thread http-7 is performing those steps:
1- gets the ManagedConnection@468c66b6 from the pool
2- sends message 548 (xa_start)
3- gets response 548 (XA_OK)
4- sends message 551 (service call)
5- gets response 551 (call OK)
6- sends message 559 (xa_end(TM_SUSPEND))
7- gets response 559 (XA_OK)
8- puts the ManagedConnection@468c66b6 back to the pool
9- sends message 560 (xa_end(TM_SUCCESS))
10- gets wrong response (overwrite by response) !!!!
Between step 9 and 10 of thread http-7, thread http-4 gets the same ManagedConnection@468c66b6 from the pool and begins its work:
1- gets the ManagedConnection@468c66b6 from the pool
2- sends message 561 (xa_start)
3- gets wrong response (overwrite by response 560) !!!!
I noticed that the problem always comes from XA orders sent after the ManagedConnection is returned to the pool.
Please help me.
Thanks in advance,
Pierre Brico
13:56:17,897-http-172.18.4.104-8180-7 TRACE [JBossManagedConnectionPool] supplying ManagedConnection from pool: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999777767 permit=false trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null]
13:56:17,898-http-172.18.4.104-8180-7 TRACE [JBossManagedConnectionPool] Got connection from pool org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999777767 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null] [InUse/Available/Max]: [1/19/20]
13:56:17,898-http-172.18.4.104-8180-7 TRACE [TxConnectionManager] Pre-enlist: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999777767 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null] threadTx=TransactionImple < ac, BasicAction: -53edfb98:e7a2:486b6b91:2abf status: ActionStatus.RUNNING >
13:56:17,898-http-172.18.4.104-8180-7 TRACE [TxConnectionManager] Get synchronizer org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999777767 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null] threadTx=TransactionImple < ac, BasicAction: -53edfb98:e7a2:486b6b91:2abf status: ActionStatus.RUNNING >
13:56:17,898-http-172.18.4.104-8180-7 TRACE [TxConnectionManager] Enlisting resource org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999777767 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=TxSync731292857{tx=TransactionImple < ac, BasicAction: -53edfb98:e7a2:486b6b91:2abf status: ActionStatus.RUNNING > wasTrackByTx=false enlisted=false}]
13:56:17,899-http-172.18.4.104-8180-7 INFO [STDOUT] Sent header 548 tsdjca.TSDManagedConnection@468c66b6
13:56:17,900-http-172.18.4.104-8180-7 INFO [STDOUT] Sent body 548 tsdjca.TSDManagedConnection@468c66b6
13:56:17,980-http-172.18.4.104-8180-7 INFO [STDOUT] Received header 548 tsdjca.TSDManagedConnection@468c66b6
13:56:17,980-http-172.18.4.104-8180-7 INFO [STDOUT] Received body 548 tsdjca.TSDManagedConnection@468c66b6
13:56:17,980-http-172.18.4.104-8180-7 TRACE [TxConnectionManager] Enlisted resource org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999777767 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=TxSync731292857{tx=TransactionImple < ac, BasicAction: -53edfb98:e7a2:486b6b91:2abf status: ActionStatus.RUNNING > wasTrackByTx=false enlisted=false}]
13:56:17,980-http-172.18.4.104-8180-7 TRACE [TxConnectionManager] Check enlisted org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999777767 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=TxSync731292857{tx=TransactionImple < ac, BasicAction: -53edfb98:e7a2:486b6b91:2abf status: ActionStatus.RUNNING > wasTrackByTx=false enlisted=true}] threadTx=TransactionImple < ac, BasicAction: -53edfb98:e7a2:486b6b91:2abf status: ActionStatus.RUNNING >
13:56:17,983-http-172.18.4.104-8180-7 INFO [STDOUT] Sent header 551 tsdjca.TSDManagedConnection@468c66b6
13:56:17,999-http-172.18.4.104-8180-7 INFO [STDOUT] Sent body 551 tsdjca.TSDManagedConnection@468c66b6
13:56:18,378-http-172.18.4.104-8180-7 INFO [STDOUT] Received header 551 tsdjca.TSDManagedConnection@468c66b6
13:56:18,442-http-172.18.4.104-8180-7 INFO [STDOUT] Received body 551 tsdjca.TSDManagedConnection@468c66b6
13:56:18,448-http-172.18.4.104-8180-7 TRACE [TxConnectionManager] connectionClosed called mc=tsdjca.TSDManagedConnection@468c66b6
13:56:18,448-http-172.18.4.104-8180-7 TRACE [TxConnectionManager] isManagedConnectionFree=true mc=tsdjca.TSDManagedConnection@468c66b6
13:56:18,448-http-172.18.4.104-8180-7 TRACE [TxConnectionManager] delisting org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999777767 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=TxSync731292857{tx=TransactionImple < ac, BasicAction: -53edfb98:e7a2:486b6b91:2abf status: ActionStatus.RUNNING > wasTrackByTx=false enlisted=true}]
13:56:18,449-http-172.18.4.104-8180-7 INFO [STDOUT] Sent header 559 tsdjca.TSDManagedConnection@468c66b6
13:56:18,450-http-172.18.4.104-8180-7 INFO [STDOUT] Sent body 559 tsdjca.TSDManagedConnection@468c66b6
13:56:18,719-http-172.18.4.104-8180-7 INFO [STDOUT] Received header 559 tsdjca.TSDManagedConnection@468c66b6
13:56:18,720-http-172.18.4.104-8180-7 INFO [STDOUT] Received body 559 tsdjca.TSDManagedConnection@468c66b6
13:56:18,720-http-172.18.4.104-8180-7 TRACE [JBossManagedConnectionPool] putting ManagedConnection back into pool kill=false cl=org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999777767 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null]
13:56:18,720-http-172.18.4.104-8180-7 TRACE [JBossManagedConnectionPool] Returning connection to pool org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999778720 permit=false trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null] [InUse/Available/Max]: [2/18/20]
13:56:18,720-http-172.18.4.104-8180-7 INFO [STDOUT] Sent header 560 tsdjca.TSDManagedConnection@468c66b6
13:56:18,722-http-172.18.4.104-8180-7 INFO [STDOUT] Sent body 560 tsdjca.TSDManagedConnection@468c66b6
13:56:18,783-http-172.18.4.104-8180-4 TRACE [JBossManagedConnectionPool] supplying ManagedConnection from pool: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999778720 permit=false trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null]
13:56:18,783-http-172.18.4.104-8180-4 TRACE [JBossManagedConnectionPool] Got connection from pool org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999778720 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null] [InUse/Available/Max]: [3/17/20]
13:56:18,784-http-172.18.4.104-8180-4 TRACE [TxConnectionManager] No transaction, no need to enlist: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999778720 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null]
13:56:18,786-http-172.18.4.104-8180-4 INFO [STDOUT] Sent header 561 tsdjca.TSDManagedConnection@468c66b6
13:56:18,791-http-172.18.4.104-8180-4 INFO [STDOUT] Sent body 561 tsdjca.TSDManagedConnection@468c66b6
13:56:18,990-http-172.18.4.104-8180-7 INFO [STDOUT] Received header 560 tsdjca.TSDManagedConnection@468c66b6
13:56:28,979-http-172.18.4.104-8180-4 INFO [STDOUT] Received header 12293 tsdjca.TSDManagedConnection@468c66b6
13:56:28,980-http-172.18.4.104-8180-4 TRACE [TxConnectionManager] connectionClosed called mc=tsdjca.TSDManagedConnection@468c66b6
13:56:28,980-http-172.18.4.104-8180-4 TRACE [TxConnectionManager] isManagedConnectionFree=true mc=tsdjca.TSDManagedConnection@468c66b6
13:56:28,980-http-172.18.4.104-8180-4 TRACE [TxConnectionManager] delisting org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999778720 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null]
13:56:28,980-http-172.18.4.104-8180-4 TRACE [JBossManagedConnectionPool] putting ManagedConnection back into pool kill=false cl=org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999778720 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null]
13:56:28,980-http-172.18.4.104-8180-4 TRACE [JBossManagedConnectionPool] Returning connection to pool org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@284ac3e1[state=NORMAL mc=tsdjca.TSDManagedConnection@468c66b6 handles=0 lastUse=1214999788980 permit=false trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@2be8ac6f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@3890c1ee xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@4481fd71 txSync=null] [InUse/Available/Max]: [5/15/20]
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162043#4162043
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162043
17 years, 9 months