Delivery Status Notification (Failure)
by postmaster＠lists.jboss.org
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
dilallo@localhost
17 years, 9 months
Delivery Notification <iliya@eng.auburn.edu, alexie@eng.auburn.edu>
by Postmaster＠lists.jboss.org
This is a delivery status notification, automatically generated by MTA im2.duc.auburn.edu on Mon, 07 Jul 2008 05:21:09 -0500
Regarding recipient(s) : iliya@eng.auburn.edu,alexie(a)eng.auburn.edu
Delivery status : Failed. Message could not be delivered to domain <eng.auburn.edu> .Failed while initiating the protocol. <[('iliya(a)eng.auburn.edu', 550, '5.1.1 <iliya(a)eng.auburn.edu>... User unknown'), ('alexie(a)eng.auburn.edu', 550, '5.1.1 <alexie(a)eng.auburn.edu>... User unknown')]>
MTA Response :550
The original message headers are included as attachment.
17 years, 9 months
[JBoss Messaging] - Re: Exception when starten 2nd node
by mbreuer
"ataylor" wrote : anonymous wrote : But this does not explain how an failover works with an MDB
|
| MDB's are outside the scope of JBM. You can find more information from the app server guys or the app server docs.
|
;-)
The app server 4.2.2 docs don't describe how jms works with new messaging. Even there's a note, that future revision will use new jboss messaging. Also it notes that messaging will work completely different from jbossmq.
The newer 5.0.0 jbossas doc is not accessible for me.
( (http://labs.jboss.com/file-access/default/members/jbossas/freezone/docs/C...)
anonymous wrote :
| anonymous wrote :
| | You should have if a node crashes, the other must do the work. Messages should not be left unprocessed in a (local) queue anonymous wrote :
| |
| | Messages will never be left unprocessed, The MDB on node A will consume messages from the queue on node A, and the MDB on node B from the queue on node B. If node A goes down, its state is replicated on node B so the messages will then be consumed on node B.
:o)
My example even does not work. But as I understand, you are (as messaging-developer) out of scope for this problem. Which forum I should post to?
Is there another way to get the latest jbossas (beta) docs?
And last but not least what is your opinion of using jboss messaging together with jbossas 4.2.2 in a clustered environment?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162778#4162778
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162778
17 years, 9 months
[Installation, Configuration & DEPLOYMENT] - Re: 5.0.0CR1: deployment error with @PersistenceContext and
by Juergen.Zimmermann
As mentioned before: it's an application that works fine with 4.2.2.
Here is the Interface without any annotation:public interface Bestellverwaltung {
|
| Bestellung findBestellungById(Long id) throws BestellungNotFoundException;
| ...
Here is the bean class:@Stateless
| @Local(Bestellverwaltung.class)
| public class BestellverwaltungBean implements Bestellverwaltung {
| @SuppressWarnings("unused")
| @PersistenceContext(name="hskaPersistence")
| private EntityManager em;
|
| @EJB
| private Kundenverwaltung kv;
|
| @EJB
| private BestellverwaltungDao dao;
|
| @SuppressWarnings("unused")
| @PreDestroy
| private void preDestroy() {...}
| ...
And also the persistence.xml:<?xml version="1.0" encoding="ISO-8859-1"?>
|
| <persistence xmlns="http://java.sun.com/xml/ns/persistence"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
| version="1.0">
|
| <persistence-unit name="hskaPersistence">
| <provider>org.hibernate.ejb.HibernatePersistence</provider>
|
| <!-- Hibernate Console: in Kommentar setzen -->
| <jta-data-source>java:/hskaDS</jta-data-source>
|
| <properties>
| <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect"/>
|
| <!-- Keine proprietaeren Erweiterungen von HQL nutzen -->
| <property name="hibernate.query.jpaql_strict_compliance" value="true"/>
|
| <!-- In der Log-Datei die SQL-Anweisungen lesbarer rausschreiben -->
| <property name="hibernate.format_sql" value="true"/>
|
| <!-- In der Log-Datei auch Kommentare zu den generierten SQL-Anweisungen hinzufuegen -->
| <property name="hibernate.use_sql_comments" value="true"/>
|
| <!-- Batch fuer DML von automatisch versionierten Datensaetzen -->
| <property name="hibernate.jdbc.batch_versioned_data" value="true"/>
|
| <property name="hibernate.cache.provider_class" value="org.hibernate.cache.HashtableCacheProvider"/>
|
| <property name="hibernate.cache.use_query_cache" value="true"/>
|
| <!-- Klassen und Collections fuer Caching der persistenten Objekte -->
| <!-- falls TreeCache statt HashtableCache: read-write aendern in transactional -->
| <property name="hibernate.ejb.classcache.de.hska.kundenverwaltung.db.Kunde" value="read-write, /kunden"/>
| <property name="hibernate.ejb.collectioncache.de.hska.kundenverwaltung.db.Kunde.bestellungen" value="read-write, /bestellungen"/>
| <property name="hibernate.ejb.classcache.de.hska.bestellverwaltung.db.Bestellung" value="read-write, /bestellungen"/>
| <property name="hibernate.ejb.classcache.de.hska.bestellverwaltung.db.Lieferung" value="read-write, /lieferungen"/>
| </properties>
| </persistence-unit>
| </persistence>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162775#4162775
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162775
17 years, 9 months
