Message-destination-descriptor

Hi, everyvone. I have recent problem with message destination mapping. I need map in weblogic-ejb-jar.xml real destination to my one written in ejb-jar. Could you please post here some example of this weblogic-ejb-jar.xml ?? Thanks a lot

Hello.
Your weblogic-ejb-jar.xml is not xsd valid.
First of all, there is no description tag which seems to be mandatory. You should check the file with a validator.
Regards.
Aurélien.

Similar Messages

DPL8007: Unsupported deployment descriptors element message-destination?

Hi All,
I am not able to run a working Java EE 5 JMS tutorial in jdk1.6.0_25, GF3.1 (bundled with Netbeans 7.0 on Windows XP) despite having re-created the whole project from scratch. Below is the code snippets of various components of the project:
C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\src\java\com\ensode\mdb\MessageReceiverBean.java
@MessageDriven(mappedName = "jms/myQueue", activationConfig = {
 @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
 @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
public class MessageReceiverBean implements MessageListener {
 @Override
 public void onMessage(Message message) {
 TextMessage textMessage = (TextMessage) message;
 try {
 System.out.println("Received message:" + textMessage.getText());
 } catch (JMSException ex) {
 Logger.getLogger(MessageReceiverBean.class.getName()).log(Level.SEVERE, null, ex);
C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProjectApplicationClient\src\java\com\ensode\jms
public class Main {
 @Resource(name = "jms/myQueue")
 private static Queue myQueue;
 @Resource(name = "jms/myQueueConnectionFactory")
 private static ConnectionFactory myQueueConnectionFactory;
 public static void main(String[] args) throws JMSException {
 new Main().sendJMSMessageToMyQueue("NetBeans makes JMS trivial!");
 private Message createJMSMessageForjmsMyQueue(Session session,
 Object messageData) throws JMSException {
 TextMessage textMessage = session.createTextMessage();
 textMessage.setText((String) messageData);
 return textMessage;
 private void sendJMSMessageToMyQueue(Object messageData) throws
 JMSException {
 Connection connection = null;
 Session session = null;
 try {
 connection = myQueueConnectionFactory.createConnection();
 session = connection.createSession(false,
 javax.jms.Session.AUTO_ACKNOWLEDGE);
 MessageProducer messageProducer = session.createProducer(myQueue);
 messageProducer.send(createJMSMessageForjmsMyQueue(session,
 messageData));
 } finally {
 if (session != null) {
 session.close();
 if (connection != null) {
 connection.close();
C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\setup\glassfish-resources.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources PUBLIC "-//GlassFish.org//DTD GlassFish Application Server 3.1 Resource Definitions//EN" "http://glassfish.org/dtds/glassfish-resources_1_5.dtd">
<resources>
<admin-object-resource enabled="true" jndi-name="jms/myQueue" object-type="user" res-adapter="jmsra" res-type="javax.jms.Queue">
 <property name="Name" value="myQueue"/>
</admin-object-resource>
<connector-resource enabled="true" jndi-name="jms/myQueueConnectionFactory" object-type="user" pool-name="jms/myQueueConnectionFactory">
 <description/>
</connector-resource>
<connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.QueueConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/myQueueFactoryPool" ping="false" pool-resize-quantity="2" pooling="true" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
<connector-resource enabled="true" jndi-name="jms/myQueueFactory" object-type="user" pool-name="jms/myQueueFactoryPool"/>
<connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.ConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/myQueueConnectionFactory" ping="false" pool-resize-quantity="2" pooling="true" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
</resources>Yet it was met with the following exception which appears to be an unsupported deployment descriptor generated by Netbeans 7.0:
_GF3.1 server log_
WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
_Application Client Outpu
t_10/05/2011 2:59:45 AM com.sun.enterprise.deployment.util.ComponentValidator accept
WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
com.sun.enterprise.container.common.spi.util.InjectionException: Exception attempting to inject Unresolved Message-Destination-Ref jms/[email protected]@null into class com.ensode.jms.Main
Caused by: javax.naming.NamingException: Lookup failed for 'java:comp/env/jms/myQueue' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]]glassfish-resources.xml used to reside in C:\Documents and Settings\jack\JMSEnterpriseProject\ setup\ sun-resources.xml back in GF2.1.
Deployment was successful which resulted in the following resources created:
Connector Resources => jms/myQueueConnectionFactory, jms/myQueueFactory.
Connector Connection Pools => jms/myQueueFactoryPool, jms/myQueueConnectionFactory.
Admin Object Resources => jms/myQueue.
Your assistance would be very much appreciated.
Thanks,
Jack

Hi,
The same unsupported deployment descriptor persists despite having removed C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\setup\glassfish-resources.xml with the following exception:
10/05/2011 11:41:22 PM com.sun.enterprise.deployment.util.ComponentValidator accept
WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
10/05/2011 11:41:28 PM org.hibernate.validator.util.Version <clinit>
INFO: Hibernate Validator 4.1.0.Final
10/05/2011 11:41:28 PM org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter: Version: 4.5 (Build 29-b) Compile: Wed Feb 9 22:53:30 PST 2011
10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter starting: broker is REMOTE, connection mode is TCP
10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter Started:REMOTE
com.sun.enterprise.container.common.spi.util.InjectionException: Exception attempting to inject Unresolved Message-Destination-Ref jms/[email protected]@null into class com.ensode.jms.Main
 at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:698)
 at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.inject(InjectionManagerImpl.java:468)
 at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectClass(InjectionManagerImpl.java:215)
 at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectClass(InjectionManagerImpl.java:207)
 at org.glassfish.appclient.client.acc.AppClientContainer$ClientMainClassSetting.getClientMainClass(AppClientContainer.java:619)
 at org.glassfish.appclient.client.acc.AppClientContainer.getMainMethod(AppClientContainer.java:511)
 at org.glassfish.appclient.client.acc.AppClientContainer.completePreparation(AppClientContainer.java:405)
 at org.glassfish.appclient.client.acc.AppClientContainer.prepare(AppClientContainer.java:319)
 at org.glassfish.appclient.client.AppClientFacade.prepareACC(AppClientFacade.java:278)
 at org.glassfish.appclient.client.acc.agent.AppClientContainerAgent.premain(AppClientContainerAgent.java:76)
 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:597)
 at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323)
 at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
Caused by: javax.naming.NamingException: Lookup failed for 'java:comp/env/jms/myQueue' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]]
 at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:518)
 at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:597)
 ... 15 more
Caused by: javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]
 at com.sun.enterprise.naming.impl.JavaURLContext.lookup(JavaURLContext.java:242)
 at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:498)
 ... 18 more
Caused by: java.lang.NullPointerException
 at javax.naming.InitialContext.getURLScheme(InitialContext.java:269)
 at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:318)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at com.sun.enterprise.naming.util.JndiNamingObjectFactory.create(JndiNamingObjectFactory.java:82)
 at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:772)
 at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:740)
 at com.sun.enterprise.naming.impl.JavaURLContext.lookup(JavaURLContext.java:172)It is running on Windows 7 as opposed to XP earlier on.
Is it possible that this is a bug since all JMS resources have been declared without using deployment descriptor at all?
Thanks,
Jack

Hp recovery on laptop gives error message "destination drive not connected"

I'm trying to carry out factory reset on my 2012 G6 laptop product code B2Y48EA*ABU serial no. [Personal Information Removed] to factory settings using set of 5 recovery discs
I followed the procedure shown here (although the screen messages are slightly different)
http://support.hp.com/gb-en/document/c01867418
I started the laptop with disc 1 in the dvd drive and the hp program was displayed. I selected "factory reset" and followed promts
When the 4 th disc is in dvd drive and the process is about53% compltete it stops with the error message
"destination drive not connected"
and fails
Earlier the recovery manager reported that the partion on the hard drive had been re-forrmatted so the drive was connected then!
All help and suggestions appreciated

Hi there @Teka,
I understand that you are having trouble with a System Recovery to a factory image using recovery disks. I am happy to help you with this.
Are those five disks a set that you created using the recovery manager, or is it a set you ordered from HP?
Is there any sign of damage, scratches or smudges on the disk it fails on?
Have you tried cleaning the DVD drive?
Also take a look through these pages, in particular the troubleshooting page, and see if anything there is of use.
Performing an HP System Recovery (Windows 7)
Troubleshooting HP System Recovery Problems (Windows 7)
Let me know how it goes for you.
Malygris1
I work on behalf of HP
Please click Accept as Solution if you feel my post solved your issue, it will help others find the solution.
Click Kudos Thumbs Up on the right to say “Thanks” for helping!

Format of "JMS Message Destination Parameter" for JMS Sender Adapter

Hi,
I am trying to use the JMS Sender Communication Channel for several Interfaces by using the "JMS Message Destination Parameter". Currently, the Comm.Channel is reading the message and puts it back on the queue with the following error:
Fehler bei der XI-Eingangsverarbeitung für Message am bzw. um 2007-07-25|09:34:12.057+0200. JMS- und XI-Identifikatoren für die Message sind ID:414d512051535749515441302020202046a4e892201c4d04 bzw. 701ec850-3a81-11dc-8176-00306e2c36a3. Der JMS-Adapter führt einen Rollback der Datenbank und der JMS-Sitzungtransaktionen durch. Wird die Sitzung ausgeführt, geht die Message nicht verloren und wird später erneut durchgeführt. Der Ausnahme-Stack-Trace ist java.lang.RuntimeException: MQJMS0003: Destination not understood or no longer valid: UserCreateRequest
at com.ibm.mq.jms.MQDestination.createDestination(MQDestination.java:790)
at com.ibm.mq.jms.MQSession.createDestination(MQSession.java:1092)
at com.ibm.jms.JMSMessage.getJMSDestination(JMSMessage.java:4127)
What is the format I will have to fill this parameter with in order for XI to understand it? I have tried the following so far which did not work:
1. (as in error message above)
Help much appreciated.
KR,
Colin.

One option in BPEL is to have a mid process receive, but this would require you to handle the Correlation of the message with BPEL process instance.
Please refer the following section in SOA Guide for the same.
Using Correlation Sets and Message Aggregation - 11g Release 1 (11.1.1.7)
Please note the example is with File adapter but the same can be achieved for Any Adapter.

[svn] 3897: BLZ-266: Ajax FABridge doesn' t pull in channel info for messaging destination

Revision: 3897
Author: [email protected]
Date: 2008-10-26 17:10:00 -0700 (Sun, 26 Oct 2008)
Log Message:
BLZ-266: Ajax FABridge doesn't pull in channel info for messaging destination
(merge branch changelist 3896 to mainline)
qa: yes
doc: no
bug: BLZ-266
checkintests: passed
Details:
/resources/fds-ajax-bridge/actionscript/FDMSBridge.as
* need to initialize the parameters for the LoaderConfig
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-266
http://bugs.adobe.com/jira/browse/BLZ-266
Modified Paths:
blazeds/trunk/resources/fds-ajax-bridge/actionscript/FDMSBridge.as

[svn] 3896: BLZ-266: Ajax FABridge doesn' t pull in channel info for messaging destination

Revision: 3896
Author: [email protected]
Date: 2008-10-26 16:02:33 -0700 (Sun, 26 Oct 2008)
Log Message:
BLZ-266: Ajax FABridge doesn't pull in channel info for messaging destination
qa: yes
doc: no
bug: BLZ-266
checkintests: passed
Details:
/resources/fds-ajax-bridge/actionscript/FDMSBridge.as
* need to initialize the parameters for the LoaderConfig
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-266
http://bugs.adobe.com/jira/browse/BLZ-266
Modified Paths:
blazeds/branches/3.0.x/resources/fds-ajax-bridge/actionscript/FDMSBridge.as

"message-destination-ref-mapping" definition in EJB3.0 style annotation

Hello,
Here is how I used to define "resource-ref-mapping" and "message-destination-ref-mapping" in ejb 2.1
<resource-ref-mapping
location = "MQJMSRASubcontext/MyQCF"
name = "jms/MQConnectionFactory"/>
<message-destination-ref-mapping
location = "MQJMSRASubcontext/MQQ"
name = "jms/MQQQueueDestination"/>
I want to do define these two properties in ejb3.0 using annotation. Any help will be much appreciated.
Thanks,
Mustafa

Hello,
Here is how I used to define "resource-ref-mapping" and "message-destination-ref-mapping" in ejb 2.1
<resource-ref-mapping
location = "MQJMSRASubcontext/MyQCF"
name = "jms/MQConnectionFactory"/>
<message-destination-ref-mapping
location = "MQJMSRASubcontext/MQQ"
name = "jms/MQQQueueDestination"/>
I want to do define these two properties in ejb3.0 using annotation. Any help will be much appreciated.
Thanks,
Mustafa

The Error Message 'Application descriptor file cannot be parsed' shows when compiling (Ctrl + Enter) Adobe AIR for Android applications on Flash Professional CS5.5

The Error Message 'Application descriptor file cannot be parsed' shows when compiling (Ctrl + Enter) Adobe AIR for Android applications on Flash Professional CS5.5
This is happening for most of the pupils and staff at our school and they are unable to complete their work.
This also happens on a fresh copy of windows and CS5.5 without any updates and also with all latest updates.
I have tried it on 32-bit and 64-bit CS5, Windows, Air and Java with the same error every time.
There are a small minority of users where this works fine for them with no issue.
I have tried re-setting user profiles.
I have tried a local admin and domain admin account with the same issue
I have noticed however that if the file is moved to the shared area it will compile. If it is on their documents area it will not compile. The users have full control in both locations. This is fine for staff but we are unable to give full control or modify access to the shared area for the pupil's
I have been through the online support section and it directed me to phone Adobe Customer care who informed me that all support has been discontinued for CS5, CS5.5 and CS6 and they will only support creative cloud.
Any ideas what to try next? There is no other information about this error and I cannot work out what is causing it.

I have tried and able to package an apk using your XML file.Could you please make sure your XML file starting from line 1 and coloumn 0.Any space will results in the error (Application Descriptor file cannot be parsed)
-Pranali

[svn] 4226: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4226 Author: [email protected] Date: 2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008) Log Message: ----------- Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. QA: Yes Doc: No Checkintests Pass: Yes Details: * Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element. Ticket Links: ------------ http://bugs.adobe.com/jira/browse/LCDS-517 Modified Paths: -------------- blazeds/trunk/modules/core/src/flex/messaging/Destination.java

Revision: 4226 Author: [email protected] Date: 2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008) Log Message: ----------- Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. QA: Yes Doc: No Checkintests Pass: Yes Details: * Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element. Ticket Links: ------------ http://bugs.adobe.com/jira/browse/LCDS-517 Modified Paths: -------------- blazeds/trunk/modules/core/src/flex/messaging/Destination.java

[svn] 4195: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4195
Author: [email protected]
Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

Revision: 4195
Author: [email protected]
Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

[svn] 4193: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4193
Author: [email protected]
Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
* Also typo in comment in AbstractConnectionAwareSession fixed.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
blazeds/trunk/modules/core/src/flex/messaging/Destination.java
blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

Revision: 4193
Author: [email protected]
Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
* Also typo in comment in AbstractConnectionAwareSession fixed.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
blazeds/trunk/modules/core/src/flex/messaging/Destination.java
blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

[svn:fx-3.x] 7197: Bug: BLZ-354 - Client still polling after calling ChannelSet.logout() when subscribed to messaging destination.

Revision: 7197
Author:   [email protected]
Date:     2009-05-21 14:49:44 -0700 (Thu, 21 May 2009)
Log Message:
Bug: BLZ-354 - Client still polling after calling ChannelSet.logout() when subscribed to messaging destination.
QA: Yes
Doc: No
Checkintests: Pass
Details: In polling channels, stop polling as soon as logout ack is received.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-354
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

Any advice would be helpful. Thanks

Can't Delete A Message: Destination mailbox does not exist

Got a spam email today and Mail won't let me delete it. Clicking Delete grays the message, but it won't move to the Trash. If I try and drag it manually, I get the error message "destination mailbox does not exist."
And it's right: the To: address is a fake one and NOT one of my accounts.
Anyone know how in the world I can get rid of this message?

Hi Ernie,
Thanks for your help. In the end, my solution was to delete the GMail account completely from Mail.app, recreate it and let it synchronise my mail back from Google (I have Mail.app set to leave messages on the server, for GMail). I now of course have all the 'correct' emails back in Mail.app, without the ones I could not delete.
I can tell you, though, that there were indeed no other files in the old INBOX.mbox folder other than the ones you mentioned. What other files might there have been?

Deployment tool application message destinations

filled out the Message Destinations sceen for my bean, including JNDI name.
Sun-specific settings screen, for the bean, includes the Message Destinations entry
Sun-specific settings screen, for the application, has an empty Message Destinations panel

See the JMS chapters in The J2EE 1.4 Tutorial for information on how to do this:
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/index.html

Adobe AIR Error Message - Application Descriptor

Upon starting my computer I keep getting an error message for Adobe AIR stating, "Application descriptor could not be found for this application. Try re-installing or contacting the publisher for assistance." I have uninstalled and re-installed Adobe AIR THREE times and have restared my computer with each new re-installation. The error message is still showing. Please let me know how to resolve this issue.
Thank you.

I successfully gotten rid of it for WINDOW 7.
This can be caused by some error/conflict with Air Adobe and any start-up programs scheduled to "open" "activated" at the first appearance of your desktop.
To find out what programs are running at the startup:
     Click "Start"
     type "msconfig" in the search engine at the bottom
     click on "msconfig" icon appearing on top
     a pop-up window titled "System Configuration" will appear
     Click on "Startup" tab
     At this point, I unclicked unnecessary programs that are not crucial in operating my computer.
     Click "apply" or "Ok"
     another pop-up window will ask you if you want to restart your computer.
I am not sure if I solved the "conflict' but certainly got rid of the annoying error message by turning off some "unnecessary" software that was automatically set to start as the computer booted.

Message-destination-descriptor

Similar Messages

Maybe you are looking for