Acknowledgement Mode

Hi All,
Can anyone explain about Acknowledgement Mode in deliviery channel and Acknowledgement Mode options (Sync and Async)
I am using AS2, I dont understand how to configure Deliviery channel, Is there any document which describes about Deliviery channel
Regards

Nitesh,
Thanks for your response
I send one 850 transaction to supplier with sync and it shows waitFA and later that I send one more 850 to supplier with ASYNC it shows waitack,
I am not receiving any MDN back from them
and the main problem is that, While sending po with sync it went with correct URL(Ex: ...../b2b/transportserver)
but after that we send another PO with ASync then it went with different url
Could you please help me whats the reason behind this?
Regards

Similar Messages

Redelivery in Auto Acknowledge Mode

Hi all,
On reading the JMS spec I found the following text
�AUTO_ACKNOWLEDGE - With this option, the session automatically acknowledges a client�s receipt of a message when it has either successfully returned from a call to receive or the MessageListener it has called to process the message successfully returns.�
I take this to mean if the call to process the message returns unsuccessfully i.e. by throwing a runtime exception. Then it will redeliver the message. It works fine in Weblogic 5.1. I was wondering if this is the correct way to do this or is there another proper way to do this?
Cheers,
Ben.

According to the spec, throwing a RuntimeException marks the client as errorneous. It might be that the provider disables the client or the client's session. At least this is what SwiftMQ does, for example. So if you throw a RuntimeException, the message is redelivered but not to the client which throwed the exception because it's disabled. However, this depends how the provider implements it.
If you want clean redelivery, I recommend to use client ack or transacted sessions.
-- Andreas

How to get transacted session in direct mode with jmsra adapter

Hi,
I use MQ 4.4u1 release with GF in EMBEDDED mode. I configured several connection factories with NoTransaction/LocalTransaction/XATransaction support. In my app I get a connection factory from JNDI tree, create connection/session/producer and send several messages to queue. Everything works fine when I don't use transactions. But, when I want to send messages in one transaction, the connection always provided to me non-transacted session. The session created via
Session session = connection.createSession(true, Session.SESSION_TRANSACTED);
request. I check the session transacted state and acknowledge mode right after i get it:
log.fine("Session: " + session + "; transacted: " + session.getTransacted() + "; ackMode: " + session.getAcknowledgeMode());
The log shows me that the session is not transacted and ackMode is 0 (DUPS_OK_ACKNOWLEDGE). If I try to commit the session after messages were sent I get the correct exception:
javax.jms.IllegalStateException: MQJMSRA_DS4001: commit():Illegal for a non-transacted Session:sessionId=3361979872663370240
Does anyone know how to get transactional session in direct mode?
Thanks, Denis.

I mentioned LOCAL because I misread your post and thought you were suggesting that LOCAL mode behaved differently.
If you want to send messages in a transaction from within a Servlet then I think you're expected to use a UserTransaction: Here's an example that worked for me:
 Connection connection = outboundConnectionFactory.createConnection();
 Session session = connection.createSession(true, Session.SESSION_TRANSACTED);
 userTransaction.begin();
 MessageProducer producer = session.createProducer(outboundQueue);
 int numberOfMessages = 10;
 for (int i = 0; i<numberOfMessages; i++) {
 Message message = session.createTextMessage("Hello world");
 producer.send(message);
 userTransaction.commit();
 connection.close();I obtained the UserTransaction with this resource declaration:
 @Resource(name = "java:comp/UserTransaction")
 private UserTransaction userTransaction;The EJB spec explicitly states that local transactions aren't supported in EJBs; I haven't found such an explicit statement for Servlets but suspect that JMSRA is taking the same approach.
As for imq.jmsra.direct.disableCM property - this appears to disable connection pooling and from your post changes other behaviour as well. How did you find out about it (other than by examining the code)? As far as I can see this is not a documented feature and is not necessarily tested or supported.

Acknowledgement vs Durable

Could someone help me understand the difference between Acknowledgement modes and Durable subscripton. Below is what I understand and my questions are:
Say, I use auto_acknowledge then what happens if I dont get any acknowldgement? Yes, the msg is resent but what if acknt is never received even after resent? How long is the wait untill the msg is resent? Is the msg removed from server after some time? Is durable subscription a solution for this?

Durable subscriptions don't have different acknowledge behavior than non-durable subscriptions.
          To get started with JMS, I suggest reading through the BEA JMS developer documentation, and also the JMS info in one of the books listed here:
          http://dev2dev.bea.com/jms/index.html
          Also start here for the various options available for controlling redelivery:
          http://edocs.bea.com/wls/docs92/jms/manage_apps.html#ManagingRolledBackRecoveredRedeliveredorExpiredMessages

JMS Message Acknowledgement

Hi,
In my application I am using a Pub/Subscribe mode for JMS. I am using a durable subscriber. In the Subscriber side, I am opening a non-transacted TopicSession with Acknowledgement mode CLIENT_ACKNOWLEDGEMENT.
I have a Message listener which processes the message.
In my Message listener, I want to achieve the following...
Process the message, if processing succeeds, acknowledge the message. I am not acknowledging messages if the processing fails due to any reason..
Once, all the messages have been consumed, the program exits. While exiting the program, I am calling Message.recover() to put back unacknowledged messages back into the Topic...But I have observed the following problem...Say I receive the messages in the following order Message1, Message2, Message3.
Now if i don't acknowledge the Message3, and acknowledge the Message1 and 2...and the program exits...Then when the subscriber starts again, Message3 is still there in the Topic as it was not acknowledged...This is all goo...
Where is creates a problem is, say if I don't acknowledge the Message1 and acknowledge Message2 and 3 and the program exits...Now when the program exits, Message1 which was not acknowledged it also not present in the Topic...So acknowledging a message basically works like acknowledging all messages received prior to the particular message?? Is there a way to get around this problems? When I consume the messages in the Listener, can I put the messages that I don't want to acknowledge in a group or something like that? What I want to achieve is any message that is unacknowledged should be redelivered...How to achive that?
Thanks
surajit

As you assert, when you acknowledge Message2, you are also acknowledging all messages not previously acknowledged on the given session (I.E. Message1). That is, per the JMS Specification, how message acknowledgement works. There is no workaround as this is how it is designed.

Tibco Remote Jms Provider - Auto-acknowledge

Hi,
We have setup Weblogic 8.1.6 with Tibco EMS 4.2 as remote JMS provider.
It works, and we have configured an MDB as below:
-ejb-jar-
<message-driven>
<display-name>Order receiver MDB</display-name>
<ejb-name>OrderMDB</ejb-name>
<ejb-class>com.company.OrderMDB</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
And the question: We are receiving this in our weblogic log ( two minute intervalls ) and is is NOT application logging. What is it?
2008-08-26 08:39:32 [5816236 TIBCO EMS TCPLink Reader (2856200)] [TIBCO EMS]: received msg from daemon conn=2856200 seqi
d=14151393 msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442
2008-08-26 08:39:32 [-488738086 ExecuteThread: '3' for queue: 'weblogic.kernel.System'] [TIBCO EMS]: send qsndr=1274771
msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442 dlvmode=1 pri=5 ttl=240000 sess=3736118
2008-08-26 08:39:32 [5816236 TIBCO EMS TCPLink Reader (2856200)] [TIBCO EMS]: post msg to session sess=3736020 cons=2737
945 seqid=14151393 msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442
2008-08-26 08:39:32 [9425697 TIBCO EMS Session Dispatcher (3736020)] [TIBCO EMS]: before onMessage sess=3736020 cons=273
7945 seqid=14151393 msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442
/ Peter

Hi,
We have setup Weblogic 8.1.6 with Tibco EMS 4.2 as remote JMS provider.
It works, and we have configured an MDB as below:
-ejb-jar-
<message-driven>
<display-name>Order receiver MDB</display-name>
<ejb-name>OrderMDB</ejb-name>
<ejb-class>com.company.OrderMDB</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
And the question: We are receiving this in our weblogic log ( two minute intervalls ) and is is NOT application logging. What is it?
2008-08-26 08:39:32 [5816236 TIBCO EMS TCPLink Reader (2856200)] [TIBCO EMS]: received msg from daemon conn=2856200 seqi
d=14151393 msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442
2008-08-26 08:39:32 [-488738086 ExecuteThread: '3' for queue: 'weblogic.kernel.System'] [TIBCO EMS]: send qsndr=1274771
msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442 dlvmode=1 pri=5 ttl=240000 sess=3736118
2008-08-26 08:39:32 [5816236 TIBCO EMS TCPLink Reader (2856200)] [TIBCO EMS]: post msg to session sess=3736020 cons=2737
945 seqid=14151393 msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442
2008-08-26 08:39:32 [9425697 TIBCO EMS Session Dispatcher (3736020)] [TIBCO EMS]: before onMessage sess=3736020 cons=273
7945 seqid=14151393 msgid=ID:EMS_SIPLA01-02T_TSS_TST.427647BDB7AF390236:442
/ Peter

Acknowledge problem when upgrading aqapi.jar

Hi,
I am trying to upgrade my java TopicSubscriber interfacing with Oracle AQ, with a later version of aqapi.jar.
When switching to the later version of aqapi.jar then the messages does not get acknowledged properly.
This code used to work fine, but with the upgrade it seems like I have to add a session.commit() to my code, otherwise the messages are being resent to my application during restart.
What is the difference between aqapi13.jar(AQAPI13_BUILT_WITH_RDBMS_VERSION_9.0.2.0.0) and aqapi.jar (AQAPI_BUILT_WITH_RDBMS_VERSION_11.1.0.7.0) in terms of acknowledgement?
How come there is a need for a commit in the newer version of aqapi and not in the older version?
Thanks!
Sample code used to reproduce this issue
import java.util.*;
import java.io.*;
import java.lang.reflect.*;
import javax.jms.*;
import javax.naming.*;
import oracle.jms.*;
import java.io.Serializable;
while(true){
try {
javax.jms.TopicSubscriber _subscriber;
javax.jms.TextMessage _message;
javax.jms.TopicConnectionFactory _myFactory      = AQjmsFactory.getTopicConnectionFactory( "localhost", "LOCALAQ", 1521, "thin" );
javax.jms.TopicConnection myConnection   = myFactory.createTopicConnection( "sys as sysdba", "**PASSWORD**" );
javax.jms.TopicSession mySession      = myConnection.createTopicSession(true,javax.jms.Session.CLIENT_ACKNOWLEDGE);
javax.jms.Topic myTopic        = ( (AQjmsSession) mySession).getTopic( "sys", "SAMPLE_JMS_Q" );
_myConnection.start();
String messageSelector = new String("");
subscriber                        = mySession.createDurableSubscriber( _myTopic, "sys", "", false);
while(true){
message                            = ( javax.jms.TextMessage ) subscriber.receive( 0 );
System.out.println("_message.getText() : "+_message.getText());
System.out.println("_message.getJMSMessageID(): "+_message.getJMSMessageID());
_message.acknowledge();
//_mySession.commit() // needed for new version of aqapi.jar
}catch(Exception e){
e.printStackTrace();
}

Where can I find documentation describing the aq session class?
I decompiled AQjmsMessage and found these differences in the code.
aqapi.jar
public void acknowledge()     throws JMSException {
     Object obj = null;
     *if(session.getAcknowledgeMode() == 2){*
          Connection connection = session.getDBConnection();
          try{
               connection.commit();
          catch(SQLException sqlexception){
               throw new AQjmsException(sqlexception);
aqapi13.jar
public void acknowledge()     throws JMSException{
     Object obj = null;
     *if(session.getAckMode() == 2){*
          Connection connection = session.getDBConnection();
          try{
               connection.commit();
          catch(SQLException sqlexception){
               throw new AQjmsException(sqlexception);
Printing out the acknowledge mode with aqapi.jar gives these results
_mySession.getAckMode(): 2
_mySession.getAcknowledgeMode(): 0
and with aqapi13.jar
_mySession.getAckMode(): 2
I believe this is the reason why acknowledge() does not work properly with the later version of aqapi.jar
Is it possible to force the AcknowledgeMode to 2 when creating the TopicSession ?
Thanks for any ideas how to solve this!
Edited by: user6102378 on Jul 1, 2010 3:57 AM

Oracle JMS Client Acknowledgement?

Hi Guy,
How can we implement Client Ack mode using BPEL and JMS adapter?
There is no activity to acknowledge a message.
I tried configuring a outbound connection factory for JMSAdapter with acknowledgment mode as CLIENT_ACKNOWLEDGMENT, but didn't work as expected.
Please advise.
--Chari

In your JMS client, you can set the system properties "oracle.jms.minSleepTime" and "oracle.jms.maxSleepTime"
For example,
    System.setProperty("oracle.jms.minSleepTime", "100");
    System.setProperty("oracle.jms.maxSleepTime", "4000");
In this case, the listener will wait for 100ms to start with and the sleep time will be doubled if there is no new message - 200, 400, 800, 1600, 3200, and 4000 ms. The sleep time won't go beyond 4000ms and will be reset to 0 whenever there is a new message.

Turning off acknowledgement/EBX Header Issue

Hi Gurus,
I am in a scenario where I send an ebms message to a client partner that is not set up for ack. I have set b2b handles ack to false on the trading partner's operational capability and have even set the ack to none on the delivery channel.
Unfortunately my message is still failing stating that there is problem with the TP. The error that they are getting is that my server still wants an ack. Is there any other settings that may cause this?
I have even disabled the above settings on the host but I am still getting a failure.
Any help would be appreciated.
Thanks in advance.
Gerald
Edited by: Gerald M. on Jun 29, 2009 6:46 AM

Hi Gerald,
Your TP is right that you are requesting for an ack. Below log lines clear this -
*2009.06.22 at 13:57:34:625: Thread-40: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:isAckRequested Enter*
*2009.06.22 at 13:57:34:625: Thread-40: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:isAckRequested returning true*
*2009.06.22 at 13:57:34:625: Thread-40: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:createMessage unsigned ack is requested back*
But the error which you are getting in log is a transport error and there is no relation between Ack and Transport -
*2009.06.22 at 13:57:35:171: Thread-40: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab [IPT_HttpSendError] HTTP encounters send error :500*
It may be that somewhere in the configuration you have set the acknowledgement mode as "sync" and that is causing the issue.
Few checkpoints are -
1. Check the configuration of particular business action(in the operational capability of your TP) and make sure that no such value has been specified.
2. Check whether your TP's delivery channel has no values(you can mention zero also) for "Time To Acknowledge"
3. No where in above configuration, mode of communication is set to "Sync"
4. Follow the same configuration as of your another TP which you have disabled ("STATCAN"). This TP has acknowledgement tuned off.
Let us know the result.
Regards,
Anuj

Acknowledge and message producers

I can't seem to find a clear explanation of the difference, if any, between the CLIENT_ACKOWLEDGE and AUTO_ACKNOWLEDGE mode from the message producer's perspective. Is it because the server acknowledge is implicitly received when the publish() or send() methods return?
Thanks in advance.

That is an implementation specific question. For example in JBossMQ, a send is a send is a send unless the Session is transacted. In short, message sending behaves the same way regardless of what the acknowledge mode is on the Session. The acknowledge mode only comes into play on the other end.
Here is 1,000 foot view of how it works. You call send/publish, the IL calls a remote "send" method on the server passing the message as an argument. When that method has retuned successfully, the producer is done. Now the server has the message and it is its responsibility to get it to the proper consumer. So the server selectes a qualified consumer and calls a method on its instance of that client proxy passing in an array of Messages for delivery. The server, however, keeps a instance of that message until it receivs an explicit Acknowledge from the consuming client(s).
So, as I said, acknolwedgement only affect the consuming client. But that is just the way that JBossMQ currently implements it. Other providers are free to implement it anyway they wish so long as it fulfills the requirments of the spec. However, aside for peer-to-peer based JMS implementations, I cannot think of a reason to put acknowledgement code on the producer.
What can I do there? Can I keep the message and require the receiving client send me an acknowledgement? Ssounds good, but doesn't work becuase producers often come on line, send a few messages, and go off line. The message has to be stored for acknowledgement on the server so acknowledgment is typically a protocol between the consumer and the server that should not affect the producer.

Issue with receiving response from web application

Hi,
I have configured B2B with business protocol as 'Custom document document over Internet', document exchange protocol as AS2-1.1 and transport protocol HTTPS1.1 to invoke a web application deployed in Oracle Application server. B2B is able to invoke the web application with HTTPS request which contains an xml.
I have set the acknowledgment mode as 'Sync' and 'Is acknowledgement handled by B2B' as true. But while receiving the response from web application which is an xml, B2B is showing the error as
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
 at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3244)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1665)
 at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2382)
 at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1825)
 at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:974)
 at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1166)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
 at java.lang.Thread.run(Thread.java:534)
I have added headers as present in the wire message of the request. In B2B, it is showing the wire message for response as follows.
TO_PARTY=XXX
AS2-To=XXX
DOCTYPE_NAME=TestAS2DT
DOCTYPE_REVISION=1.0
Date=Tue, 03 Nov 2009 06:09:22 GMT
AS2-Version=1.1
AS2-From=YYY
Content-Transfer-Encoding=binary
[email protected]
ACTION_NAME=TestAS2_BA
Content-Type=application/xml
Server=Oracle-Application-Server-10g/10.1.3.4.0 Oracle-HTTP-Server
MIME-version=1.0
User-Agent=AS2 Server
FROM_PARTY=YYY
Content-Disposition=attachment; filename=1.0
Connection=Keep-Alive
From=YYY
Keep-Alive=timeout=15, max=100
<?xml version="1.0" encoding="UTF-8"?>
<Books>
<Book>
<BookTitle>Ajax Hacks</BookTitle>
<Author>Bruce W. Perry</Author>
<PubDate>March 2006</PubDate>
</Book>
</Books>
I am able to see the xml sent as response from web application in Payload as follows.
<?xml version="1.0" encoding="UTF-8"?>
<Books>
<Book>
<BookTitle>Ajax Hacks</BookTitle>
<Author>Bruce W. Perry</Author>
<PubDate>March 2006</PubDate>
</Book>
</Books>
I am able to see the HTTP response in b2b_dc_transport.log. In transport log it is not showing any error. Please help me to fix this issue.

Hi,
Request and Response should be part of same agreement. I hope you are not confused between Acknowledgement and Response. Acknowledgement can be received in the same session (sync mode) but Response will always come in a different session and will be treated as a different document. If, for request, party A is initiator and B is responder then for response party B will be initiator and party A will be responder (as Requset and Response are two docs in case of Custom Document)
For configuring X-Path, please refer section 8.3.11 Configuring the XPath Expression for a Custom XML Document at below link -
http://download.oracle.com/docs/cd/B14099_19/integrate.1012/b19370/busact_coll.htm#sthref784
Please let us know whether you are trying to receive a response or Ack?
Regards,
Anuj

MDB (2-phase commit) behavior during abnormal JMS termination

Hello to everyone!
I plan to test the following scenario tomorrow (sort of a bug replication in our system).
Anyway, wanted to know in advance the expected behavior (just in case one of you already know
or have an experience related to this test). Thank you in advance.
Scenario:
I want to test/know the behavior of a 2-phase commit (2PC) MDB when JMS server abnormally exits
(say the process was killed).
Test flow:
start app server --> deploy 2pc-mdb --> send dummy data --> kill jms process --> restart jms process
1. will the connection be closed properly?
2. when jms server restarts, will the value of active consumer(count) doubled?
note: i think after mdb deployment, corresponding destination consumer count is 1.
the problem that occurred in our system was that the consumer count doubled after server restarted.
it seem like the previous connection was not closed when the jms server abnormally terminated.
any inputs will be greatly appreciated.
thanks and best regards.

You have to use TxDataSource for container managed tx or if you are using JTA (in
addition to ofcourse doing 2PC).
S
"Dale Olzer" <[email protected]> wrote:
>
Using weblogic 6.1 SP 4
I have a simple container managed Message Driven Bean. Using a destination
type
javax.jms.Queue.
When the onMessage method finishes the Message is still Pending on the
queue.
see the ejb-jar.xml below
<ejb-jar>
<enterprise-beans>
<message-driven>
<display-name>IvrMessageBean</display-name>
<ejb-name>IvrMsgBean</ejb-name>
<ejb-class>com.edocs.ps.ivr.IvrMsgBean</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
I noticed when I set a JDBC TX DataSource to 2 Phase Commit, the JMS
transaction
started commitig and nothing was left pending in the Queue.
Does 2PC have to be set in a DataSource for Container Managed MDB's to
work?

Error in setting up destination name in depolyment descriptor

the error is, 
[EJB:011113]Error: The Message Driven Bean 'MessageAccess(Application: mssp, EJBComponent: mssp-MDB.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
 the ejb-jar entry is, 
<message-driven >
<description><![CDATA[Bean to access messages]]></description>
<display-name>MessageAccessBean</display-name>
<ejb-name>MessageAccess</ejb-name>
<ejb-class>com.valimo.mssp.jms.j2ee.MSSPListenerBean2</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
</message-driven-destination>
</message-driven>
 and weblogic-ejb-jar entry is like, 
<weblogic-ejb-jar>

<weblogic-enterprise-bean>
<ejb-name>MessageAccess</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>topic/Topic</destination-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
 
can you help?

They should be able to log into their account via http://appleid.apple.com and update their name.

Error while deploying an application on Weblogic 10.3 Application Server

Hi All,
i have installed latest weblogic 10.3 Application server.
- installation of Weblogic was successful.
- tried to deploy my application but it failed to do so during that point of time and throw an exception:-
!MESSAGE [javax.management.RuntimeMBeanException: java.lang.RuntimeException: weblogic.management.provider.EditSaveChangesFailedException: Can not save changes while prepare changes are still in progress.
- then i tried tyo install my appliction's .ear file manually from weblogic console then i get the different exception:-
Unable to access the selected application.
Exception in AppMerge flows' progression
Exception in AppMerge flows' progression
VALIDATION PROBLEMS WERE FOUND problem: cvc-id.2: Duplicate ID value 'MessageDriven_1044495979312':<null> problem: cvc-id.2: Duplicate ID value 'MessageDriven_1044495979312':<null> problem: cvc-id.2: Duplicate ID value 'MessageDriven_1044495979312':<null> problem: cvc-id.2: Duplicate ID value
- my application has server and console, when i tried to install only console, i was lucky to deploy the console, but not the server.
Any body having any idea regarding these exceptions, what should i do to overcome these errors.
Please shred some light and suggest some pointers to this issue.
Regards
Avninder.

We are not using Anotations as we are on EJB 2, we use Deployment Descriptors.
I have investigated and find out that in ejb-jar.xml there is one tag <acknowledge-mode>
in my ejb-jar.xml we have 7 MD beans, this tag is mentioned only in enactment bean and email dispatcher bean. For these 2 beans i am getting conflict, so i removed <acknowledge-mode> tag from these 2 beans and create the .ear again and deploy.
i was succeed in this.
As per my understanding Weblogic 10.3 is using ejb 3.0 and its xsd is different from ejb 2.0 xsd, so if i remove these tags from my ejb-jar.xml beans then in future i'll not be able to deploy it on weblogic 9.2.
i think weblogic has not provide the backward compatibility, Weblogic has to support the structure as many applications using WL 9.2.
Below is the sample of my ejb-jar.xml where these tags differ
<message-driven id="MessageDriven_1044495979312">
 <display-name>EmailDispatcher</display-name>
 <ejb-name>EmailDispatcher</ejb-name>
 <ejb-class>com.fujitsu.iflow.serveree.impl.globalnotification.EmailDispatcherMB</ejb-class>
 <transaction-type>Bean</transaction-type>
 <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
 <message-driven-destination id="MessageDrivenDestination_1044498867079">
 <destination-type>javax.jms.Topic</destination-type>
 <subscription-durability>NonDurable</subscription-durability>
 </message-driven-destination>
 </message-driven>
 <message-driven id="MessageDriven_1044495979297">
 <display-name>Enactment</display-name>
 <ejb-name>Enactment</ejb-name>
 <ejb-class>com.fujitsu.iflow.serveree.impl.wfengine.EnactmentMB</ejb-class>
 <transaction-type>Bean</transaction-type>
 <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
 <message-driven-destination id="MessageDrivenDestination_1044498867078">
 <destination-type>javax.jms.Topic</destination-type>
 <subscription-durability>NonDurable</subscription-durability>
 </message-driven-destination>
 </message-driven>
 <message-driven id="MessageDriven_1063157666983">
 <display-name>JmsEnactor</display-name>
 <ejb-name>JmsEnactor</ejb-name>
 <ejb-class>com.fujitsu.iflow.connectorsee.msgconnector.JmsEnactmentMB</ejb-class>
 <transaction-type>Bean</transaction-type>
 <message-driven-destination>
 <destination-type>javax.jms.Topic</destination-type>
 </message-driven-destination>
 </message-driven>
 <message-driven id="MessageDriven_1063157666982">
 <display-name>SmsConnector</display-name>
 <ejb-name>SmsConnector</ejb-name>
 <ejb-class>com.fujitsu.iflow.connectorsee.smsconnector.SmsConnectorMB</ejb-class>
 <transaction-type>Bean</transaction-type>
 <message-driven-destination>
 <destination-type>javax.jms.Topic</destination-type>
 </message-driven-destination>
 </message-driven>
Kindly help me out.
Suggest is there any workaround so that i can use my application in both the versions.
cheers :)

JBoss message driven bean calling a session bean

Hi guys, can you please help me? I want my mdb to call my session bean....can you provide me some examples of ejb-jar.xml and jboss.xml with regards to this configuration....thanks...im creating my deployment descriptors manually

Here is a little example, I hope it will help you.
ejb-jar.xml
=============================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar >
<enterprise-beans>

<session >
<display-name>TestSessionEJB</display-name>
<ejb-name>TestSession</ejb-name>
<home>mdbtest.interfaces.TestSessionHome</home>
<remote>mdbtest.interfaces.TestSession</remote>
<local-home>mdbtest.interfaces.TestSessionLocalHome</local-home>
<local>mdbtest.interfaces.TestSessionLocal</local>
<ejb-class>mdbtest.session.TestSessionEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
... </session>

<message-driven >
<description><![CDATA[]]></description>
<display-name>TestMessageEJB</display-name>
<ejb-name>TestMessage</ejb-name>
<ejb-class>mdbtest.message.TestMessageEJB</ejb-class>
<transaction-type>Container</transaction-type>
<message-selector></message-selector>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
<ejb-local-ref >
<ejb-ref-name>ejb/TestEjb</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>mdbtest.interfaces.TestSessionLocalHome</local-home>
<local>mdbtest.interfaces.TestSessionLocal</local>
<ejb-link>TestSession</ejb-link>
</ejb-local-ref>
</message-driven>
</enterprise-beans>
</ejb-jar>
jboss.xml:
=============================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>TestSession</ejb-name>
<jndi-name>ejb/MdbTest/TestSession</jndi-name>
<local-jndi-name>TestSessionLocal</local-jndi-name>
<configuration-name>Standard Stateless SessionBean</configuration-name>
</session>
<message-driven>
<ejb-name>TestMessage</ejb-name>
<destination-jndi-name>queue/MyTestQueue</destination-jndi-name>
<configuration-name>Standard Message Driven Bean</configuration-name>
</message-driven>
</enterprise-beans>
<resource-managers>
</resource-managers>
</jboss>

Acknowledgement Mode

Similar Messages

Maybe you are looking for