WLS - WLE Connections and Transactions in multithreaded

Hi .
We have a legacy system which was based on Tuxedo and now move to WLE
(4.0)
For our Internet applications we use WLS (4.03) as application server in
top of the legacy system.
We have problems trying to run more than one transaction on the WLS
which propagate to the WLE .
Looking at documentation we didn't understood how should we deal with
more than one client on the WLS . Each client should have its own
transaction and they should run simulstanly .
We only succeded when we synchronize the threads (Run just one thread
which get the transaction use it and then uses bt.destroy_current()
before activating the next thread to do the same)
It seems that the documantation in the WLE and WLS don't fit together .
Has someone use WLS-WLE connectivity with multiple clients/threads.
Can someone tell me how to use the Bootstrap object(destroy current?)
and the Transaction Control (begin , suspend, resume, commit) in order
to make it works.
Regards

I would strongly suggest that you not use WLE 4.0 which is rather old (4.2,
5.0.1 and 5.1 have all since been released), but move to the newest version
of WLE which is WLE 5.1.
WLS 4.0 is also an old release.
I am not sure how long these 2 releases will be supported, so the customer
should upgrade to the latest of both WLE and WLS.
Shlomo Rothschild wrote:
Hi .
We have a legacy system which was based on Tuxedo and now move to WLE
(4.0)
For our Internet applications we use WLS (4.03) as application server in
top of the legacy system.
We have problems trying to run more than one transaction on the WLS
which propagate to the WLE .
Looking at documentation we didn't understood how should we deal with
more than one client on the WLS . Each client should have its own
transaction and they should run simulstanly .
We only succeded when we synchronize the threads (Run just one thread
which get the transaction use it and then uses bt.destroy_current()
before activating the next thread to do the same)
It seems that the documantation in the WLE and WLS don't fit together .
Has someone use WLS-WLE connectivity with multiple clients/threads.
Can someone tell me how to use the Bootstrap object(destroy current?)
and the Transaction Control (begin , suspend, resume, commit) in order
to make it works.
Regards

Similar Messages

Db connections and transactions

I'm fairly new to EJB and recently have
been handed an application to maintain.
The app has a bunch of entity beans and
a bunch of session beans.
Each entity bean method that reads or writes
to the database gets a new database connection
by calling DataSource's getConnection method.
The app also has session facades that
call various methods on entity beans.
My understanding is that one of the intentions
of the session facade is that the work that
is done in one session bean method all happens
within the same database transaction.
I also undertand that a single database
transaction can only occur over one database
connection.
It seems to me that if each entity bean method
is using its own connection, then the work in
a session bean method is not all done within
the same database transaction.
Is the above analysis correct?
If I want each session bean method to be covered by
a single transaction, what do I need to do?

Tim Davenport wrote:
I'm fairly new to EJB and recently have
been handed an application to maintain.
The app has a bunch of entity beans and
a bunch of session beans.
Each entity bean method that reads or writes
to the database gets a new database connection
by calling DataSource's getConnection method.
This is good practice. I'll explain below why it's not always actually
getting a new database connection.
The app also has session facades that
call various methods on entity beans.
My understanding is that one of the intentions
of the session facade is that the work that
is done in one session bean method all happens
within the same database transaction.
Yes, assuming the transaction attributes are set appropriately.
I also undertand that a single database
transaction can only occur over one database
connection.
Note that with XA it is possible to run a single transaction over
multiple JDBC connections, but that's more trivia than answering your
question.
It seems to me that if each entity bean method
is using its own connection, then the work in
a session bean method is not all done within
the same database transaction.
Is the above analysis correct?
No. The basics are that you need to ensure that the DataSources
configured in weblogic are TxDataSources. An easy check is to look at
your config.xml. It should say TxDataSource not DataSource.
Your EJB's transaction will be managed by the WLS Transaction Manager.
The TxDataSource will ensure that all calls to getConnection for the
same datasource within the same transaction will return the same
connection. So in reality, all of these getConnection calls are
returning the same jdbc connection.
-- Rob
If I want each session bean method to be covered by
a single transaction, what do I need to do?

Connections and transactions

Hi all,
I need advice on managing transactions across multiple persistent objects. Currently we have a number of objects that can save their state to the database: they open a connection, perform insert/update, then close the connection:
class PersistentObject
public void store()
// get connection from pool
Connection conn = ConnectionMgr.getConnection();
// do insert/update
// Return connection to pool
conn.close();
We are using Tomcat's built-in connection pool, so ConnectionMgr simply encapsulates the JNDI lookup followed by a call to DataSource.getConnection().
Now we need to be able to store two or more objects in one transaction, something like this:
try {
// begin transaction
object1.store();
object2.store();
// commit
} catch( SQLException ex ) {
// rollback
Problem is that a transaction requires multiple SQL calls to use the same Connection.One way to do this, of course, is to open the connection externally and pass it to each object. However, ideally, it should be more implicit. Ideally, if the transaction is in progress when object2 tries to get connection, it should receive the same one that object1 used. Is there any way to do it? (Well, I can think of one: binding a connection to a session, but I also see a number of disadvatages of that approach).
thanks in advace,
CodeSlinger

this is what i know. Can you not use JTS? With weblogic app server you can use the weblogic.jdbc.jts.Driver to get a connection. Then you can start a transaction and have calls to multiple components say A, B and C. Each component closes the connection when done but the next component gets the same connection if in same execute thread. The connection is returned to pool only when you commit/rollback and all components are in the same transaction. I hope this helps. You should have similar thing with Tomcat.

How to improve jdbc 4 connection and Transact-SQL

I am using a jdbc 4 connection to connect to Database.
With code
Class.forName("org.postgresql.Driver");
String url = "jdbc:msql://athens.imaginary.com:4333/db_web";
username = �mycon�;
password = �mycon�;
Connection conn = DriverManager.getConnection(url, username, password);And quering and updating with database with TSQL
Sample code
Statement select = con.createStatement();
ResultSet result = select.executeQuery("SELECT key, val FROM t_test"); I am able to get the result
But i want to improve it.
Whether i should use any other api or any other configrational changes I need to imporove the rilibility and increase the speed.
Any suggestions?

Please don't cross-post. You have a thread for this in the JDBC forum (which is where it belongs, if anywhere), so keep the discussion there, please.

Connection failover and transaction failover

Connection failover and transaction failover
I need to know more about a behavior in a RAC cluster. When a node goes down that is executing one of my transaction through JDBC , does the connection and transaction failover to a new node without me needing to restart tran or reconnect ?
Please provide some insight
Thanks

Transactions are NOT automatically rolled back. The application must do this otherwise the session will get disconnected.
If you code TAF, all sessions will failover to the backup connection. You can specify that select statements are automatically re-executed after the failover. Insert/update/delete transactions must be explicitly rolled back and resubmitted by the application.
IF you are using an ORacle Connection pool, the connection pool will automatically cleanup connections to the failed instance, abort inflight transactions. The application will either retry or it will propagate the error to the end user.
See the whitepaper on the OTN RAC page (otn.oracle.com/rac) Workload Management with Oracle RAC for more information.

Using oracle's connection pools and transactional context

Hi!
I have an implementations of existing interfaces ( let's call this layer as
data access layer) which abstracts the connection and transactional session
from the calling application. This implementaion makes use of Oracles JVM
inside the oracle database (8.1.7) to create and maintain the connection
pools and the transactional session (transactional context). I would like
to create differenent implementation, if the calling application is a
session bean running inside the weblogic application server. is there way I
can still use the connection pools and transactinal context that I got from
the oralce if the calling application is a session bean running inside the
weblogic app.. server?
do I have to change any configuration settings in weblogic?. there might
be two scenarios..
the data access layer (the classes which deal with the connection pools and
transactions) might be running inside the oracle's JVM..
the data access layer might be running inside weblogic application server...
thanks...
Srinivas

Certainly this from SPAM. Now from anothe user :). Note sure whether I should mark you as you as SPAM as you're posting questions which are available in stackoverflow
http://stackoverflow.com/questions/26531161/biztalk-and-odp-net-connection-pools-and-connection-strings
Details provided in the other forum should provide you the answer.
I don’t want to duplicate this thread just for the sake of giving reply.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

PostgreSQL 8.2, WLS 9.2 and XA Transactions

Hi all,
I've got an application that's working great with WLS 8.1sp5 and PostgreSQL 8.2, utilizing XA transactions.
I'm in the process of upgrading to WLS 9.2, and have ran into the issue that WLS seems to be convinced that Postgresql does not support XA transactions.
When defining the datasource in the console, if I choose Postgresql as the database type, it then says "You have selected non-XA JDBC driver to create database connection in your new data source." and it then only gives me the options of "emulate 2pc", "one phase commit", and "logging last resource".
So, since the configuration console seems to be retarded in its knowledge, I thought I'd beat it by going ahead and defining the datasource, then tweak the resulting config file by hand, such that reads:
<global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
instead of:
<global-transactions-protocol>OnePhaseCommit</global-transactions-protocol>
Restarting the server, it accepts the change and all appears OK. But when I use my application I run into this:
Caused by: java.sql.SQLException: Connection has already been created in this tx context for pool named DS_1. Illegal attempt to create connection from another pool: DS_2
...I do indeed have a few different datasources - all using postgres, but logging into different schemas.
What gives? Why can I use PostgreSQL + WLS 8.1 + XA transactions but not PostsgresQL + WLS 9.2.1 + XA ?
Thanks!

I seem to have resolved this issue, though I'm not happy with the work-around that I've come up with.
First off, as far as I can tell, it's impossible to create the datasource configuration via the console. If I choose PostgreSQL or Postgres and the database type, the configurator excludes XA transaction support as an option. If I choose "other" as the database type (thinking that I'd then specify all the specifics of PostgreSQL directly), it also excludes XA transaction support as an option.
So, as far as I can tell, the only way to get a working setup is to build the configuration by hand -- after which the console application is happy, and so, seemingly, is WLS during runtime.
It would be really nice if a future version of WLS included a change to the console application that added the understanding that there are XA-capable databases out there, other than the limited few that it believes.
==============================================
<name>DS_1</name>
<jdbc-driver-params>
<url>jdbc:postgresql://xxx.xxx.net:5432/dev</url>
<driver-name>org.postgresql.xa.PGXADataSource</driver-name>
<properties>
<property>
<name>port</name>
<value>5432</value>
</property>
<property>
<name>user</name>
<value>dev</value>
</property>
<property>
<name>databaseName</name>
<value>dev</value>
</property>
<property>
<name>server</name>
<value>xxx.xxx.net</value>
</property>
</properties>
<password-encrypted>{3DES}g1iK4zhw27k=</password-encrypted>
<use-xa-data-source-interface>true</use-xa-data-source-interface>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<test-connections-on-reserve>true</test-connections-on-reserve>
<test-table-name>SQL SELECT 1</test-table-name>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>datasource/DS_1/jndi-name>
<global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>
=================================================
Notes about the above:
1- Notice that I'm specifying the PGXADataSource rather than the driver class as the driver name. A little strange, in that PGXADataSource does not implement Driver.
2- Notice that I'm specifying properties for host, port, database name, etc. that are redundant to what is in the URL. This is the only way I've been able to make it work. It's as if the URL is completely ignored.

Master Data and Transaction Data For DB Connect extracted Data...

Dear Experts,
I have been working on SAP NetWeaver BW 7.3 and for the first time I have extracted data from Oracle DBMS by using DB Connect. I have successfully extracted data of a View namely Sales_View into BW by creating a DataSource. This View has about 100 fields and I have been told that this view consists of Master Data and Transaction Data too. For my further reporting needs say building a Dashboard or InfoSpace I have to design a DSO and InfoCube for this DataSource. I'm bit confused about the Master Data and Transaction Data of this DataSource.
1. Should I create all custom InfoObject against all fields of DataSource for DSO and InfoCube design?
2. Do I need to create and load the Master Data for all InfoObjects or I need to create or load the Master Data for only those InfoOjects which will be
used for drill down or reporting in Dashboard or InfoSpace?
3. Do I need to load the Master Data manually by creating Flat Files and using these files for Master Data loading for required objects?
4. How should I approach the designing of DSO and InfoCube?
I will appreciate your inputs in this matter.
Many thanks!
Tariq Ashraf

Thanks!

ConnectionPool problems with WLS 7.0 and Oracle 9.2

Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
application on the productive system (and only there) we constantly encounter
a whole set of SQLExceptions which have all in common that the Connection from
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSet
- Connection has already been closed
- Closed Statement
- Transaction is no longer active - status committing
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()
There are no special Statements which create these errors. They are spread at
random across practically every query the application creates, and the same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSets are
closed immediately after use. As an example, I attached a code snippet and a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrent usern,
since in the approval tests on an almost identical test system these errors never
occurred.
I also followed the advice from Oracle and installed the latest Oracle JDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in the application
classpath (via a reference in the Manifest file of the application jar), not in
the system classpath? There has never been a problem with that, but in a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script creates for the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath? If
it is possible, why is it necessary?
Best regards,
Andreas Zehrt
[CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

Andreas Zehrt wrote:
Hi Joe,
Your hint that there is a threading problem was right:
On further investigation of the code I found out that the class that passes the
Connection to the DAO not only stores it as a member at some point (which is not
a good idea anyway) but is also a singleton - then, of course, it's no surprise
that the Connection gets invalid in a incalculable way when concurrent threads
share it.
The singleton instantiation was not so obvious because the way of instantiation
is controlled by a configuration parameter that can be overridden at different
levels.
I changed it and the productive logfiles indicate that the SQLExceptions related
to that class have disappeared.I am happy to have helped.
So, thanks a lot for the advice.
But I am still wondering why this code has worked for so long a time with WLS
5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
it was multi-user environment.Mo idea.
I still believe that there is a difference between WLS 5.1 and 7.0 in the way
it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
a little more explicit about those changes and possible version incompatabilities
beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
effect in this case, I will certainly do what I can to see that our documentation
is explicit about changes.
Joe
Best regards, Andreas
Joe Weinstein <[email protected]> wrote:
Hi Andreas.
Andreas Zehrt wrote:
Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
application on the productive system (and only there) we constantlyencounter
a whole set of SQLExceptions which have all in common that the Connectionfrom
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSetThat is typically if the statement that created it is either re-executed
or closed.
- Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
would show
where it was originally closed.
- Closed Statementsame as above.
- Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
datasource,
and then later trying to use it after the transaction which it was associated
with,
is finished.
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
There are no special Statements which create these errors. They arespread at
random across practically every query the application creates, andthe same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSetsare
closed immediately after use. As an example, I attached a code snippetand a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrentusern,
since in the approval tests on an almost identical test system theseerrors never
occurred.
I also followed the advice from Oracle and installed the latest OracleJDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in theapplication
classpath (via a reference in the Manifest file of the applicationjar), not in
the system classpath? There has never been a problem with that, butin a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script createsfor the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath?If
it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
We also ship
an oracle thin driver, which becomes obsolete soon...
I am concerned that your code creates pool connections to be used later.
The problems
can arise if more than one thread ever gets the same connection, or if
the connection
is used in the same thread, spanning transactions. It does also seem
that there may
be a threading issue, because if two threads each call the code to create
a connection,
and two connections are made, but one over-writes the other, the two
threads can
end up using the same connection, and closing it. The over-written one
never gets closed,
resulting in that leak message you got...
Joe
The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
several classes in the business layer, but not used, until the DAOtakes it to make the query.
So, the Connection is closed where it was opened, not in the DAO class.
public class ConcernDAOImpl extends BaseDAO {
     public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
throws DataAccessException, ConstraintException, ComaParseException{>
sqlMessage.append(")");
String sqlStmt = sqlMessage.toString();
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
pstmt = conn.prepareStatement(sqlStmt);
rs = pstmt.executeQuery();
while (rs != null && rs.next()) {
final Concern concern =
new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
return concerns;
} catch (SQLException sqle) {
// Wrapps real SQL exception
String[] message = new String[]{sqle.getMessage(), sqlStmt};
throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
sqle);
} finally {
closeAll(rs, pstmt);
_logger.exitDebug(method);
Here, the Connection is acquired and finally closed
public class ComaServiceProviderClassicImpl {
     public void updateComplaint(
final Request updateRequest,
final ResponseSingleElement response,
final Principal principal)
throws SystemException {
try {
logger.info("updateComplaint", "store incident");
// store the incident in the database
incidentManager.storeIncident(getConnection(), updateIncident);
// reload the incident from Cache and / or the databaseto get the ContactReferences.
Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
getConnection(), updateIncident.getOID());
} catch (RemoteException rex) {
// remote exceptions
rollbackIfNecessary();
CoreUtils.unwrapRemoteException(rex, logger);
} catch (SystemException e) {
// all other exceptions --> rollback if necessary and rethrow
rollbackIfNecessary();
throw e;
} finally {
removeConnection();
logger.exitDebug("updateComplaint");
This is the resulting StackTrace:
sql exception: [Closed Statement: next] - sql statement: [select *
     at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
     at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
     at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
was detected. A Connection leak occurs when a connection obtained from
the pool was not closed explicitly by calling close() and then was disposed
by the garbage collector and returned to the connection pool. The following
stack trace at create shows where the leaked connection was created.
Stack trace at connection create:
     at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
     at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
     at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
     at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
     at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
     at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

Current server is the coordinator and transaction is not found

Hi,
We're using Weblogic 8.1 SP3. We have a single weblogic domain and 2 clusters in it. EAR1 is deployed in cluster 1 and EAR2 is deployed in cluster 2. EAR2 is compiled and created using j2ee.jar and not weblogic.jar.
We have a MessageDrivenBean which is CMT / Required in EAR1 calls a BMT Stateless Session Bean in EAR2.
A new transaction is begun in the BMT SB method and commit or rollback is called based on exception. A RuntimeException is thrown back to the MDB in case the transaction is rolled back in Bean Managed SB.
Sometimes from the Bean Managed SB the following exception is thrown:
javax.transaction.TransactionRolledbackException: Current server is the coordinator and transaction is not found. It was probably rolled back and forgotten already.
     at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
     at com.oakgrovesystems.reactor.frontDesk.EJBFrontDeskBean_1gq9kv_EOImpl_813_WLStub.handleRequest(Unknown Source)
     at com.oakgrovesystems.reactor.requests.ReactorRequest.send(ReactorRequest.java:212)
     at com.oakgrovesystems.reactor.client.EJBReactorProxy.sendRequest(EJBReactorProxy.java:44)
     at com.oakgrovesystems.reactor.client.AbstractReactorProxy.handleRequest(AbstractReactorProxy.java:52)
     at sun.reflect.GeneratedMethodAccessor153.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at tavant.bpm.client.proxy.DynamicFailoverReactorProxy.invoke(DynamicFailoverReactorProxy.java:84)
     at $Proxy11.handleRequest(Unknown Source)
     at tavant.bpm.client.ProcessHome.handleRequest(ProcessHome.java:298)
     at tavant.bpm.client.ProcessHome.startProcess(ProcessHome.java:87)
     at tavant.bpm.client.processor.CreateWorkflowInstance.startProcess(CreateWorkflowInstance.java:70)
     at tavant.bpm.client.processor.CreateWorkflowInstance.invoke(CreateWorkflowInstance.java:51)
     at tavant.bpm.ejb.AsynchronousProcessorMessageBean.onMessage(AsynchronousProcessorMessageBean.java:58)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
This is not consistently reproducible though it happens when server is heavily loaded. When this exception occurs, the transaction in the BMT Session Bean is actually getting committed! The message gets redelivered from the MDB.
What could be the problem?
Regards
Sandhya

I'm seeing a similiar problem on our servers recently and thought I would add my problem as well. We are using Weblogic 8.1; don't know which SP is in production. We have an EAR file with an SB EJB that puts messages in a queue. The EAR is deployed in a cluster along with the queues. The errors below occurred in 3 of the 4 WLS instances in our cluster. This happened during a peak period and lasted for several seconds in Production.
###<Jul 1, 2005 11:18:12 AM EDT> <Warning> <RMI> <exsdxtxeax1x.prod.xxxx.xxx> <ems-04> <ExecuteThread: '12' for queue: 'web
logic.kernel.Default'> <<WLS Kernel>> <> <BEA-080006> <Failed to associate the transaction context with the response while marshall
ing an exception to the client:
javax.transaction.TransactionRolledbackException: Current server is the coordinator and transaction is not found. It was probably
rolled back and forgotten already..
javax.transaction.TransactionRolledbackException: Current server is the coordinator and transaction is not found. It was probably
rolled back and forgotten already.
at weblogic.transaction.internal.TransactionManagerImpl.sendResponse(Ljava.lang.Object;)Ljava.lang.Object;(TransactionManag
erImpl.java:1438)
at weblogic.rmi.internal.BasicServerRef.associateTxContext(Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundRespo
nse;)V(BasicServerRef.java:490)
at weblogic.rmi.internal.BasicServerRef.postInvoke(Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;Lweblogic.rmi.sp
i.InboundRequest;Lweblogic.rmi.spi.OutboundResponse;Ljava.lang.Throwable;)V(Optimized Method)
at weblogic.rmi.internal.BasicServerRef.handleRequest(Lweblogic.rmi.spi.InboundRequest;)V(Optimized Method)
at weblogic.rmi.internal.BasicExecuteRequest.execute(Lweblogic.kernel.ExecuteThread;)V(Optimized Method)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(Optimized Method)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>

How to specify a variable in the path prefix of an External HTTP (RFC) connection (in transaction SM59)

Hi There,
Please can someone tell me how to specify a variable in the path prefix of an External HTTP (RFC) connection in transaction SM59?
For example if my path prefix is /invoke/test/example?input=XYZ; how do I replace "XYZ" with a variable so that I can pass in any value after "=" ?
Thanks,
Brendon

Hi,
This is SAP Business one system administration forum. Please find correct forum and repost above discussion to get quick assistance.
Please close this thread here with helpful answer.
Thanks & Regards,
Nagarajan

File Adapter creating huge connections and not releasing.

Hi,
We see high no. of current connections in file adapter from weblogic console against eis/HAFileAdapter under deployments -> fileadapter -> monitoring -> Outbound Connection Pools and are concerned about the same. It seems like fileadapter is not releasing the connection and hence no. of connections are piling up over a days and depending upon the transactions. coz after a restart the values comes down from 36000 to 10 ( which is default initial connection).
But when i see at the datasource level i don't see that much number of active connections. Need to know why this is happening and is this behavior is expected?
We are using SOA 11g PS2
Below is the deployment plan for fileadpater in use:
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>connectors</application-name>
<variable-definition>
<variable>
<name>ConfigProperty_controlDir_Value_12732617703910</name>
<value>/var/opt/soa_nfs/data/SOA_PRD_DOMAIN/config/FileAdapter</value>
</variable>
<variable>
<name>ConfigProperty_outboundLockTypeForWrite_Value_12737938820080</name>
<value>oracle</value>
</variable>
<variable>
<name>ConnectionInstance_eis/HAFileAdapter1_JNDIName_13010279387490</name>
<value>eis/HAFileAdapter1</value>
</variable>
<variable>
<name>ConfigProperty_controlDir_Value_13010283495591</name>
<value>/var/opt/soa_nfs/data/SOA_PRD_DOMAIN/config/FileAdapter</value>
</variable>
<variable>
<name>ConfigProperty_inboundDataSource_Value_13010283655032</name>
<value>jdbc/SOADataSource</value>
</variable>
<variable>
<name>ConfigProperty_outboundDataSource_Value_13010283782973</name>
<value>jdbc/SOADataSource</value>
</variable>
<variable>
<name>ConfigProperty_outboundDataSourceLocal_Value_13010283877514</name>
<value>jdbc/SOALocalTxDataSource</value>
</variable>
<variable>
<name>ConfigProperty_outboundLockTypeForWrite_Value_13010283941445</name>
<value>oracle</value>
</variable>
<variable>
<name>ConfigProperty_inboundDataSource_Value_13081683627140</name>
<value>jdbc/SOADataSource</value>
</variable>
<variable>
<name>ConfigProperty_outboundDataSource_Value_13081683875571</name>
<value>jdbc/SOADataSource</value>
</variable>
<variable>
<name>ConfigProperty_outboundDataSourceLocal_Value_13081684137432</name>
<value>jdbc/SOALocalTxDataSource</value>
</variable>
<variable>
<name>ConnectionInstance_eis/HAFileAdapter_Wedb_JNDIName_13369118887880</name>
<value>eis/HAFileAdapter_Wedb</value>
</variable>
<variable>
<name>ConfigProperty_controlDir_Value_13369119117411</name>
<value>/var/opt/soa_nfs/data/SOA_PRD_DOMAIN/config/FileAdapter</value>
</variable>
<variable>
<name>ConfigProperty_inboundDataSource_Value_13369119237302</name>
<value>jdbc/SOADataSource</value>
</variable>
<variable>
<name>ConfigProperty_outboundDataSource_Value_13369119486683</name>
<value>jdbc/SOADataSource</value>
</variable>
<variable>
<name>ConfigProperty_outboundDataSourceLocal_Value_13369119703484</name>
<value>jdbc/SOALocalTxDataSource</value>
</variable>
<variable>
<name>ConfigProperty_outboundLockTypeForWrite_Value_13369119820485</name>
<value>oracle</value>
</variable>
</variable-definition>
<module-override>
<module-name>FileAdapter.rar</module-name>
<module-type>rar</module-type>
<module-descriptor external="false">
<root-element>weblogic-connector</root-element>
<uri>META-INF/weblogic-ra.xml</uri>
<variable-assignment>
<name>ConfigProperty_controlDir_Value_12732617703910</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter"]/connection-properties/properties/property/[name="controlDir"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_outboundLockTypeForWrite_Value_12737938820080</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter"]/connection-properties/properties/property/[name="outboundLockTypeForWrite"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConnectionInstance_eis/HAFileAdapter1_JNDIName_13010279387490</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter1"]/jndi-name</xpath>
<origin>planbased</origin>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_controlDir_Value_13010283495591</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter1"]/connection-properties/properties/property/[name="controlDir"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_inboundDataSource_Value_13010283655032</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter1"]/connection-properties/properties/property/[name="inboundDataSource"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_outboundDataSource_Value_13010283782973</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter1"]/connection-properties/properties/property/[name="outboundDataSource"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_outboundDataSourceLocal_Value_13010283877514</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter1"]/connection-properties/properties/property/[name="outboundDataSourceLocal"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_outboundLockTypeForWrite_Value_13010283941445</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter1"]/connection-properties/properties/property/[name="outboundLockTypeForWrite"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_inboundDataSource_Value_13081683627140</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter"]/connection-properties/properties/property/[name="inboundDataSource"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_outboundDataSource_Value_13081683875571</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter"]/connection-properties/properties/property/[name="outboundDataSource"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_outboundDataSourceLocal_Value_13081684137432</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter"]/connection-properties/properties/property/[name="outboundDataSourceLocal"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConnectionInstance_eis/HAFileAdapter_Wedb_JNDIName_13369118887880</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter_Wedb"]/jndi-name</xpath>
<origin>planbased</origin>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_controlDir_Value_13369119117411</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter_Wedb"]/connection-properties/properties/property/[name="controlDir"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_inboundDataSource_Value_13369119237302</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter_Wedb"]/connection-properties/properties/property/[name="inboundDataSource"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_outboundDataSource_Value_13369119486683</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter_Wedb"]/connection-properties/properties/property/[name="outboundDataSource"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_outboundDataSourceLocal_Value_13369119703484</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter_Wedb"]/connection-properties/properties/property/[name="outboundDataSourceLocal"]/value</xpath>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_outboundLockTypeForWrite_Value_13369119820485</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="javax.resource.cci.ConnectionFactory"]/connection-instance/[jndi-name="eis/HAFileAdapter_Wedb"]/connection-properties/properties/property/[name="outboundLockTypeForWrite"]/value</xpath>
</variable-assignment>
</module-descriptor>
<module-descriptor external="false">
<root-element>connector</root-element>
<uri>META-INF/ra.xml</uri>
</module-descriptor>
<module-descriptor external="true">
<root-element>wldf-resource</root-element>
<uri>META-INF/weblogic-diagnostics.xml</uri>
</module-descriptor>
</module-override>
<config-root>/opt/soauser/products/soa11.1/Oracle_SOA1/soa/connectors/plan</config-root>
</deployment-plan>
-Rohit

Hi Arik,
To answer your questions :
You are using HAFileAdapter in your processes JNDI defenitions? --Yes
Check in your HAFileAdapter Connection Pool if Shrinking Enabled is set to true. --Its set to true
I would recomend also to change the properties Test Connections On Reserve to true, and Test Frequency Seconds(900 is the default). --These properties are also in place
-Rohit

11g TP2 ADF Task Flows and Transaction Management

I'm wondering how ADF Task Flow Transaction Management works vis-a-vis database sessions and using stored procedure calls in an environment with connection pooling. I haven't written the code yet but am looking for a better understanding of how it works before I try.
Example:
I create a bounded adf task flow. I set the "transaction" property to "new-transaction" and the "data control scope" to "isolated".
As the task flow is running, the user clicks buttons that navigate from page to page in the flow. Each button click posts the page back to the app server. On the app server a backing bean method in each page calls a stored procedure in a database package to modify some values in one or more tables in the database. The procedure does not commit these changes.
Each time a backing bean makes a stored procedure call will it be in the same database session? Or will connection pooling possibly return a different database connection and therefore a different database session?
If the transaction management feature of the adf task flows guarantees me that I will always be in the same database session then I don't have to write any extra code to make this work. Will it do that or not?

I don't know if it is documented in the adf documentation currently available for 11g TP2 but what you ask for is a normal transaction management with connection pooling and i can't imagine it is not implemented in ADF BC layer like it is in JPA or other persistence layer.
A transaction will always be executed in the same session. Normally your web session will stay in the same session even you start more than one transaction. You don't have to write any code to manage the session pooling. It is a good practices to customize it at the persistence layer during installation depending on your infrastructure.
Take a look into Fusion Developer Guide ... i'm sure you will find some better explanations about this.

Alert: WebServices connectivity (Internal) transaction failure - The credentials can't be used to test Web Services.

Hi.
Could you please help me to resolve this issue.
I have SCOM 2012 installed to monitor environment with Exchnage 2010 SP3. There are 2 sites with Exchnage servers within the organization. There are 2 mailboxes being created to test both sites.
I am getting following alert:
Alert: WebServices connectivity (Internal) transaction failure - The credentials can't be used to test Web Services.
description: The test mailbox was not initialized. Run new-TestCasConnectivityUser.ps1 to ensure that the test mailbox is created.
Detailed information:
[Microsoft.Exchange.Monitoring.CasHealthUserNotFoundException]: The user wasn't found in Active Directory. UserPrincipalName: extest*****@****.local. Additional error information: [System.Security.SecurityException]:
Logon failure: unknown user name or bad password.
Diagnostic command: "Test-WebServicesConnectivity -MonitoringContext:$true -TrustAnySSLCertificate:$true -LightMode:$true"
EventSourceName: MSExchange Monitoring WebServicesConnectivity Internal
I have tried the next steps:
1. Verified that mailbox is exist and it's not locked (same for the second mailbox)
2. Deleted those mailboxes and created a new using new-TestCasConnectivityUser.ps1 verified that this mailbox is visible on all DC's accross the forest (both mailboxes)
and that temporary password was accepted;
3. Cleared the cache on the SCOM 2012;
4. Still getting the same alert
I will really appriciate any help.
Thanks.

Hi,
Hope these posts help you:
http://thoughtsonopsmgr.blogspot.ca/2013/11/exchange-server-2010-mp-no-synthetic.html
https://social.technet.microsoft.com/Forums/systemcenter/en-US/437f2bbb-cd96-40c3-8c56-6d4d176a9520/exchange-2010-mp-constantly-throws-webservices-connectivity-internal-transaction-failure?forum=operationsmanagermgmtpacks
Natalya
### If my post helped you, please take a moment to Vote as Helpful and\or Mark as an Answer

Transactions in Multithreaded app

Is it safe to use the same java.sql.Connection instance all over multithreaded app? Is transaction session associated with a thread? Or one Connection keeps just one transaction session for all threads?
Any help's appreciated.

Is it safe to use the same java.sql.Connection
instance all over multithreaded app?Yes, providing your access/uses is thread safe, i.e. syncronised.
Is transaction
session associated with a thread?No a connection.
Or one Connection
keeps just one transaction session for all threads?Yes.
A transactions should be autonomous, if all threads use the same transaction, it would be pointless using transactions in the first place.
Any help's appreciated.Checkout these link, your should
http://developer.java.sun.com/developer/onlineTraining/Programming/JDCBook/bmp.html
http://developer.java.sun.com/developer/onlineTraining/Programming/JDCBook/jdbc.html
http://developer.java.sun.com/developer/technicalArticles/xml/metadata/

WLS - WLE Connections and Transactions in multithreaded

Similar Messages

Maybe you are looking for