Personalization Scheduling Engine does not start -- Bug?

Question

Hi there. I don't know if it's the correct forum to post my question. If I'm wrong I ask you to redirect to
the correct one.
I've correctly installed Oracle AS 10g release 1 according to the following topology, on the production
environment :
Server 1 --> Here we are three oracle homes : Identity Management , Middle Tier (Portal and Wireless) ,
Personalization.
Server 2 --> MetadataRepository
My problem focuses on Personalization. I advise that in my developing environment I've not got any problem.
So , I've installed Oracle AS Personalization without wornings. I've created RE,MOR and MTR schemas as the
procedure dictates. Problem's that Personalization Scheduling Engine does not start. It should start
automatically but It didn't. So I tried to start it by hand following "Oracle Application Server Hi there.
I don't know if it's the correct forum to post my question. If I'm wrong I ask you to redirect to the
correct one.
I've correctly installed Oracle AS 10g release 1 according to the following topology, on the production
environment :
Server 1 --> Here we are three oracle homes : Identity Management , Middle Tier (Portal and Wireless) ,
Personalization.
Server 2 --> MetadataRepository
My problem focuses on Personalization. I advise that in my developing environment I've not got any problem.
So , I've installed Oracle AS Personalization without wornings. I've created RE,MOR and MTR schemas as the
procedure dictates. Problem's that Personalization Scheduling Engine does not start. It should start
automatically but It didn't. So I tried to start it by hand following "Oracle Application Server
Personalization Administrator's Guide 10g(9.0.4)". Specifically , when I try to start the scheduling engine
with the command "execute OP_START_ENGINE" in the MOR schema I obtain an error linked to DBMS_JOB.run()
method. Digging deep into the Oracle alert log file I found this brief linked to the error executin the
script :
Thu Apr 14 17:57:28 2005
Errors in file E:\MetadataRepositoryHome\admin\asdb\udump\ORA01860.TRC:
ORA-12012: error on auto execute of job 119
ORA-29532: Java call terminated by uncaught Java exception: java.lang.Exception: Scheduler Workflow Error:
9756161113494248343 java.lang.NumberFormatException: 9756161113494248343
at java.lang.Long.parseLong(Long.java)
at java.lang.Long.parseLong(Long.java)
at oracle.dmt.op.util.messagelog.MessageLog.getExecutionContextID(MessageLog.java:857)
at oracle.dmt.op.workflow.SchedulerWorkflowClass.main_method(SchedulerWorkflowClass.java:101)
at oracle.dmt.op.workflow.SchedulerWorkflowClass.SchedulerWorkflowJava(SchedulerWorkflowClass.java:91)
ORA-06512: at "MOR_PORTALE.DMT_CLIENT_IDARWIN_WORKFLOW", line 0
ORA-06512: at line 1
So as the main error is "NumberFormatException" , I executed reverse engineering decompiling two Oracle
classes , just to know the origin of the error :
oracle.dmt.op.util.messagelog.MessageLog and
oracle.dmt.op.workflow.SchedulerWorkflowClass
After simple tracing I think I reached the origin and I shocked myself to see it!! The problem starts in the
main_method of oracle.dmt.op.workflow.SchedulerWorkflowClass, i.e. :
private void main_method()
throws Exception
String event_msg_args[];
traceMsg += "Start";
moduleID = "SchedulerWorkflowClass.main_method";
traceMsg += "-executionContextID";
executionContextID = MessageLog.getExecutionContextID();
The problem resides in the getExectiongContextID() method of oracle.dmt.op.util.messagelog.MessageLog class.
Code of this method is this :
public static long getExecutionContextID()
String hostIP = null;
try
InetAddress host = InetAddress.getLocalHost();
hostIP = host.getHostAddress();
catch(UnknownHostException ex) { }
StringBuffer buf = new StringBuffer(20);
if(hostIP != null)
for(StringTokenizer st = new StringTokenizer(hostIP, "."); st.hasMoreTokens(); buf.append
(st.nextToken()));
buf.append((new Date()).getTime());
String tmpString = buf.toString();
String idString = tmpString.replace('?', ' ');
idString = idString.trim();
int len = idString.length();
if(len > 19)
idString = idString.substring(len - 19);
long id = Long.parseLong(idString);
return id;
Simply , code obtains IP address of the Host , concats it with the current time and if the length of the
result string is longer than 19 it obtains substring of (len -19) length!! I think , Oracle programmer
thought to prevent NumberFormatException with the control "if(len > 19)
idString = idString.substring(len - 19);"
but that's strange , very strange!! In fact , in my case(with my IP Address 160.97.*.*) , method outputs
NumberFormatExceptio 'couse long "id = Long.parseLong(idString);" is not able to convert the String
"9756161113494248343" to java.lang.Long!!! 'couse it exceedes maximum value ( 2EXP(63)-1)!! So , I think
it's bug but I don't know how to solve it!! Problem's in method's semantic. It should control that the
String it creates is lower that the maximum value allowed for a long , not its length lower or equal 19!!!
I mean , I cannot modify Oracle Java Class file.
With kind regards,
Nicola

Answer 1

Fix in OracleAS 10.1.2.0.2 if you file a bug referencing bug 4397235 a backport of the fix can be provided on metalink.