JTS transaction controller working with WAS 6
We are using TopLink 9.0.4.4. It provides the controller class JTSExternalTransactionController_5_0 to work with WAS 5.0 .
Where can I get JTS transaction controller that works with WAS 6 application server?
Your info would be greatly appreciated.
Haiwei
I believe that the JTSExternalTransactionController_5_1 controller will work with WebSphere 6.
Similar Messages
-
How Transaction Manager work with Resource Manager, like Connection pool?
hi,
I'm using BEA Webloigc8.1 Stateless Session Bean/DAO/Oracle stored proc.
but I'm not quite clear how Transaction Manager work with Resource Manager, like Connection pool.
my understanding is that, in a weblogic transaction, a stateless session bean interact with several DAOs, and for each method of DAO a connection is acquired from connection pool. I've heard that the connection will not return to pool until the transaction commits.
My question is that, does it mean that for a weblogic transaction, multiple connections might be allocated to it? and if multiple connections are allocated, then how many oracle transactions would be started? or multiple connections share the same oracle transaction?
I didn't feel it make sense to start multiple oracle transactions, cause deadlock might be incurred in a single weblogic transaction.
any help appreciated!Xin Zhuang wrote:
hi,
I'm using BEA Webloigc8.1 Stateless Session Bean/DAO/Oracle stored proc.
but I'm not quite clear how Transaction Manager work with Resource Manager, like Connection pool.
my understanding is that, in a weblogic transaction, a stateless session bean interact with several DAOs, and for each method of DAO a connection is acquired from connection pool. I've heard that the connection will not return to pool until the transaction commits.
My question is that, does it mean that for a weblogic transaction, multiple connections might be allocated to it? and if multiple connections are allocated, then how many oracle transactions would be started? or multiple connections share the same oracle transaction?
I didn't feel it make sense to start multiple oracle transactions, cause deadlock might be incurred in a single weblogic transaction.
any help appreciated!Hi. If you configure your WLS DataSource to use keep a connection for
the duration of a tx, it will do that, and in any case there can be
no deadlock however many connections operate for a given XA transaction.
Here is the best coding form for DAOs or any other user-written code
for using WebLogic DataSources. This is important for two reasons:
1 - Thread-safety is maintained as long as the connection is a
method-level object.
2 - It is crucial to notify WebLogic that you are done with a connection
ASAP, by your calling close() on it. We will then put it back in the
pool, or keep it under the covers for your next request if it's in a
transaction etc. The pool is optimized for quick get-use-close scenarios.
public void one_of_my_main_JDBC_Methods()
Connection con=null; // Must be a method level object for thread-safety
// It will be closed by the end of the method.
try {
con = myDataSource.getConnection(); // Get the connection in the try
// block, directly from the WebLogic
// datasource
// do all the JDBC within this try block. You can pass the
// connection to subordinate methods, but not to anywhere
// that thinks it can use the connection later.
rs.close(); // close any result set asap
stmt.close(); // then close any statement asap
// When you're done with JDBC
con.close(); // close the connection asap
con = null; // nullify it so the finally knows it's done
catch (Exception e) {
// do whatever catch stuff you want. You don't
// need a catch block if you don't want one...
finally {
// It is important to close a JDBC connection ASAP when it's not needed.
// without fail, and regardless of exit path. Do everything in your
// finally block in it's own try-catch-ignore so everything is done.
try { if (con != null) con.close();} catch (Exception ignore){}
return ret;
} -
Will an Xbox 360 Wired Controller Work with an iMac G5?
I was just wondering, because my friend got it to work with his new iMac (the current one). If it does, does anyone know how to set it up?
Please reply.
Thanks.This should do the trick.
http://tattiebogle.net/index.php/ProjectRoot/Xbox360Controller/OsxDriver -
Can Wlan Controller work with Third party Aps
Can Cisco Wlan Controller work for 3rd party Aps which does not have LWAPP running. If yes How.If no then how we can manage existing Ap's of say 3com in the network...
Hi Friend,
No, Cisco WLC will not support any third party APs. Even if Cisco APs are not lwapp AP then WLC will not be able to manage them.
We need to have Cisco Lwapp APs only for wireless lan controller to manage them.
For 3com Aps you need to talk to 3com guys or any third party tool if available to manage these APs.
HTH
Ankur -
HttpSession Invalidate not working with WAS LTPA
I normally handle site logout with a JSP that executes <% session.invalidate(); %> then redirects to the home page. Now I am running on WebSphere Application Server 5.1 authenticating against a Novell eDirectory LDAP server using LTPA and a SSL Certificate. Session.invalidate() does not work. Someone suggested it is because WAS is using LTPA. LTPA creates an authentication cookie that is not cleared by session.invalidate (?).
IBM does have a proprietary logout JSP I could use**, but I don't want to use a vendor specific solution. Has anybody tackled a session logout that clears the LTPA cookie without being tied to a vendor's J2EE container?
Thanks!
Steve Mitchell
http://www.byteworksinc.com
** http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/xsec_formlogin.htmlI saw this old post of mine and thought I would follow-up. I never found a vendor neutral solution. When running on WebSphere I redirect to a JSP that posts to ibm_security_logout. When testing on Tomcat I just call session.invalidate(). My Struts LogoutAction does the following:
if ( serverInfo.toUpperCase( ).indexOf( "WEBSPHERE" ) > -1 )
return mapping.findForward( "websphereLogoutForward" );
session.invalidate( );
return mapping.findForward( "success" );
Steve Mitchell
http://www.byteworksinc.com -
Will a PS4 dualShock 4 wireless controller work with my mini for racing games?
I purchased Real Racing 2 from the app store. It shows that I can connect an external control to it. Just doesn't specify what kind.
It should work since it works for others:
http://www.pcmag.com/article2/0,2817,2429965,00.asp
http://www.macworld.com/article/2597642/how-to-use-a-game-controller-with-your-m ac.html
http://www.tekrevue.com/tip/ps4-controller-mac/
http://www.mactrast.com/2013/10/use-playstation-4-dualshock-4-controller-play-ga mes-mac/
https://www.youtube.com/watch?v=Ub-KYXUkIzw -
Which gaming controller works with games from the app store?
I want to play the first person shooter game Modern Combat with a gamming controller that has the same format as the xbox 360 controlers but cant find any in stores that are compatiable with apple products , people have suggested that i might be able to download the drivers for controllers online but have not been spcific as to which contolers and where on the internet . any help would be great.
Redeem the card into your iTunes account and make purchases.
Apple - iTunes - Inside iTunes - How to Redeem Free Download Codes and Gift Cards In the App Store and iTunes -
Will the Razer Onza controller work with my Macbook Pro or iMac?
I am thinking about getting one, and this will be the dealbreaker for me. I will be using it for gaming on my Xbox and Macbook Pro. I primarily want to play Steam games like TF2 on my Mac. I'm on Lion OS.
Yes, it works.
Why wouldn't it?
It just uses bluetooth.
-Scott -
Does the M-audio iControl work with the newest version of Garageband (2013)
I'm looking for a dedicated controller for garageband. It seems that the m-audio icontrol was the only one ever made and was released in 2005. I've read it worked with all versions of GB up to '11. Would this 8 year old controller work with the newest version of garageband (newest version as of october 2013)? Or are there any new dedicated controllers that are an option.
Haven't checked all the options, but yes, M-Audio iControl works with Garageband 10.0.1 and with Logic Pro X (10.0.4).
I am astounded that a) they stopped making it b) no-one has stepped in to offer a similar (or better) hardware solution - especially as GB is now free.
If you can get one, grab it! -
Hi,
we are working on SAP WAS 700. We have just moved from WAS 640 and NWDS 2.0.09 to WAS 700 and NWDS 640. I am having a problem that when I try to open the UME from the WAS home page, I get the following error :
Application error occurred during the request procession.
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
Error compiling [/index.jsp] of alias [useradmin] of J2EE application [sap.com/com.sap.security.core.admin].
The log gives the following message for this :
#1.5#00174212003F004C000002D000000ADC00043341A6CA4DEF#1182256971041#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.engine.docs.examples finished successfully on server 307377350#
#1.5#00174212003F004C000002D100000ADC00043341A6CA4E37#1182256971041#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.engine.docs.examples finished on current cluster node for 52474 ms.#
#1.5#00174212003F004C000002D200000ADC00043341A6D48193#1182256971713#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.engine.class.download] finished successfully on Web Container.#
#1.5#00174212003F004C000002D300000ADC00043341A6D483EC#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.engine.class.download finished successfully on server 307377350#
#1.5#00174212003F004C000002D400000ADC00043341A6D48446#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.engine.class.download finished on current cluster node for 672 ms.#
#1.5#00174212003F004C000002D500000ADC00043341A6D4A26C#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/cafummetadata~content finished successfully on server 307377350#
#1.5#00174212003F004C000002D600000ADC00043341A6D4A2D8#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/cafummetadata~content finished on current cluster node for 0 ms.#
#1.5#00174212003F004C000002D700000ADC00043341A6DB2A79#1182256972135#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.lcr.saprfc finished successfully on server 307377350#
#1.5#00174212003F004C000002D800000ADC00043341A6DB2AE9#1182256972151#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.lcr.saprfc finished on current cluster node for 438 ms.#
#1.5#00174212003F004C000002D900000ADC00043341A6DB482F#1182256972151#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/cafeugp~content finished successfully on server 307377350#
#1.5#00174212003F004C000002DA00000ADC00043341A6DB489B#1182256972151#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/cafeugp~content finished on current cluster node for 0 ms.#
#1.5#00174212003F004C000002E200000ADC00043341A6E854CD#1182256973010#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/cafruntimemonitoring~ear] finished successfully on Web Container.#
#1.5#00174212003F004C000002E300000ADC00043341A6E85755#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/cafruntimemonitoringear : Application sap.com/cafruntimemonitoringear has a weak reference to resource jmsfactory/TopicConnectionFactory with type javax.jms.TopicConnectionFactory but the resource is not available and the application may not work correctly!#
#1.5#00174212003F004C000002E400000ADC00043341A6E857BE#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/cafruntimemonitoring~ear finished successfully on server 307377350#
#1.5#00174212003F004C000002E500000ADC00043341A6E85806#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/cafruntimemonitoring~ear finished on current cluster node for 859 ms.#
#1.5#00174212003F004C000002E600000ADC00043341A6E87157#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###New internal library C:
usr
sap
F48
JC30
j2ee
cluster
server0
apps
sap.com/com.sap.ip.bi.sdk.dac.olap
bi_sdk_olap.jar will be downloaded.#
#1.5#00174212003F004C000002E700000ADC00043341A7042104#1182256974823#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###New internal library C:
usr
sap
F48
JC30
j2ee
cluster
server0
apps
sap.com/com.sap.ip.bi.sdk.dac.olap
bi_sdk_olap_xmi.jar will be downloaded.#
#1.5#00174212003F004C000002E800000ADC00043341A732696B#1182256977854#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.ip.bi.sdk.dac.olap finished successfully on server 307377350#
#1.5#00174212003F004C000002E900000ADC00043341A73269DB#1182256977854#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.ip.bi.sdk.dac.olap finished on current cluster node for 4844 ms.#
#1.5#00174212003F004C000002EA00000ADC00043341A7383749#1182256978245#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.ip.bi.sdk.monitoring] finished successfully on Web Container.#
#1.5#00174212003F004C000002EB00000ADC00043341A73839D0#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.ip.bi.sdk.monitoring finished successfully on server 307377350#
#1.5#00174212003F004C000002EC00000ADC00043341A7383A33#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.ip.bi.sdk.monitoring finished on current cluster node for 375 ms.#
#1.5#00174212003F004C000002ED00000ADC00043341A7385752#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/cafeugpmodelpwflocaluwlconn finished successfully on server 307377350#
#1.5#00174212003F004C000002EE00000ADC00043341A73857C1#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/cafeugpmodelpwflocaluwlconn finished on current cluster node for 0 ms.#
#1.5#00174212003F004C000002F600000ADC00043341A796016E#1182256984386#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /SLDStart/plain, appName sap.com/tclmwebadminsldstartapp#
#1.5#00174212003F004C000002F700000ADC00043341A796024E#1182256984386#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /SLDStart/secure, appName sap.com/tclmwebadminsldstartapp#
#1.5#00174212003F004C000002F800000ADC00043341A79602A2#1182256984386#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tclmwebadminsldstartapp] finished successfully on Web Container.#
#1.5#00174212003F004C000002F900000ADC00043341A79605A7#1182256984386#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/tclmwebadminsldstartapp : JAR File: sap.comtclmwebadminsldstart~ejb.jar XML file: ejb-j2ee-engine.xml Element: description is empty. It is not recommended to use empty value elements. Please remove the element or define its value!#
#1.5#00174212003F004C000002FA00000ADC00043341A7960610#1182256984386#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tclmwebadminsldstartapp finished successfully on server 307377350#
#1.5#00174212003F004C000002FB00000ADC00043341A7960657#1182256984386#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tclmwebadminsldstartapp finished on current cluster node for 6141 ms.#
#1.5#00174212003F004C000002FC00000ADC00043341A83A10A5#1182256995138#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.netweaver.bc.uwl.moni] finished successfully on Web Container.#
#1.5#00174212003F004C000002FD00000ADC00043341A83A1407#1182256995138#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.netweaver.bc.uwl.moni finished successfully on server 307377350#
#1.5#00174212003F004C000002FE00000ADC00043341A83A1524#1182256995138#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.netweaver.bc.uwl.moni finished on current cluster node for 10752 ms.#
#1.5#00174212003F004C000002FF00000ADC00043341A84C226F#1182256996325#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tcwdpdfsvrchal] finished successfully on Web Container.#
#1.5#00174212003F004C0000030000000ADC00043341A84C2558#1182256996325#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tcwdpdfsvrchal finished successfully on server 307377350#
#1.5#00174212003F004C0000030100000ADC00043341A84C25DE#1182256996325#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tcwdpdfsvrchal finished on current cluster node for 1187 ms.#
#1.5#00174212003F004C0000030900000ADC00043341A9823866#1182257016640#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/tc~uddi' application started successfully.#
#1.5#00174212003F004C0000030A00000ADC00043341A98238DF#1182257016640#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tc~uddi] finished successfully on Web Container.#
#1.5#00174212003F004C0000030B00000ADC00043341A9823B30#1182257016640#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tc~uddi finished successfully on server 307377350#
#1.5#00174212003F004C0000030C00000ADC00043341A9823B84#1182257016640#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tc~uddi finished on current cluster node for 20315 ms.#
#1.5#00174212003F004C0000031400000ADC00043341A99803D0#1182257018078#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tcsupportplatformwd finished successfully on server 307377350#
#1.5#00174212003F004C0000031500000ADC00043341A998043E#1182257018078#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tcsupportplatformwd finished on current cluster node for 1438 ms.#
#1.5#00174212003F004C0000031600000ADC00043341A9C56179#1182257021047#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/cafeugpmodeliforms~eap] finished successfully on Web Container.#
#1.5#00174212003F004C0000031700000ADC00043341A9C563D0#1182257021047#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/cafeugpmodeliformseap : JAR File: sap.comcafeugpmodeliforms~ejb.jar XML file: ejb-j2ee-engine.xml Element: description is empty. It is not recommended to use empty value elements. Please remove the element or define its value!#
#1.5#00174212003F004C0000031800000ADC00043341A9C56434#1182257021047#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/cafeugpmodeliforms~eap finished successfully on server 307377350#
#1.5#00174212003F004C0000031900000ADC00043341A9C5647C#1182257021047#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/cafeugpmodeliforms~eap finished on current cluster node for 2969 ms.#
#1.5#00174212003F004C0000031A00000ADC00043341A9F0EE76#1182257023891#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tclmwebadminsysconfigapp] finished successfully on Web Container.#
#1.5#00174212003F004C0000031B00000ADC00043341A9F0F0C9#1182257023891#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tclmwebadminsysconfigapp finished successfully on server 307377350#
#1.5#00174212003F004C0000031C00000ADC00043341A9F0F120#1182257023891#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tclmwebadminsysconfigapp finished on current cluster node for 2844 ms.#
#1.5#00174212003F004C0000032400000ADC00043341AA3CEBEA#1182257028876#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tclmwebadminperformanceprovider_ear] finished successfully on Web Container.#
#1.5#00174212003F004C0000032500000ADC00043341AA3CEE34#1182257028876#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tclmwebadminperformanceprovider_ear finished successfully on server 307377350#
#1.5#00174212003F004C0000032600000ADC00043341AA3CEE8D#1182257028876#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tclmwebadminperformanceprovider_ear finished on current cluster node for 4970 ms.#
#1.5#00174212003F004C0000032E00000ADC00043341AAB4C8A8#1182257036736#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /BizcCommLayerUtilities/Config1, appName sap.com/tcbizcws~ear#
#1.5#00174212003F004C0000032F00000ADC00043341AAB4CA9D#1182257036736#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /BizcCommLayerAuthoring/Config1, appName sap.com/tcbizcws~ear#
#1.5#00174212003F004C0000033000000ADC00043341AAB4CAF2#1182257036736#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tcbizcws~ear] finished successfully on Web Container.#
#1.5#00174212003F004C0000033100000ADC00043341AAB4CD69#1182257036736#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tcbizcws~ear finished successfully on server 307377350#
#1.5#00174212003F004C0000033200000ADC00043341AAB4CDBF#1182257036736#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tcbizcws~ear finished on current cluster node for 7860 ms.#
#1.5#00174212003F004C0000033300000ADC00043341AAB582F5#1182257036783#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/caf~km.ep.kmtaskservice finished successfully on server 307377350#
#1.5#00174212003F004C0000033400000ADC00043341AAB58363#1182257036783#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/caf~km.ep.kmtaskservice finished on current cluster node for 47 ms.#
#1.5#00174212003F004C0000033500000ADC00043341AB3A1074#1182257045471#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader com.sap/irj on the system, but will register reference for furture usage.#2#sap.com/sap.comtckmccoll.room.wsdepl#com.sap/irj#
#1.5#00174212003F004C0000033600000ADC00043341AB4D215A#1182257046721#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /RoomABAPWS/Config1, appName sap.com/sap.comtckmccoll.room.wsdepl#
#1.5#00174212003F004C0000033700000ADC00043341AB4D21D7#1182257046721#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/sap.comtckmccoll.room.wsdepl] finished successfully on Web Container.#
#1.5#00174212003F004C0000033800000ADC00043341AB4D24E1#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/sap.comtckmccoll.room.wsdepl : Application sap.com/sap.comtckmccoll.room.wsdepl has hard reference to application sap.com/com.sap.km.application and is starting it!#
#1.5#00174212003F004C0000033900000ADC00043341AB4D2542#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/sap.comtckmccoll.room.wsdepl : Application sap.com/sap.comtckmccoll.room.wsdepl has weak reference to application sap.com/com.sap.netweaver.coll.appl.room.rfcadapter and is starting it!#
#1.5#00174212003F004C0000033A00000ADC00043341AB4D2599#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/sap.comtckmccoll.room.wsdepl : Application sap.com/sap.comtckmccoll.room.wsdepl has weak reference to application com.sap/irj and is starting it!#
#1.5#00174212003F004C0000033B00000ADC00043341AB4D25E8#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/sap.comtckmccoll.room.wsdepl finished successfully on server 307377350#
#1.5#00174212003F004C0000033C00000ADC00043341AB4D262F#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/sap.comtckmccoll.room.wsdepl finished on current cluster node for 9938 ms.#
#1.5#00174212003F004C0000033D00000ADC00043341AB4F884D#1182257046878#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader library:kernel.sda on the system, but will register reference for furture usage.#2#sap.com/com.sapportals.supportplatform#library:kernel.sda#
#1.5#00174212003F004C0000033E00000ADC00043341AB4F89A8#1182257046878#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader library:com.sap.engine.client.lib on the system, but will register reference for furture usage.#2#sap.com/com.sapportals.supportplatform#library:com.sap.engine.client.lib#
#1.5#00174212003F004C0000033F00000ADC00043341AB4F8A6D#1182257046878#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.runtime.application.jcoclient on the system, but will register reference for furture usage.#2#sap.com/com.sapportals.supportplatform#sap.com/com.sap.portal.runtime.application.jcoclient#
#1.5#00174212003F004C0000034700000ADC00043341AB96ACB5#1182257051534#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sapportals.supportplatform' application started successfully.#
#1.5#00174212003F004C0000034800000ADC00043341AB96AD31#1182257051534#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sapportals.supportplatform] finished successfully on Web Container.#
#1.5#00174212003F004C0000034900000ADC00043341AB96AFE4#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Library kernel.sda is not deployed or loaded, but resolving of application sap.com/com.sapportals.supportplatform continues because it has weak reference to this library.#
#1.5#00174212003F004C0000034A00000ADC00043341AB96B101#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Library com.sap.engine.client.lib is not deployed or loaded, but resolving of application sap.com/com.sapportals.supportplatform continues because it has weak reference to this library.#
#1.5#00174212003F004C0000034B00000ADC00043341AB96B154#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.pcd.glservice and is starting it!#
#1.5#00174212003F004C0000034C00000ADC00043341AB96B1B2#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.contentmigration.contentmigrationservice and is starting it!#
#1.5#00174212003F004C0000034D00000ADC00043341AB96B1FF#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.httpconnectivity.urlfetcherservice and is starting it!#
#1.5#00174212003F004C0000034E00000ADC00043341AB96B24C#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.ivs.connectorservice and is starting it!#
#1.5#00174212003F004C0000034F00000ADC00043341AB96B2A4#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.runtime.application.jcoclient and is starting it!#
#1.5#00174212003F004C0000035000000ADC00043341AB96B2F1#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.ivs.systemlandscapeservice and is starting it!#
#1.5#00174212003F004C0000035100000ADC00043341AB96B33B#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.ivs.iviewservice and is starting it!#
#1.5#00174212003F004C0000035200000ADC00043341AB96B38C#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.themes.designservice and is starting it!#
#1.5#00174212003F004C0000035300000ADC00043341AB96B3D7#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.themes.lafservice and is starting it!#
#1.5#00174212003F004C0000035400000ADC00043341AB96B421#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.productivity.resolverservice and is starting it!#
#1.5#00174212003F004C0000035500000ADC00043341AB96B46C#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.runtime.config and is starting it!#
#1.5#00174212003F004C0000035600000ADC00043341AB96B4B6#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has a weak reference to resource jdbc/Resource1 with type javax.sql.DataSource but the resource is not available and the application may not work correctly!#
#1.5#00174212003F004C0000035700000ADC00043341AB96B510#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sapportals.supportplatform finished successfully on server 307377350#
#1.5#00174212003F004C0000035800000ADC00043341AB96B557#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sapportals.supportplatform finished on current cluster node for 4813 ms.#
#1.5#00174212003F004C0000036000000ADC00043341AB9A0CF9#1182257051753#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tclmwebadminclusteradminwd finished successfully on server 307377350#
#1.5#00174212003F004C0000036100000ADC00043341AB9A0D67#1182257051753#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tclmwebadminclusteradminwd finished on current cluster node for 219 ms.#
#1.5#00174212003F004C0000036900000ADC00043341AC476D74#1182257063114#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tc~workflowmodeler] finished successfully on Web Container.#
#1.5#00174212003F004C0000036A00000ADC00043341AC4770C7#1182257063114#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tc~workflowmodeler finished successfully on server 307377350#
#1.5#00174212003F004C0000036B00000ADC00043341AC47712A#1182257063114#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tc~workflowmodeler finished on current cluster node for 11361 ms.#
#1.5#00174212003F004C0000037300000ADC00043341AD0C9DC4#1182257076037#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv] finished successfully on Web Container.#
#1.5#00174212003F004C0000037400000ADC00043341AD0CA03B#1182257076037#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv finished successfully on server 307377350#
#1.5#00174212003F004C0000037500000ADC00043341AD0CA099#1182257076037#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv finished on current cluster node for 12923 ms.#
#1.5#00174212003F004C0000037D00000ADC00043341AD0D14D7#1182257076068#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.ip.bi.biloggingconfig finished successfully on server 307377350#
#1.5#00174212003F004C0000037E00000ADC00043341AD0D1549#1182257076068#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.ip.bi.biloggingconfig finished on current cluster node for 31 ms.#
#1.5#00174212003F004C0000038600000ADC00043341AD0FDBFC#1182257076256#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.netweaver.bc.uwl.logging finished successfully on server 307377350#
#1.5#00174212003F004C0000038700000ADC00043341AD0FDC70#1182257076256#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.netweaver.bc.uwl.logging finished on current cluster node for 188 ms.#
#1.5#00174212003F004C0000038F00000ADC00043341AD383B60#1182257078897#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tcsldstartup~app] finished successfully on Web Container.#
#1.5#00174212003F004C0000039000000ADC00043341AD383DD5#1182257078897#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tcsldstartup~app finished successfully on server 307377350#
#1.5#00174212003F004C0000039100000ADC00043341AD383E2D#1182257078897#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tcsldstartup~app finished on current cluster node for 2641 ms.#
#1.5#00174212003F004C0000039900000ADC00043341AD48B35C#1182257079975#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.ip.bi.sdk.datasource.sys finished successfully on server 307377350#
#1.5#00174212003F004C0000039A00000ADC00043341AD48B3CE#1182257079975#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.ip.bi.sdk.datasource.sys finished on current cluster node for 1078 ms.#
#1.5#00174212003F004C000003A200000ADC00043341AD619BAC#1182257081616#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tclmwebadminmonitorcomplib~wd finished successfully on server 307377350#
#1.5#00174212003F004C000003A300000ADC00043341AD619C1D#1182257081616#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tclmwebadminmonitorcomplib~wd finished on current cluster node for 1641 ms.#
#1.5#00174212003F004C000003A400000ADC00043341AD794D3C#1182257083163#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.workflow.j2eemoni] finished successfully on Web Container.#
#1.5#00174212003F004C000003A500000ADC00043341AD795057#1182257083163#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
Warning occurred on server 307377350 during startApp sap.com/com.sap.workflow.j2eemoni : Application sap.com/com.sap.workflow.j2eemoni has weak reference to application sap.com/com.sap.workflow.apps and is starting it!#
#1.5#00174212003F004C000003A600000ADC00043341AD7950BD#1182257083163#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/com.sap.workflow.j2eemoni finished successfully on server 307377350#
#1.5#00174212003F004C000003A700000ADC00043341AD795105#1182257083163#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/com.sap.workflow.j2eemoni finished on current cluster node for 1547 ms.#
#1.5#00174212003F004C000003A800000ADC00043341AD7AF3AE#1182257083272#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###The synchronization of applications with DB completed for 1631354 ms.#
#1.5#00174212003F004D0000005B00000ADC00043341CABE84F0#1182257574096#/System/Server/WebRequests#sap.com/com.sap.security.core.admin#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2####fedffd001e6311dcc5e900174212003f#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Processing HTTP request to servlet [jsp] finished with error.
The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
Exception in thread "main"
Exception id: [00174212003F004D0000005A00000ADC00043341CABE8396]#
#1.5#00174212003F004D0000005E00000ADC00043341CAD04526#1182257575252#/System/Server/WebRequests#sap.com/com.sap.security.core.admin#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2####fedffd001e6311dcc5e900174212003f#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Processing an HTTP request by the error page [/error.jsp] finished with errors. Probably the exception [com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
Exception in thread "main"
].] thrown by the requested servlet [/useradmin/error.jsp] cannot be processed.
The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
Exception in thread "main"
Exception id: [00174212003F004D0000005D00000ADC00043341CAD04370]#
I have JDK 1.4.2_014 installed on the system and WAS has its own JDK installed inside its own folder. I am having a similar problem with NWDS where it always picks up my JRE as default which is not installed inside my jdk 1.4._014. This remains the same even when I change the jre path inside the NWDS preference from the Window->Preferences menu.
This problem has stayed the same even after I uninstalled the jdk , NWDS, and WAS and reinstalled them from the scratch. Before that, I had actually got NWDS working when I added the tools.jar file from the jdk 1.4_014 to the jre my NWDS was pointing to. but this trick is not working with WAS.
Also when I had deployed the web dynpro project, it did not show in the browser window which stayed blank.
Please help me with it.I don't know. You would have to find people who pay attention to such things. Maybe try the developer forums at http://devforums.apple.com. From everything I have read, iAd is not one of the best advertising networks. Even the best advertising networks pay very, very little. I think it is much better to provide functionality that people are willing to pay for, probably via in-app purchases.
-
What is the best way to work with mixed media in 1080 timeline?
Hi there,
I have a project shot mostly in 1080 24p but a bit of 720 24p and 4x3 30p footage.
What is the best way to work with this mixed media?
Thanks!
StevenHi Shane,
Ok just to recap (thanks for being patient by the way)...I have put some questions in here...feel free to write in caps to respond and we'll put this baby to rest!
1) I will work in a 1080p FCP sequence, correct?
2) HD 1080p footage captured as applepro res hq I will leave as is and work with?
3) HD 720p footage which was captured as applepro res hq. Can I just drop in 1080 timeline and let FCP do its work? Or should i run through compressor, if so what setting shall I submit it too?
4) I dont have a budget for an external hardware to convert SD to HD...should I capture my SD Beta through Final Cut and just leave and let FCP do its work? Or should I run through compressor? If so what setting shall I submit it too?
5) For for my master sequence in FCP am I not using an I-Frame format apple pro res if I am using my apple pro res hq 1080 footage as my formatted sequence? I am not sure what you mean by GOP?
6) I also found some 60p footage 1080p XDCAM compressor shot with the same XDCAM camera. I put in the 1080p 24p timeline but it was pretty choppy...any ideas of this conform?
Thanks very much for all your help it has gone along way,
Steven
Saying what CODECS you are working with was my question. 1080, 720, 4:3...really says nothing. There are a dozen 1080 codecs, another dozen 720 codecs, and nearly 100 4:3 formats.
Best to capture all the footage to one uniform codec.
Second best is to work with one format and let FCP conform the rest to that...IF and only IF that format is an I-Frame format like ProRes. GOP formats as master sequence formats cause TONS of issues.
What I'd do is work 1080 ProRes, just add the 720p footage (Use Compressor to convert it if you didn't have a lot, but if you had a lot, just add it), but I'd capture all the SD 4:3 footage via a Kona 3 or Matrox MXO2 as 1080 ProRes. Hardware conversion of SD to HD is much better than anything FCP can do. AE might do good as well. But then use Compressor to convert 29.97 footage captured (you can't convert 29.97 to 23.98 when you capture) to get to 23.98. -
HELP - PULL-DOWN ISSUE WORKING WITH ARCHIVAL FILM IN 24P
Bear with me here... I'm working on a historical doc for a local PBS station. Camera footage was originated using the HDX 200 in 720p-24n. Much of the program uses old 16mm film that's been xfer'd to an uncompressed video file using the 16mm "Sniper" (a psuedo-telecine transfer system. The system scans the film frames into a pc one at a time and stores the images as a single movie file using a proprietary codec). You can tell the Sniper's software what frame rate the original film footage was shot at - i.e. 18fps, 24fps and so-on. However, when you export it back out it only outputs to a 29.97 interlaced file.
Here's the problem: The film I'm working with was originated at 18fps - not 24. But, I'm working with a 24p sequence. I need to convert the footage so that it plays cleanly in a 24p environment. But I can't run it through CT and do a reverse telecine to remove the pull-down because that's designed for footage that was originated at 24fps only. When I try to do it on footage that was shot at 18fps, I end up with a wierd flashing/banding thing as it tries to apply a 24 frame pull-down to an 18 frame image.
I'm thinking that there has to be a plug-in either for FCP, CT or for the Sniper that can work a pull-down from 18fps film to 24p video.
Anyone have any ideas?
Tim Walton
KVIE Public TelevisionYeah, I thoought of that. But I kinda wanted to keep the program in native 24p if I could.
If I did it that way, wouldn't I have to go ahead and edit the program in 24p, then export it out at 29.97, then re-import it into a 29.97 Sequence and finally add the archive material? -
Does GetTextExtentPoint32 work with dpi settings above 100%?
I hope I have the right forum.
I use GetTextExtentPoint32 to measure the width and height of some text. I use the size data to size an edit control I then show in the app. Works fine for most cases. But I have a customer with a Japanese OS on a surface pro 2 and the code doesn't quite
fit the text. Eventually I found that the machine has the dpi setting set to 150%. So I set that up on my English OS desktop machine. Sure enough, the text doesn't fit in that config either. Then I tried something out. I took the number of characters in my
string and multiplied that by the average char width in the font structure and ... the size I calculate and the size GetTextExtentPoint32 returns are always the same value when running at 150% (but not at 100%). Is GetTextExtentPoint32 actually measuring the
exact size the text will render at exactly when running at 150% or is it giving me back incorrect data?
R.D. HollandMea culpa! The code I was working with was being passed a DC that had no font selected into it! Hence the system used a default font. Once I realized that and selected the font that would eventually be used at display time, I got back good results and
the text fits nicely.
R.D. Holland -
Oracle 11g jars not being compatible with WAS 6.1.x versions
Hi,
We have an issue with Oracle 11g jars not being compatible with WAS 6.1.x versions.
If we use Oracle10g client jars then they are working with the 11g database.
Below are the findings
Working fine With Ojdbc14.jar
Not working With Ojdbc5.jar
WAS 6.0
Working fine With Ojdbc14.jar
Not working With Ojdbc5.jar
WAS 6.013
Working fine With Ojdbc14.jar
Not working With Ojdbc5.jar
As per IBM website link Oracle 11g should be working with WAS 6.1.0.21 upwards
Could somebody please help me regarding the same.
thanks & Regards,
Anoop# Download the full Firefox installer from http://www.mozilla.com/
# Delete the Firefox [http://kb.mozillazine.org/Installation_directory installation directory], making sure all the Firefox files and folders are removed. The default location on 32 bit Windows is C:\Program Files\Mozilla Firefox\
# Re-install Firefox
Note that deleting the Firefox installation directory will not remove your bookmarks or other Firefox user data, they are stored elsewhere. -
Xbox 360 Wired Controller is not working with Windows 7.
Not to long ago I was playing Halo 2 PC using my wired Xbox 360 Controller. All of a sudden my computer (which uses Windows 7) decides not to recognize it. Every time I plug in the controller in now it comes up as "Unknown Device". I have not changed anything,
I mean anything. Yes I have tried all methods of fixing the problem but they do not work. If someone knows a sure fine way to get the controller working again it would be much appreciated.I 'm using a wired Gamestop Xbox 360 controller and I got mine to work using these steps. Good luck.
If you already have the software installed, go to programs and features and uninstall Microsoft XBOX 360 Accessories 1.2.
1) Download the drivers from
http://www.microsoft.com/hardware/download/download.aspx?category=gaming
2) Choose Gaming >
Xbox 360 Controller for Windows > Windows 7 64 bit > English.Don’t run the drivers.
Save them to a folder. (Or Xbox 360 Wireless Controller for Windows depending on your controller)
3) Right click the
Xbox360_64Eng file in the folder you downloaded to and click "create shortcut"
4) Right click the shortcut you created.
Select properties.
5) On the compatibility tab in properties, click "Run this program in compatibility mode"
ChooseWindows Server 2008 Service Pack 1 as the compatibility mode. Apply setting and click ok.
6) Right Click on the shortcut and select "Run as administrator"
7) With your controller plugged in go to
Device Manager. You should see Microsoft Common Controller for Windows Class. It located under Mice and other pointing if you do, you have arrived. If you don't, try this.
Continue only if you don’t see Microsoft Common Controller for Windows Class in Device Manager
8) Right click the unknown device that shows a problem.
9) Update Driver Software > Browse My computer for Driver Software > Let Me Pick from a List of Drivers
10) Choose Microsoft Common Controller for Windows Class > XBOX 360 Wireless Receiver for Windows
Ignore the warning.
Should work now.
Maybe you are looking for
-
Error on registering Flights of Fancy application(Partner Application, JPDK) provide
Hi When i try to add a provider for Flights of Fancy application i am getting this error An error occurred when attempting to call the providers register function. (WWC-43134) The following error occurred during the call to Web provider: Unable to in
-
Can you view 3 categories at once?
I am working on organizing my iCal (I am finally trying to make the switch to using iCal as my primary address organizer), but I can't seem to find a way to view Groups, Contacts, and Contact Information (3 separate categories) all at the same time.
-
IMac will not boot with iPod connected
Hello everyone I have a new iMac Core 2 Duo 17 inch 2.0 ghz and it seems to have a problem starting up when a 5th generation iPod is connected to the computer. When the computer is turned on with the iPod connected, the blank grey screen comes on, ye
-
Is there a lead to connect the Ipad 4 to latest ipod
I need a lead to connect the latest ipod to latest ipad, think its ipad4 to ipod5
-
Wireless Speed Test Great - Browsing Not So Great
I have a wireless setup and my MacBook Pro web browsing seems to be a bit slow. I ran a speed test (FTP) and it was blazing for my connection (over 1MBPS on Hughes.netb Satellite). The web browsing doesn't equate to this speed. Are there any Safari s