Skip to Main Content
Forums

Java EE (Java Enterprise Edition) General Discussion

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

UserTransaction

mohitanchliaNov 13 2008
Inside servlet I am creating UserTransaction and then calling Session bean. Does servlet propogate the transaction to session bean?

If someone could shed some light on transaction from servlet to bean would be helpful.

Comments

Anuj Dwivedi-Oracle
Please refer section "24.6 Troubleshooting Oracle User Messaging Service" at -

http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10226/ns_config.htm

Possible cause -
The UMS Driver for the appropriate channel is configured with a specific list of SenderAddresses, and the message sent by the application has set a non-matching Sender Address.

Note: UMS Server matches the outbound message's sender address, if set, against the available drivers' SenderAddresses to find a matching driver to use for delivering the message. If a driver has set one or more SenderAddresses, then the UMS Server only sends messages with the matching sender address to it.
Solutions -
1) Check the following settings in the appropriate UMS Driver using Oracle Fusion Middleware Control:
SenderAddresses
Note: The format for SenderAddresses is a comma-delimited list of <DeliveryType>:<Address>.
For example:
EMAIL:sender@example.com, EMAIL:sender@example2.com

2) Leave this property blank, if you want this driver to service outbound messages for all sender addresses for this channel (delivery type).

3) If there are multiple driver instances deployed for the same channel (delivery type) with different configurations, use the SenderAddresses to differentiate the driver instances. For example, one instance can be set with a specific value in SenderAddresses to only service outbound messages with that matching sender address, while the other instance can keep the SenderAddresses blank in order to service all outbound messages that do not specify any sender address or one that does not match that of the first driver instance.

4) SenderAddresses that are configured with the incorrect syntax (such as missing <DeliveryType>:) are ignored by the UMS Server for the purpose of driver selection.
Regards,
Anuj
1 person found this helpful
KHein
Hi Anuj,

Thanks for the prompt reply. I leave the Send Addresses field blank, and the previous problem was solved. But now I am getting another problem as shown below. Do you have any idea what the cause could be? Thanks again.


<Jul 1, 2011 5:30:01 PM SGT> <Error> <oracle.sdp.messaging.driver.xmpp> <SDP-26225> <Received Error Message. Code: 404 Text: null.>
<Jul 1, 2011 5:30:01 PM SGT> <Error> <oracle.soa.services.notification> <BEA-000000> <<.> Error status received from UMS.
Status detail :
Status type : DELIVERY_TO_DEVICE:FAILURE,
Status Content : An error was reported by the gateway. Error Code: 404, Error Text: null,
Addressed to : IM:pat.morely,
UMS Driver : Farm_base_domain/base_domain/soa_server1/usermessagingdriver-xmpp-was:oracle_sdpmessagingdriver_xmpp#XMPP-IM-Driver,
UMS Message Id : e50889ee0aba751a00a15a56d845e8ef,
Gateway message Id : e50889ee0aba751a00a15a56d845e8ef-1wNKi-10,
Status Received at : Fri Jul 01 17:30:01 SGT 2011.
Check status details and fix the underlying reason, which caused error.
>

Regards,

K Hein
Anuj Dwivedi-Oracle
Hello,

This is XMPP server configuration/connectivity issue. Generally code 404 is used to inform a sender that no recipient was found matching with the ID. Cross check with XMPP server admin whether specified recipient address is correct and reachable.

Regards,
Anuj
1 person found this helpful
KHein
Hi Anuj,

I made some changes some configuration and now I can send out IM messages. But I am still having one issue there. I am having the below error message on the console.

Jul 4, 2011 11:15:07 AM SGT> <Error> <oracle.sdp.messaging.driver.xmpp> <SDP-26217> <Could not locate an account to deliver this message from sender jabber|IMRespondToAddress@imhost.com. Using the first account ( admin@host1.example.com ) to deliver this message.>


I have already setup Default Sender Address in XMPP driver properties configration page, but it seems like it can't locate the account to send out the message and just using the first account found on the jabber server. How could I fix this issue. Thank you so much for your replies.

Regards,

K Hein
Anuj Dwivedi-Oracle
To retain the original message sender, add sender of the message to 'IMServerUsername' configuration property of the driver.

Regards,
Anuj
1 person found this helpful
KHein
Hi Anuj,

I have already set IMServerUsername and Default Sender Address properties of the XMPP driver. But from the BPEL process, I couldn't set sender address for the IM invocation. I am using drag and drop IM component, and I only can set To and Body fields from that IM compoment.

Did I miss out anything? Thanks agin.

Regards,

K.Hein
Anuj Dwivedi-Oracle
Hello K.Hein,

No, you did not miss anything. Make sure that in IMServerUsername field you are providing the user name without domain name. For e.g. if user name is abc.def@dom.com then IMServerUsername must have value "abc.def" only and IMServerHost should hold value "dom.com"

Regards,
Anuj
1 person found this helpful
KHein
Hi Anuj,

I have set IMServerUsername and IMServerHost properties as you mentioned as well. Sending of IM is working fine too, just that the error message comes out on the console everytime I trigger my BPEL to send an IM. So I am wondering if there is anything wrong in my configuration or if this error could cause any other implication. Thanks again for your replies.

Regards,

K Hein
1 - 8
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Dec 11 2008
Added on Nov 13 2008
#java-servlet
0 comments
94 views