Strange Error = HELP !!!!!!!!!!!!!!!!!!!!!
Hi everybody,
Trying to start BEA Server, I got a strange error : java.net.UnknownHostException : sproerp07: sproerp07 where sproerp07 is my hostname.
I work on AIX 5.1 with WL 8.1. Can you help me.
I suppose this is a java error.
But how to resolve it? I don't know. It seems that My hostname is written twice.
Help Me .... For me, Everything is ok. Hostname : ok. hosts file Ok, but Error in starting the server
===============================================
extract of my error:
The WebLogic Server did not start up properly.
java.net.UnknownHostException: sproerp07: sproerp07
at java.net.InetAddress.getLocalHost(InetAddress.java:1199)
at weblogic.rjvm.JVMID.setLocalID(JVMID.java:122)
at weblogic.rjvm.JVMID.localID(JVMID.java:102)
at weblogic.protocol.configuration.NetworkChannel.<init>(NetworkChannel.java:350)
at weblogic.protocol.configuration.NetworkChannelGroup.<init>(NetworkChannelGroup.java:141)
at weblogic.server.Server.initNetWorkChannels(Server.java:49)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:773)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.utils.NestedError: Local host not known?! - with nested exception:
[java.net.UnknownHostException: sproerp07: sproerp07]
at weblogic.rjvm.JVMID.setLocalID(JVMID.java:126)
at weblogic.rjvm.JVMID.localID(JVMID.java:102)
at weblogic.protocol.configuration.NetworkChannel.<init>(NetworkChannel.java:350)
at weblogic.protocol.configuration.NetworkChannelGroup.<init>(NetworkChannelGroup.java:141)
at weblogic.server.Server.initNetWorkChannels(Server.java:49)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:773)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
at weblogic.Server.main(Server.java:32)
Reason: Local host not known?!
I'm seeing this same issue as well. The only difference is that I have WebLogic 8.1 running on Windows 2003. I can start up the server fine as long as I'm connected to the network. When I do not have a connection, weblogic throws an UnknownHostException stating that it cannot find my server.
Any help is greatly appreciated.
Thanks,
George
Similar Messages
-
Sample java client not running--showing a strange error-- help urgently
Hi,
I have followed all the steps, given in JDevloper help, to create and deploy an EJB onto a 9ias server and I have been successful in creating the EJB and deploying it from the JDevloper machine to 9ias machine.My JDevloper is on one machine and 9ias is on another. After deploying when I am creating a sample java client, as given in the JDevloper help file, it gives a very strange error
java.lang.NullPointerException
void Samplemypackage1.MySessionEJB1Client.main(java.lang.String[])
Process exited with exit code 0.
I have tried a lot but it's not happening. Is it becuase
1. 9ias and JDevloper should be on the same machine
2. some configurational changes need to be done in the settings
3. jdk1.3.1 is not compatible with JDevloper.
I am enclosing the code snippet for your quick reference.
package Samplemypackage1;
import java.util.Hashtable;
//import javax.rmi.PortableRemoteObject;
import javax.naming.Context;
import javax.naming.InitialContext;
import mypackage1.MySessionEJB1;
import mypackage1.MySessionEJB1Home;
public class MySessionEJB1Client
public static void main(String [] args)
MySessionEJB1Client mySessionEJB1Client = new MySessionEJB1Client();
try
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "admin");
env.put(Context.PROVIDER_URL, "ormi://9ias:23791/MySessionEJB1");
Context ctx = new InitialContext(env);
MySessionEJB1Home mySessionEJB1Home = (MySessionEJB1Home)ctx.lookup("MySessionEJB1");
MySessionEJB1 mySessionEJB1;
// Use one of the create() methods below to create a new instance
mySessionEJB1 = mySessionEJB1Home.create();
// Call any of the Remote methods below to access the EJB
System.out.println(mySessionEJB1.calc("om sri"));
catch(NullPointerException ne)
ne.printStackTrace();
catch(Throwable ex)
ex.printStackTrace();
When I tried to debug the program I found that the line " mySessionEJB1 = mySessionEJB1Home.create()" returns a null. I really fail to understand as to why it is happening.
Please help me.
ThankxThat's strange. home.create() should never return a null.
Do you see any exception trace on the server side?
Do you have the same version of oc4j.jar on client and server machine? Which version of Jdeveloper and 9iAs are you using?
Try copying oc4j.jar from the server machine to client machine and use that to connect to the bean.
HTH
Dhiraj -
Strange error - HELP! : temp.as - Error #1046
Hi all,
I am converting a project to AS3. However I get a stranger
error :
**Error** ...\temp.as : Line 1, Column 210 : [Compiler] Error
#1046: Type was not found or was not a compile-time constant: List.
À€
The strange thing is that THERE IS NO FILE NAMED temps.as.
I've searched everywhere. I know that I did not create any, so
maybe Flash 9 does it. Anyone has got an idea about that?
Another strange thing is that after the error, instead of
writing the code responsible for it, there is this 'À' which
is actually followed by a square. I m a bit confused.
Please help, thanksquote:
Originally posted by:
Nico22_be
Another strange behavior related to that temp.as file. Since
there is no such file, I decided to create one like this :
package {
class temp {}
And to test. I then get new errors :
**Error** \temp.as : Line 2, Column 8 : [Compiler] Error
#1131: Classes must not be nested.
class temp {}
**Error** \temp.as : Line 1, Column 1 : [Compiler] Error
#1153: A constructor can only be declared public.
package {
When declaring a package, you must give the path to the
package
package com.mysite.utilities {
When Flash compiles, I believe it already creates a package{
line but who knows for sure until Adobe says so. As a result, you
cannot next base level packages which is what the error is for.
The second error is because of your class declaration....
it's missing a constructor
package {
class temp {}
should be
package com.mysite.tempstuff {
class temp{
public function temp() {
Every class must have a "public" constructor to initialize it
when it is called with the "new" flag.
temp.as - this is probably an issue where Flash cannot create
the temporary as file that it loads into the debugger when it runs
in the dev environment. -
In my Web application (bc4j+uixml)I always got such a error,and does not go away when I RECREATE the project:
oracle.jbo.AttributeLoadException: JBO-27022: Laden von Wert bei Index 27 mit Java-Objekt vom Typ java.lang.String aufgrund von java.sql.SQLException nicht möglich.
oracle.jbo.AttributeLoadException: JBO-27022: Laden von Wert bei Index 27 mit Java-Objekt vom Typ java.lang.String aufgrund von java.sql.SQLException nicht möglich.
at oracle.jbo.server.OracleSQLBuilderImpl.doLoadFromResultSet(OracleSQLBuilderImpl.java:1037)
at oracle.jbo.server.AttributeDefImpl.loadFromResultSet(AttributeDefImpl.java:1482)
at oracle.jbo.server.ViewObjectImpl.buildDiscrVals(ViewObjectImpl.java:2005)
at oracle.jbo.server.ViewObjectImpl.createRowFromResultSet(ViewObjectImpl.java:2020)
at oracle.jbo.server.ViewObjectImpl.createInstanceFromResultSet(ViewObjectImpl.java:1964)
at oracle.jbo.server.QueryCollection.populateRow(QueryCollection.java:1390)
at oracle.jbo.server.QueryCollection.fetch(QueryCollection.java:1241)
at oracle.jbo.server.QueryCollection.get(QueryCollection.java:831)
at oracle.jbo.server.ViewRowSetImpl.getRow(ViewRowSetImpl.java:2619)
at oracle.jbo.server.ViewRowSetIteratorImpl.doFetch(ViewRowSetIteratorImpl.java:2347)
at oracle.jbo.server.ViewRowSetIteratorImpl.ensureRefreshed(ViewRowSetIteratorImpl.java:2211)
at oracle.jbo.server.ViewRowSetIteratorImpl.refresh(ViewRowSetIteratorImpl.java:2412)
at oracle.jbo.server.ViewRowSetImpl.notifyRefresh(ViewRowSetImpl.java:1554)
at oracle.jbo.server.ViewRowSetImpl.refreshRowSet(ViewRowSetImpl.java:3333)
at oracle.jbo.server.ViewRowSetIteratorImpl.notifyDetailRowSets(ViewRowSetIteratorImpl.java:2842)
at oracle.jbo.server.ViewRowSetIteratorImpl.notifyNavigation(ViewRowSetIteratorImpl.java:2948)
at oracle.jbo.server.ViewRowSetIteratorImpl.internalSetCurrentRow(ViewRowSetIteratorImpl.java:2734)
at oracle.jbo.server.ViewRowSetIteratorImpl.first(ViewRowSetIteratorImpl.java:1148)
at oracle.jbo.server.ViewRowSetImpl.first(ViewRowSetImpl.java:2240)
Can somebody tell me its a error about :
Database?
or
BC4J?
or
Uix?
Thanks!
yongSung:
Here a little more Debug information:
if open the page ---success:
arget URL -- http://3.224.30.135:8995/medora-TempPro-context-root/PatientDataView_View.uix
2003-07-09 09:18:38,595 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:38,923 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:38,938 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:38,954 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:39,126 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:39,360 [HttpRequestHandler-10038190] DEBUG - BoneOracleSqlBuilder created: Bone Oracle SQL Builder $Revision: 1.10 $ based on com.ge.med.bone.bc4j.server.BoneOracleSqlBuilder@bbfa5c
2003-07-09 09:18:40,095 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:40,110 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:40,110 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:40,141 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:40,251 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:41,188 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:41,220 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:41,235 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:41,235 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:41,251 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:41,470 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:41,516 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:41,516 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:41,516 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:41,516 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:41,782 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:41,923 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:41,923 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:41,923 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:42,032 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:42,626 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:42,657 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:42,657 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:42,673 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:42,782 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:43,313 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:43,345 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:43,345 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:43,360 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:43,548 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:44,220 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:44,235 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:44,251 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:44,251 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:44,282 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:44,798 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:44,845 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:44,845 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:44,845 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:45,048 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:45,673 [HttpRequestHandler-10038190] DEBUG - BaseEntityDefImpl created
2003-07-09 09:18:45,704 [HttpRequestHandler-10038190] DEBUG - ENTERING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:45,704 [HttpRequestHandler-10038190] DEBUG - ensure that new EOs are unique (in cache and database)
2003-07-09 09:18:45,704 [HttpRequestHandler-10038190] DEBUG - Read the custom properties for the attributes
2003-07-09 09:18:45,782 [HttpRequestHandler-10038190] DEBUG - LEAVING com.ge.med.bone.bc4j.common.BaseEntityDefImpl.createDef
2003-07-09 09:18:50,641 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: first!
2003-07-09 09:18:51,735 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: executeQueryForCollection
2003-07-09 09:18:51,766 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:51,860 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:51,860 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:51,876 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:51,891 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:52,032 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:52,048 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:52,048 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:52,063 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:52,313 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:52,313 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:52,313 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:52,329 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:18:54,251 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 0
2003-07-09 09:18:54,954 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 1
2003-07-09 09:18:54,970 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 2
2003-07-09 09:18:54,985 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 3
2003-07-09 09:18:55,016 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 4
2003-07-09 09:18:55,048 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 5
2003-07-09 09:18:55,095 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 6
2003-07-09 09:18:55,110 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 7
2003-07-09 09:18:55,126 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 8
2003-07-09 09:18:55,313 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 9
2003-07-09 09:18:55,329 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 10
2003-07-09 09:18:55,345 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 11
2003-07-09 09:18:55,360 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 12
2003-07-09 09:18:55,829 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 0
2003-07-09 09:18:55,860 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 1
2003-07-09 09:18:55,923 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 2
2003-07-09 09:18:55,954 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 3
2003-07-09 09:18:56,079 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 4
2003-07-09 09:18:56,110 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 5
2003-07-09 09:18:56,173 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 6
2003-07-09 09:18:56,204 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 7
2003-07-09 09:18:56,329 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 8
2003-07-09 09:18:56,376 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 9
2003-07-09 09:18:56,438 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 10
2003-07-09 09:18:56,470 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 11
2003-07-09 09:18:56,579 [HttpRequestHandler-10038190] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 12
---if event "goto " success:----
2003-07-09 09:41:00,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,220 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,235 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,345 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,345 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,376 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,391 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,704 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,704 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,751 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,891 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:00,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,141 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,157 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,157 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,407 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,407 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,407 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,641 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,657 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,657 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:01,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,157 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,157 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,157 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,407 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,407 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,407 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,657 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,657 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,657 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:02,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,157 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,157 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,157 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,407 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,407 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,407 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,657 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,657 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,657 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,704 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,907 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:03,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,157 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,454 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:04,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,204 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,704 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:05,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,454 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:06,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,204 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:07,954 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,704 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:08,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,454 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:09,954 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,720 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:10,954 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,204 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,470 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,704 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,923 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:11,954 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,173 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,220 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,454 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,673 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,720 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:12,954 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,204 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,470 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,704 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:13,954 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,188 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,220 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,485 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,501 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,501 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,516 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,516 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,516 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,516 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:14,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,063 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,532 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,532 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:15,813 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,032 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,032 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,563 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,563 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:16,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,032 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,032 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,313 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,313 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,532 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,532 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:17,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,063 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,063 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,532 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,532 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,813 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:18,813 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,032 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,032 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,563 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,563 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:19,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,032 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,032 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,313 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,313 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,532 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,548 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,782 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:20,798 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:21,048 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:21,063 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:21,063 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.patient.PatientDataCoreImpl created
2003-07-09 09:41:21,579 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 0
2003-07-09 09:41:21,626 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:21,735 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.core.AddressImpl created
2003-07-09 09:41:21,829 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AppointmentDataViewImpl: executeQueryForCollection
2003-07-09 09:41:21,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 1
2003-07-09 09:41:22,001 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:22,079 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.core.AddressImpl created
2003-07-09 09:41:22,204 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AppointmentDataViewImpl: executeQueryForCollection
2003-07-09 09:41:22,266 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 2
2003-07-09 09:41:22,345 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:22,423 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.core.AddressImpl created
2003-07-09 09:41:22,501 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AppointmentDataViewImpl: executeQueryForCollection
2003-07-09 09:41:22,579 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 3
2003-07-09 09:41:22,688 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:22,735 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.core.AddressImpl created
2003-07-09 09:41:22,813 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AppointmentDataViewImpl: executeQueryForCollection
2003-07-09 09:41:22,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 4
2003-07-09 09:41:23,001 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:23,079 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.core.AddressImpl created
2003-07-09 09:41:23,204 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AppointmentDataViewImpl: executeQueryForCollection
2003-07-09 09:41:23,282 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 5
2003-07-09 09:41:23,360 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:23,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.core.AddressImpl created
2003-07-09 09:41:23,501 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AppointmentDataViewImpl: executeQueryForCollection
2003-07-09 09:41:23,579 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 6
2003-07-09 09:41:23,704 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:23,751 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.core.AddressImpl created
2003-07-09 09:41:23,813 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AppointmentDataViewImpl: executeQueryForCollection
2003-07-09 09:41:23,938 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 7
2003-07-09 09:41:24,016 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:24,079 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.core.AddressImpl created
2003-07-09 09:41:24,220 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AppointmentDataViewImpl: executeQueryForCollection
2003-07-09 09:41:24,298 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 8
2003-07-09 09:41:24,360 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:24,438 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medora.modules.main.bc.core.AddressImpl created
2003-07-09 09:41:24,516 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AppointmentDataViewImpl: executeQueryForCollection
2003-07-09 09:41:24,595 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.PatientDataViewImpl: setCurrentRowAtRangeIndex: 9
2003-07-09 09:41:24,720 [HttpRequestHandler-11153138] DEBUG - com.ge.med.medweb.scheduler.bc.AddressDataViewImpl: executeQueryForCollection
2003-07-09 09:41:24,751 [HttpRequestHandler -
Strange error in APP server installation
Hi All,
We installed Oracle Application server Version 10.1.2.3.0 in E drive
Oracle Home: E:\oracle\FRHome_1
While testing we get following errors.
Java Plug-in 1.6.0_26
Using JRE version 1.6.0_26-b03 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\log2kor
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
proxyHost=null
proxyPort=0
connectMode=HTTP, native.
Forms Applet version is : 10.1.2.3
Exception in thread "thread applet-oracle.forms.engine.Main-1" java.lang.NoSuchMethodError: oracle.ewt.util.BIDIText.setDigitSubstitution(I)V
at oracle.forms.engine.Runform.onUpdate(Unknown Source)
at oracle.forms.engine.Runform.onUpdateHandler(Unknown Source)
at oracle.forms.engine.Runform.processMessage(Unknown Source)
at oracle.forms.engine.Runform.processSet(Unknown Source)
at oracle.forms.engine.Runform.onMessageReal(Unknown Source)
at oracle.forms.engine.Runform.onMessage(Unknown Source)
at oracle.forms.engine.Runform.sendInitialMessage(Unknown Source)
at oracle.forms.engine.Runform.startRunform(Unknown Source)
at oracle.forms.engine.Main.createRunform(Unknown Source)
at oracle.forms.engine.Main.start(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)If I remove the ewt jar , I get a strange error Error open Error opening Oracle*Terminal file C:\Oracle\Product\OracleMidTier10gR2\Forms\pc_tastatur.res . If Appserver is installed in E drive why there is a hard-coded values like this*
C:\Oracle\Product\OracleMidTier10gR2\Forms\*
Regards,
Lokanath
Solution :-> Old config was copied so removed.
Edited by: Lokanath Giri on १८ जनवरी, २०१२ ११:०० पूर्वाह्नAssuming that you are following the written instructions available at http://docs.oracle.com that walk you through the install. And assuming you installed the correct versions of libraries. And assuming you set permissions correctly.
I'd suggest metalink and opening an SR.
If you didn't follow the docs ... rm -rf would be a good place to start. -
Strange error regarding libmlib.so.2 after upgrading to gcc3.4.6
Hello everyone,
I just upgraded my sparc Solaris 10 system to gcc3.4.6, plus a BUNCH of additional tools and libraries that rely on gcc3.4.6 libraries, from www.sunfreeware.com. I'm now getting a very strange error on a few of the tools, regarding the libmlib.so.2 library.
For example, when attempting to run gtk-demo, I'm getting the following:
sun440:root# gtk-demo
ld.so.1: gtk-demo: fatal: libmlib.so.2: version `SUNW_2.3' not found (required by file /usr/local/lib/libgdk_pixbuf-2.0.so.0)
ld.so.1: gtk-demo: fatal: libmlib.so.2: open failed: No such file or directory
Killed
If I do an ldd on gtk-demo, this is what I see:
sun440:root# ldd /usr/local/bin/gtk-demo
libgdk_pixbuf-2.0.so.0 => /usr/local/lib/libgdk_pixbuf-2.0.so.0
libgdk-x11-2.0.so.0 => /usr/local/lib/libgdk-x11-2.0.so.0
libgtk-x11-2.0.so.0 => /usr/local/lib/libgtk-x11-2.0.so.0
libXrandr.so.2 => /usr/lib/libXrandr.so.2
libXext.so.0 => /usr/lib/libXext.so.0
libpangocairo-1.0.so.0 => /usr/local/lib/libpangocairo-1.0.so.0
libpangoft2-1.0.so.0 => /usr/local/lib/libpangoft2-1.0.so.0
libpango-1.0.so.0 => /usr/local/lib/libpango-1.0.so.0
libatk-1.0.so.0 => /usr/local/lib/libatk-1.0.so.0
libgobject-2.0.so.0 => /usr/local/lib/libgobject-2.0.so.0
libgmodule-2.0.so.0 => /usr/local/lib/libgmodule-2.0.so.0
libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0
libiconv.so.2 => /usr/local/lib/libiconv.so.2
libcairo.so.2 => /usr/local/lib/libcairo.so.2
libfontconfig.so.1 => /usr/local/lib/libfontconfig.so.1
libfreetype.so.6 => /usr/local/lib/libfreetype.so.6
libexpat.so.0 => /usr/local/lib/libexpat.so.0
libpng12.so.0 => /usr/local/lib/libpng12.so.0
libz.so => /usr/local/lib/libz.so
libXrender.so.1 => /usr/local/lib/libXrender.so.1
libSM.so.6 => /usr/lib/libSM.so.6
libICE.so.6 => /usr/lib/libICE.so.6
libX11.so.4 => /usr/lib/libX11.so.4
libsocket.so.1 => /lib/libsocket.so.1
libnsl.so.1 => /lib/libnsl.so.1
libm.so.2 => /lib/libm.so.2
libmlib.so.2 => /usr/lib/libmlib.so.2
libc.so.1 => /lib/libc.so.1
libmlib.so.2 (SUNW_2.3) => (version not found)
libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
libmlib.so.2 (SUNW_2.3) => (version not found)
libXrender.so.1 (RENDER_0.6) => (version not found)
libintl.so.8 => /usr/local/lib/libintl.so.8
libsec.so.1 => /lib/libsec.so.1
libdl.so.1 => /lib/libdl.so.1
libmp.so.2 => /lib/libmp.so.2
libmd.so.1 => /lib/libmd.so.1
libscf.so.1 => /lib/libscf.so.1
libavl.so.1 => /lib/libavl.so.1
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
libgen.so.1 => /lib/libgen.so.1
/usr/lib/cpu/sparcv9+vis2/libmlib.so.2
/platform/SUNW,Sun-Fire-V440/lib/libc_psr.so.1
/platform/SUNW,Sun-Fire-V440/lib/libmd_psr.so.1
I am also getting this same error repeatedly when trying to run Firefox 3.6. Any ideas? I do have this library installed:
sun440:root# ls -la /usr/lib/libmlib*
lrwxrwxrwx 1 root root 14 Nov 15 2006 /usr/lib/libmlib.so -> ./libmlib.so.2
-r-xr-xr-x 1 root bin 20260528 Jan 22 2005 /usr/lib/libmlib.so.2
Any ideas? It's very frustrating. Thanks in advance,
jeff daveyI don't understand how that would help. libmlib.so.2 is not part of gcc, it's from Sun package SUNWmlib. There is no libmlib.so.2 as part of the gcc or gcclibs packages from sunfreeware.
I did do a search for all instances of libmlib.so.2, and I got the following results:
./usr/lib/sparcv9/libmlib.so.2
./usr/lib/cpu/sparcv8plus/libmlib.so.2
./usr/lib/cpu/sparcv8plus+vis/libmlib.so.2
./usr/lib/cpu/sparcv9+vis/sparcv9/libmlib.so.2
./usr/lib/cpu/sparcv9+vis2/sparcv9/libmlib.so.2
./usr/lib/cpu/sparcv9+vis2/libmlib.so.2
./usr/lib/libmlib.so.2
./opt/SUNWmlib/lib/libmlib.so.2
./opt/SUNWmlib/lib/sparcv8/libmlib.so.2
./opt/SUNWmlib/lib/sparcv8plus/libmlib.so.2
./opt/SUNWmlib/lib/sparcv8plus+vis/libmlib.so.2
./opt/SUNWmlib/lib/sparcv8plus+vis2/libmlib.so.2
./opt/SUNWmlib/lib/sparcv9/libmlib.so.2
./opt/SUNWmlib/lib/sparcv9+vis/libmlib.so.2
./opt/SUNWmlib/lib/sparcv9+vis2/libmlib.so.2
Then, as a test, I updated my LD_LIBRARY_PATH to incorporate the paths so the various versions would be seen first, and it did not make any difference. I keep getting this when running ldd on gtk-demo:
libmlib.so.2 (SUNW_2.3) => (version not found)
libmlib.so.2 (SUNW_2.3) => (version not found)
libXrender.so.1 (RENDER_0.6) => (version not found)
I'm also confused about the libXrender not being found as well. Can anyone else shed some light on this? Thanks! -
Strange error message when I tried to use the "collaborate" function under "File"
Has anyone else met this before? : I am trying to share my project with my team members. Tried File -> Collaborate and then try three options under it. Non e of them works. It asks for your Adobe ID in order to sign in and upload. However, every time I typed in my Adobe ID and password, it gave me strange error messages. The first time it says: User has not verified email address yet. I have been using this Adobe ID since 2008 or 2009 and of course I have verified my email address. But to make sure, I went back to my email box and search for emails about Adobe ID verification but I didn't find any (I never delete emails such as this).
Then I tried to register a new Adobe ID. This time when I tried to singn in with the new Adobe ID, it will either say "Network may not be available" (which is not true because I am able to surf on the Internet at the same time), or it says "User has not accepted user condition/agreement".
I feel so frustrated because I feel this is definitely not my mistake which caused the failure of log in.
Hope someone can tell me what the reason is and how to fix it though.
Thanks a lot.Hi Lilybiri,
Thanks for your quick response. I followed your suggestion and verified my Adobe ID on acrobat.com.
Now I can enter the collaborate function. However, everytime when I tried to send it to myself (for test purpose) I got another error message "You need to enter a valid emaill address". I saw someone else on this forum has met the same problem. Do you have any suggestion on what is the possible reason for this to happen?
Again, thanks for the fast response. You have been helping me and other ppl so much. -
Strange error while creating form/report pages [ORA-20001]
While creating two new pages with a form and report on it, I've got a strange error. I tried to create the pages several times, but I always got the same error:
ORA-20001: Unable to create query and update page. ORA-20001: Unable to create form on table. ORA-20001: Error creating shortcut id="" ORA-00001: unique constraint (FLOWS_030000.WWV_FLOW_SHORTCUT_IDX1) violated
Error creating query and update.
Return to application.
I'm using the wizard to get the pages, like I did many times before (without problems), but this time it will not work!
Greetings,
JanBelow is a view or sql query i want to create in XE to show users report on startdate,end date,road name,etc,i am having a problem making this view work when i put the code in the sql script. Kindly help me with this if you can please. Thanks. CREATE OR REPLACE FORCE VIEW "RESULTS_DETAILS_VIEW" ("STARTDATE","ENDDATE","ROAD","NAME","STATUS","TYPE","UTILITIES","DATES","LUTON",
AS SELECT
d.Startdate,
d.EndDate,
l.Road,
u.Name,
ws.Status,
wt.Type,
cb.startdate,
cb.enddate,
cb.road,
cb.utility,
cb.type,
cb.status
FROM
Dates d,
Luton l,
Utilities u,
WorkStatus ws,
WorkType wt,
Comb cb
WHERE cb.startDate = d.StartDate
AND cb.endDate = d.EndDate
AND cb.road = l.Road
AND cb.utility = u.Name
AND cb.type = wt.Type
AND cb.status = ws.Status
WITH READ ONLY
/ -
Strange error while executing a stored procedure: Incorrect syntax near '@p0'
All, I am getting a strange error while executing a stored procedure: Incorrect syntax near '@p0' using JDBC CallableStatment.
Here is my code...
CallableStatement cStmt = con.prepareCall("{call SET CHAINED ON EXEC <dbName>.<schemaName>.<SPName> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}");
cStmt.setString(1, "2012005881");
cStmt.setString(2, "07");
cStmt.setString(3, "10");
cStmt.setString(4, "Case title");
cStmt.setString(5, "Open");
java.sql.Date dt1 = new java.sql.Date(2014,10,20);
cStmt.setDate(6, dt1);
cStmt.setString(7, "01");
cStmt.setString(8, "N");
cStmt.setString(9, "ADA Test");
cStmt.setString(10, "N");
cStmt.setString(11, "English");
cStmt.setString(12, "N");
cStmt.setString(13, "N");
cStmt.setString(14, "N");
cStmt.setString(15, "N");
cStmt.setString(16, "N");
cStmt.setString(17, "N");
cStmt.setString(18, "07");
cStmt.setString(19, "10");
cStmt.setString(20, "juache0");
java.sql.Date dt2 = new java.sql.Date(2014,10,20);
java.sql.Date dt3 = new java.sql.Date(2014,10,20);
cStmt.setDate(21, dt2);
cStmt.setDate(22, dt3);
cStmt.setString(23, "userid0");
cStmt.setString(24, "");
cStmt.setString(25, "");
cStmt.setString(26, "");
java.math.BigDecimal bg1 = new java.math.BigDecimal(10);
cStmt.setBigDecimal(27, bg1);
cStmt.setString(28, "userid");
cStmt.setString(29, "userid");
int hadResults = cStmt.executeUpdate();
Your help is greatly appreciated.
I am executing the above using Jconnect3.0 driver, inside WebSphere Application Server V8.0
Thanks
NagsNOTE: I don't work with JDBC/jConnect so (at this point) just some questions ...
1 - are you sending this to ASE, ASA, IQ, or some other RDBMS?
2 - what is the value of <schemaname>?
3 - do you have other prepareCall() instances that successfully call a stored proc? [would be interesting to see if there's a difference in the format of the calls]
A quick google search shows a couple ways to submit a stored proc execution to the RDBMS, with the format depending on the format expected by the target RDBMS.
I'm wondering if you really need/want the parentheses around the argument list, ie, what happens if you change
from
-- parentheses around args
EXEC <dbName>.<schemaName>.<SPName> ( ?,?,?,?,?,...,? )
to
-- no parentheses around args
EXEC <dbName>.<schemaName>.<SPName> ?,?,?,?,?,...,?
In ASE if I wrap the parameters in parentheses I get the same error you're getting:
================== w/ parentheses => error
1> sp_who (sa)
2> go
Msg 102, Level 15, State 1:
Server 'CC1_V1', Line 1:
Incorrect syntax near 'sa'. <<=== sa == @p0 ??
================== w/out parentheses => works
1> sp_who sa
2> go
fid spid status loginame origname ...
0 17 running sa sa ...
================== -
Getting an strange error in "PluginPrefix.pch" while compiling a plugin code with InDesign CS4 SDK.
Hi everybody,
Currently trying to compile/build the existing Plugin code (C++) with InDesign CS4 SDK on my Mac OS X 10.5 machine but getting following strange errors.
/Volumes/MAC Extended/Inbetween Extended/Visual Studio/Adobe InDesign CS4 SDK/source/precomp/gcc/PluginPrefix.pch:26:27: error: MemoryStatics.h: No such file or directory
/Volumes/MAC Extended/Inbetween Extended/Visual Studio/Adobe InDesign CS4 SDK/source/precomp/gcc/PluginPrefix.pch:39:30: error: PluginBuildFlags.h: No such file or directory
/Volumes/MAC Extended/Inbetween Extended/Visual Studio/Adobe InDesign CS4 SDK/source/precomp/gcc/PluginPrefix.pch:40:28: error: AnsiBasedTypes.h: No such file or directory
/Volumes/MAC Extended/Inbetween Extended/Visual Studio/Adobe InDesign CS4 SDK/source/precomp/gcc/PluginPrefix.pch:41:26: error: ShukHeaders.cp: No such file or directory
Though above mentioned files are present at the following directory
/Volumes/../../../Adobe InDesign CS4 SDK/source/precomp/common/
Note : However initially I did not find “MemoryStatics.h” and “AnsiBasedTypes.h” files in the installed SDK directory. I have downloaded them from the net and copied those into the above mentioned directory.
I am not much familiar with Mac OS environment and compiling/building C++ code with Xcode. Can anyone help me to resolve this issue (might be very trivial and related to Xcode project configuration) ?Thanks for the quick response,
Yes, current build settings include path shortcuts as mentioned below and it also contains “$(CS_SDK_PATH)/source/public/includes” path in HEADER_SEARCH_PATHS settings. But still I am getting the same error: MemoryStatics.h: No such file or directory
CS_SDK_PATH= /Volumes/MAC Extended/Inbetween Extended/Visual Studio/Adobe InDesign CS4 SDK
CS_SDK_PRJ_PATH=/Volumes/MAC Extended/Inbetween Extended/Visual Studio/InBetweenDev/Projects/InBetweenCS/IBClientPluginCS3/prjCS4/mac
Just for clarification : my Plugin code /project files are not inside the InDesign SDK (build/mac/prj). All the plugin project is outside of the InDesign SDK directory. Thus above mentioned CS_SDK_PATH and CS_SDK_PRJ_PATH are completely different.
Is it expected that the plugin code/project files should be inside the InDesign SDK/build/mac/prj directory only ? or is it okay if we put it in the completely another directory structure and modify the SDK_PRJ_PATH accordingly (as in my case) ?
Please let me know if you want me to elaborate the situation further. -
Strange Errors from Import Server on Schema-based maps for repeating nodes
I have already posted one thread about this, but perhaps some more in-depth information is required:
We have uploaded our schema into the console, and have mapped the following multi-node file to it:
CUSTOMER <repeating node>
MDM_CUST (new Customer number returned)
CUSTOMER(mapped back from XI for RECORD MATCHING)
CREATE_DATE (text field)
CONTACT<repeating node>
CONTACT_NO (RECORD MATCHING : NON-QUALIFIER)
CONTACT_SAP_NO (QUALIFIER)
[NOTE: There are other qualifers for CONTACT, but only this one
qualifier is being returned and is the only field that would and should be updated.
The other fields should be left alone. However, it appears to overwrite EVERYthing
with NULL other than these two fields. The CONTACT_NO is the sole qualifer on
the table. It is a calculated field that equals the Auto-ID that is also produced on
the table - but obviously not mapped.]
PARTNER<repeating node>
CUSTOMER_NO (RECORD MATCHING : NON-QUALIFER)
PARTNER_FUNC (NON-QUALIFIER - Code given to lookup from PARTNER_FUNCTION table which has Code and Desc)
PARTNER_NO (NON-QUALIFIER)
DEFAULT_PARTNER_FLAG (QUALIFIER)
<CLOSE CUSTOMER NODE>
In the Customer main table, all records are matched on CUSTOMER. The CONTACT_NO non-qualifer is matched to the CONTACT qualified lookup table directly since it is the only available non-qualifier. For the PARTNER table, the three qualifiers are mapped and then a compound field is created to map to the PARTNER table entry.
We have the Configurations set at:
Default Multi-Valued Update: Replace
Default Qualified Update: Replace
Default Matching Qualifiers: None
Our record matching is: Create / Update(ALL MAPPED FIELDS) / Update(ALL MAPPED FIELDS)
When the map is reused, the repeating nodes are all recognized, be it one node or many. However, when the map is reused, it does not automatically map the values for many of the Partner fields (nor the compound field) though the fields are correctly mapped.
Also, when we attempt to use Import Server to automate the mapping, we use the mdis.ini set to
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
We get a very strange error saying that :
[code]Encountered a pre-SP4 map. The map needs to be upgraded to SP4.
Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map.[code]
Could it be that our MDM 5.5 SP4 is not compatible with schemas generated with XI v.7 SP9?
All of our MDM is 5.5 SP4. It makes no sense that we would get THIS kind of error. Also, I am questioning our combination of these and other configurations since it doesn't always seem to do what it shouldHi Donald,
this sounds good so far. Just a short hint: you've set "Default Qualified Update: Replace". This explains why Import server "appears to overwrite EVERYthing
with NULL other than these two fields.". The reason is the replace. A replace means that the old values are completely deleted and only the new incoming ones are stored. I'd suggest to use any of the Update possibilities.
Note: the definitions you set in in the record matching step are mainly for the new records in the main table! Records in qualified look ups are handled differently! If you open your map in Import Manager, switch to tab "Map Fields/Values". Select a field that is your non qualifier. Right-Click on it and choose "Set qualified update" from the context menu. Now you can define which qualifiers can be used for the qualified look up matching. And you can define as well what should happen with new and/or existing records.
Regarding the value mapping: do you use keymapping? Or do you use simple values only? Do you save the map everytime you add a new value mapping?
Regarding the issue "Encountered a pre-SP4 map. The map needs to be upgraded to SP4. Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map". This sounds very likely like a bug in MDIS and should be reported to SAP!
Hope that helps
Michael -
Strange error in JDeveloper 11.1.1.0 Technology Preview 4
I download starter workspace from
http://www.oracle.com/technology/oramag/oracle/08-jul/o48frame.html
A Home for Your Chrome and open in JDev 11g TP4 then go to Application Resources and change scott connection Oracle JDBC and test the connection I get Success!.
when Run HRModule and select Departments to show data I get this error
(oracle.jbo.SQLStmtException) JBO-27122: SQL error during statement preparation. Statement: SELECT Dept.DEPTNO, Dept.DNAME, Dept.LOC FROM DEPT Dept
If press Details button in error I get
(oracle.jbo.SQLStmtException) JBO-27122: SQL error during statement preparation. Statement: SELECT Dept.DEPTNO, Dept.DNAME, Dept.LOC FROM DEPT Dept
----- Level 1: Detail 0 -----
(java.sql.SQLException) ORA-01866: the datetime class is invalid
In Log:
C:\jdevstudio1111\jdk\bin\javaw.exe -client -classpath C:\jdevstudio1111\BC4J\jlib\bc4jtester.jar;C:\jdevstudio1111\BC4J\lib\bc4jsyscat.jar;C:\jdevstudio1111\BC4J\lib\db-ca.jar;C:\jdevstudio1111\BC4J\jlib\bc4jwizard.jar;C:\jdevstudio1111\jlib\jdev-cm.jar;C:\jdevstudio1111\lib\xmlparserv2.jar;C:\jdevstudio1111\jlib\ohj.jar;C:\jdevstudio1111\jlib\help-share.jar;C:\jdevstudio1111\jlib\share.jar;C:\jdevstudio1111\jlib\jewt4.jar;C:\jdevstudio1111\jlib\oracle_ice.jar;C:\jdevstudio1111\jlib\ojmisc.jar;C:\jdevstudio1111\ide\lib\idert.jar;C:\jdevstudio1111\ide\lib\javatools.jar;C:\jdevstudio1111\jdk\jre\lib\rt.jar;C:\jdevstudio1111\jdk\jre\lib\i18n.jar;C:\jdevstudio1111\jdk\jre\lib\sunrsasign.jar;C:\jdevstudio1111\jdk\jre\lib\jsse.jar;C:\jdevstudio1111\jdk\jre\lib\jce.jar;C:\jdevstudio1111\jdk\jre\lib\charsets.jar;C:\jdevstudio1111\jdk\jre\classes;C:\jdevstudio1111\mywork\FrameworksJulAug2008\.adf;C:\jdevstudio1111\mywork\FrameworksJulAug2008\Model\classes;C:\jdevstudio1111\BC4J\lib\adf-share-support.jar;C:\jdevstudio1111\BC4J\lib\adf-sh are-ca.jar;C:\jdevstudio1111\BC4J\lib\adf-share-base.jar;C:\jdevstudio1111\jlib\identitystore.jar;C:\jdevstudio1111\BC4J\lib\adfm.jar;C:\jdevstudio1111\BC4J\lib\groovy-all-1.0.jar;C:\jdevstudio1111\jlib\commons-el.jar;C:\jdevstudio1111\jlib\jsp-el-api.jar;C:\jdevstudio1111\jlib\oracle-el.jar;C:\jdevstudio1111\jlib\resourcebundle.jar;C:\jdevstudio1111\lib\java\api\jaxb-api.jar;C:\jdevstudio1111\lib\java\api\jsr173_api.jar;C:\jdevstudio1111\j2ee\home\lib\activation.jar;C:\jdevstudio1111\lib\java\shared\sun.jaxb\2.0\jaxb-xjc.jar;C:\jdevstudio1111\lib\java\shared\sun.jaxb\2.0\jaxb-impl.jar;C:\jdevstudio1111\lib\java\shared\sun.jaxb\2.0\jaxb1-impl.jar;C:\jdevstudio1111\BC4J\lib\adfshare.jar;C:\jdevstudio1111\adfdt\lib\adf-dt-at-rt.jar;C:\jdevstudio1111\adfdt\lib\adf-transactions-dt.jar;C:\jdevstudio1111\adfdt\lib\adfdt_common.jar;C:\jdevstudio1111\mds\lib\mdsrt.jar;C:\jdevstudio1111\j2ee\home\lib\servlet.jar;C:\jdevstudio1111\jdbc\lib\ojdbc5dms.jar;C:\jdevstudio1111\jlib\commons-c li-1.0.jar;C:\jdevstudio1111\jlib\xmlef.jar;C:\jdevstudio1111\jlib\dms.jar;C:\jdevstudio1111\j2ee\home\lib\oc4j-unsupported-api.jar;C:\jdevstudio1111\lib\xml.jar;C:\jdevstudio1111\lib\java\api\cache.jar;C:\jdevstudio1111\j2ee\home\lib\pcl.jar;C:\jdevstudio1111\ucp\lib\ucp.jar;C:\jdevstudio1111\lib\java\shared\oracle.javatools\11.1.1.0.0\dafrt.jar;C:\jdevstudio1111\lib\java\shared\oracle.javatools\11.1.1.0.0\javatools-nodeps.jar;C:\jdevstudio1111\j2ee\home\jazn.jar;C:\jdevstudio1111\j2ee\home\jazncore.jar;C:\jdevstudio1111\j2ee\home\jps-api.jar;C:\jdevstudio1111\j2ee\home\jps-common.jar;C:\jdevstudio1111\j2ee\home\jps-internal.jar;C:\jdevstudio1111\j2ee\home\jps-fmw.jar;C:\jdevstudio1111\j2ee\home\jps-unsupported-api.jar;C:\jdevstudio1111\j2ee\home\lib\jacc-api.jar;C:\jdevstudio1111\j2ee\home\lib\security-api.jar;C:\jdevstudio1111\jlib\orai18n.jar;C:\jdevstudio1111\jlib\ojdl.jar;C:\jdevstudio1111\dvt\lib\dvt-jclient.jar;C:\jdevstudio1111\dvt\lib\dvt-utils.jar;C:\jdevstudio1111 \jlib\LW_PfjBean.jar; oracle.jbo.jbotester.MainFrame -X 11A6DAF0C7F -H "jar:file:/C:/jdevstudio1111/jdev/doc/studio_doc/ohj/bc4j_f1.jar!/bc4j_f1.hs"
Jun 9, 2008 5:16:08 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory handleLocation
WARNING: [XmlConfigurationFactory.handleLocation] Exception occurred when handling origLocation=/C:/jdevstudio1111/j2ee/home/config/system-jazn-data.xml : no protocol: /C:/jdevstudio1111/j2ee/home/config/system-jazn-data.xml
Jun 9, 2008 5:16:08 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory handleLocation
WARNING: [XmlConfigurationFactory.handleLocation] Exception occurred when handling origLocation=/C:/jdevstudio1111/j2ee/home/config/system-jazn-data.xml : no protocol: /C:/jdevstudio1111/j2ee/home/config/system-jazn-data.xml
[JpsAuth] For permisson ( CredentialAccessPermission credstore.provider.credstore.ADF.anonymous#scott read), domain that failed: ProtectionDomain cs(file:/C:/jdevstudio1111/BC4J/lib/adf-share-support.jar), []
If I build new JSF page and drag and drop Departments to show as read only table when run page I show the Table without data but only statement
Fetching Data…
Please if anybody can help me and tell me where is the problem.
Note1: This error happen in all application created in Jdev 11g TP4 I have Jdev 10g and it is working perfect.
Note2:In Log Please show this message:
[JpsAuth] For permisson ( CredentialAccessPermission credstore.provider.credstore.ADF.anonymous#scott read), domain that failed: ProtectionDomain cs(file:/C:/jdevstudio1111/BC4J/lib/adf-share-support.jar), []
Best Regards
Zuhair JawishHi Frank,
I unzip Jdev 11g in C:\jdevstudio1111
and the workspace in C:\jdevstudio1111\mywork\FrameworksJulAug2008
no space in the path of Jdev and the application
I think it is strange error i format my machine for this error but i did not resolve the problem.
maybe the problem in some environment variables.
Thanks
Zuhair -
Strange error in SUM function in XI
Hi geeks,
We are encountering a strange issue in SUM functionality in XI.
The Scenario is :
We have a pipe delimited source file and INVOIC01 idoc as target. each line in the source file will create a segment E1EDP01 in the target IDOC.
All the values given in the file should be summed and mapped to E1EDS01 segment in the idoc.
In one such strange case the sum of the values generated by the SUM function in XI is 2 cents lesser what we manually calculate using Calculator or Excel . There are about 100+ items in the file. This not the case always it happens once in a while.
Have any of you faced such strange errors. If yes please throw some light on the solution for this issue.
Thanks,
NoorulHi folks,
Thanks for your help. I solved this by writing my own code
double sum = 0;
String value;
for (int i= 0; i< a.length; i++)
sum = sum + Double.parseDouble(a<i>);
value = Double.toString(sum);
BigDecimal bg1 = new BigDecimal(value);
BigDecimal bg2 = bg1.setScale(2, BigDecimal.ROUND_HALF_DOWN);
result.addValue(bg2.toString()); -
Strange error in BAPI_BUSINESS_PARTNER_CHANGE
Hello,
trying to use the function module BAPI_BUSINESS_PARTNER_CHANGE i get very strange error. I try to change the authorization group of the Business Partner,
so no tables parameters except return are filled. All of obligatory fields are filled with values from BUT000 Table, also PARTNERGENATTRBT and PARTNERGENATTRBTX Imports are filled. If i try to execute the function module i get the message R1 105 (Activity category &1 does not exist) with no value in the field &1, so the full message is really only "Activity category does not exist".
Can someone help me with this problem, please?
Thank you very much in advance
AndreyHello,
the function is used like this:
DATA: ls_attrib LIKE bapi_bp_atrbut_1,
ls_attribx LIKE bapi_bp_atrbut_1_x,
LOOP AT lt_but000.
Selektieren der Berechtigungsgruppe anhand der Tabelle TB037
SELECT SINGLE augrp FROM tb037
INTO lv_augrp
WHERE auobj = 'BUPA' AND
augrp = lt_but000-bu_group.
IF sy-subrc = 0.
ls_attrib-authgroup = lv_augrp.
ls_attribx-authgroup = 'X'.
Wenn sy-subrc <> 0 => kein Eintrag in der Tabelle =>
Berechtigungsgruppe soll auch leer bleiben
CALL FUNCTION 'BAPI_BUSINESS_PARTNER_CHANGE'
EXPORTING
businesspartner = lt_but000-partner
partnercategory = lt_but000-type
partnertype = lt_but000-bpkind
partnergroup = lt_but000-bu_group
partnerextno =
partnergenattrbt = ls_attrib
partnergenattrbtx = ls_attribx
PARTNERGENATTRBTADM =
PARTNERGENATTRBTADMX =
TABLES
partneraddr =
partneraddrx =
PARTNERADDRUSE =
PARTNERADDRUSEX =
PARTNERBANKATTR =
PARTNERBANKATTRX =
PARTNERCCATTR =
PARTNERCCATTRX =
return = lt_return
DESCRIBE TABLE lt_return LINES lv_lines.
IF lv_lines = 0.
ADD 1 TO lv_count_succ.
ELSE.
ADD 1 TO lv_count_err.
WRITE: / 'Geschäftspartner: ', lt_but000-partner, ' konnte nicht aktualisiert werden!'.
ENDIF.
COMMIT WORK.
CLEAR: ls_attrib, ls_attribx.
ELSE.
ADD 1 TO lv_count_noact.
ENDIF.
ENDLOOP.
Thank You -
Strange error in SQL 2014 - is it a bug?
Hi everybody,
I was writing a query to help in a recent thread and then got a very strange error:
declare @dt date = CURRENT_TIMESTAMP;
select convert(varchar(10), 103, @dt);
Run this code in SQL 2014 and see if it works for you or not. In BOL I didn't find anything indicating that CONVERT is not going to work with DATE type. Can you point me to BOL explaining the problem or confirm it's a bug?
UPDATE. Same error in SQL 2012. Does it mean I can not use CONVERT function with DATE type or some styles are not available? If yes, which codes I can use and which I can not?
UPDATE 2. I tried a few different styles and I got the same error message every time. That's new to me, looks like DATE type is not supported by CONVERT function at all?
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
My TechNet articlesIt should be declare @dt date = CURRENT_TIMESTAMP;
select convert(varchar(10), @dt,103);Correct me if I'm wrong.--Prashanth
Maybe you are looking for
-
What is the last version of Final Cut available for the G5 PPC & OS X 10.5?
What was the last version of Final Cut available for the G5 PPC running OS X Leopard? I'd like to get a copy (from ebay or some other vendor).
-
Strange LOV behaviour in new rows (UIX)
Hi all, we are using UIX for a JHS implementation project and came across a "JHS-00107: Table data are out of date, please requery" error while testing our JHS-generated forms. The problem arises in a table with multi-row-insert enabled where some of
-
Special Leder and FI balance sheet do not reconcile
Hi, I have issues with reconciling special ledger and FI balance sheet accounts. The month-end process GWUL (currency translation for SPL) was executed and business users did not execute F.05 for FI, probably this was missed out more than one month.
-
Hi frnds, i hav to do some calculations for invoice quantity. Units still to be invoiceIf not history (not matching records of EKPO in EKBE) INVOI_QTY = order_quantity = EKPO-MENGEIf there is history:INVOI_QTY = Order_quantity sum_of_I
-
I bought the Office 2008 student version (3 liscences) and then updated it to 2011 by web. I installed it on my new iMac. Now I am going to buy and Air and want to install the 2008 version and update to 2011 again. I thought I read somewhere that thi