web analytics
free online training

Error Messages

Home → Tutorials → SOASUITE → Error Messages

SDP-25342: Cannot find default address for user weblogic.

On October 27, 2011   /   Error Messages   /   Leave a comment

: : Cannot find default address for user weblogic.

Oracle User Messaging Service (UMS) is pre-integrated with Oracle Human Workflow. Wokflow expects e-mail ID for the authorized users so as to send actionable messages to and receive replies from users over email. These details need to be specified using UMS UI that can be accessed using URL similar to:

http://192.168.0.6:7001/sdpmessaging/userprefs-ui 

Oracle UMS Add Channel

Oracle UMS Channel List

See Oracle documentation for more details below:

http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/ns_rulebasednotification.htm#BCFDGHIA

VN:F [1.9.17_1161]
Rating: 10.0/10 (1 vote cast)
VN:F [1.9.17_1161]
Rating: 0 (from 0 votes)
Permanent link to this post (95 words, 2 images, estimated 23 secs reading time)

Related posts

  • No related posts.
Back to Top

oracle.xml.parser.v2.XMLElement cannot be cast to java.lang.String

On October 25, 2011   /   Error Messages   /   Leave a comment

I encountered a strange problem in the weekend while trying to demo BPEL’s compare function. Expression used shown below:

xp20:compare(bpws:getVariableData(‘inputVariable’,'payload’,'/client:process/client:input’),’World’)=0

This resulted into XPath error at runtime. I realized the reason after looking at the error log.

getVariableData returns an XMLElement and we were trying to compare it against java.lang.String resulting in conversion error – oracle.xml.parser.v2.XMLElement cannot be cast to java.lang.String. To fix this issue, we need to use ora:getNodeValue function to extract string value from XMLElement.

Alternatively, BPEL implicitly does above steps if we use the expression:

bpws:getVariableData(‘inputVariable’,'payload’,'/client:process/client:input’) = ‘World’.

VN:F [1.9.17_1161]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.17_1161]
Rating: 0 (from 0 votes)
Permanent link to this post (103 words, 0 images, estimated 25 secs reading time)

Related posts

  • No related posts.
Back to Top

java.sql.SQLException: JDBC LLR, table verify failed for table ‘WL_LLR_ADMINSERVER’

On October 16, 2011   /   Error Messages   /   Leave a comment

I created a single server domain to hold my SOA, OSB and BAM servers instead of separate managed servers. Since I only have on 3+ GB laptop (win32 limitation), single-server configuration would scale well. However, after creating new domain and starting Admin server, I encountered

javax.transaction.SystemException: weblogic.transaction.loggingresource.: java.sql.SQLException: JDBC LLR, table verify failed for table ‘’, row ‘JDBC LLR Domain//Server’ record had unexpected value ‘soa-single-server//AdminServer’ expected ‘soadomain//AdminServer’***

Fix:

Modify WL_LLR_ADMINSERVER table entry from DEV_SOAINFRA schema as shown below.

 image

VN:F [1.9.17_1161]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.17_1161]
Rating: 0 (from 0 votes)
Permanent link to this post (91 words, 1 image, estimated 22 secs reading time)

Related posts

  • No related posts.
Back to Top

Sequence Increment and Pre-Allocation size

On January 28, 2011   /   Error Messages, Quick Bites   /   Leave a comment

"The sequence named [ORDER_SEQ] is setup incorrectly. Its increment does not match its pre-allocation size."

This issue arises because DbAdapter by default sets pre-allocation size as 50. This should match with Database Sequence’s increment size. Steps to rectify this issue:

VN:F [1.9.17_1161]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.17_1161]
Rating: 0 (from 0 votes)
This is a preview of Sequence Increment and Pre-Allocation size. Read the full post (110 words, 6 images, estimated 26 secs reading time)
Back to Top
goin up