Calling bls transaction on MII server startup

Hi expert,
is it possible to call bls transaction on MII server startup?
Thanks.

Not that I am aware of - at least nothing directly. The first thought that would come to mind would be a scheduled job (something with a reasonable interval but not too frequent) that would check /XMII/Illuminator?Service=SystemInfo&Mode=Uptime and do a datediff check between datenow and the xml resulting StartTime.
At least you will know how long MII's been up and running.

Similar Messages

Lag when calling BLS Transaction from within another

Using MII 12.0.
In MII class, they told us a "best practice" was to check the "Reload Transaction after Execution" box in the configuration of a Transaction call within a BLS. The reasoning behind it was that should this not be checked, a previous result of that called BLS transaction would still be cached in memory and used instead of the newly assigned values from within your calling BLS.
Checking the "Reload transaction after Execution" box forces MII to reload that transaction when it is called.
In time analysis, what has been noticed is that there's a significant - up to 9 seconds - lag time when one BLS calls another BLS. On a time-sensitive operation, that is an eternity. That amount of overhead defeats any hope of using common code libraries.
Questions -
1. Is this a true "best practice", or is it one that adds unnecessary overhead to a BLS?
2. If the calling BLS executes 1 time - but is subject to be executed multiple times over a certain interval - is checking the Reload box of the BLS it is calling unnecessary?
3. Even if you pass new data each time you call that BLS, is it still going to use/return whatever data it has cached until the cache expires?
4. Is there another way to ensure that the called BLS uses the data you pass it (and returns the corresponding result set) without incurring the amount of overhead that we have noted?
Thanks

The version we're on is 12.0.6 Build 13, and moving to 12.1 (something I am not directly involved in). In this version, I'm not seeing the menu options you describe, so it's apparently in 12.1 or later.
The issue we are having if the "Reload transaction after execution" box is not selected is indeed caching of values.
For example -
BLS1 runs every 5 minutes
BLS2 is called from BLS1, and in this case, retrieves error log info from a table - a common module used by several BLS's.
BLS3 is also called from BLS1, and in this case, writes to an error log using information retrieved from BLS2 from within the execution of BLS1. BLS2 & BLS3's calls are in 2 separate sequences, one after the other.
If BLS2 & BLS3 DO NOT have the "Reload Transaction after execution" checked, each will run with whatever the cached data in memory is for them, even though inside BLS1 I am assigning values to the input of BLS1 to send to BLS2, and passing the returned data from BLS2 into BLS3. Unless it's checked, BLS2 & BLS3 would continue to be called, however, it would be with whatever data has been cached for them.
If that "Reload" switch is checked, it will reload each transaction & call it with whatever data is being passed.
This was mentioned in the MII class I was in also. This is a generalization, but the way they described it was being similar to how you might save a web page to your local PC, and that unless that page is refreshed & changed, that from that point on, every time you brought up your saved web page, it would always display the same values in it. They didn't go into great deal to explain the mechanics of it, but MII would only load it the first time it executed, and that unless you forced it (by checking the Reload switch), it would always execute using the same cached values no matter what you were passing.

Error calling BLS Transaction as Web service

Hi,
I am trying to call BLS tranx as Webservice from another BLS Tranx.
I craeted the simple BLS with no input parameter and set only one output parameter.
Then i created the WSDL as
http://<server:port>/XMII/WSDLGen/<Transaction path>.
In new BLS tranx, i created the Web Service action block and gave this WSDL URL (http://<server:port>/XMII/WSDLGen/<Transaction path>).
I gave username and password and selected the port(XacuteWSSoap) and then operation( xacute).
In Links, I gave the Loginname and Password.
But while executing, it showed the error as
Error Invoking Web Service Action: Status (401): Unauthorized
My username and Loginname and passwords are correct only.
What is the problem and how to solve it.
Regards,
Senthil

Hi,
Which SAP MII version you are using?
I have tested one piece in MII 12.0.9 it works for me following are steps which i followed.
After WSDL generation
1. in Web service action block --> cofigure i am passing following parameters
WSDL base URL: http://<server:port>/XMII/WSDLGen/<transaction Path>
User Name: XXX
Password: XXX
2. in Web service action block --> Links I am passing following parameters
WSDLUrl : http://<server:port>/XMII/WSDLGen/<transaction Path>
Web_Service_0.XacuteRequest{/ns1:XacuteRequest/ns1:LoginName} : XXX
Web_Service_0.XacuteRequest{/ns1:XacuteRequest/ns1:LoginPassword} : XXX
Refer below SDN thread may be helpfull:
[Web Service Action Block;
Hope it helps!!
Regards,
Manoj Bilthare

IDOC Listener not calling BLS Transaction

All,
I am running xmii 11.5.4. I have a single IDOC Listener configured with a Routing Rule for Message Type = "PROCESS_MESS_DOWNLOAD". The Routing Rule is defined to trigger a BLS called "TEST_BLS". The Listener is configured with the BLS Input Parameter.
The Listener processes the incoming message by writing the XML file to the defined Path with no problems.
The issue is the BLS Transaction will not trigger. The Transaction has a single Transaction Property of data type XML with no default value defined.
I have tried using a simple Transaction with nothing but an Event Logger or XML Trace actions to verify the Transaction is being executed. But nothing occurs.
I have viewed the General Log and see no errors or warnings or fatal log entries.
The Transaction works fine manually from inside Logic Editor and even runs from a URL invokation.
Any ideas of what to look for or try would be greatly appreciated.
Thanks,
Chuck

Udayan,
The Transaction consists of only an Event Logger Action and an XML Tracer Action. Neither of these are apparently executing. No event is logged and no entry is made to the XML Tracer file. The Transaction has a Transaction Property defined as stated in my first post.
I have noticed through trial and error that the IDOC Listener only works with the asterick message type. The actual message type of the IDOC is evidently not being read by the Listener. The IDOC being created is coming from a PPPI Process Message. The first few lines are:
<?xml version="1.0" encoding="UTF-8"?>
<PROCESS_MESS_DOWNLOAD>
<INPUT>
<CLIENT>200</CLIENT>
</INPUT>
<TABLES>
<MSEL>
<item>
<MSID>100000000000000537</MSID>
Thanks,
Chuck

Is it possible to call a java control upon server startup

I have a java control that creates business rules for validation of files submitted by users. This control
makes many calls to db controls and performs a lot of
fetch operations . Is it possible to invoke this control
upon server startup and cache the results

In the current release(8.1), calling controls from a plain Java class is not supported. Controls can only be invoked from a any one of the following Workshop components JWS/JPD/JPFs/or another control.
Hope this helps.
Raj Alagumalai

XML INPUT parameter in a MII BLS Transaction

Hi.
Please anybody has some good XSD file that can be used as a data type for a xml input parameter of a BLS Transaction ? could share it with us ? I will use it as a sample to create my own XSD file.
Until now, all XSD files that I created worked but I could not import the webservice on ECC.

Hi Stephen Kuykendall, thank you.
I still have to following error message when try to execute the webservice in wsnavigator:
[location : http://srvsdmii01.malwee.com.br:50000/XMII/WSDLGen/Default/teste2] ERROR : Definition of /definitions/types/s:schema/s:complexType[1]/s:sequence/s:element/s:complexType/s:sequence/s:element is not correct. Missing top level component (uri: 'http://schemas.xmlsoap.org/wsdl/'; name: 'GET_DETAILS').
I created a XSD file and put your xsd contente there:
so, I created a transaction propert of type "Input" with Data Type "xml" and assined your XSD with the element "GET_DETAILS":
The WSDL url (/XMII/WSDLGen/Default/teste2) generated the wsdl with the following content:
<?xml version="1.0" encoding="UTF-8"?><definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.sap.com/xMII" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.sap.com/xMII">
    
    <types>
        <s:schema elementFormDefault="qualified" targetNamespace="http://www.sap.com/xMII"><s:import schemaLocation="http://srvsdmii01.malwee.com.br:50000/XMII/WSDLGen/db/Default/WEB/Entrada.xsd"/>
            <s:complexType name="InputParams">
                <s:sequence id="InputSequence">
                <s:element maxOccurs="1" minOccurs="0" name="P_Entrada"><s:complexType><s:sequence><s:element ref="GET_DETAILS"/></s:sequence></s:complexType></s:element></s:sequence>
            </s:complexType>
            <s:element name="XacuteRequest">
                <s:complexType>
                    <s:sequence>
                        <s:element maxOccurs="1" minOccurs="0" name="LoginName" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="LoginPassword" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:InputParams"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:complexType name="Rowset">
                <s:sequence>
                    <s:element maxOccurs="unbounded" minOccurs="0" name="Row" type="s0:Row"/>
                </s:sequence>
                <s:attribute name="Message" type="s:string"/>
            </s:complexType>
            <s:complexType name="Row">
                <s:sequence id="RowSequence">
                <s:element maxOccurs="1" minOccurs="1" name="P_Saida" type="s:string"/></s:sequence>
            </s:complexType>
            <s:element name="XacuteResponse">
                <s:complexType>
                    <s:sequence>
                        <s:element maxOccurs="1" minOccurs="0" name="Rowset" type="s0:Rowset"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
        </s:schema>
    </types>
    
    <message name="XacuteSoapIn">
        <part element="s0:XacuteRequest" name="parameters"/>
    </message>
    <message name="XacuteSoapOut">
        <part element="s0:XacuteResponse" name="parameters"/>
    </message>
    
    <portType name="XacuteWSSoap">
        <operation name="Xacute">
            <input message="s0:XacuteSoapIn"/>
            <output message="s0:XacuteSoapOut"/>
        </operation>
    </portType>
    
    <binding name="XacuteWSSoap" type="s0:XacuteWSSoap">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="Xacute">
            <soap:operation soapAction="http://www.sap.com/xMII" style="document"/>
            <input>
                <soap:body use="literal"/>
            </input>
            <output>
                <soap:body use="literal"/>
            </output>
        </operation>
    </binding>
    
    <service name="XacuteWS">
        <port binding="s0:XacuteWSSoap" name="XacuteWSSoap">
            <soap:address location="http://srvsdmii01.malwee.com.br:50000/XMII/SOAPRunner/Default/teste2"/>
        </port>
    </service>
</definitions>

Error calling BLS from oracle database

Hi Experts,
We have a scenario in which we are calling BLS from oracle database using trigger. The call is made using the following URL:
http://<Host name>:50000/XMII/Runner?Transaction=<TRX_Path>&Material=MATNR&Pallet_id=PALLET&Plant=PLANT&Proc_order=PROC&Prodline=PROD&Quantity=QTY&Start_Date=DAT&Start_Time=TIM&Status=STAT&UOM=UOM1&User_name=USER&OutputParameter=*
This used to work fine in 11.5 but when we upgraded to 14.0 it is not working. We have maintained server details in \etc\host file.
We were getting error in file 'Error 1 Text.txt'. "A possible Cross-Frame Scripting attack has been prevented. Please contact your system administrator or refer to" this was the last error message. We checked this on SCN and based on the search results we have implemented SAP note 1651004 wherein setting in netweaver is required to be changed. After note was implemented we are getting another error text ('Error 2 Text.txt') "This will happen if the browser running the page tha". We tried a few ways but could not capture the full message coming.
Has anybody of faced similar problem? I would highly appreciate any hint which could help in solving this problem.
System Information:
NW 7.31 SP 10
Oracle 11.2.0.4
MII 14.0 SP5 patch 7
Regards,
Darshan

Hi Christian/Anushree,
I have now modified the URL by adding Illum login name and password:
http://<Host name>:50000/XMII/Runner?Transaction=<TRX_Path>&Material=MATNR&Pallet_id=PALLET&Plant=PLANT&Proc_order=PROC&…
When i run the url in browser it gives me the expected results but when i try to trigger it from Oracle i am still getting the error as below:
"<script>
var inPortalScript = false
var webpath = "/logon_ui_resources/"
</script>
<html>
<head>
<BASE target="_self">
<link rel=stylesheet href="/logon_ui_resources/css/ur/ur_ie5.css">
<title>User Management, SAP AG</title>
<script language="javascript">
var originWindowName=window.name;
window.name="logonAppPage";
function restoreWindow() {
try{
window.name=originWindowName;
} catch(ex){}
</script>
<script language="JavaScript">
function putFocus(formInst, elementInst) {
if (document.forms.length > 0) {
    document.forms[formInst].elements[elementInst].focus();
function setValuesAutoCreation() {
var form = document.getElementById('logonForm');
form.j_username.value="";
form.j_password.value="";
form.automaticAccountCreation.value="true";
function submitForm() {
var form = document.getElementById('logonForm');
form.submit();
function clearEntries() {
document.logonForm.longUid.value="";
document.logonForm.password.value="";
function setFocusToFirstField() {
myform = document.logonForm;
try{
   for (i=0; i<myform.length; i++) {
    elem = myform.elements[i];
    if (!elem.disabled) {
      elemType = elem.type;
      if (elemType=="text" || elemType=="password") {
       if (!elem.readOnly) {
          elem.focus();
          break;
      if (elemType=="select-one" || elemType=="select-multiple" || elemType=="checkbox" || elemType=="radio") {
        elem.focus();
        break;
} catch(ex){
function addTenantPrefix() {
return true;
</script>
</head>
<body class="urBdyStd" bgcolor="#F7F9FB" onLoad="setFocusToFirstField()" onUnload="restoreWindow()">
Thanks,
Darshan
<script language="JavaScript">
var blockPage = false;
</script>
<script language="JavaScript">
try {
if (top.document.domain != self.document.domain) {
blockPage = true;
} catch (error) {
// This will happen if the browser running the page tha"

Problem to clear JCo Cache of the MII Server

Hi All,
I am connecting SAP ERP 4.7 from MII 12.0.7 Build(20) .
Some R3 signature is changed during development and to get that new structure in BLS I called the following URL
http://<SERVER>:<PORT>/XMII/JCOProxy?Mode=Reset
This is supposed to clear the Server JCo cache. And it does that but after invoking this URL no one can log in to the server. Looks like connection to UME is broken.
FYI - In our landscape, R3 and MII are sharing same UME. So using same user id and password user can login to both the system.
The only solution for this problem is to restart the MII Server what I can see..
Any better solution from anybody?
Thanks,
Soumen

You don't say whether the admin link is in the HTML or part of the application, but I guess that you have seperate links in the HTML and somehow the login process is outside Flex?
If the login process was inside the Flex app, I would guess that there wouldn't be a problem.
The usual trick to force a reload of the page when navigating via a supplied link URL is to add a cachebuster string to make the signature of the URL differrent every time. Have a go with google and cachebuster.

Posting an XML Variable to a BLS Transaction from a web page

I am working in xMII 11.5 with all the latest service packs. I know this is probably a really basic question but I am stumped.
I am trying to pass a multi row and multi column XML data set from a web page into a BLS transaction (actually, two of them) in order to populate the parameter. I want to use the Web Service interface to the transaction. I have tried using parameters on an Xacute Query in an Applet as well with an equal lack of success. I cannot persuade the transaction to see the incoming variable as an XML data type. I have tried encoding and decoding and string to xml conversions and nothing seems to successfully allow the data set to be seen withing the BLS as anything but a string. The String to XML action will not handle the number of columns in the dataset though it seems to work if the data set has only one column. The data set is formatted in the proper "Rowsets/Rowset/Row" format. I have considered writing the data to an XML file on the server (I know I can deal with that) but that is not acceptable in this application.
Can someone share the secret with me?
...Sparks

Parameter value:
r1d1,r1d2,r1d3;r2d1,r2d2,r2d3;r3d1,r3d2,r3d2
Pass thru String List to Xml Parser with delim ";"
<Row>
<Item>r1d1,r1d2,r1d3</Item>
</Row>
<Row>
<Item>r2d1,r2d2,r2d3</Item>
</Row>
<Row>
<Item>r3d1,r3d2,r3d2</Item>
</Row>
Repeat on each row/item and pass thru String List to Xml Parser with delim ","
<Row>
<Item>r1d1</Item>
</Row>
<Row>
<Item>r1d2</Item>
</Row>
<Row>
<Item>r1d3</Item>
</Row>
Of course, your columns aren't flat but they are easy to ref, to get "column 2" for example:
StringListToXml_1.Output{/Rowsets/Rowset/Row[2]/Item}
So now you have rows and columns. Assign your data to your BAPI structured as needed.
We have passed complex XML via the SOAP interface in 11.5, but it involved some "hacks". Basically we passed the sterilized XML via a String Type Parameter, and then unserialized it inside the BLT.
I have been told on this board that there is a solution to passing XML data vie the SOAP interface using ref docs, but i have never personally seen a working example.

Upgrading a 10.3.2 portal application to 10.3.6 - server startup error

Hi,
I have upgraded from weblogic portal 10.3.2 to 10.3.6. I have followed the necessary steps required for this upgrade. However, I am facing issue in server startup after this. The stack trace reads :
Dec 10, 2013 5:13:11 AM EST> <Notice> <DeploymentRequestTimeoutLogger> <BEA-000000> <[DeploymentService:290051]The commit message for the deployment '1,386,670,091,597' could not be completed because the deployment timed out. : Targets to respond : [AdminServer]>
<Dec 10, 2013 5:13:11 AM EST> <Notice> <DeploymentRequestTimeoutLogger> <BEA-000000> <ThreadDumps on servers [AdminServer]{
ThreadDump for AdminServer<
"Store opaCache Spool Thread" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
net.sf.ehcache.store.DiskStore.spoolThreadMain(DiskStore.java:556)
net.sf.ehcache.store.DiskStore.access$600(DiskStore.java:59)
net.sf.ehcache.store.DiskStore$SpoolThread.run(DiskStore.java:990)
"Store userCache Expiry Thread" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
net.sf.ehcache.store.DiskStore.expiryThreadMain(DiskStore.java:831)
net.sf.ehcache.store.DiskStore.access$700(DiskStore.java:59)
net.sf.ehcache.store.DiskStore$ExpiryThread.run(DiskStore.java:1008)
"Store userCache Spool Thread" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
net.sf.ehcache.store.DiskStore.spoolThreadMain(DiskStore.java:556)
net.sf.ehcache.store.DiskStore.access$600(DiskStore.java:59)
net.sf.ehcache.store.DiskStore$SpoolThread.run(DiskStore.java:990)
"Timer-7" waiting for lock java.util.TaskQueue@13f02d4 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
java.util.TimerThread.mainLoop(Timer.java:483)
java.util.TimerThread.run(Timer.java:462)
"GC Daemon" waiting for lock sun.misc.GC$LatencyLock@1d2e34d TIMED_WAITING
java.lang.Object.wait(Native Method)
sun.misc.GC$Daemon.run(GC.java:100)
"Timer-6" waiting for lock java.util.TaskQueue@4910a9 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Timer-5" waiting for lock java.util.TaskQueue@e4fcbc TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Timer-4" waiting for lock java.util.TaskQueue@18ca55b TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@8c1627 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1b9a044 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1c21cbf WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@14a117f WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@59fb35 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@6de8b3 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@34ba01 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1216186 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@a1aeaa WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1e6f458 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@9e2d71 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock com.sun.jmx.remote.internal.ArrayNotificationBuffer@bc1d09 TIMED_WAITING
java.lang.Object.wait(Native Method)
com.sun.jmx.remote.internal.ArrayNotificationBuffer.fetchNotifications(ArrayNotificationBuffer.java:417)
com.sun.jmx.remote.internal.ArrayNotificationBuffer$ShareBuffer.fetchNotifications(ArrayNotificationBuffer.java:209)
com.sun.jmx.remote.internal.ServerNotifForwarder.fetchNotifs(ServerNotifForwarder.java:258)
javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1227)
javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1225)
java.security.AccessController.doPrivileged(Native Method)
javax.management.remote.rmi.RMIConnectionImpl.fetchNotifications(RMIConnectionImpl.java:1233)
javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
"[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
oracle.net.ns.Packet.receive(Packet.java:300)
oracle.net.ns.DataPacket.receive(DataPacket.java:106)
oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:315)
oracle.net.ns.NetInputStream.read(NetInputStream.java:260)
oracle.net.ns.NetInputStream.read(NetInputStream.java:185)
oracle.net.ns.NetInputStream.read(NetInputStream.java:102)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInputStreamWrapper.java:124)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWrapper.java:80)
oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1137)
oracle.jdbc.driver.T4CMAREngine.unmarshalCLR(T4CMAREngine.java:1755)
oracle.jdbc.driver.T4CMAREngine.unmarshalCLR(T4CMAREngine.java:1718)
oracle.jdbc.driver.T4CMAREngine.unmarshalCLR(T4CMAREngine.java:1711)
oracle.jdbc.driver.T4CVarcharAccessor.unmarshalOneRow(T4CVarcharAccessor.java:206)
oracle.jdbc.driver.T4CTTIrxd.unmarshal(T4CTTIrxd.java:933)
oracle.jdbc.driver.T4CTTIrxd.unmarshal(T4CTTIrxd.java:853)
oracle.jdbc.driver.T4C8Oall.readRXD(T4C8Oall.java:712)
oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:340)
oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:884)
oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167)
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289)
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3593)
oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3637)
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1495)
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1868)
weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
"[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@825b20 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock java.util.concurrent.CountDownLatch$Sync@164481 TIMED_WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:196)
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1011)
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1303)
java.util.concurrent.CountDownLatch.await(CountDownLatch.java:253)
weblogic.deploy.internal.targetserver.DeploymentManager.configCommitCompleted(DeploymentManager.java:664)
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commitCompleted(DeploymentServiceDispatcher.java:180)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCompletedCallback(DeploymentReceiverCallbackDeliverer.java:266)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$400(DeploymentReceiverCallbackDeliverer.java:13)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$5.run(DeploymentReceiverCallbackDeliverer.java:111)
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
"[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1feab6f WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"DynamicListenThread[Default[1]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[4]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[3]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[2]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[5]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[6]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"weblogic.GCMonitor" waiting for lock java.lang.ref.ReferenceQueue$Lock@1eb9726 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
weblogic.platform.GCMonitorThread.waitForNotification(GCMonitorThread.java:88)
weblogic.platform.GCMonitorThread.run(GCMonitorThread.java:64)
"[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@159fb5c WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"Thread-16" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@107f59 WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:676)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:751)
java.lang.Thread.run(Thread.java:662)
"[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE
sun.management.ThreadImpl.getThreadInfo1(Native Method)
sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:154)
weblogic.platform.VM15.threadDumpAsString(VM15.java:22)
weblogic.platform.VM.threadDumpAsString(VM.java:137)
weblogic.t3.srvr.JVMRuntime.getThreadStackDump(JVMRuntime.java:114)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:525)
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:666)
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
java.security.AccessController.doPrivileged(Native Method)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
weblogic.management.mbeanservers.internal.JMXContextInterceptor.getAttribute(JMXContextInterceptor.java:157)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
java.security.AccessController.doPrivileged(Native Method)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:299)
weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:279)
weblogic.management.mbeanservers.domainruntime.internal.ManagedMBeanServerConnection.getAttribute(ManagedMBeanServerConnection.java:304)
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:263)
weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:504)
weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:380)
$Proxy682.getThreadStackDump(Unknown Source)
weblogic.deploy.service.internal.adminserver.AdminRequestStatus.getThreadDumpsOnServers(AdminRequestStatus.java:2093)
weblogic.deploy.service.internal.adminserver.AdminRequestStatus.signalCommitFailed(AdminRequestStatus.java:1002)
weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCommitResponses.requestTimedOut(AwaitingCommitResponses.java:42)
weblogic.deploy.service.internal.adminserver.AdminRequestImpl.requestTimedout(AdminRequestImpl.java:354)
weblogic.deploy.service.internal.RequestImpl$TimeoutMonitor.timerExpired(RequestImpl.java:242)
weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
"[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@c0dc01 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1077c9d WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@46530 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"Thread-15" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@118c09b WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:676)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:751)
java.lang.Thread.run(Thread.java:662)
"Thread-14" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@d2abb WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:676)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:751)
java.lang.Thread.run(Thread.java:662)
"Thread-13" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@709ba4 WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:676)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:751)
java.lang.Thread.run(Thread.java:662)
"Timer-3" waiting for lock java.util.TaskQueue@fa3571 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Timer-2" waiting for lock java.util.TaskQueue@ca9d9a TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"DoSManager" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
com.octetstring.vde.DoSManager.run(DoSManager.java:433)
"VDE Transaction Processor Thread" waiting for lock com.octetstring.vde.backend.standard.TransactionProcessor@3108a4 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(TransactionProcessor.java:367)
com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:212)
"ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@57828d WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"weblogic.timers.TimerThread" waiting for lock weblogic.timers.internal.TimerThread@12e546b TIMED_WAITING
java.lang.Object.wait(Native Method)
weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:262)
"weblogic.time.TimeEventGenerator" waiting for lock weblogic.time.common.internal.TimeTable@a84182 TIMED_WAITING
java.lang.Object.wait(Native Method)
weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:286)
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:117)
java.lang.Thread.run(Thread.java:662)
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1ab5dae WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"Timer-1" waiting for lock java.util.TaskQueue@64def7 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Timer-0" waiting for lock java.util.TaskQueue@6a5ea5 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Attach Listener" RUNNABLE
null
"Signal Dispatcher" RUNNABLE
null
"Finalizer" waiting for lock java.lang.ref.ReferenceQueue$Lock@16bd831 WAITING
java.lang.Object.wait(Native Method)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" waiting for lock java.lang.ref.Reference$Lock@13e8914 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
"main" waiting for lock weblogic.t3.srvr.T3Srvr@99b1ec WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:981)
weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:490)
weblogic.Server.main(Server.java:71)
>
>
<Dec 10, 2013 5:13:11 AM EST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application xyz-ear'.>
<Dec 10, 2013 5:13:11 AM EST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
java.lang.Exception: [DeploymentService:290051]The commit message for the deployment '1,386,670,091,597' could not be completed because the deployment timed out.
at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.signalCommitFailed(AdminRequestStatus.java:1007)
at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCommitResponses.requestTimedOut(AwaitingCommitResponses.java:42)
at weblogic.deploy.service.internal.adminserver.AdminRequestImpl.requestTimedout(AdminRequestImpl.java:354)
at weblogic.deploy.service.internal.RequestImpl$TimeoutMonitor.timerExpired(RequestImpl.java:242)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
Truncated. see log file for complete stacktrace
>
java.lang.NullPointerException
at com.bea.p13n.jobmanager.config.JobManagerConfigHelper.shouldStartJobManager(JobManagerConfigHelper.java:124)
at com.bea.p13n.jobmanager.internal.JobManagerImpl.shouldStartJobManager(JobManagerImpl.java:1345)
at com.bea.p13n.jobmanager.internal.JobManagerImpl.getInstance(JobManagerImpl.java:624)
at com.bea.p13n.jobmanager.internal.JobServlet.init(JobServlet.java:30)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
WARN: The method class org.apache.commons.logging.impl.SLF4JLogFactory#release() was invoked.
WARN: Please see http://www.slf4j.org/codes.html#release for an explanation.
<Dec 10, 2013 5:14:24 AM EST> <Warning> <J2EE> <BEA-160181> <An error was encountered and ignored during undeployment. The error was: weblogic.utils.ErrorCollectionException:
There are 1 nested errors:
There are 11 nested errors:
java.lang.NullPointerException
at com.bea.wlw.runtime.descriptor.module.ConfigModuleFactory.deactivate(ConfigModuleFactory.java:185)
at weblogic.application.config.DefaultModule.deactivate(DefaultModule.java:319)
at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:677)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
Can anyone help on this ?
Thanks

Hi,
it seems that you try to deploy your application but it's taking a very long time that exceeds the timeout.
Are you deploying your application from Eclipse (oepe) or from the admin console ?
Emmanuel

Message bean does not start automatically during application server startup

I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                ... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                at java.lang.Class.getDeclaredConstructors0(Native Method)
                at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                at java.lang.Class.getConstructor0(Class.java:1930)
                at java.lang.Class.newInstance0(Class.java:278)
                at java.lang.Class.newInstance(Class.java:261)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                at java.security.AccessController.doPrivileged(Native Method)
                at javax.security.auth.Subject.doAs(Subject.java:379)
                at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve

Work Manager 6.0 for SMP 2.3 - standalone server - Startup Exceptions

Hello Experts.
I am installing a standalone Agentry Server for Work Manager 6.0 on the server where we have installed SMP 2.3.
It has been installed successfully and does start up, however I get some annoying error messages during start up.
It seems that the server is running - I can succesfully synchronize to an ATE client.
Due to the results from this thread, I have changed all ports in the Agentry.ini file to separate ports numbered 7521, 7522, 7523 and 7524.
Port issues - SMP and Agentry
Errors from the startup.log:
13:26:00 05/05/2014: HTTP-XML Back End Back End: Started
13:26:00 05/05/2014: Server: Starting threads.
13:26:00 05/05/2014: 1 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: Event: 20, 4, Server v6.1.0.3
13:26:00 05/05/2014: Starting front ends
13:26:00 05/05/2014: ANGEL Front End: Starting threads.
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: 3 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: ANGEL Front End: opening listen socket on port 7523
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 17, 10, 0.0.0.0:7523 open
13:26:00 05/05/2014: Event: 17, 10, ANGEL Front End v6.1.0.3
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 0, 0, Old log files moved into Logs-Rolled\2014-05-05-132546
13:26:00 05/05/2014: Event: 0, 23, 4
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:01 05/05/2014: Event: 0, 2, Server startup is complete.
13:26:01 05/05/2014: Agentry Application startup complete
Can anybody help with the meaning and implications of these errors ?
Thank you.
Søren Hansen.

Damn... I missed one port
You are correct. The default port (8282) of Agentry is used multiple places in the Agentry.ini file, and collides with SMP.
Thanks Steve.
For others:
Please make sure the following ports of the Agentry.ini file are unique across all applications on the server. In this case I have chosen to call all my ports on this instance 752X.
Now the server starts without errors.
[ANGEL Front End Ports]
1=7523
[TCP Front End]
listenOn=7521
[Java-1]
nonStandardJavaOptions=-Xdebug -Xrunjdwp:transport=dt_socket,address=7524,server=y,suspend=n
[HTTPXML-2]
baseURL=http://localhost:7522
listenOn=7525
Søren Hansen.

Read Idoc Data In xMII 12 BLS Transaction

Hi All,
I am new to xMII.
I followed the instructions suggested in the Document "How to Send an IDoc from the SAP R/3 Enterprise to the SAP xMII IDoc Listener" By Diana Hoppe and Michael Appleby written on 04 Dec 2008. It was pretty simple and i was able to complete all the steps.
In the Message Monitor in xMII 12.0 i am able to see " 5 Messags Found" and they are listed below in a grild with the server name, Message Name, Message Type etc
Example
Server Name Message Type Message Name Message Category Received Time Processing Time
MII_IDOC IDoc LOIPRO01 MII_IDOC 2009-07-10 02:11:25.911
Now i would like to know how do i read the contents of this IDOC i.e Production order? Is there a sample or stepby step guide which explains how i can get this data into an xML message in a BLS Transaction?
Are there any simple steps to be followed to get this data from the IDOC?
Please help me undestand this. Thanks in advance.
Regards
Suraj Prabhu

Hi Dipankar,
I had Pre ordered your book and I just received a copy. The first impression wrt the Contents & Coverage of the book looks excellent.
Congratulations to you and Abesh on this achievement. Writing a book on a topic which there has been no book written earlier is a great feat on its own.
Will be spending more time with the book today evening.
My Expectations from this book:
1. A good intermediate to Expert developer/ BA / Architect guidance.
2. Error Handling & Implementation - Best practices
3. A Reference book for the current implementation I am doing with a customer :).
Will keep you updated with my comments on the book. Since this is a first time I am working on a xMII implementation this book will be a life saver for me and could not have come at a better time. Thanks again.
BTW u2013 First thing I checked in the book was steps on how to read the data from the IDOC in the Buffer and that has been explained pretty well and in detailsu2026.. Thanks again for that.
Regards
Suraj Prabhu

RRI not working for calling up transaction BI admin cockpit

Hi,
We have implemented BI admin cockpit and all technical contents and settings are OK, but when we try to navigate to call any transaction (Monitor, Process status TCode ST22, RSA1, RSMO, RSPC etc) by calling RRI than instead of getting the desired transaction screen we are getting the SAP Easy Access screen. Although we can navigate to Second level web template thru RRI and if we define target system other that BI (i.e. ECC or CRM) than we are able to navigate any transaction transaction i.e. SE38 or SE37 etc,
Any suggestion or help would be appriciated.
thanks
Dev

Hi Sunny,
as per your reply i have check the BI usage types using that URL.
And the below is the result.
Information about Active Usage Types
Active Usage Types
Product                     UT Code      Short Name      Description
NetWeaver                  BI                  BI Java      BI Java
NetWeaver                 AS                 AS Java      Application Server Java
NetWeaver                  DI                          DI      Development Infrastructure
NetWeaver                 EPC                      EP Core      Enterprise Portal Core Components
NetWeaver                     EP                           EP      Enterprise Portal
Can you please help.
Thanks
AS

Pending message redelivery wait period after server startup

Hi, I have seen an strange behaviour in the way pending JMS messages are
          redelivered to MDBs at server startup.
          In my unit test I have seen that, killing Weblogic during an MDB code
          execution as expected makes the container to redelivery unconfirmed message
          at server startup. I have also seen that it's redelivered about 4 minutes
          after server is started (more info of this in thread: "Problem with
          persistent messages and MDBs" 25 October 2002)
          After a recent crash we have had on the system in wich there were a lot of
          messages pending to deliver to an MDB we saw that they were being
          redelivered just after the MDBs were deployed while system was starting. Of
          course due to the fact that some components needed by the MDB were not
          deployed by that time, a lot of exceptions were raised making messages to be
          queued again and promptly delivered wich caused more exceptions. Just a big
          mess!
          I'm tring to figure a good work-around about this, what I wanted to know is
          how is implemented the "delay" to send messages after server startup. Is it
          done by comparing timestamp of message (when did it enter the queue and
          thereby persisted on the store) with current system time?. That approach of
          course will fail if any of the messages were sent before that "delay" time.
          If this is the case and there isn't a fix for it this is what I have in
          mind:
          Each MDB will have a private attribute wich will be used to detect when
          system has completely started. By default it will be false and after a
          message is sent to the MDB the first line of the onMessage method will test
          wether system has started or not (by checking weblogic connection port i.e.
          7001. Btw. is there any better way of checking server has finished start-up)
          if not, a runtime exception will be launched that will force message to be
          redelivered (without trying to execute any MDB code), I think setting a
          proper redelivery delay i.e. 30-60 secs. will allow server to startup with
          less problems (in the situation I described above JVM crashed with an 11
          system signal)
          Any other ideas to deal with this?
          Thanks in advance.
          Regards.
          Ignacio.


Hi Ignacio,
          I think you can usually control the order in which ejb's are booted,
          through a combination of console settings and
          meta file entries. I suggest posting to the ejb newsgroup
          to find out how.
          The four minute delay you see is normal for resolving
          interrupted transactions, but I believe that an enhancement
          was put into a 7.0 SP to reduce or eliminate this interval,
          and that 8.1 has no interval. Post to the transaction
          newsgroup for more info, or contact customer support.
          Given that you referenced earlier posts on this issue, you
          probably already know how to tune the interval down to one
          minute even without the enhancements.
          There is no other delay for sending messages at system startup,
          as soon as the MDB is booted it attaches to JMS, and JMS
          starts delivering messages whose transactional state is known.
          Tom
          P.S. I suppose one way to detect end-of-boot is to
          place a startup class last in the boot order.
          P.P.S. For MDBs one alternative is to code a "sleep" in the onMessage if
          an unavailable resource is detected - this
          is hokey, but works as long as you have made sure that
          max-beans-in-free-pool totals do not come near or exceed
          available thread pool size.
          Ignacio G. Dupont wrote:
          > Hi, I have seen an strange behaviour in the way pending JMS messages are
          > redelivered to MDBs at server startup.
          >
          > In my unit test I have seen that, killing Weblogic during an MDB code
          > execution as expected makes the container to redelivery unconfirmed message
          > at server startup. I have also seen that it's redelivered about 4 minutes
          > after server is started (more info of this in thread: "Problem with
          > persistent messages and MDBs" 25 October 2002)
          >
          > After a recent crash we have had on the system in wich there were a lot of
          > messages pending to deliver to an MDB we saw that they were being
          > redelivered just after the MDBs were deployed while system was starting. Of
          > course due to the fact that some components needed by the MDB were not
          > deployed by that time, a lot of exceptions were raised making messages to be
          > queued again and promptly delivered wich caused more exceptions. Just a big
          > mess!
          >
          > I'm tring to figure a good work-around about this, what I wanted to know is
          > how is implemented the "delay" to send messages after server startup. Is it
          > done by comparing timestamp of message (when did it enter the queue and
          > thereby persisted on the store) with current system time?. That approach of
          > course will fail if any of the messages were sent before that "delay" time.
          >
          > If this is the case and there isn't a fix for it this is what I have in
          > mind:
          >
          > Each MDB will have a private attribute wich will be used to detect when
          > system has completely started. By default it will be false and after a
          > message is sent to the MDB the first line of the onMessage method will test
          > wether system has started or not (by checking weblogic connection port i.e.
          > 7001. Btw. is there any better way of checking server has finished start-up)
          > if not, a runtime exception will be launched that will force message to be
          > redelivered (without trying to execute any MDB code), I think setting a
          > proper redelivery delay i.e. 30-60 secs. will allow server to startup with
          > less problems (in the situation I described above JVM crashed with an 11
          > system signal)
          >
          > Any other ideas to deal with this?
          >
          > Thanks in advance.
          >
          > Regards.
          >
          > Ignacio.
          >
          >

Calling bls transaction on MII server startup

Similar Messages

Maybe you are looking for