CWLMS DFM root cause functionality.

According to the CWLMS Deployment Guide 3.0:
"Device Fault Manager provides the ability to monitor device faults in real-time and determine the root cause by correlating device-level fault conditions."
Can anyone explain in a little more detail exactly how this works, and how the "root cause" event and it's "symptom events" are displayed in the DFM?
Does it use the same "Codebook Correlation Technology" that is used in EMC Smarts?

just a comment...
DFM ... it has its own story .....
DFM 1.2 was really good (at least compared to DFM 2.0+). It has had a GUI where you did see correlated alarms in different colors on a split window and a good classification of the alarm. DFM 2.0+ is an awful castrated version of the original. If you look at the code DFM has its own mechanism to discover the network to know the topology. It does not need any other application to know this - but it is not used in LMS. It has mechanisms to correlate events - but they are not implemented.
I would like to know who made the decission to code something like this (and I would realy like to discuss it...)
1) try to reach EVERY IP address a device has with ICMP (BY DEFAULT !!)
and need a couple of time to implement a script to remove this again
2) REMOVE the feature to start a script based on an event, - just allow email and trap-forwarding
[if anbody was successfull in registering the script notifier again it would be great to share this information...]
3) show up these very special alarmIDs in the GUI and provide them on the device center GUI (Device Alert Identifier) without making it a link to the "Alerts and Activities Detail" Page
4) do not provide the posibility to add a specific trap as a customized event
5) do not show detailed information in "Detailed Device View" if a device is in an unknown state - this could be interesting for troubleshooting..
... and there are a few more ...

Similar Messages

Issue Root Cause Question - WebIntelligenceProcessingServer

Hi,
Yesterday our SAP BI based portal server suffered a dramatic decrease of perfomance that prevented reports to be viewed (users were able to login into portal, but when clicked on a given report it showed the clock progress bar with no results..) . We finally decided to restart all the servers in order to try to workaround the situation. Luckily it works but I am focused in trying to understand what cause the issue.
We have been reviewing the performance counters of all involved servers (CPU, Memory consumption) duing the period of time when the issue appeared and we don't find any quick explanation. Our more intersting clue are the info contained in the BO server tace files (*.glf files) , and particularly the WebIntelligenceProcessingServer trace.
At the time of the issue (and several minutes before) the next list of errors were triggered repeteadly
**ERROR:cdzContext:ExtensionManagementException has been raised [cdzContext.cpp;1193]
**ERROR:cdzContext:All the servers with CMS es-w08-bient1:6400, cluster @es-w08-bient1.f4e.org:6400, kind pjs which host service DSLBridge, are down or disabled [cdzContext.cpp;1194]
**ERROR:DSLBridgeController:BrigdeController::getDslBridge : the IExtension reference is null [src/DSLBrigdeController.cpp;157]
**ERROR:DSLBridgeController:Error: Failed to load SL Service extension
I suspect that we have some configuration issue related with the WebIntelligenceProcessingServer but by reviewing the data provided by the monitoring application (Memory max threshould count,....) we don't see which would be the cause of the stuff.
Any idea? Thanks for sharing your thoughs.
Alfons

Hello Alfons,
Finding root cause of the issue is really a part of investigation as there are many other components/areas we need to consider/review before we comment anything on your issue.
However, here are some practices we need to follow for better performace.
It's recommended to have Web Intelligence servers recycle. There are two settings that are used in this functionality. The Web Intelligence server is recycled when BOTH conditions are met.
Maximum Documents Before Recycling: default is 50. Range is 10 - 1000.
Timeout Before Recycling (seconds): default is 1200. Range is 100 - 10000.
In addition to this, kindly tune your WIPS as reccomended by SAP. For more information, please go through below blog:
http://scn.sap.com/people/matthew.shaw/blog/2011/04/06/performance-tips-getting-the-most-out-of-your-web-intelligence-processing-servers
Hope this will help.
Regards,
Mahesh

How do I find the root cause of a NetConnection closed event?

Hi,
I am maintaining a large project developed in Flex/Actionscript.
The application is using tunneling (RTMPT), and we often get Netconnection "closed" events.
There is no problem with the physical network.
I think the event may be caused by either a TCP/HTTP/RTMP event, or may be caused by
some function in the client calling close() on the connection.
How can I find the root cause of the "closed" event being thrown?
Thanks,
David

Thanks for the information. It is helpful but it seems there must be a specification of
what the client side is expecting, independent of any server implementation.
When I say client side, I mean the Adobe communication libraries.
Where is the specification or source code for how the client libraries treat HTTP tunneled requests and responses?
One question in particular: How does the client side library treat a
Connection: Keep-Alive
versuse
Connection:close
HTTP header setting?

E2E Root cause analysis in solution manager

Hi
How to add the E2E root cause analysis, the new functionality in solution manager 4.0 with the E2E root cause analysis functionality does it require support pack which level of SP required to use the new functionaltiy
Regards
Dinaker vikas

Hi,
If you have PI system in your landscape, I would strongly recommend to upgrade to SP15.
Trace monitoring for PI is to be available from SP17 (Not yet released)
Check [this Link.|http://service.sap.com/e2e].
Hope this solves your problem.
Feel free to revert back.
--Ragu

What is the diff of Solution monitoring and E2E Root cause analysis

Hi,
I want to know what is the different for Solution Manager Solution Monitoring and End to End root cause analysis. Currently we have implemented change management and Implementing and Upgrading SAP Solutions, if i would like to explore the solution monitoring, and end to end root cause analysis, what is the steps of configuration i need?
if i would like to have a check on the system whether is performing well, or setup the functionality of sending alert when system is having problem, which feature would be better? end of end functionality or Solution Monitoring?
Please advice..
thanks
-Fung

Hi,
If you have PI system in your landscape, I would strongly recommend to upgrade to SP15.
Trace monitoring for PI is to be available from SP17 (Not yet released)
Check [this Link.|http://service.sap.com/e2e].
Hope this solves your problem.
Feel free to revert back.
--Ragu

Root cause of ServletException.javax.servlet.jsp.JspException:

Hi guys, hope you all can help me on this.
I have added this repeater netui tag into my jsp page and always get this servletException
error, not very sure why. when i remove this repeater tag everything seems alright.
anyone can give me any hints or clue on this? the checkbox repeater tag is wrong,
i need to ask you guys on that the next posting! thanks!
The Repeater tag in my jsp
<netui-data:callPageFlow method="getFunctionHashtable" resultId="funcNamehashtable"/>
<netui-data:repeater dataSource="{actionForm.functionHashtable}">
<netui-data:repeaterHeader>
<table border="1">
<tr>
<td><b>Functions</b></td>
<td><b>Assign/Unassign</b></td>
</tr>
</netui-data:repeaterHeader>
<netui-data:repeaterItem>
<tr>
<td>
<netui:label value="{container.item}" />
</td>
<td>
<netui:checkBox dataSource="{pageFlow.initchecked}" onClick="checkFunctions();"/>
</td>
</tr>
</netui-data:repeaterItem>
<netui-data:repeaterFooter>
</table>
</netui-data:repeaterFooter>
</netui-data:repeater>
and here's the exception error i have got.
id=16240211,name=RapidWeb,context-path=/RapidWeb)] Root cause of ServletExceptio
n.
javax.servlet.jsp.JspException: Input/output error: java.net.SocketException:
Co
nnection reset by peer: socket write error
at org.apache.struts.util.ResponseUtils.write(ResponseUtils.java:160)
at com.bea.wlw.netui.tags.html.Html.doEndTag(Html.java:282)
at jsp_servlet._assignunassignfunctions.__getrole._jspService(getRole.js
p:78)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:402)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
va:27)
at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilt

Hi
The message java.net.SocketException: Connection reset by peer is caused by network problem or even forced closure of IE browser.
This should not affect functionality and is harmless.
If the page process is too long, the user closed the browser or the user reloaded the page, this error could happen. Reloading a page or closing the browser is very common, and so we should not log this message.
BEA has a known issue CR219602 where we catch the SocketException and ignore the logging in the doEndTag() method.
If this error message is annonying please contact BEA Support to get a patch.
Thanks
Vimala

From which table feed back partner and root cause partner

hi,
can any body tell me ,from which table feed back partner and root cause partner
can be find.
i need to add this in datasource 0crm_sales_act_1.
thanks in advance.
regards,
sridhar M

It is always advsible to use function modules in CRM instead of making direct table access. Unlike R/3, CRM tables and buffering are quite complex.
In your case, to read the values of maintained Sales Areas, use the function module <h5>CRMA_BUPA_GET_SALES_AREAS</h5>
The function module takes the BP Guid (BUT000-PARTNER_GUID)
However you can also find your information in tables<h5>
CRMM_BUT_LNK0011 - BP Sales rule list
CRMM_BUT_LNK0010 - BP Sales rule list
CRMM_BUT_SET0010 - BP Sales rule set</h5>
Hope this helps.
Easwar Ram
http://www.parxlns.com

Tools for root cause analysis of stack corruption?

I'm experiencing extremely rare stack corruption that results in SEGV core dumps for a large and complex C++ program. Having run all the standard tools such as IBM Rational Purify, Sun mdb/libumem and dbx/rtc (although unfortunately using dbx check -access takes inordinately long and eventually crashes before the main() function is executed), I am no closer to discovering the root cause of the stack corruption. I'm confident based on the tools run and on the stack trace from the core dump that the problem is not heap corruption, but stack corruption.
The environment is Sun Studio 12 (but not update 1) on Solaris 10 on SPARC. The program is compiled with minor optimisation (-xO2 -xbuiltin=%all).
Is anyone aware of other tools or approaches that could help pinpoint the problem? Your help would be much appreciated!
Thanks in advance,
Simon

If you are in fact having stack corruption issues, I don't think any of the tools you mentioned other than Purify would help you identify it.
You may also be simply running out of stack space, and not having corruption issues. Is your app multi-threaded? If so, you could increase the stack size your threads use to something larger than the default.
Another thing you can look for are syslog entries stating "no swap space to grow stack" for your process, you've run out of virtual memory. To avoid this, you can "pre-allocate" your stack memory with code similar to this:
void growStack( size_t bytes )
    char *mem = ( char * ) alloca( bytes );
    memset( mem, 0, bytes );
    return;
}That code, when called, will force the creation of stack memory virtual pages backed by swap, before your server gets into a situation where free memory might be in short supply.
I also seem to recall that Solaris under certain circumstances will allocate stack memory with the MAP_NORESERVE option, which means swap space won't be reserved for your stack. If your process gets swapped out, its stack(s) will be lost and you'll probably get a SIGSEGV or SIGBUS. See this bug:
[http://bugs.opensolaris.org/view_bug.do?bug_id=1221729|http://bugs.opensolaris.org/view_bug.do?bug_id=1221729]
I remember working a similar issue for a customer running large apps on Sun E15Ks, maybe about 5 years ago. To work around this behavoir, I think you'll need to explicitly allocate stack memory for any threads you may be creating. I think that's what we had to do.

Root cause for delivery to show up on LX47 transaction

All,
I am new to SAP and supporting an off site warehouse location. I'm trying to research and locate the root cause for why a delivery shows up on LX47.
The situation the warehouse is experiencing is that they are having to run the LX47 transaction multiple times a day to correct delivery issues.
I know from my initial research that deliveries show up on LX47 due to the OB Delivery being blocked, and that this is caused by the OB delivery and related Transfer Orders do not match in the system.
What I'm trying to figure out is, from an Operations standpoint, what is causing the OB Delivery and the TO's not to match?
Is there only 1 reason? Are there 100? This is what I'm trying to understand.
The only thing I have found thus far is that 2 people/transactions are in the delivery at the time of the update. Is this accurate?

Hi Nicholas,
I am sure you are very much aware about the process flow however i just want to narrate again, if the plant and storage location is WM managed then you generally create a transfer order with reference to the delivery document to perform the picking process now at the time of confirmation of the transfer order you can update the Delivery immediately (Standard SAP) or you can set the indicator to delay the delivery update(Check the below mentioned screen and IMG path).if you choose to delay the delivery update those delivery will appear in the LX47 and you have the provision to manually update the Delivery from there. (Apart from the above mentioned there are some instance where after confirmation of the transfer order and in between updating the delivery either material master / Batch master / or some other relevant parameter is in edit mode or locked which cause failure to update the delivery immediately and you will find those delivery will also appear in the LX47)
Hope this will help to get some idea about LX47 and reason for delivery whose appear in the LX47
SPRO PATH
SPRO---Logistic Execution---Warehouse management ---Shipping ----Define Shipping control -- Shipping control per warehouse

Need to find the root cause of the XML Publisher report erroring out.

Hello All,
After I ran for a Particular Invoice, to have output in XML Publisher Report for Invoice Priting. It got errored out with the below details which i got from the OPP Log file.
From the below information, how do I get exact root cause. Please do the needful.
=======================================================================
[8/6/09 11:16:32 AM] [774712:RT14922832] Executing post-processing actions for request 14922832.
[8/6/09 11:16:32 AM] [774712:RT14922832] Starting XML Publisher post-processing action.
[8/6/09 11:16:32 AM] [774712:RT14922832]
Template code: XXBIORAXINV_PHY
Template app: BIO_AR
Language: en
Territory: 00
Output type: PDF
[8/6/09 11:16:33 AM] [UNEXPECTED] [774712:RT14922832] java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at oracle.apps.xdo.common.xml.XSLT10gR1.invokeParse(XSLT10gR1.java:517)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:224)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:177)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1044)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:997)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
     at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1657)
     at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:967)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5888)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3438)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3527)
     at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:229)
     at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:153)
Caused by: oracle.xdo.parser.v2.XMLParseException: Unexpected EOF.
     at oracle.xdo.parser.v2.XMLError.flushErrors1(XMLError.java:324)
     at oracle.xdo.parser.v2.XMLReader.popXMLReader(XMLReader.java:526)
     at oracle.xdo.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1287)
     at oracle.xdo.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:314)
     at oracle.xdo.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:281)
     at oracle.xdo.parser.v2.XMLParser.parse(XMLParser.java:266)
     ... 17 more
[8/6/09 11:16:33 AM] [774712:RT14922832] Completed post-processing actions for request 14922832.
=======================================================================
Please do the needful. Suggest the steps to get rid of this critical - issue.
Thanks,
Abdul

Please check if Output Post Processor concurrent manager is down/ inactive.
Restart the manager/ get it restarted and test the issue.
System Admin >> Concurrent >> Manager >> Administer

Oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25058. Error message parameters

Dear Guru's,
I am not able to solve the above issue for last couple of days.
I am newbie to the webservice
My Issue...
I am using Jdeveloper 11.1.2.4.0 Release 2
1. Using Jdev I built one small Web Service with two methods.
        While testing the Webservice...
               I passed User Id as Parameter and it successfully return the values (user id, user name and description) from fnd_user table
2. I created another application to consume the web service i created.
               1. I added the webservice SOAP and added the method.
               2. Created a jsf page and drag and drop the parameter and return values to the jsf page.
3. While executing the created jsf page I received the error message as below
"oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25058. Error message parameters are {0=Attribute, 1=UserName, 2=UserName}"
Even I know that this issue is repeated one in our forum, I was not able to solve this issue.
Can anybody help to solve this issue.
Thanks and Regards,
Durai S E

Dear Guru's,
I am not able to solve the above issue for last couple of days.
I am newbie to the webservice
My Issue...
I am using Jdeveloper 11.1.2.4.0 Release 2
1. Using Jdev I built one small Web Service with two methods.
        While testing the Webservice...
               I passed User Id as Parameter and it successfully return the values (user id, user name and description) from fnd_user table
2. I created another application to consume the web service i created.
               1. I added the webservice SOAP and added the method.
               2. Created a jsf page and drag and drop the parameter and return values to the jsf page.
3. While executing the created jsf page I received the error message as below
"oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25058. Error message parameters are {0=Attribute, 1=UserName, 2=UserName}"
Even I know that this issue is repeated one in our forum, I was not able to solve this issue.
Can anybody help to solve this issue.
Thanks and Regards,
Durai S E

Render Service Problem - Root Cause ALC-DSC-127-000

I have decided to write a Form Guide renderer instead of using one from the Samples. The renderer process was created by carefully observing the one in the samples. After creating the renderer, I activated it and used it in my process. In the livecycle workspace, when I try to access the initialization task, A popup error shows up. Looking at the logs revealed the following error/exception:
exception: flex.messaging.MessageException: ALC-WKS-005-028: A problem occurred in the Render Service. Please review the render orchestration for this process.
2007-12-26 13:34:23,190 INFO [STDOUT] [Flex] Exception when invoking service: remoting-service
with message: Flex Message (flex.messaging.messages.RemotingMessage)
operation = render
clientId = 60F1A10E-C009-251A-6C47-179779FEB2B7
destination = task-actions
messageId = F65756D8-8D22-85D3-598E-17BBDA529B7E
timestamp = 1198694062784
timeToLive = 1198694062784
body = null
hdr(DSEndpoint) = workspace-polling-amf
hdr(DSId) = 60F1373F-590F-5AC8-B6A5-1296C747EA45
exception: flex.messaging.MessageException: ALC-WKS-005-028: A problem occurred in the Render Service. Please review the render orchestration for this process.
2007-12-26 13:34:23,377 INFO [STDOUT] [Flex] [ERROR] Root cause: ALC-DSC-127-000: com.adobe.idp.dsc.LongLivedInvocationException: The Long Lived Service i3Renderer can not be invoked synchronously.
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:76)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:88)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:21 0)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.idp.taskmanager.dsc.service.TaskManagerServiceImpl.renderForm(TaskManagerServic eImpl.java:3404)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:181)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:134)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:336)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew (EjbTransactionCMTAdapterBean.java:282)
at sun.reflect.GeneratedMethodAccessor258.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:214)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:149)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:154)
at org.jboss.webservice.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor. java:54)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:

Hi Gary,
I am getting following error message, can you pls help me with this
Mar 26, 2008 5:25:53 PM com.adobe.workspace.processes.ProcessActions getProcessInstance
WARNING: ALC-WKS-005-059: An error occurred while retrieving the list of process instances for process "Process Packages".
[Flex] Exception when invoking service: remoting-service
with message: Flex Message (flex.messaging.messages.RemotingMessage)
operation = getProcessInstance
clientId = DA923519-C11F-EDFE-A537-D10A27A3FA00
destination = process-actions
messageId = A9726928-7AEA-8308-B7C4-ECFB90EFA472
timestamp = 1206566753361
timeToLive = 1206566753361
body = null
hdr(DSEndpoint) = workspace-polling-amf
hdr(DSId) = DA8DF62D-CD1E-2718-618C-0902E3DF178A
exception: flex.messaging.MessageException: ALC-WKS-005-059: An error occurred while retrieving the list of process instances for process "Process Packages".
[Flex] [ERROR] Exception when invoking service: remoting-service
with message: Flex Message (flex.messaging.messages.RemotingMessage)
operation = getProcessInstance
clientId = DA923519-C11F-EDFE-A537-D10A27A3FA00
destination = process-actions
messageId = A9726928-7AEA-8308-B7C4-ECFB90EFA472
timestamp = 1206566753361
timeToLive = 1206566753361
body = null
hdr(DSEndpoint) = workspace-polling-amf
hdr(DSId) = DA8DF62D-CD1E-2718-618C-0902E3DF178A
exception: flex.messaging.MessageException: ALC-WKS-005-059: An error occurred while retrieving the list of process instances for process "Process Packages".
[Flex] Root cause: com.adobe.idp.taskmanager.dsc.client.query.TaskQueryServiceException: com.adobe.pof.schema.AttributeNotFoundException: Attribute: creator_id does not exist on object-type: workflow.pt_process packages.
at com.adobe.idp.taskmanager.dsc.queryservice.TaskManagerQueryServiceImpl.processSearch(Task ManagerQueryServiceImpl.java:730)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:181)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:134)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:336)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(Ej bTransactionCMTAdapterBean.java:212)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapter_z73hg_ELOImpl.doS upports(EjbTransactionCMTAdapter_z73hg_ELOImpl.java:67)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:104)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:80)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:113)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:102)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:88)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:18 3)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.idp.taskmanager.dsc.client.TypedTaskManagerQueryService.processSearch(TypedTask ManagerQueryService.java:245)
at com.adobe.workspace.processes.ProcessActions.getProcessInstance(ProcessActions.java:174)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
Caused by: com.adobe.pof.schema.AttributeNotFoundException: Attribute: creator_id does not exist on object-type: workflow.pt_process packages.
at com.adobe.pof.schema.POFAbstractObjectType.getAttribute(POFAbstractObjectType.java:177)
at com.adobe.pof.omapi.POFDefaultQuery.projectAttribute(POFDefaultQuery.java:634)
at com.adobe.idp.taskmanager.dsc.queryservice.TaskManagerQueryServiceImpl.processSearch(Task ManagerQueryServiceImpl.java:627)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:181)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:134)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:336)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(Ej bTransactionCMTAdapterBean.java:212)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapter_z73hg_ELOImpl.doS upports(EjbTransactionCMTAdapter_z73hg_ELOImpl.java:67)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:104)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:80)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:113)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:102)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:88)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:18 3)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.idp.taskmanager.dsc.client.TypedTaskManagerQueryService.processSearch(TypedTask ManagerQueryService.java:245)
at com.adobe.workspace.processes.ProcessActions.getProcessInstance(ProcessActions.java:174)
[Flex] [ERROR] Root cause: com.adobe.idp.taskmanager.dsc.client.query.TaskQueryServiceException: com.adobe.pof.schema.AttributeNotFoundException: Attribute: creator_id does not exist on object-type: workflow.pt_process packages.
at com.adobe.idp.taskmanager.dsc.queryservice.TaskManagerQueryServiceImpl.processSearch(Task ManagerQueryServiceImpl.java:730)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.ad

Root Cause Analysis - Breakpoints in ABAP

Gurus ,
We had this breakpoints in the ECC - datasource extractors which got transported in the production and I have been given the task to identify the root cause analysis as to why was it not caught in dev,qa and testing.
can any one share their experience as to how to avoid this negligence and the additional steps required to ensure this does not happen again ?
Thanks in advance

Hi,
To identify the break points and avoid the transport of breakpoints. U can run the extended program check and there you can find in EPC error in superfluous statements the break points present in ur report.
Regards,
Vasanth

Root Cause Analysis (OS and DB - OS Command Console) Connection problem!

Dear Community,
i've got a problem with the Root Cause Analysis OS Command console!
Currently I try to read the System MemStat info from the console, without success!
I've got the following errors:
Error1:
Error to parse the data returns by 'SAPOSCol', cause :com.sap.smd.plugin.remoteos.exception.SAPOSColDataParserException: Unknown Error during the parsing of saposcol output; nested exception is:
java.lang.NullPointerException
Error2:
'SAPOSCol' Service not availbale, detail :com.sap.smd.plugin.remoteos.exception.SAPOScolNotAvailable: SAPOSCol not available (detail output: )
The saposcol service is running, when I look on the server, I've got the correct status:
server:<sid>adm> saposcol -s
Collector Versions :
running : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux
dialog : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16
Shared Memory       : attached
Number of records   : 5758
Active Flag         : active (01)
Operating System    : Linux server 2.6.5-7.283-smp #1 SMP Wed Nov 29
Collector PID       : 9536 (00002540)
Collector           : running
Start time coll.    : Wed Apr 23 15:00:58 2008
Current Time        : Wed Apr 23 15:12:08 2008
Last write access   : Wed Apr 23 15:12:04 2008
Last Read Access   : Wed Apr 23 15:12:03 2008
Collection Interval : 10 sec (next delay).
Collection Interval : 10 sec (last ).
Status              : free
Collect Details     : required
Refresh             : required
Header Extention Structure
Number of x-header      Records : 1
Number of Communication Records : 60
Number of free Com.     Records : 60
Resulting offset to 1.data rec. : 61
Trace level             : 2
Collector in IDLE - mode ? : NO
become idle after 300 sec without read access.
Length of Idle Interval : 60 sec
Length of norm.Interval : 10 sec
The strange thing is, sometimes it works, sometimes not!
Any Ideas?
System: Solution Manager 4.0 SP Stack 13
Thanks and regards
Sascha

>   running : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux
>   dialog : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16
I suggest you upgrade your saposcol on the Linux box, it's more than a year old and it's possible, that the SMD client needs a newer version that provides the data you're requesting.
Markus

Javax.servlet.servletException and root cause error(how to solve?)

Hi! ALL,
I have created a enterprise application using netbeans IDE , j2ee and jboss server.Now I want to run that enterprise application in remote server as jboss.I have uploaded that application in remote server.I am running in this way
http://IP Address/CustomerBook2-war/CustomerDetail.

Read the exception message of the root cause. If you don't understand the message, copypaste that message in Google and check the results.

CWLMS DFM root cause functionality.

Similar Messages

Maybe you are looking for