13 Replies Latest reply on Feb 19, 2009 12:30 PM by Siddharth Bhargava

    Exception coming in creating our own Connection Factory

    Siddharth Bhargava Newbie

      Hi All,

      I am using JBoss-5.0.0.G.A.

      I am creating my own Connection Factory. I removed the comments in the file connection-factories-service.xml. Following are the excerpts from the file

      <!-- An example connection factory with all attributes shown -->
      
       <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
       name="jboss.messaging.connectionfactory:service=MyExampleConnectionFactory"
       xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
      
       <constructor>
      
       <!-- You can specify the default Client ID to use for connections created using this factory -->
      
       <arg type="java.lang.String" value="MyClientID"/>
      
       </constructor>
      
       <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
      
       <!-- The transport to use - can be bisocket, sslbisocket or http -->
      
       <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=http</depends>
      
       <depends>jboss.messaging:service=PostOffice</depends>
      
       <!-- PrefetchSize determines the approximate maximum number of messages the client consumer will buffer locally -->
      
       <attribute name="PrefetchSize">150</attribute>
      
       <!-- Paging params to be used for temporary queues -->
      
       <attribute name="DefaultTempQueueFullSize">200000</attribute>
      
       <attribute name="DefaultTempQueuePageSizeSize">2000</attribute>
      
       <attribute name="DefaultTempQueueDownCacheSize">2000</attribute>
      
       <!-- The batch size to use when using the DUPS_OK_ACKNOWLEDGE acknowledgement mode -->
      
       <attribute name="DupsOKBatchSize">5000</attribute>
      
       <!-- Does this connection factory support automatic failover? -->
      
       <attribute name="SupportsFailover">false</attribute>
      
       <!-- Does this connection factory support automatic client side load balancing? -->
      
       <attribute name="SupportsLoadBalancing">false</attribute>
      
       <!-- The class name of the factory used to create the load balancing policy to use on the client side -->
      
       <attribute name="LoadBalancingFactory">org.jboss.jms.client.plugin.RoundRobinLoadBalancingFactory</attribute>
      
       <!-- Whether we should be strict TCK compliant, i.e. how we deal with foreign messages, defaults to false -->
      
       <attribute name="StrictTck">true</attribute>
      
       <!-- Should acknowledgements be sent asynchronously? -->
      
       <attribute name="SendAcksAsync">false</attribute>
      
       <!-- Disable JBoss Remoting Connector sanity checks - There is rarely a good reason to set this to true -->
      
       <attribute name="DisableRemotingChecks">false</attribute>
      
       <!-- The connection factory will be bound in the following places in JNDI -->
      
       <attribute name="JNDIBindings">
      
       <bindings>
      
       <binding>/QueueConnectionFactory</binding>
      
       <!--
       <binding>/acme/MyExampleConnectionFactoryDupe</binding>
      
       <binding>java:/xyz/CF1</binding>
      
       <binding>java:/connectionfactories/acme/connection_factory</binding>
       -->
      
       </bindings>
      
       </attribute>
      
       </mbean>


      I am getting the following exception while running the server.


      09:56:58,830 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      09:56:58,861 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1b40d64 started
      09:56:59,627 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
      09:56:59,642 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
      09:56:59,642 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      09:56:59,642 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@d67aa2 started
      09:56:59,705 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      09:56:59,705 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@215d51 started
      09:56:59,798 ERROR [AbstractKernelController] Error installing to Configured: name=jboss.messaging.connectionfactory:service=MyExampleConnectionFactory state=Instantiated mode=Manual requiredState=Configured
      java.lang.RuntimeException: No Attribute found with name: DefaultTempQueuePageSizeSize for jboss.messaging.connectionfactory:service=MyExampleConnectionFactory, attributes: [DefaultTempQueuePageSize, DefaultTempQueueFullSize, SupportsLoadBalancing, DisableRemotingChecks, ServerPeer, DefaultTempQueueDownCacheSize, ClientID, Connector, SlowConsumers, LoadBalancingFactory, StrictTck, SendAcksAsync, JNDIBindings, DupsOKBatchSize, SupportsFailover, PrefetchSize]
      at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:142)
      at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:114)
      at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58)
      at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:42)
      at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
      at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
      at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)


      09:56:59,892 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@215d51 undeployed
      09:56:59,892 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@d67aa2 undeployed
      09:56:59,908 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1b40d64 undeployed
      09:56:59,908 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/D:/jboss-5.0.0.GA/server/default/deploy/messaging/connection-factories-service.xml state=PreReal mode=Manual requiredState=Real
      org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.messaging.connectionfactory:service=MyExampleConnectionFactory
      at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
      at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:123)
      at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45)


      Caused by: java.lang.RuntimeException: No Attribute found with name: DefaultTempQueuePageSizeSize for jboss.messaging.connectionfactory:service=MyExampleConnectionFactory, attributes: [DefaultTempQueuePageSize, DefaultTempQueueFullSize, SupportsLoadBalancing, DisableRemotingChecks, ServerPeer, DefaultTempQueueDownCacheSize, ClientID, Connector, SlowConsumers, LoadBalancingFactory, StrictTck, SendAcksAsync, JNDIBindings, DupsOKBatchSize, SupportsFailover, PrefetchSize]
      at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:142)
      at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:114)
      at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58)


      *** CONTEXTS IN ERROR: Name -> Error

      vfsfile:/D:/jboss-5.0.0.GA/server/default/deploy/messaging/connection-factories-service.xml -> java.lang.RuntimeException: No Attribute found with name: DefaultTempQueuePageSizeSize for jboss.messaging.connectionfactory:service=MyExampleConnectionFactory, attributes: [DefaultTempQueuePageSize, DefaultTempQueueFullSize, SupportsLoadBalancing, DisableRemotingChecks, ServerPeer, DefaultTempQueueDownCacheSize, ClientID, Connector, SlowConsumers, LoadBalancingFactory, StrictTck, SendAcksAsync, JNDIBindings, DupsOKBatchSize, SupportsFailover, PrefetchSize]


      at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)




      Please help me in making my own connection factory. I want to make my own connection factory for use in durable subscriptions.

      Any help will be highly appreciated. Thanks in advance.

        • 1. Re: Exception coming in creating our own Connection Factory
          Yong Hao Gao Master

          The attribute name DefaultTempQueuePageSizeSize in the configu file is not correct, should be DefaultTempQueuePageSize

          • 2. Re: Exception coming in creating our own Connection Factory
            Siddharth Bhargava Newbie

            Hi,

            Thanks for you help.

            I corrected it and ran the server. I got the following exception

            13:49:44,129 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
            13:49:44,738 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
            13:49:45,020 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
            
            *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
            
            jboss.messaging.connectionfactory:service=MyExampleConnectionFactory
             -> jboss.messaging:service=Connector,transport=http{Create:** NOT FOUND Depends on 'jboss.messaging:service=Connector,transport=http' **}
            
            
            *** CONTEXTS IN ERROR: Name -> Error
            
            jboss.messaging:service=Connector,transport=http -> ** NOT FOUND Depends on 'jboss.messaging:service=Connector,transport=http' **
            
            
            13:49:45,035 ERROR [Http11Protocol] Error starting endpoint
            java.net.BindException: Address already in use: JVM_Bind /127.0.0.1:8080
             at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:504)
             at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:520)
             at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:203)
             at org.apache.catalina.connector.Connector.start(Connector.java:1102)
             at org.jboss.web.tomcat.service.deployers.TomcatService.startConnectors(TomcatService.java:629)
             at org.jboss.web.tomcat.service.deployers.TomcatService.handleNotification(TomcatService.java:670)
             at sun.reflect.GeneratedMethodAccessor205.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:153)
             at $Proxy85.handleNotification(Unknown Source)
             at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
             at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
             at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:425)
             at org.jboss.Main.boot(Main.java:209)
             at org.jboss.Main$1.run(Main.java:547)
             at java.lang.Thread.run(Thread.java:595)
            13:49:45,035 WARN [TomcatService] Failed to startConnectors
            LifecycleException: service.getName(): "jboss.web"; Protocol handler start failed: java.net.BindException: Address already in use: JVM_Bind /127.0.0.1:8080
             at org.apache.catalina.connector.Connector.start(Connector.java:1109)
             at org.jboss.web.tomcat.service.deployers.TomcatService.startConnectors(TomcatService.java:629)
             at org.jboss.web.tomcat.service.deployers.TomcatService.handleNotification(TomcatService.java:670)
             at sun.reflect.GeneratedMethodAccessor205.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:153)
             at $Proxy85.handleNotification(Unknown Source)
             at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
             at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
             at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:425)
             at org.jboss.Main.boot(Main.java:209)
             at org.jboss.Main$1.run(Main.java:547)
             at java.lang.Thread.run(Thread.java:595)
            13:49:45,035 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812041714)] Started in 1m:23s:47ms


            How to solve this. Please guide me. Why are there so many errors coming in the sample connection-factories-service.xml.

            Any help would be highly appreciated. Thanks in advance.

            • 3. Re: Exception coming in creating our own Connection Factory
              Andy Taylor Master

              Looks like your already running something on port 8080. Either stop this or change the port.

              • 4. Re: Exception coming in creating our own Connection Factory
                Siddharth Bhargava Newbie

                Hi,

                Thanks for your help.

                I stopped the port 8080. Then I again started the server. But I am still getting the exception. Please Help !!!

                18:50:45,478 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
                18:50:45,994 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
                
                *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
                
                jboss.messaging.connectionfactory:service=MyExampleConnectionFactory
                 -> jboss.messaging:service=Connector,transport=http{Create:** NOT FOUND Depends on 'jboss.messaging:service=Connector,transport=http' **}
                
                
                *** CONTEXTS IN ERROR: Name -> Error
                
                jboss.messaging:service=Connector,transport=http -> ** NOT FOUND Depends on 'jboss.messaging:service=Connector,transport=http' **
                
                
                18:50:46,056 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
                18:50:46,087 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
                18:50:46,103 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812041714)] Started in 1m:7s:944ms


                Any help will be highly appreciated. Thanks in advance

                • 5. Re: Exception coming in creating our own Connection Factory
                  Siddharth Bhargava Newbie

                  Hi All,

                  Any update on my post. Please help me in solving this. I am not able to proceed because of this exception. I am again printing the whole console trace.

                  ===============================================================================
                  
                   JBoss Bootstrap Environment
                  
                   JBOSS_HOME: C:\Softwares\jboss-5.0.0.GA
                  
                   JAVA: C:\Program Files\Java\jdk1.5.0_14\bin\java
                  
                   JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
                  
                   CLASSPATH: C:\Softwares\jboss-5.0.0.GA\bin\run.jar
                  
                  ===============================================================================
                  
                  23:22:36,687 INFO [ServerImpl] Starting JBoss (Microcontainer)...
                  23:22:36,750 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812041714)
                  23:22:36,750 INFO [ServerImpl] Bootstrap URL: null
                  23:22:36,750 INFO [ServerImpl] Home Dir: C:\Softwares\jboss-5.0.0.GA
                  23:22:36,750 INFO [ServerImpl] Home URL: file:/C:/Softwares/jboss-5.0.0.GA/
                  23:22:36,750 INFO [ServerImpl] Library URL: file:/C:/Softwares/jboss-5.0.0.GA/lib/
                  23:22:36,750 INFO [ServerImpl] Patch URL: null
                  23:22:36,750 INFO [ServerImpl] Common Base URL: file:/C:/Softwares/jboss-5.0.0.GA/common/
                  23:22:36,750 INFO [ServerImpl] Common Library URL: file:/C:/Softwares/jboss-5.0.0.GA/common/lib/
                  23:22:36,750 INFO [ServerImpl] Server Name: default
                  23:22:36,750 INFO [ServerImpl] Server Base Dir: C:\Softwares\jboss-5.0.0.GA\server
                  23:22:36,750 INFO [ServerImpl] Server Base URL: file:/C:/Softwares/jboss-5.0.0.GA/server/
                  23:22:36,750 INFO [ServerImpl] Server Config URL: file:/C:/Softwares/jboss-5.0.0.GA/server/default/conf/
                  23:22:36,750 INFO [ServerImpl] Server Home Dir: C:\Softwares\jboss-5.0.0.GA\server\default
                  23:22:36,750 INFO [ServerImpl] Server Home URL: file:/C:/Softwares/jboss-5.0.0.GA/server/default/
                  23:22:36,750 INFO [ServerImpl] Server Data Dir: C:\Softwares\jboss-5.0.0.GA\server\default\data
                  23:22:36,750 INFO [ServerImpl] Server Library URL: file:/C:/Softwares/jboss-5.0.0.GA/server/default/lib/
                  23:22:36,750 INFO [ServerImpl] Server Log Dir: C:\Softwares\jboss-5.0.0.GA\server\default\log
                  23:22:36,750 INFO [ServerImpl] Server Native Dir: C:\Softwares\jboss-5.0.0.GA\server\default\tmp\native
                  23:22:36,750 INFO [ServerImpl] Server Temp Dir: C:\Softwares\jboss-5.0.0.GA\server\default\tmp
                  23:22:36,750 INFO [ServerImpl] Server Temp Deploy Dir: C:\Softwares\jboss-5.0.0.GA\server\default\tmp\deploy
                  23:22:42,609 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Softwares/jboss-5.0.0.GA/server/default/conf/bootstrap.xml
                  23:22:45,828 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.IterableTimedVFSCache]
                  23:22:45,890 INFO [VFSCacheFactory] Using VFSCache [IterableTimedVFSCache{lifetime=1800, resolution=60}]
                  23:22:47,578 INFO [CopyMechanism] VFS temp dir: C:\Softwares\jboss-5.0.0.GA\server\default\tmp
                  23:22:47,593 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
                  23:22:52,515 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
                  23:22:52,515 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_14-b03,Sun Microsystems Inc.
                  23:22:52,515 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
                  23:22:52,671 INFO [JMXKernel] Legacy JMX core initialized
                  23:22:59,859 INFO [ProfileServiceImpl] Loading profile: default from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@130cb4b(root=C:\Softwares\jboss-5.0.0.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
                  23:22:59,875 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@130cb4b(root=C:\Softwares\jboss-5.0.0.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
                  23:22:59,875 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl@1b7a553{key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default]}
                  23:23:08,843 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
                  23:23:30,203 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
                  23:23:30,203 INFO [NativeServerConfig] 3.0.4.SP1
                  23:23:59,609 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
                  23:24:00,015 INFO [MailService] Mail Service bound to java:/Mail
                  23:24:05,671 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages 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.
                  23:24:05,750 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
                  23:24:06,328 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
                  23:24:06,328 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
                  23:24:07,359 INFO [TransactionManagerService] Initializing recovery manager
                  23:24:07,671 INFO [TransactionManagerService] Recovery manager configured
                  23:24:07,671 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
                  23:24:07,796 INFO [TransactionManagerService] Starting transaction recovery manager
                  23:24:10,437 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
                  23:24:10,437 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
                  23:24:10,437 INFO [StandardService] Starting service jboss.web
                  23:24:10,453 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.GA
                  23:24:10,671 INFO [Catalina] Server startup in 542 ms
                  23:24:10,859 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
                  23:24:15,171 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
                  23:24:17,046 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war
                  23:24:17,687 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Softwares/jboss-5.0.0.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
                  23:24:17,843 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Softwares/jboss-5.0.0.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
                  23:24:18,156 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Softwares/jboss-5.0.0.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
                  23:24:18,296 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Softwares/jboss-5.0.0.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
                  23:24:18,484 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/Softwares/jboss-5.0.0.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
                  23:24:19,046 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
                  23:24:19,125 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                  23:24:19,125 INFO [RAMJobStore] RAMJobStore initialized.
                  23:24:19,125 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
                  23:24:19,125 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                  23:24:19,140 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
                  23:24:22,421 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
                  23:24:24,906 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE QRTZ_JOB_DETAILS(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80) NOT NULL, DESCRIPTION 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) NOT NULL, REQUESTS_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINARY NULL, PRIMARY KEY (JOB_NAME,JOB_GROUP))
                  23:24:25,062 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
                  23:24:25,062 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                  23:24:25,062 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
                  23:24:25,093 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
                  23:24:25,093 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
                  23:24:25,093 INFO [JobStoreCMT] JobStoreCMT initialized.
                  23:24:25,093 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided properties instance.
                  23:24:25,093 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                  23:24:25,109 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
                  23:24:25,109 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
                  23:24:25,109 INFO [JobStoreCMT] Recovery complete.
                  23:24:25,109 INFO [JobStoreCMT] Removed 0 'complete' triggers.
                  23:24:25,125 INFO [JobStoreCMT] Removed 0 stale fired job entries.
                  23:24:25,125 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
                  23:24:26,156 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
                  23:24:26,687 INFO [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:26,687 INFO [TopicService] Topic[/topic/testDistributedTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:26,750 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
                  23:24:26,750 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
                  23:24:27,093 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                  23:24:27,093 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@12c5f73 started
                  23:24:27,109 INFO [QueueService] Queue[/queue/B] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,109 INFO [QueueService] Queue[/queue/ex] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,109 INFO [QueueService] Queue[/queue/testDistributedQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,109 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,109 INFO [QueueService] Queue[/queue/C] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,125 INFO [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,125 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                  23:24:27,125 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1bdc523 started
                  23:24:27,125 INFO [QueueService] Queue[/queue/D] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,140 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                  23:24:27,140 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@19e67d4 started
                  23:24:27,156 INFO [TopicService] Topic[/topic/testDurableTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,156 INFO [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,156 INFO [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,171 INFO [QueueService] Queue[/queue/testQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,171 INFO [QueueService] Queue[/queue/PrivateExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,171 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,171 INFO [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,187 INFO [QueueService] Queue[/queue/A] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,187 INFO [TopicService] Topic[/topic/securedTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,187 INFO [TopicService] Topic[/topic/testTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  23:24:27,640 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
                  23:24:27,718 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
                  23:24:28,625 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
                  23:24:29,421 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
                  
                  *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
                  
                  jboss.messaging.connectionfactory:service=MyExampleConnectionFactory
                   -> jboss.messaging:service=Connector,transport=http{Create:** NOT FOUND Depends on 'jboss.messaging:service=Connector,transport=http' **}
                  
                  
                  *** CONTEXTS IN ERROR: Name -> Error
                  
                  jboss.messaging:service=Connector,transport=http -> ** NOT FOUND Depends on 'jboss.messaging:service=Connector,transport=http' **
                  
                  
                  23:24:29,796 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
                  23:24:29,921 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
                  23:24:29,937 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812041714)] Started in 1m:53s:156ms
                  
                  



                  Waiting for replies. Thanks in advance.

                  • 6. Re: Exception coming in creating our own Connection Factory
                    Yong Hao Gao Master

                    It looks like you configure the factory to use http transport but you didn't deploy it accordingly. If so you need to deploy the http transport. You can find in http example the sample http configure file.

                    • 7. Re: Exception coming in creating our own Connection Factory
                      Siddharth Bhargava Newbie

                      Hi,


                      It looks like you configure the factory to use http transport but you didn't deploy it accordingly. If so you need to deploy the http transport. You can find in http example the sample http configure file.


                      How do we do this? Where is the http example in the sample http configure file?. Do we need to deploy for http transport specially?

                      I just uncommented the entry in the jboss-5.0.0.GA\server\default\deploy\messaging\connection-factories-service.xml for creating our own connection factory. I just uncommented the entry from here and started the server. When I started the server I got the trace which I just pasted in this post.

                      How do I solve this exception? Please guide me.

                      Thanks in advance.

                      • 8. Re: Exception coming in creating our own Connection Factory
                        Andy Taylor Master

                        You need to deploy the http remoting transport. There should be an example, remoting-http-service.xml.

                        The Remoting docs will have instructions on how to do this.

                        • 9. Re: Exception coming in creating our own Connection Factory
                          Siddharth Bhargava Newbie

                          Hi,

                          You need to deploy the http remoting transport. There should be an example, remoting-http-service.xml.

                          The Remoting docs will have instructions on how to do this.


                          What do I need to do to deploy the http remoting transport. Where is this file : remoting-http-service.xml? I am able to see only the file remoting-bisocket-service.xml in the path (jboss-5.0.0.GA\server\default\deploy\messaging).

                          Where are the remoting docs? Please tell me the path.

                          Do I need to specifically deploy http remoting transport for the messaging examples. We weren't required to do this in JBoss-4.2.2.G.A

                          Please guide me. I am not able to proceed because of this. Thanks in advance.


                          • 10. Re: Exception coming in creating our own Connection Factory
                            Yong Hao Gao Master

                            bisocket is the default transport JBM uses. you can find remoting-http-service.xml under 5.0.0.GA/docs/examples/jms directory.

                            • 11. Re: Exception coming in creating our own Connection Factory
                              Siddharth Bhargava Newbie

                              Hi,


                              bisocket is the default transport JBM uses. you can find remoting-http-service.xml under 5.0.0.GA/docs/examples/jms directory.


                              I found the file at this path. Now what do I do ? Do I copy this file at location (jboss-5.0.0.GA\server\default\deploy\messaging). Do I need to do anything else.? Now should I start the server ?

                              Please Help. Thanks in advance.

                              • 12. Re: Exception coming in creating our own Connection Factory
                                Yong Hao Gao Master

                                You can drop this file to jboss-5.0.0.GA\server\default\deploy and start the server. Please refer to the http example that comes up with jbm 1.4.1.GA.

                                • 13. Re: Exception coming in creating our own Connection Factory
                                  Siddharth Bhargava Newbie

                                  Hi,

                                  You can drop this file to jboss-5.0.0.GA\server\default\deploy and start the server. Please refer to the http example that comes up with jbm 1.4.1.GA.


                                  I dropped the file at the said location at then I started the server. It worked. The server started without any exception. Thanks a lot.