Workflow instance number = 0000000000, and no log..??

Hi Workflowers
I have a situation where my workflow has been triggered (by an event from a business object - ZBUS2032 - extending BUS2032) but the workflow appears to be frozen in a 'START' status, and goes nowhere..
I am using SWI1 to list work items: the instance number shows as 000000000000, the start date and time are zero, the 'Started by' field is blank, etc. No log can be viewed, but I do have a Work Item number. It must be specifically related to this workflow, because other WS tasks are running OK.
If I click on the instance number, I get the message
<i>Work Item 000000000000 cannot be read.</i>
Any advice on what might be causing this..?

Hi TB,
are you creating an event through SWUE or so ?
by directly testing the ZBUS2032 ?
In that case it would ask for an instance number, have you mentioned any of the salesorder number there ?
Create a salesorder and see whether your WF triggers.
Aditya

Similar Messages

BPM an Mapping: Get the workflow instance number?

Hi everybody,
wen need in some cases the message-ID that was generated in message-mapping.
But when I take this message-ID and try to find it via SXMB_MONI the message could'nt be found due to reasons I do not know.
So now I would like to capture the BPM instance number. Is this possible in message-mapping?
Thanks regards
Mario

I doubt you would be able to get the BPM instance no. However, I don't understand why u r facing problem with message ID.
Regards,
Prateek

What instance number and config set number am I supposed to use for ODISRV?

I'm trying to get one way sync working from ADS to OID using the OID that comes with Collaboration Suite 10.1.2 on Windows. The sync works fine if I run it manually (I forget the command I used for that). I can see user accounts show up in the DIT. The problem is that the sync never happens on a scheduled basis and it looks like it is due to ODISRV not running even after I did what the docs said and attempted to start it. It started with no errors but I guess the log file contained all the actual errors.
The docs say to specify an instance number > 0 and a config set. Well, it's clear as mud as to which number to actually use. I assmed the configset value happened to match the nubmer in the Directory Manager GUI under the Integration Server entry (which was configset1 for me). I've tried to specify 1 2 and 3 for the instance numbers and I don't know what I'm supposed to use (and some of them are already being used so the command fails). How many instances are there running by default for ODISRV and how many for OID itself? What number should I be using based on that?
Here are some entries in my logs:
oidldap01s1304.log- OpName=search, duplicate while inserting in Hash Table.
My comment on that snippet is a duplicate what? and what the hell hash table is it trying to use? The info isn't helpful at all.
odisrv02.log- port 389/profile grp 999: registration failure, config set 1 already being executed by instance 0
odisrv01.log- port 636/profile default: config set 0 already being executed by instance 2.
oidmon.log - retry counts exceeded are listed for both odisrv01 and 02
In all those logs the those errors keep repeating. I don't need OID on port 636 so is there a way I can stop/delete that while I'm fixing the sync issue? I saw nothing in the OEM website that allowed me to remove the SSL configuration.
If I try stopping either instance 0 or 1 and try to restart I can't because the instance number is already used. What the hell am I supposed to do then? That means I can stop everything and not be able to start anything back up, does it not?
any ideas how to make sense of this mess oracle developed?

There are two configsets by default. Configset 1 is
for synchronization and Configset 0 is used by
provisioning (again, these are default settings).
You cannot have two odisrv (Provisioning and Synch)
with the same instance #.
So, instance 1 could be Provisioning and instance 2
could be Synch.
Have you setup your synchronization mapping files?
I would suggest you use the DIPTester utility to
setup the synch. It might also be helpful to post the
commands and the odisrv* logs (not the full dump, but
the last snippet).Well I was trying to use ConfigSet 1 for synchronization but it either wouldn't let me because of how it is designed or I had screwed it up at that point since I didn't know what numbers to use for anything and it prevented me from using Set1 because of that. In the end I created a ConfigSet 2 and was able to get another instance of ODISRV running with that. That finally got the sync working on a scheduled basis. I'm now trying to get SSO working between OID and ADS and it seems that OID is too stupid to know that a user exists. I log onto the Windows PC into the domain and attempt to go to http://ssoServer.com:7778/pls/portal and login and I get an authorization denied message.
I have debugging turned on as much as I can and the defaultIsland log file (forget the full filename but its an OC4J file in $ORACLE_HOME\opmn\logs directory). It says that I was denied access because the user could not be found and yet I see the user in the directory tree and it comes back in a search as well. The krbprinicipalname, uid, and orclcommonprinicipalname (I think that's what it's called) are all the same ([email protected]) and the orclusersearchbase is set to dc=mycompany,dc=com so I don't know why the account can't be found.
ANy ideas on that issue?

Workflow instances problem

My problem is that in workflow i am sending workitem for manager approval.If manager rejects the workitem it goes to employee back for correction and resubmission.But what is happening once workitem is send to employee for correction the current workflow instance is completed and when user changes the report and resubmits it a new workflow instance will be created.This all increases load on the working system.
Can we keep the same workflow instance working till report is rejected or accepeted and then only workflow instance is completed.

I think you can make use of Function module
SAP_WAPI_WORKITEMS_TO_OBJECT
in a virtual attribute that will check whether any existing wflow is already triggered for it. If yes set the Flag(Virtual attribute) value as X. Make use of this attribute in th Start ciondition of the wflow in SWB_COND Tcode.
Now in your workflow the approval step should be inside a loop that loops until the request is approved. Inside the loop the approval step should be in fork with 2 parallel branch and 1 necessary. In 1 branch put approval step and in other branch put the Wait for event step.
Thanks
Arghadip

Getting WLI Workflow Instance getting NULL.

Hi All WLI Users,
I am getting following problem while executing WLI workflow. After work
flow gets triggered by an XML event and instantiated, after some time workflow
instance becomes null.
and the execution is aborted. Kindly give me a solution to this problem.
Thanks
Kiran

Hi tony
It won't be possible for us to send us the workflow, beacuse it has
lots of interfaces
like MQ series and TCP/IP adpater.
But I can explain u in brief the workflow.
Workflow sends message to HOST1 after getting successfull response
from HOST1 it sends
another request to HOST2 and waits for the response.
Now this can iterate for say 200-500 times (depends on response
from HOST1).
Each message length is aroung 5000 bytes.During this iteration the
instance somehow sets to NULL.
I hope you can simulate the same at your end.
Also note we also do XML transformation before sending the request.
Thanks
"tony lodge" <[email protected]> wrote in message
news:[email protected]...
Hi
I recommend given this level of detail you open a case, what I amseeing
looks like a valid bug. Please provide the sample workflow if possible
Tony
"Saurabh" <[email protected]> wrote in message
news:[email protected]...
Hi,
The Versio ni am using is wlisp2.1 (service pack 2.1)
and Exception Stack trace is as follows,
<Mar 30, 2002 1:53:55 AM GMT-05:00> <Error> <T3Services> <Workflowtrace:Template=28003
Template Definition=31003
Instance=null>
Workflow warning: com.bea.wlpi.common.WorkflowException: The system
could
not
find the specified workflow instance: null.
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
nce(WorkflowProcessorBean.java:537)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
nceData(WorkflowProcessorBean.java:551
atcom.bea.wlpi.server.workflow.Variable.setValue(Variable.java:92)
atcom.bea.wlpi.server.workflow.Workflow.setVariable(Workflow.java:833)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.setVariableValue
(WorkflowProcessorBean.java:1017)
at
com.bea.wlaiplugin.server.WLAIServiceImpl.execute(WLAIServiceImpl.java:211)
atcom.bea.wlpi.server.workflow.action.ActionPlugin.execute(ActionPlugin.java:1
23)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Start.activate(Start.java:168)
at
com.bea.wlpi.server.workflow.Workflow.start(Workflow.java:657)
atcom.bea.wlpi.server.workflow.Workflow.instantiate(Workflow.java:617)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean$1.invoke(Workflo
wProcessorBean.java:713)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.performWithError
Handling(WorkflowProcessorBean.java:11
32)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.instantiate(Work
flowProcessorBean.java:709)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.in
stantiate(WorkflowProcessorBean_h7kt4j
_EOImpl.java:78)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.checkTrigger(EventProcesso
r.java:358)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
a:244)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
ean.java:130)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Mar 30, 2002 1:53:55 AM GMT-05:00> <Notice> <EJB> <Error markingtransaction
for rollback: java.lang.IllegalStateException:
Cannot mark the transaction for rollback. xid=4883:97fdb06e981bb8b8,status=Rolled
back. [Reason=weblogic.transaction.interna
l.TimedOutException: Transaction timed out after 89 seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
java.lang.IllegalStateException: Cannot mark the transaction for
rollback.
xid=4883:97fdb06e981bb8b8,
status=Rolled back. [Re
ason=weblogic.transaction.internal.TimedOutException: Transaction timedout after
89 seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
at
weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(Tra
nsactionImpl.java:1486)
at
weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImp
l.java:466)
at
weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.j
ava:255)
at
weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
5)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
er.java:371)
at
weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
java:756)
at
weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
move(WorkflowProcessorBean_h7kt4j_EOIm
pl.java:856)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
cessor.java:510)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
a:284)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
ean.java:130)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
javax.transaction.TransactionRolledbackException: EJB Exception: :weblogic.transaction.internal.TimedOutException:
Transacti
on timed out after 89 seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1122)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImp
l.java:441)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1581)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:404)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1547)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 89seconds
>
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out
after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1475)
at
weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
ServerTransactionImpl.java:435)
at
weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
at
weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
0)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
er.java:371)
at
weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
java:756)
at
weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
move(WorkflowProcessorBean_h7kt4j_EOIm
pl.java:856)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
cessor.java:510)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
a:284)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
ean.java:130)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
; nested exception is:
weblogic.transaction.RollbackException: Transaction timed outafter 89
seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out
after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
weblogic.transaction.internal.TimedOutException: Transaction timed outafter 89
seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1122)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImp
l.java:441)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1581)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:404)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1547)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 89seconds
>
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out
after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1475)
at
weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
ServerTransactionImpl.java:435)
at
weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
at
weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
0)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
er.java:371)
at
weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
java:756)
at
weblo

I am totally frustrated by the fact that now i have gone to iCloud and after a few synchs, my contacts are all mixed up with the wrong information. For instance, my email and phone number comes up under someone else's name (a thousand contacts)

I am totally frustrated by the fact that now i have gone to iCloud and after a few synchs, my contacts are all mixed up with the wrong information. For instance, my email and phone number comes up under someone else's name (a thousand contacts). I dont know how to repair this. what a nightmare

An icloud account is designed to be used by just one user. If you have given your ID or set up your account on someone else's device, then their data will be mingled with your or worse.

Custom Workflow generates a thousand of Workflow Instances and EREs

Hi everyone,
I developed a Custom Workflow that complete user attributes information when a user select a value from a drop down list. I tested this workflow with a Request MPR with an Action Type "Create" and the workflow Works perfectly. But now, I
have to use this workflow in an Action Type "Modify" , when I changed it, the workflow Works fine but generates a thousand of Workflow Instances and in consequence a thousand of EREs.
Can you help me please?
Thanks in advance,

Make sure that the change invoked by your workflow is not used as button to run another workflow - described scenario looks like you have created a loop.
If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

The difference of minor number and instance number

I study how to develop device drivers. I am beginner.
I'm confusing the differece of minor number and instance number
what is the exact difference of them???

Hi,
I guess a good example would be a disk. Each disk you have would be a different instance. To use a disk it is divided into slices, each of which has a different minor number.
Your device driver needs to map the minor number to the correct instance of the device. How you do this is completely up to you, so to start you could map them one to one.
Hope that helps.
Ralph
SUN DTS

LOAD BALANCE (CSS) and Portal Port Number based on Instance Number

Hi,
My doubt is about LOAD BALANCE (CSS) and Portal Port Number based on Instance Number.
I have to install 3 servers machines and 2 servers databases cluster. There will be a HIGH AVAILABILITY environment. There will be a MIGRATION and UPGRADE.
Today there are 2 servers machines in Windows NLB. Today my production Portal is 6 6.20.
Once, I did something for LABORATORY TEST. Migration (6 6.40) and Upgrade (7.0)in two other machines. But they were with Windows NLB. When I did the installation, for each server machine and during the instalation I had to give one Instance Number for each and in result there was a different Port Number for each.
But I accessed both machines throught a virtual url(dns) with a specific port number. And it works!
NOW, with a HARDWARE LOAD BALANCE _ CSS I don't know how to do.
A guy who works with it tell us that couldn't redirect one Port Number for different port numbers. He couldn't configure the CSS like this.
My question is: Is he write? And if he is, there is a way to give the same instance number for my 3 new Portal servers machines? Example: 5(02)00.
Could you understand?
I need help.
Regards,
cheers,
Nivia

Nivia,
I have used F5 for load balancing, I am sure you can do the same with CSS. Yes, you can configure a virtual IP on the load balancer with standard ports (80 or 443) and load balancing the traffic to multiple servers with different ports. You can have different ports for each instance.
-Regards
RK

Message Server Port and Instance Number

Hi All,
I need to create Technical System and Business System in SLD for my IDOC-XI-FILE Scenario. There i need to specify the Message Server port under Message Server and Instance Number in Central Application Server. Please let me know where i have to found these. Please help as soon as possible.
Thanks & Regards,
Nagarjuna.

Hi Nagarujna,
Instance Number : - just check the logon pad.. select your Ecc or R/3 system and click on chane item.... Usally it is 00.
Message server port : it is 3600 + instance no.
3600 + 00 = 3600
Sachin

Text Log shows texts to same number over and over

Hello I just signed up to manage my Verizon online. Upon reading my text logs they are all to the same phone number that I do not know. When I call the number it says its a disconnected Verizon phone #
They match up to texts I have actually sent or received, my call log is fine though. How can I get my account to list the actual numbers I text?

Hi Christina,
Correct, so when I log into My Verizon and select "texts" in the usage category, it lists my phone number TO and the FROM number is always the same one, which I do not recognize.
These (from the number I dont know) correlate with text messages I sent/recieved in my regular messaging app provided by my device by default.
I also use WhatsApp, however those text messages do not appear to be on my bill usage.
Thank you

Hostname and Instance Number

Hello,
I have installed SAP hana studio and client on my personal computer.
How can i find the hostname and instance number when adding a system in Hana studio?
Thank you.

You must have access to some Hana installation, in a cloud or elsewhere. See the CSN Hana home page http://scn.sap.com/docs/DOC-31722 for some examples. If you already have access to Hana, you should know the IP or hostname of the computer where it is running.
-- Micha

Instance number and minor number

hi
can somebody tell me what is actually instance number and what is the relationship between an instance number and minor number of a device .

I'm not 100% sure but my reading of it is:
Usually one has a 1:1 direct mapping of minor number to instance number, but this doesn't have to be the case.
The instance number is linked to your hardware device and say if you move its base address you will get a new instance number with the old one retained for the original address.
If you had 3 cards I think you would have instance No.s 0, 1, and 2.
The minor number can be anything YOU want it to be.
I have a situation where I have a card carrier with 3 cards mounted on it - I can only have one instance and I need to differentiate between the cards used - I use the minor number that is a part of the device handle and can be returned by using getminor from driver code.
As usual the Writing DD SUN book is all there is available.
Any further points - let me know.
Cheers.

Error while creating concurrent workflow instances with dynamic participant

Hi All,
I have a workflow which has 3 interactive activites. The second interactive activity has requires approval of atleast 3 users to proceed. The participants are also not known in advance and are created dynamically by creating the directory session. The workflow is instantiated using an external trigger. The approval for interactive activities is also provided by an external trigger (API call).
Now, there is a scenario where i have 1000 requests coming in to ALBPM and workflow instance should be created for each of them. But only one instance is created and for the rest i get the following exception. This also happens with just 2 requests. I also tried calling the API in a synchronized way but didnt help.
Is anybody aware why is this error encountered anf how it can be resolved?
java.lang.IllegalStateException: Cannot set the directory Connector Service while connector service is started
at fuego.connector.CompositeConnectorService.setDirectoryConnectorService(CompositeConnectorService.java:97)
at fuego.connector.CompositeConnectorService.restartDirectoryConnectorService(CompositeConnectorService.java:52)
at fuego.directory.DirectoryConfigurationManager.loadDirectoryConfiguration(DirectoryConfigurationManager.java:265)
at fuego.directory.DirectoryConfigurationManager.getDirectoryConfiguration(DirectoryConfigurationManager.java:217)
at fuego.directory.DirectoryConfigurationManager.getDirectoryConfigType(DirectoryConfigurationManager.java:199)
at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:214)
at fuego.directory.Directory.fillPassport(Directory.java:122)
at fuego.directory.DirectoryPassport.fillPassport(DirectoryPassport.java:274)

Hi Dan,
Thanks for replying and giving attention. I have the following scenario :-
1. I am getting a list of identifiers(some number) from a third party application along with the users/participants who are liable to approve the workflow instance.
2. I create a workflow instance using this identifier through PAPI using process service session and also create the user/participant through PAPI by using the following code. Please note that i dont create participant in ALBPM instead i do it programatically in java using the PAPI :-
DirectorySession directorysession = null;
if (userVO != null && userVO.getUserId() != null && !userVO.getUserId().trim().equals(""))
+{+
+     directorysession = this.createFDISession();+
+     List<RoleAssignment> roleAssignmentList = new ArrayList<RoleAssignment>();+
+     try {+
DirOrganizationalRole[] dirOrganizationalRoleArray = DirOrganizationalRole.fetchAll(directorysession);
for(int i=0; dirOrganizationalRoleArray!=null && i<dirOrganizationalRoleArray.length; i+) {+
+DirOrganizationalRole role = dirOrganizationalRoleArray;+
+}+
int permissions = -1;
permissions
+= 0 |+
DirHumanParticipant.getPermissionValue("X") |
DirHumanParticipant.getPermissionValue("R") |
DirHumanParticipant.getPermissionValue("S") |
DirHumanParticipant.getPermissionValue("A") |
DirHumanParticipant.getPermissionValue("D") |
DirHumanParticipant.getPermissionValue("E") |
+0;+
+String[] whichRoles = new String[]{+
+"Approver",+
+"Requestor",+
+};+
+DirHumanParticipant.RoleAssignment[] roleAssignments = new DirHumanParticipant.RoleAssignment[whichRoles.length];+
for(int i=0; i<whichRoles.length; i+) {+
+roleAssignments[i] = new DirHumanParticipant.RoleAssignment(whichRoles[i], permissions, DirOrganizationalRole.fetch(directorysession, whichRoles[i]).getIn());+
+}+
+     String organizationUnit = configuration.getProperty("ORGANIZATION_UNIT");//fuegoFileProperties.getProperty(BVIDConstants.FUEGO_CONNECTIVITY_KEY_ORGANIZATION_UNIT);+
+     String newUserPwd = configuration.getProperty("FUEGO_FDI_NEW_USER_PASSWORD");//fuegoFileProperties.getProperty(BVIDConstants.FUEGO_CONNECTIVITY_KEY_FDI_PWD);+
+     DirOrganizationalUnit orgUnit = DirOrganizationalUnit.fetch(directorysession,organizationUnit);+
+     DirHumanParticipant user = DirHumanParticipant.create(directorysession, userVO.getUserId(), userVO.getFirstName(), userVO.getLastName(),+
+                              userVO.getFirstName(), userVO.getEmail(), userVO.getPhone(), "",+
+                              newUserPwd, orgUnit,roleAssignments, true);+
+     user.update();+
+     }+
+     finally+
+     {+
+               log.info("diconnecting the directory session created for creating participant");+
+               directorysession.disconnect();+
+     }+
+}+
3. The workflow instance then waits at interactive activity to get the next trigger with the same identifier to move the workflow ahead.
4. Now the case is that i can get 1000 such identifiers at a time in a file which i ll read for which i need to create 1000 workflow instances parallely. During this process i get the following exception : -
java.lang.IllegalStateException: Cannot set the directory Connector Service while connector service is started
at fuego.connector.CompositeConnectorService.setDirectoryConnectorService(CompositeConnectorService.java:97)
at fuego.connector.CompositeConnectorService.restartDirectoryConnectorService(CompositeConnectorService.java:52)
at fuego.directory.DirectoryConfigurationManager.loadDirectoryConfiguration(DirectoryConfigurationManager.java:265)
at fuego.directory.DirectoryConfigurationManager.getDirectoryConfiguration(DirectoryConfigurationManager.java:217)
at fuego.directory.DirectoryConfigurationManager.getDirectoryConfigType(DirectoryConfigurationManager.java:199)
at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:214)
at fuego.directory.Directory.fillPassport(Directory.java:122)
at fuego.directory.DirectoryPassport.fillPassport(DirectoryPassport.java:274)
Please let me know if you need any more information. awaiting your help
Thanks,
Anand

How can I correlate an Java instance number with a server id?

I have 6 Web App Server running ABAP and the JAVA stacks. I can log into the Central Instance server and run /usr/sap/<SID>DVEBMSG00/j2ee/configtool/configtool.sh and bring up the GUI interface to "see" all the instances and their variables. I don't see an easy way to trace back the Java INSTANCE to the physical server's hostname.
Is there a central repository to correlate a Web App Server Java instance number to the actual hostid/hostname of the target server? I realize I can log into each Web App Server and look at the /usr/sap/<SID>D00/j2ee/cluster/instance.properties and find the Instance number, but I was wondering if this information was held in the SAP Central instance or SAP Database somewhere.

Hi Timothy,
The instance ID used for the JAVA cluster is generated at installation time, and -amongst other things- takes into account the time it was generated. We installed two instances in parallel (on different hosts) and ended up with almost the same instance ID.
Because this can be very confusing, we asked SAP if this was changable - in theory it is only an ID which could be changed as long as it is updated on all places the identifier is stored - but SAP indicated that that is not possible, nor supported. We ended up with a diagram of the system architecture with all the identifiers on our desk.
Note that in the config tool - all instances are displayed with their system instance number. If you were to install a new system it might be usefull to install all instances with different instance numbers so you and distinguish more easily between them.
Hope this helps,
Cheers,
Walter

Workflow instance number = 0000000000, and no log..??

Similar Messages

Maybe you are looking for