JMS Queue Not bound

Configured JMS communication to connect to external JMS Queue.
When i see the status in Adapter monitor, it shows an error "Receiver channel details:<queuename> not bound".
Would like to know , where is the problem this error is related to?
Thnx
Sunil

Hi,
First of all check all your configuration steps in the directory. i.e Receiver Determination/Interface Determination/Receiver Agreement etc
Are you getting any error in the SXMB_MONI ?
ALso check the RWB->Message Monitoring ->Message Display tool and check the status
If there is no error in the above, if the error is only in the Adapter monitor, then check the Adapter configuration .
Regards,
moorthy

Similar Messages

  • MDB in a Cluster using Local JMS Queue (not distributed)

              Can I create a MDB that receives messages from a Local JMS Queue (created on each
              node) rather than a distributed queue?
              When I try to deploy such an MDB I get the following exception:
              weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException:
              activate failed for TestLocalMDBCluster Module: TestLocalMDBCluster Error: Exception
              activating module: EJBModule(TestLocalMDBCluster,status=PREPARED) Unable to deploy
              EJB: AsyncProcessor from TestLocalMDBCluster.jar: [EJB:011046]Unable to create
              EJBRuntimeMBean. javax.management.InstanceAlreadyExistsException: mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,Location=Node2,Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,ServerRuntime=Node2,Type=MessageDrivenEJBRuntime
              at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
              at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
              at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
              at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
              at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
              at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
              at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
              at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
              at weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.java:33)
              at weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:30)
              at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDrivenBeanPoolInfoImpl.java:182)
              at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.activate(MessageDrivenBeanPoolInfoImpl.java:245)
              at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.activatePoolInfo(MessageDrivenBeanInfoImpl.java:474)
              at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanInfoImpl.java:440)
              at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1327) at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
              at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
              at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
              at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
              at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
              at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
              at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:608)
              at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              Is there any way to do this?
              

    I assume you are using queues.
              I truly wonder what you are doing different. Since the
              error is occuring outside of JMS and in the EJB - before JMS is called -
              I suggest posting to the ejb newsgroup.
              Note that yours is a standard use case which distributed destinations
              are actually specifically designed for (if you
              are using customer connection factories, just
              make sure ServerAffinity is enabled on the connection factory to
              ensure that clients always connect to the local physical destination,
              configure the MDB to refer to the JNDI name of the distributed
              destination, and then target the MDB to the cluster - an MDB pool
              will then automatically be dedicated to each physical destination).
              Tom
              Mark Colwell wrote:
              > Nope. It happens every time we try the scenario no matter what the application
              > is or which cluster. It always happens if we try to deploy even just a single
              > MDB (no other beans in the jar) to a cluster where the queue specified in the
              > deployment descripter is a local queue created on each node in the cluster. When
              > the jar is deployed we get the error.
              >
              > We have a strange situation were we really need the queue to be local and not
              > distributed but existing on every node. We can create all the local queues no
              > problem but trying to then deploy the application goes boom.
              >
              > Thanks for the response!
              >
              > Cheers,
              > Mark
              >
              > Tom Barnes <[email protected].bea.com>
              > wrote:
              >
              >>Mark Colwell wrote:
              >>
              >>
              >>>Can I create a MDB that receives messages from a Local JMS Queue (created
              >>
              >>on each
              >>
              >>>node) rather than a distributed queue?
              >>
              >>Yes. In fact this is the most common use case.
              >>
              >>
              >>>When I try to deploy such an MDB I get the following exception:
              >>
              >>I don't recall seeing this exception before. It looks like a naming
              >>conflict - it appears that somehow something is already running with
              >>the same name. Are you somehow deploying the same app twice?
              >>
              >>javax.management.InstanceAlreadyExistsException:
              >>mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,
              >>EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,
              >>Location=Node2,
              >>Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,
              >>ServerRuntime=Node2,
              >>Type=MessageDrivenEJBRuntime
              >>
              >>FYI: As of one or two weeks ago, the MDB section of the
              >>EJB docs has been heavily updated. I highly recommend
              >>reading it.
              >>
              >>
              >>>weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException:
              >>>activate failed for TestLocalMDBCluster Module: TestLocalMDBCluster
              >>
              >>Error: Exception
              >>
              >>>activating module: EJBModule(TestLocalMDBCluster,status=PREPARED) Unable
              >>
              >>to deploy
              >>
              >>>EJB: AsyncProcessor from TestLocalMDBCluster.jar: [EJB:011046]Unable
              >>
              >>to create
              >>
              >>>EJBRuntimeMBean. javax.management.InstanceAlreadyExistsException: mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,Location=Node2,Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,ServerRuntime=Node2,Type=MessageDrivenEJBRuntime
              >>>at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
              >>>at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
              >>>at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
              >>>at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
              >>>at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
              >>>at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
              >>>at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
              >>>at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
              >>>at weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.java:33)
              >>>at weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:30)
              >>>at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDrivenBeanPoolInfoImpl.java:182)
              >>>at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.activate(MessageDrivenBeanPoolInfoImpl.java:245)
              >>>at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.activatePoolInfo(MessageDrivenBeanInfoImpl.java:474)
              >>>at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanInfoImpl.java:440)
              >>>at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1327)
              >>
              >>at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
              >>
              >>>at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
              >>>at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
              >>>at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
              >>>at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
              >>>at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
              >>>at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
              >>>at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:608)
              >>>at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
              >>>at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at
              >>
              >>weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >>
              >>>Is there any way to do this?
              >>
              >
              

  • JMS Queue Works in JDeveloper 10g, but not in Oracle 10g AS

    Hello --
    I have set up a JMS Queue on my local OC4J included with JDeveloper. I added my ConnectionQueueFactory and ConnectionQueue to the JMS.XML file in my environment. Everything works the way it should using JDeveloper with the embedded OC4J.
    As soon as I deploy the application to Oracle Application Server, for some reason my MailSender Message Driven Bean cannot take delivery of the message. I don't know what I could be doing wrong but my JMS.XML file on the Application Server has been updated with the same ConnectionQueue information that is on my local JMS.XML file. In my log file I can see that the message is being posted to the queue, just no delivery.
    If anyone out there has a suggestion I would appreciate it. This is my first attempt at ever using JMS.
    Thanks,
    Frank

    Willy_B wrote:
    I removed the one that was listed, thinking that it was implicit to that line. BUT of course, I just went back and removed EVERY empty line, even between the comments and all...and it worked.
    So the lesson here is that PL/SQL could care less about white space, but SQLPlus is picky....
    Thanks. :)Exactly. And I have to make note of that in my written procedure for restoring some of our test databases from a cold backup of production. Turns out the control file trace script (backup controlfile to trace) inserts a blank line ... then sqlplus chokes on it when executing ..

  • Message posted from BPEL not found in oc4j JMS queue

    Hi,
    I am facing a weird problem when I try to post a message in oc4j JMS from a BPEL process.
    There is no exception(Not even in the logs) and the BPEL process gets completed. But the message is missing(Could not find it while monitoring the queue).
    I am using SOA suite 10.1.3.5 and the oc4j JMS queue which comes with the installation.
    Can someone help me please.
    Saptarishi
    Edited by: saptarishi on May 25, 2010 3:51 PM

    Got a solution.

  • Weblogic 10.3 Not Removing Expired Messages from JMS Queues

    Dear All,
    We have an application that is running on Weblogic 10.3.
    This application (let us call this application Y) receives messages on a JMS queue. These messages are placed on the queue by another application (let us call this application X). We would like to have these messages expire within a certain amount of time (i.e. 90000 ms) if they are not consumed.
    Now when application X places the messages onto the queue for application Y to consume, the JMS producer sets the time to live to 90000 ms. We can see that expiration time has been set appropriately in the weblogic console. If a message sits on the queue for longer than 90000 ms the state string of the message is changed to "receive expired". What we don't understand is why the expired messages still end up being consumed from the queue.
    We understand that Weblogic is supposed to have an 'Active Message Expiration' thread that will remove expired messages from the queue. The Expiration Scan Interval for the JMS Server is set to 30 (seconds).
    Can anyone tell us why our expired messages don't seem to be deleted from the queues?
    Tim

    Thank you for the response Rene.
    We have set up both the active expiration scan and the message expiration policy. The active expiration scan is set for every 30 seconds. The message expiration policy is set to "discard". However, the expired messages are still being consumed. Is it possible we are doing something wrong? See a portion of our configuration files below.
    We have set up the expiration scan time interval. See a portion of our config.xml below:
    <jms-server>
    <name>brokerJMSServer</name>
    <target>AdminServer</target>
    <persistent-store xsi:nil="true"></persistent-store>
    <store-enabled>true</store-enabled>
    <allows-persistent-downgrade>false</allows-persistent-downgrade>
    <hosting-temporary-destinations>true</hosting-temporary-destinations>
    <temporary-template-resource xsi:nil="true"></temporary-template-resource>
    <temporary-template-name xsi:nil="true"></temporary-template-name>
    <message-buffer-size>-1</message-buffer-size>
    *<expiration-scan-interval>30</expiration-scan-interval>*
    <production-paused-at-startup>false</production-paused-at-startup>
    <insertion-paused-at-startup>false</insertion-paused-at-startup>
    <consumption-paused-at-startup>false</consumption-paused-at-startup>
    </jms-server>
    <jms-system-resource>
    <name>broker-jms</name>
    <target>AdminServer</target>
    <sub-deployment>
    <name>EhrBrokerRequestQueue</name>
    <target>brokerJMSServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/broker-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <admin-server-name>AdminServer</admin-server-name>
    We have set up the message expiration policy in our jms descriptor. See a portion below:
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
    <queue name="EhrBrokerRequestQueue">
    <delivery-params-overrides>
    <redelivery-delay>-1</redelivery-delay>
    </delivery-params-overrides>
    <delivery-failure-params>
    <redelivery-limit>-1</redelivery-limit>
    *<expiration-policy>Discard</expiration-policy>*
    </delivery-failure-params>
    <jndi-name>EhrBrokerRequestQueue</jndi-name>
    </queue>
    </weblogic-jms>
    What could we be doing wrong?
    Kind Regards,
    Tim

  • JMS Queue is not accepting requests after restarting the weblogic server

    Hi,
    JMS queue is able to receive message after redeploying the application or restarting the weblogic server. It is intermittent , not happening every time.
    Please suggest how to resolve this issue. do we missed any configuration settings we are missing at clinet side or server side.
    we are using Weblogic 92 MP2 version.
    thanks.
    [email protected]

    I assume you meant "is unable to receive messages".
    Are you getting any exceptions in the code, or errors in the log, or is nothing happening when you know there's a message on the queue to be read?
    Are you perhaps reading from a distributed destination?

  • BPEL not able to read JMS Queue defined on a remote Application Server

    We are trying to access a JMS queue (defined on an Oracle AS different from the SOA Suite AS) through BPEL and read the payload. When I am trying to read the JMS queue, somehow it is trying to get the queue information from my local application server and not going to the remote one.
    I have done the following setups on my local SOA Suite Enterprise manager for the queue connection factory. The adapter name is "eis/jms/XXXQueueAdapter"
    connectionFactoryLocation: jms/ESBSubscriberQueue
    factoryProperties:
    java.naming.factory.initial=oracle.j2ee.rmi.RMIInitialContextFactory;java.naming.provider.url=opmn.ormi://hostname:port; java.naming.security.principal=oc4jadmin;java.naming.security.credentials=Password
    Where "hostname:port" is for the remote Application Server.
    On the BPEL side, I have created a connection for the Remote server in the Enterprise Manager. Then I have created a partnerlink using this connection. The OEMS is "File/Memory". The Destination Name is the Queue name on the Remote AS which I can browse. The JNDI name is "eis/jms/XXXQueueAdapter" (Which is the name of the connection I created on my local). Somehow when the BPEL process is run, it is trying to look for the JMS Queue on my local server.
    I have also used the Third Party option instead of Oracle AS with the same configuration and it does not work either.
    Any help would be really appreciated.
    Asif Hussain

    Got a solution.

  • JMS Default queue not found

    I do not have any knowledge of JMS and I am getting couple of warnings of this kind . Can anyone please explain it to me.
    <WSEE>Warning: JMS queue 'weblogic.wee.DefaultQueue' is not found, as a result, Web Service async responses via jms transport is not supported. If the target service uses JMS transport, the responses will not be able to come back.<JmsQueueListener.connect:227>

    Hi,
    This WARNING can be ignored ... Or if you dont want to see any such message next time..then please apply "-Dweblogic.wsee.skip.async.response=true"
    Details:
    Async web service support is not fully configured. The async response web service uri for this server was not fully deployed because the JMS reliability queue was not defined/deployed: queueName. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.
    More Details:
    http://download.oracle.com/docs/cd/E15523_01/apirefs.1111/e14397/WebService.html
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

  • Why we use MQ not JMS Queues or AQ ?

    Hi,
    Is there any specific reason most of the companies using MQ for messaging and not using AQ or JMS Queues ?

    Hi,
    AFAIK, the companies that have IBM infrastructure in place prefer using the MQs. Also as MQ is capable of being accessed using JMS as well as MQ, it adds to the usability.
    Following could be helpful.
    How to configure MQ with WLS (JMS MQ vs Native MQ)
    Regards,
    Neeraj Sehgal

  • QueueBrowser not scaning all messages in JMS queue (ie not showing inprogre

    Hi all,
    I am using JMS in jboss-3.2.3, when scaning for pending messages i am using QueueBrowser.
    But QueueBrowser not scaning all messages in JMS queue (ie not showing inprogress message)
    But i need to know all messages including ongoing messages..
    Antone plz help me
    I am using Queuesender and QueueReceiver ..But some Exception or Error causes my JMS server(QueueReceiver listening for onMessage()) hanged up..and not responding to remaining messages...So i need to find pending messags in JMS queue..How can find?
    Now i am using QueueBrowser to get list of pending msgs in queue... But doesn't contains Message which passed for processing (called onMessage())
    .. But i need to find this also..How can?
    Thanks,
    Thilsen

    You're right in thinking that the behaviour you describe looks wrong.
    Take a look at the QueueBrowser interface which can be used to inspect a queue. You get one using QueueSession.createBrowser(Queue). The QueueBrowser allows you to scan a queue without consuming the messages. However note that the state of the queue may change while you're observing it through the QueueBrowser so what you see might not always be a 100% accurate representation of the queue at any given time.
    Other things to check:
    - message selectors - are you setting a message selector on your queue receiver which is resulting in not all of the messages 'matching'.
    - expired messages - are you setting a time-to-live on the messages that you publish.
    Hope this helps,
    David Ingham
    http://www.arjuna.com

  • How to check the jms Queue is persistance or not in jboss application serve

    hi,
    i am using jboss as application server for jms and database is postgres.For an message store i am using the "*database store*".while starting the jms adding queue it is adding the messages to the jms queue after starting the jms receiver the datas are received sucessfully....afte some 10 to 13 hours i am getting java.lang.OutOfMemoryError in jms..so i checked the postgres table space.Table space is increased gradually...I think that the after receiver received that message the messages are not deleted in the database.how to debugg the the secnario in jboss as wel as in database.....how to chaeck the queue is in persistance or not persistance...
    regards.
    naresh govindaswamy.

    Send a request to the server somehow, so that the server is aware of this. AJAX may be very useful in this if you want to do this asynchronously.
    its very urgently This is irrelevant information. That's your problem. We don't care less or more. Some users here will even refuse to help you if you're putting pressure.

  • Error While accessing JMS Queue on Weblogic***** ASSERTION FAILED *****[ Environment not found on thread ]

    Hi,
    I am trying to read response from JMS Queue hosted on Weblogic server and getting below exception. Any help on this will be appreciable.
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Environment not found on thread ]
          at weblogic.jndi.internal.NamingNodeReplicaHandler.<init>(NamingNodeReplicaHandler.java:148)
          at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
          at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
          at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
          at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
          at java.lang.Class.newInstance0(Class.java:308)
          at java.lang.Class.newInstance(Class.java:261)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:90)
          at weblogic.common.internal.ChunkedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:159)
          at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:341)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.readExternal(ReplicaAwareRemoteRef.java:356)
          at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1686)
          at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1644)
          at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
          at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:452)
          at weblogic.rmi.internal.StubInfo.readObject(StubInfo.java:95)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)
          at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
          at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
          at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:111)
          at weblogic.common.internal.ChunkedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:159)
          at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:341)
          at weblogic.jndi.internal.WLContextImpl.readExternal(WLContextImpl.java:425)
          at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1686)
          at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1644)
          at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
          at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
          at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
          at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
          at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
          at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
          at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
          at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
          at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:111)
          at weblogic.rjvm.ResponseImpl.getThrowable(ResponseImpl.java:117)
          at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:106)
          at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:127)
          at weblogic.jms.dispatcher.DispatcherImpl_1035_WLStub.dispatchSyncNoTranFuture(Unknown Source)
          at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:341)
          at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:1735)
          at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:1296)
    Thanks

    Hi,
    I am trying to read Queue standalone. Please find the code snippet below.  code highlighted in  where i am getting exception.
    public static void main(String[] args) {
    String jmsServerUrl = "t3://10.51.245.45:5858";
    String jmsUserName = "weblogic";
    String jmsPassword = "welcome123";
    String jndiFactory = "weblogic.jndi.WLInitialContextFactory";
    String jmsFactory = "jms/CBCMReplyConnectionFactory";
    String qName = "jms/CBCMOrderReplyQueue";
    QueueReceiver qReciever = null;
    JMSQueueReader.getQueueSession(jmsServerUrl,jmsUserName,jmsPassword,jndiFactory,jmsFactory);
    qReciever = JMSQueueReader.getQueueReceiver(qName);
    if (qReciever == null) {
    System.out.println("Unable to find JMS Queue Reciever for Queue Name: "
    + qName + " and JMS Server URL:"
    + jmsServerUrl);
    //isProcess = false;
    private static InitialContext getInitialContext(String url, String userName, String password,  String jndiFactory) throws NamingException {
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY, jndiFactory);
    env.put(Context.PROVIDER_URL, url);
    env.put(Context.SECURITY_PRINCIPAL, userName);
    env.put(Context.SECURITY_CREDENTIALS, password);
    return new InitialContext(env);
    public static QueueReceiver getQueueReceiver(String qName) {
    try {
    if(qReceiver == null || !qName.equals(queueName))
    queueName = qName;
    if(qReceiver != null)
    qReceiver.close();
    qReceiver = null;
    javax.jms.Queue queue = qSession.createQueue(queueName);
    //qReceiver = qSession.createReceiver(queue);
    qReceiver = qSession.createReceiver(queue, "JMSCorrelationID LIKE '"+SOHConstant.CBCM_BSCS_CORRELATION_ID_PREFIX+"%'");
                } catch (Throwable e) {
    e.printStackTrace();
    return qReceiver;

  • JMS queue hes been binding during server startup but  not looking up

    Hi,
    I have created a queue connection factory as jms/AlertACF and destination resources as jms/AlertQueue with properties
    key : imqDestinationName
    value : AlertQueue
    and
    Physical destination as AlertQueue.
    I have applied all the changes to the server instance and restrated the server instance. In the log file the startup message like
    [08/Aug/2006:11:58:05] INFO ( 5768): JMS5015: Install JMS resources ...
    [08/Aug/2006:11:58:06] INFO ( 5768): JMS5002: Binding [< JMS Destination: jms/AlertQueue, javax.jms.Queue, [ imqDestinationName=AlertQueue ] >]
    [08/Aug/2006:11:58:06] INFO ( 5768): JMS5002: Binding [< JMS Connection Factory: jms/AlertACF, javax.jms.QueueConnectionFactory, No properties >]along with few other messages about ejb's uploaded successfully...
    Now, when I run my test case to test the JMS service, i am getting
    [08/Aug/2006:12:03:39] INFO ( 5768): CORE3282: stdout: javax.naming.NameNotFoundException: jms/AlertQueue.........
    can anybody help me out in this.......
    Thank you very much
    Regards,
    Mike

    Hi,
    I have created a queue connection factory as jms/AlertACF and destination resources as jms/AlertQueue with properties
    key : imqDestinationName
    value : AlertQueue
    and
    Physical destination as AlertQueue.
    I have applied all the changes to the server instance and restrated the server instance. In the log file the startup message like
    [08/Aug/2006:11:58:05] INFO ( 5768): JMS5015: Install JMS resources ...
    [08/Aug/2006:11:58:06] INFO ( 5768): JMS5002: Binding [< JMS Destination: jms/AlertQueue, javax.jms.Queue, [ imqDestinationName=AlertQueue ] >]
    [08/Aug/2006:11:58:06] INFO ( 5768): JMS5002: Binding [< JMS Connection Factory: jms/AlertACF, javax.jms.QueueConnectionFactory, No properties >]along with few other messages about ejb's uploaded successfully...
    Now, when I run my test case to test the JMS service, i am getting
    [08/Aug/2006:12:03:39] INFO ( 5768): CORE3282: stdout: javax.naming.NameNotFoundException: jms/AlertQueue.........
    can anybody help me out in this.......
    Thank you very much
    Regards,
    Mike

  • Jms not bound

    I'm getting this <connection factory> not bound exeption when I deploy my application.
    String factoryJNDI = "ConnectionFactory";
      Context context = new InitialContext();
       log.debug("Lookup ConnectionFactory: " + factoryJNDI);
        TopicConnectionFactory topicFactory =
             (TopicConnectionFactory)context.lookup(factoryJNDI);
        topicConnection = topicFactory.createTopicConnection();I'm useing JBoss 3.2.5 server. I call this Subcriber class from non-ejb class. Should I add something to some conf file? I have added a Topic to jbossmq-destinations-service.xml file and I want to use that default connection factory, that is ConnectionFactory. What is wrong with this?

    u need to write jboss.xml file where u have to specify the JNDI name.
    & also check , have u specified the resource-ref tags in ejb-jar.xml file that will hold the name of the topic u have created.
    regards
    vanan

  • Error: ConnectionFactory not bound

    Hi,
    I have created a method in session bean to send message. below is the code of my method
    public void sendMessage() throws NamingException,JMSException{
    QueueConnectionFactory cf;
    QueueConnection connection;
    QueueSession session;
    Queue destination;
    QueueSender sender;
    TextMessage message;
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY,
    "org.jnp.interfaces.NamingContextFactory");
    env.put(Context.PROVIDER_URL,
    "localhost:1099");
    Context ctx = new InitialContext(env);
    //ctx = new InitialContext();
    cf = (QueueConnectionFactory)ctx.lookup("ConnectionFactory");
    destination = (Queue)ctx.lookup("queue/testQueue");
    connection = cf.createQueueConnection();
    session = connection.createQueueSession(false,
    Session.AUTO_ACKNOWLEDGE);
    sender = session.createSender(destination);
    message = session.createTextMessage();
    message.setText("Hello World1!");
    System.out.println("Sending Message.");
    sender.send(message);
    connection.close();
    System.out.println("Done.");
    I am getting the following error in the browser
    javax.naming.NameNotFoundException: ConnectionFactory not bound
    Can anyone tell me why this error is coming
    Thanks

    I am getting the following errors in the console. Please check it
    ===============================================================================
    JBoss Bootstrap Environment
    JBOSS_HOME: C:\jboss-4.0.1\bin\\..
    JAVA: D:\j2sdk1.4.2_07\bin\java
    JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m
    CLASSPATH: D:\j2sdk1.4.2_07\lib\tools.jar;C:\jboss-4.0.1\bin\\run.jar
    ===============================================================================
    14:31:23,312 INFO [Server] Starting JBoss (MX MicroKernel)...
    14:31:23,312 INFO [Server] Release ID: JBoss [Zion] 4.0.1 (build: CVSTag=JBoss_4_0_1 date=200412230944)
    14:31:23,312 INFO [Server] Home Dir: C:\jboss-4.0.1
    14:31:23,312 INFO [Server] Home URL: file:/C:/jboss-4.0.1/
    14:31:23,312 INFO [Server] Library URL: file:/C:/jboss-4.0.1/lib/
    14:31:23,312 INFO [Server] Patch URL: null
    14:31:23,312 INFO [Server] Server Name: default
    14:31:23,328 INFO [Server] Server Home Dir: C:\jboss-4.0.1\server\default
    14:31:23,328 INFO [Server] Server Home URL: file:/C:/jboss-4.0.1/server/default/
    14:31:23,328 INFO [Server] Server Data Dir: C:\jboss-4.0.1\server\default\data
    14:31:23,328 INFO [Server] Server Temp Dir: C:\jboss-4.0.1\server\default\tmp
    14:31:23,343 INFO [Server] Server Config URL: file:/C:/jboss-4.0.1/server/default/conf/
    14:31:23,343 INFO [Server] Server Library URL: file:/C:/jboss-4.0.1/server/default/lib/
    14:31:23,343 INFO [Server] Root Deployment Filename: jboss-service.xml
    14:31:23,343 INFO [Server] Starting General Purpose Architecture (GPA)...
    14:31:24,312 INFO [ServerInfo] Java version: 1.4.2_07,Sun Microsystems Inc.
    14:31:24,312 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_07-b05,Sun Microsystems Inc.
    14:31:24,312 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
    14:31:25,203 INFO [Server] Core system initialized
    14:31:28,468 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
    14:31:28,828 INFO [WebService] Using RMI server codebase: http://Mukti:8083/
    14:31:29,140 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
    14:31:38,968 INFO [Embedded] Catalina naming disabled
    14:31:40,250 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
    14:31:40,343 INFO [Catalina] Initialization processed in 1203 ms
    14:31:40,343 INFO [StandardService] Starting service jboss.web
    14:31:40,359 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.0.28
    14:31:40,421 INFO [StandardHost] XML validation disabled
    14:31:40,453 INFO [Catalina] Server startup in 110 ms
    14:31:40,750 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/C:/jboss-4.0.1/server/default/deploy/http-invoker.sar/invoker.war/
    14:31:42,859 INFO [TomcatDeployer] deploy, ctxPath=/ws4ee, warUrl=file:/C:/jboss-4.0.1/server/default/tmp/deploy/tmp4763jboss-ws4ee-exp.war/
    14:31:43,234 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/C:/jboss-4.0.1/server/default/deploy/jbossweb-tomcat50.sar/ROOT.war/
    14:31:43,703 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/C:/jboss-4.0.1/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
    14:31:48,765 INFO [MailService] Mail Service bound to java:/Mail
    14:31:49,984 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss-4.0.1/server/default/deploy/jboss-local-jdbc.rar
    14:31:50,375 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss-4.0.1/server/default/deploy/jboss-xa-jdbc.rar
    14:31:50,734 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss-4.0.1/server/default/deploy/jms/jms-ra.rar
    14:31:51,046 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss-4.0.1/server/default/deploy/mail-ra.rar
    14:31:51,968 ERROR [HypersonicDatabase] Starting failed jboss:database=localDB,service=Hypersonic
    java.sql.SQLException: General error: java.lang.NullPointerException
         at org.hsqldb.jdbc.jdbcUtil.sqlException(Unknown Source)
         at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
         at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
         at org.hsqldb.jdbcDriver.connect(Unknown Source)
         at java.sql.DriverManager.getConnection(DriverManager.java:512)
         at java.sql.DriverManager.getConnection(DriverManager.java:171)
         at org.jboss.jdbc.HypersonicDatabase.getConnection(HypersonicDatabase.java:806)
         at org.jboss.jdbc.HypersonicDatabase.startStandaloneDatabase(HypersonicDatabase.java:617)
         at org.jboss.jdbc.HypersonicDatabase.startService(HypersonicDatabase.java:587)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
         at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
         at $Proxy0.start(Unknown Source)
         at org.jboss.system.ServiceController.start(ServiceController.java:416)
         at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy4.start(Unknown Source)
         at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:272)
         at $Proxy34.start(Unknown Source)
         at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:228)
         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
         at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy8.deploy(Unknown Source)
         at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
         at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
         at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
         at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
         at $Proxy0.start(Unknown Source)
         at org.jboss.system.ServiceController.start(ServiceController.java:416)
         at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy4.start(Unknown Source)
         at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy5.deploy(Unknown Source)
         at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:413)
         at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
         at org.jboss.Main.boot(Main.java:162)
         at org.jboss.Main$1.run(Main.java:423)
         at java.lang.Thread.run(Thread.java:534)
    14:31:51,968 WARN [ServiceController] Problem starting service jboss:database=localDB,service=Hypersonic
    java.sql.SQLException: General error: java.lang.NullPointerException
         at org.hsqldb.jdbc.jdbcUtil.sqlException(Unknown Source)
         at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
         at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
         at org.hsqldb.jdbcDriver.connect(Unknown Source)
         at java.sql.DriverManager.getConnection(DriverManager.java:512)
         at java.sql.DriverManager.getConnection(DriverManager.java:171)
         at org.jboss.jdbc.HypersonicDatabase.getConnection(HypersonicDatabase.java:806)
         at org.jboss.jdbc.HypersonicDatabase.startStandaloneDatabase(HypersonicDatabase.java:617)
         at org.jboss.jdbc.HypersonicDatabase.startService(HypersonicDatabase.java:587)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
         at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
         at $Proxy0.start(Unknown Source)
         at org.jboss.system.ServiceController.start(ServiceController.java:416)
         at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy4.start(Unknown Source)
         at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:272)
         at $Proxy34.start(Unknown Source)
         at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:228)
         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
         at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy8.deploy(Unknown Source)
         at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
         at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
         at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
         at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
         at $Proxy0.start(Unknown Source)
         at org.jboss.system.ServiceController.start(ServiceController.java:416)
         at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy4.start(Unknown Source)
         at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy5.deploy(Unknown Source)
         at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:413)
         at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
         at org.jboss.Main.boot(Main.java:162)
         at org.jboss.Main$1.run(Main.java:423)
         at java.lang.Thread.run(Thread.java:534)
    14:31:52,562 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:name=JmsXA,service=ConnectionFactoryBinding to JNDI name 'java:JmsXA'
    14:31:52,921 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:name=MySqlDS,service=DataSourceBinding to JNDI name 'java:MySqlDS'
    14:31:53,000 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C:/jboss-4.0.1/server/default/deploy/jmx-console.war/
    14:31:53,515 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C:/jboss-4.0.1/server/default/deploy/management/web-console.war/
    14:31:54,859 INFO [EARDeployer] Init J2EE application: file:/C:/jboss-4.0.1/server/default/deploy/teste.ear
    14:31:56,125 INFO [EjbModule] Deploying Teste
    14:31:56,421 WARN [StatelessSessionContainer] No resource manager found for jms/PointToPoint
    14:31:56,453 INFO [EJBDeployer] Deployed: file:/C:/jboss-4.0.1/server/default/tmp/deploy/tmp4815teste.ear-contents/teste-ejb.jar
    14:31:56,562 INFO [TomcatDeployer] deploy, ctxPath=/teste, warUrl=file:/C:/jboss-4.0.1/server/default/tmp/deploy/tmp4815teste.ear-contents/teste-exp.war/
    14:31:56,937 INFO [EARDeployer] Started J2EE application: file:/C:/jboss-4.0.1/server/default/deploy/teste.ear
    14:31:56,937 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
    MBeans waiting for other MBeans:
    ObjectName: jboss.ejb:persistencePolicy=database,service=EJBTimerService
    state: CREATED
    I Depend On: jboss.jca:name=DefaultDS,service=DataSourceBinding
    Depends On Me:
    ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
    state: CREATED
    I Depend On: jboss.mq:service=Invoker
    jboss.web:service=WebServer
    Depends On Me:
    ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
    state: CREATED
    I Depend On: jboss:service=TransactionManager
    jboss.jca:name=DefaultDS,service=DataSourceBinding
    Depends On Me:
    ObjectName: jboss.mq:service=StateManager
    state: CREATED
    I Depend On: jboss.jca:name=DefaultDS,service=DataSourceBinding
    Depends On Me: jboss.mq:service=DestinationManager
    ObjectName: jboss.mq:service=DestinationManager
    state: CREATED
    I Depend On: jboss.mq:service=MessageCache
    jboss.mq:service=PersistenceManager
    jboss.mq:service=StateManager
    Depends On Me: jboss.mq.destination:name=testTopic,service=Topic
    jboss.mq.destination:name=securedTopic,service=Topic
    jboss.mq.destination:name=testDurableTopic,service=Topic
    jboss.mq.destination:name=testQueue,service=Queue
    jboss.mq.destination:name=A,service=Queue
    jboss.mq.destination:name=B,service=Queue
    jboss.mq.destination:name=C,service=Queue
    jboss.mq.destination:name=D,service=Queue
    jboss.mq.destination:name=ex,service=Queue
    jboss.mq:service=SecurityManager
    jboss.mq.destination:name=DLQ,service=Queue
    ObjectName: jboss.mq:service=PersistenceManager
    state: CREATED
    I Depend On: jboss.jca:name=DefaultDS,service=DataSourceBinding
    Depends On Me: jboss.mq:service=DestinationManager
    ObjectName: jboss.mq.destination:name=testTopic,service=Topic
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    jboss.mq:service=SecurityManager
    Depends On Me:
    ObjectName: jboss.mq.destination:name=securedTopic,service=Topic
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    jboss.mq:service=SecurityManager
    Depends On Me:
    ObjectName: jboss.mq.destination:name=testDurableTopic,service=Topic
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    jboss.mq:service=SecurityManager
    Depends On Me:
    ObjectName: jboss.mq.destination:name=testQueue,service=Queue
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    jboss.mq:service=SecurityManager
    Depends On Me:
    ObjectName: jboss.mq.destination:name=A,service=Queue
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    Depends On Me:
    ObjectName: jboss.mq.destination:name=B,service=Queue
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    Depends On Me:
    ObjectName: jboss.mq.destination:name=C,service=Queue
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    Depends On Me:
    ObjectName: jboss.mq.destination:name=D,service=Queue
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    Depends On Me:
    ObjectName: jboss.mq.destination:name=ex,service=Queue
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    Depends On Me:
    ObjectName: jboss.mq:service=Invoker
    state: CREATED
    I Depend On: jboss.mq:service=TracingInterceptor
    Depends On Me: jboss.mq:service=InvocationLayer,type=HTTP
    jboss.mq:service=InvocationLayer,type=JVM
    jboss.mq:service=InvocationLayer,type=UIL2
    ObjectName: jboss.mq:service=TracingInterceptor
    state: CREATED
    I Depend On: jboss.mq:service=SecurityManager
    Depends On Me: jboss.mq:service=Invoker
    ObjectName: jboss.mq:service=SecurityManager
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    Depends On Me: jboss.mq.destination:name=testTopic,service=Topic
    jboss.mq.destination:name=securedTopic,service=Topic
    jboss.mq.destination:name=testDurableTopic,service=Topic
    jboss.mq.destination:name=testQueue,service=Queue
    jboss.mq:service=TracingInterceptor
    jboss.mq.destination:name=DLQ,service=Queue
    ObjectName: jboss.mq.destination:name=DLQ,service=Queue
    state: CREATED
    I Depend On: jboss.mq:service=DestinationManager
    jboss.mq:service=SecurityManager
    Depends On Me:
    ObjectName: jboss.mq:service=InvocationLayer,type=JVM
    state: CREATED
    I Depend On: jboss.mq:service=Invoker
    Depends On Me:
    ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
    state: CREATED
    I Depend On: jboss.mq:service=Invoker
    Depends On Me:
    ObjectName: jboss.jca:name=DefaultDS,service=LocalTxCM
    state: CREATED
    I Depend On: jboss.jca:name=DefaultDS,service=ManagedConnectionPool
    jboss.jca:service=CachedConnectionManager
    jboss.security:service=JaasSecurityManager
    jboss:service=TransactionManager
    Depends On Me: jboss.jca:name=DefaultDS,service=DataSourceBinding
    ObjectName: jboss.jca:name=DefaultDS,service=ManagedConnectionPool
    state: CREATED
    I Depend On: jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
    Depends On Me: jboss.jca:name=DefaultDS,service=LocalTxCM
    ObjectName: jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
    state: CREATED
    I Depend On: jboss:database=localDB,service=Hypersonic
    jboss.jca:name='jboss-local-jdbc.rar',service=RARDeployment
    Depends On Me: jboss.jca:name=DefaultDS,service=ManagedConnectionPool
    ObjectName: jboss.jca:name=DefaultDS,service=DataSourceBinding
    state: CREATED
    I Depend On: jboss.jca:name=DefaultDS,service=LocalTxCM
    jboss:service=invoker,type=jrmp
    Depends On Me: jboss.ejb:persistencePolicy=database,service=EJBTimerService
    jboss:service=KeyGeneratorFactory,type=HiLo
    jboss.mq:service=StateManager
    jboss.mq:service=PersistenceManager
    ObjectName: jboss:database=localDB,service=Hypersonic
    state: FAILED
    I Depend On:
    Depends On Me: jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
    java.sql.SQLException: General error: java.lang.NullPointerException
    MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
    ObjectName: jboss:database=localDB,service=Hypersonic
    state: FAILED
    I Depend On:
    Depends On Me: jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
    java.sql.SQLException: General error: java.lang.NullPointerException
    14:31:57,265 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
    14:31:57,578 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
    14:31:57,609 INFO [JkMain] Jk running ID=0 time=0/141 config=null
    14:31:57,625 INFO [Server] JBoss (MX MicroKernel) [4.0.1 (build: CVSTag=JBoss_4_0_1 date=200412230944)] Started in 33s:766ms

Maybe you are looking for

  • HT1351 iTunes won't sync a tv show to my iPod Classic

    I just bought a new tv show from iTunes the other day. When I connect my ipod classic to iTunes, it automtically adds all new media that I've download to iTunes. But now I get this alert message telling me that the tv show I just bought, on iTunes, c

  • Gallery unable to access images in memory card

    Hi!  I am using E71 and recently I find that Gallery can't access the images and videos in the memory card.  Images in Phone Memory is accesible.  I can access those files from File Manager though.  Does anybody know how to fix this?  Would appreciat

  • Deski report which is using a Store Procedure - Redirecting connection

    I have a DeskI report which is using a Store Procedure as its data provider. This is an Oracle based Store Procedure. Where can i see wich connection (connections listed in CMC) is used in DeskI report ? How can i redirect one connection to point to

  • V30.0.016 update not showing on NSU

    ON the can I update page it says that V30.0.016 is available for product code 0570817 but it doesn't show up on NSU! Has anyone been able to update yet? N900 (V3.2010.02-8.203.1 / Rx-51) N97 (V21.0.102 / RM-505)

  • Resource execution time..

    Hi gurus, version:11.0.6.0 platform:windows 7 we daily execute around 170-180 sql queries to fetch data from different-different servers and also use spool function in each query to save the output onto csv file but it take a lot time while execution