0 Replies Latest reply on Jan 23, 2012 5:18 AM by kelevra

pooled-connection-factories and queues not bounded at JBoss startup

kelevra Jan 23, 2012 5:18 AM

Hi all,

I’m currently blocked with my messaging configuration in JBoss AS 7.1.0 RC1B.

I’m using the default configuration file standalone.xml, modified for our project, but it seems that some problems occur when I’m starting the server.

My pooled-connection-factory does not appear in the JBoss’s web console and if I restart the server, my standalone.xml is overridden by JBoss, using its current console state, so this means that my pooled-connection-factory disappears.

Because it not appears in the web console, all my queues and topics not appear too and are overridden too in my standalone.xml after stopping the server.

To solve the problem I have defined a normal connection-factory to keep my queues in my configuration because it seems that no one pooled-connection-factory is bounded at server’s startup as you can see on the following log and if I don't set a fake connection-factory, no one factory will be present and the queues will be bounded :

Calling "D:\Development\Servers\JBoss.AS.7.1.0.RC1B\bin\standalone.conf.bat"

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

JBoss Bootstrap Environment

JBOSS_HOME: D:\Development\Servers\JBoss.AS.7.1.0.RC1B

JAVA: C:\Program Files\Java\jdk1.6.0_27\bin\java

JAVA_OPTS: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -server

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

09:57:22,228 INFO [org.jboss.modules] JBoss Modules version 1.1.0.CR6

09:57:22,419 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA

09:57:22,457 INFO [org.jboss.as] JBoss AS 7.1.0.CR1b "Flux Capacitor" starting

09:57:23,019 INFO [org.jboss.as] Creating http management service using socket-binding (management-http)

09:57:23,021 INFO [org.xnio] XNIO Version 3.0.0.CR7

09:57:23,030 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.0.CR7

09:57:23,036 INFO [org.jboss.remoting] JBoss Remoting version 3.2.0.CR8

09:57:23,049 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

09:57:23,055 INFO [org.jboss.as.security] (ServerService Thread Pool -- 35) Activating Security Subsystem

09:57:23,057 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 31) JBAS011800: Activating Naming Subsystem

09:57:23,057 INFO [org.jboss.as.clustering] (ServerService Thread Pool -- 26) JBAS010300: Activating Infinispan subsystem.

09:57:23,069 INFO [org.jboss.as.security] (MSC service thread 1-11) Picketbox version=4.0.6.Beta2

09:57:23,105 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

09:57:23,106 INFO [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.6.Final)

09:57:23,131 WARN [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

09:57:23,146 INFO [org.jboss.as.remoting] (MSC service thread 1-2) Listening on /127.0.0.1:4447

09:57:23,199 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-14) live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=D:\Development\Servers\JBoss.AS.7.1.0.RC1B\standalone\data\messagingjournal,bindingsDirectory=D:\Development\Servers\JBoss.AS.7.1.0.RC1B\standalone\data\messagingbindings,largeMessagesDirectory=D:\Development\Servers\JBoss.AS.7.1.0.RC1B\standalone\data\messaginglargemessages,pagingDirectory=D:\Development\Servers\JBoss.AS.7.1.0.RC1B\standalone\data\messagingpaging)

09:57:23,207 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-14) Waiting to obtain live lock

09:57:23,236 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 21) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)

09:57:23,289 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 21) JBAS010404: Deploying non-JDBC-compliant driver class net.sourceforge.jtds.jdbc.Driver (version 1.2)

09:57:23,381 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-14) Using NIO Journal

09:57:23,447 ATTENTION [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-14) Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.

09:57:23,628 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-14) Waiting to obtain live lock

09:57:23,628 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-14) Live Server Obtained live lock

09:57:24,125 INFO [org.jboss.as.remoting] (MSC service thread 1-8) Listening on /127.0.0.1:9999

09:57:24,165 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory D:\Development\Servers\JBoss.AS.7.1.0.RC1B\standalone\deployments

09:57:24,229 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-13) JBAS010400: Bound data source [java:/pie2/jdbc/CommunDS]

09:57:24,229 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-13) JBAS010400: Bound data source [java:/pie2/jdbc/EL2DS]

09:57:24,229 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-13) JBAS010400: Bound data source [java:/pie2/jdbc/EL1DS]

09:57:24,230 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-13) JBAS010400: Bound data source [java:/pie2/jdbc/AxaptaDS]

09:57:24,236 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-1) HornetQ resource adaptor started

09:57:24,237 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorHornetQConnectionFactory

09:57:24,324 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-6) Démarrage de Coyote HTTP/1.1 sur http--127.0.0.1-8080

09:57:24,325 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-14) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} localhost:5445 for CORE protocol

09:57:24,327 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-14) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} localhost:5455 for CORE protocol

09:57:24,328 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-14) Server is now live

09:57:24,328 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-14) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [5a047785-40f6-11e1-b0fd-d0df9a814543] started

09:57:24,330 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-16) trying to deploy queue jms.queue.MGMDLQ

09:57:24,339 INFO [org.jboss.as.messaging] (MSC service thread 1-16) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/mgm/DLQ

09:57:24,349 INFO [org.jboss.as.messaging] (MSC service thread 1-10) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/JmsConnectionFactory

09:57:24,349 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-9) trying to deploy queue jms.queue.DMRDLQ

09:57:24,350 INFO [org.jboss.as.messaging] (MSC service thread 1-9) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/dmr/DLQ

09:57:24,350 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) trying to deploy queue jms.queue.MaMaQueue

09:57:24,351 INFO [org.jboss.as.messaging] (MSC service thread 1-6) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/mama/Queue

09:57:24,351 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-11) trying to deploy queue jms.queue.RegValExpiry

09:57:24,351 INFO [org.jboss.as.messaging] (MSC service thread 1-11) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/regval/Expiry

09:57:24,352 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) trying to deploy queue jms.queue.MGMExpiry

09:57:24,352 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/mgm/Expiry

09:57:24,353 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) trying to deploy queue jms.queue.MaMaDLQ

09:57:24,353 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/mama/DLQ

09:57:24,353 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-12) trying to deploy queue jms.queue.MGMQueue

09:57:24,354 INFO [org.jboss.as.messaging] (MSC service thread 1-12) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/mgm/Queue

09:57:24,354 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-14) trying to deploy queue jms.queue.RegValDLQ

09:57:24,354 INFO [org.jboss.as.messaging] (MSC service thread 1-14) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/regval/DLQ

09:57:24,355 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-13) trying to deploy queue jms.queue.MaMaExpiry

09:57:24,355 INFO [org.jboss.as.messaging] (MSC service thread 1-13) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/mama/Expiry

09:57:24,355 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-15) trying to deploy queue jms.topic.JMSTopic

09:57:24,373 INFO [org.jboss.as.messaging] (MSC service thread 1-15) JBAS011601: Bound messaging object to jndi name java:jboss/jms/topic

09:57:24,373 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) trying to deploy queue jms.queue.DMRQueue

09:57:24,374 INFO [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/dmr/Queue

09:57:24,374 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) trying to deploy queue jms.queue.RegValQueue

09:57:24,375 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/regval/Queue

09:57:24,375 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) trying to deploy queue jms.queue.DMRExpiry

09:57:24,376 INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:/pie2/jms/queue/dmr/Expiry

09:57:24,396 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.CR1b "Flux Capacitor" started in 2293ms - Started 159 of 220 services (39 services are passive or on-demand)

And in addition, I think it is the reason of my periodic warns in my log when the server attempts to connect to my MDB Containers like the following:

10:00:04,823 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (massMailingCampaignMdbContainer-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@1f640285[state=NORMAL managed connection=org.hornetq.ra.HornetQRAManagedConnection@40fc8791 connection handles=0 lastUse=1327309204823 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@32861ec pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2399c277 xaResource=XAResourceWrapperImpl@12428c00[xaResource=org.hornetq.ra.HornetQRAXAResource@685c1bd9 pad=false overrideRmValue=false productName=HornetQ productVersion=2.0 jndiName=java:/pie2/jms/JmsXAConnectionFactory] txSync=null]

10:00:04,823 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (regValMdbContainer-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@69a3d2cc[state=NORMAL managed connection=org.hornetq.ra.HornetQRAManagedConnection@6bb31fae connection handles=0 lastUse=1327309204823 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@32861ec pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2399c277 xaResource=XAResourceWrapperImpl@2648543[xaResource=org.hornetq.ra.HornetQRAXAResource@3ce50fbf pad=false overrideRmValue=false productName=HornetQ productVersion=2.0 jndiName=java:/pie2/jms/JmsXAConnectionFactory] txSync=null]

10:00:05,847 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (crmRequestDmrMdbContainer-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@5ffb5664[state=NORMAL managed connection=org.hornetq.ra.HornetQRAManagedConnection@307890f2 connection handles=0 lastUse=1327309205847 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@32861ec pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2399c277 xaResource=XAResourceWrapperImpl@4ec4ad2a[xaResource=org.hornetq.ra.HornetQRAXAResource@3b7418ba pad=false overrideRmValue=false productName=HornetQ productVersion=2.0 jndiName=java:/pie2/jms/JmsXAConnectionFactory] txSync=null]

10:00:05,849 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (massMailingCampaignSenderMdbContainer-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@10b406b7[state=NORMAL managed connection=org.hornetq.ra.HornetQRAManagedConnection@6a1a0efa connection handles=0 lastUse=1327309205846 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@32861ec pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2399c277 xaResource=XAResourceWrapperImpl@5ee179dc[xaResource=org.hornetq.ra.HornetQRAXAResource@54cd7581 pad=false overrideRmValue=false productName=HornetQ productVersion=2.0 jndiName=java:/pie2/jms/JmsXAConnectionFactory] txSync=null]

10:00:08,891 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (massMailingCampaignMdbContainer-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@5ffaf43a[state=NORMAL managed connection=org.hornetq.ra.HornetQRAManagedConnection@7742f3be connection handles=0 lastUse=1327309208889 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@32861ec pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2399c277 xaResource=XAResourceWrapperImpl@54b83d10[xaResource=org.hornetq.ra.HornetQRAXAResource@4c907c1d pad=false overrideRmValue=false productName=HornetQ productVersion=2.0 jndiName=java:/pie2/jms/JmsXAConnectionFactory] txSync=null]

Here is my standalone description of messaging subsystem >>>>

<hornetq-server>

<persistence-enabled>true</persistence-enabled>

<journal-file-size>5242880</journal-file-size>

<journal-min-files>2</journal-min-files>

<netty-connector name="netty" socket-binding="messaging" />

<netty-connector name="netty-throughput" socket-binding="messaging-throughput">

</netty-connector>

<in-vm-connector name="in-vm" server-id="0"/>

</connectors>

<netty-acceptor name="netty" socket-binding="messaging"/>

<netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">

</netty-acceptor>

<in-vm-acceptor name="in-vm" server-id="0"/>

</acceptors>

<security-settings>

<security-setting match="#">

</security-setting>

</security-settings>

<address-settings>

<address-setting match="jms.queue.MaMaQueue">

<dead-letter-address>jms.queue.MaMaDLQ</dead-letter-address>

<expiry-address>jms.queue.MaMaExpiry</expiry-address>

<redelivery-delay>5000</redelivery-delay>

<max-size-bytes>10485760</max-size-bytes>

<message-counter-history-day-limit>10</message-counter-history-day-limit>

<address-full-policy>BLOCK</address-full-policy>

<max-delivery-attempts>5</max-delivery-attempts>

</address-setting>

<address-setting match="jms.queue.RegValQueue">

<dead-letter-address>jms.queue.RegValDLQ</dead-letter-address>

<expiry-address>jms.queue.RegValExpiry</expiry-address>

<redelivery-delay>5000</redelivery-delay>

<max-size-bytes>10485760</max-size-bytes>

<message-counter-history-day-limit>10</message-counter-history-day-limit>

<address-full-policy>BLOCK</address-full-policy>

<max-delivery-attempts>5</max-delivery-attempts>

</address-setting>

<address-setting match="jms.queue.MGMQueue">

<dead-letter-address>jms.queue.MGMDLQ</dead-letter-address>

<expiry-address>jms.queue.MGMExpiry</expiry-address>

<redelivery-delay>5000</redelivery-delay>

<max-size-bytes>10485760</max-size-bytes>

<message-counter-history-day-limit>10</message-counter-history-day-limit>

<address-full-policy>BLOCK</address-full-policy>

<max-delivery-attempts>5</max-delivery-attempts>

</address-setting>

<address-setting match="jms.queue.DMRQueue">

<dead-letter-address>jms.queue.DMRDLQ</dead-letter-address>

<expiry-address>jms.queue.DMRExpiry</expiry-address>

<redelivery-delay>5000</redelivery-delay>

<max-size-bytes>10485760</max-size-bytes>

<message-counter-history-day-limit>10</message-counter-history-day-limit>

<address-full-policy>BLOCK</address-full-policy>

<max-delivery-attempts>5</max-delivery-attempts>

</address-setting>

</address-settings>

<jms-connection-factories>

<connection-factory name="RemoteConnectionFactory">

<connectors>

<connector-ref connector-name="in-vm"/>

</connectors>

<entries>

<entry name="java:/pie2/jms/JmsConnectionFactory"/>

</entries>

</connection-factory>

<pooled-connection-factory name="HornetQConnectionFactory">

<transaction mode="xa"/>

<connectors>

<connector-ref connector-name="in-vm"/>

</connectors>

<entries>

<entry name="java:/pie2/jms/JmsXAConnectionFactory"/>

</entries>

</pooled-connection-factory>

</jms-connection-factories>

<jms-destinations>

<jms-queue name="MaMaQueue">

</jms-queue>

<jms-queue name="MaMaDLQ">

</jms-queue>

<jms-queue name="MaMaExpiry">

</jms-queue>

<jms-queue name="MGMQueue">

</jms-queue>

<jms-queue name="MGMDLQ">

</jms-queue>

<jms-queue name="MGMExpiry">

</jms-queue>

<jms-queue name="RegValQueue">

</jms-queue>

<jms-queue name="RegValDLQ">

</jms-queue>

<jms-queue name="RegValExpiry">

</jms-queue>

<jms-queue name="DMRQueue">

</jms-queue>

<jms-queue name="DMRDLQ">

</jms-queue>

<jms-queue name="DMRExpiry">

</jms-queue>

<jms-topic name="JMSTopic">

</jms-topic>

</jms-destinations>

</hornetq-server>

</subsystem>

Finally, I would like to bound my queues with a pooled-connection-factory that works fine, and don’t see another WARNING about my MDB Containers.

Can you help me please because I’m lost?

Thanks all.