(!) just another weblog
Weblogic Integration throws unbelievable errors sometimes, even when you haven’t changed squat.
I deleted some of the suspended and frozen transactions and it worked on one particular server.
(though i am still struggling with another one)
In any case,
WLI_PROCESS_INSTANCE_INFO.PROCESS_STATUS column values and meanings.
0 = Running
1 = Aborted
2 = Suspended
3 = Complete
4 = Frozen
5 = Terminated
Just logged in to the WP dashboard for a pleasant surprise of a fresh new UI. i likes!
Very nice, WP. keep it up.
on a side note, I should blog often.
UPDATE!
Before you try to run the scripts, there’s a simple resolution: try restarting the DB instance. Maybe that’s what is causing this error. Sometimes there is some issue with the TNS Listener and that might throw this error.
After a loooooong time spent debugging this issue, i have found the solution.
So the situation is this. you are trying to start up the Weblogic Integration domain and it just won’t start up. It was working fine the last time you looked at it. You didn’t change a thing. No deployments, no config changes, no nothing. But now when it is starting, you get some weird errors like this:
<000000>
com.bea.wli.init.WLIDBCreateException: Could not execute (possibly among others) CREATE statement for INDEX IX_WLI_MESSA
GE_BROKER_DYNAMIC: CREATE INDEX IX_WLI_MESSAGE_BROKER_DYNAMIC ON WLI_MESSAGE_BROKER_DYNAMIC( HASH_ID)
at com.bea.wli.init.WLIDBCreate$WLIDataSource.createDBObjects(WLIDBCreate.java:671)
at com.bea.wli.init.WLIDBCreate.init(WLIDBCreate.java:1008)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Truncated. see log file for complete stacktrace
Your boss won't believe you when you say that you didn't change a thing, but shit like this happens.
You try debugging the shit outta this WLIDBCreate.class file (after you spend hours searching where the shitty jar file is in which it is sitting pretty... btw, it is jpd.jar, located in weblogic92/server/lib in your weblogic 9.2 install location).
okay, i get it. i'm getting to the damn resolution.
The thing is, it is the DB that's messed up. How? i have no idea. But it has.
So if you run this sql file that i have compiled, you should be all set and ready to hit the ground running.
Obv. you are running this at your own risk, as defined in my disclaimer section (conveniently worded).
but this shit works.
In case you are wondering how i debugged it, i should say it wasn't all that simple.
but to cut a long story short, when i tried to create a new domain, i used the 'Run Scripts' command located just after the screen where you configure your datasources. I let it use the default pointbase server, then i copied the sql commands it ran, cleaned the shit out from it, tweaked it so that it runs on oracle, and then finally ran it to restore it to its former glory.
So there goes nothing... best of luck!
…is similar to the difference between hanging up on a telephone conversation and actually killing the caller on the other end. Both end the conversation, but the end results are a little different.
…as read somewhere online
“1 kilogram of matter confined to 1 liter of space can perform at most 1051 operations per second on at most 1031 bits of information.”
Maximizing usage of available power capacity is the key!
Power subscription at the facility level seems promising (whatever that means)
large systems should utilise power efficiently.
Q and A going on…
… almost ending, so i guess i can switch this off.
Oh
I forgot.
Conclusion (from Luiz’s slides):
Power/ energy efficient and fault tolerance are central to the design of large scale computing systems today.
Technology trends are likely to make them even more relevent in the future, increasingly affecting smaller scale systems.
Power efficient datacenters:
Idle machines also consume power.
Compared to humans, power consumption for machines is waay high, since humans use less power while resting, but high while performing. Machines don’t have that high gap between idle and high activity power consumptions.
“Fault Tolerance systems lie.
Disk failures: Failure rates < 1% per year.
Study conducted proves that irrespective of age, disk failed... (couldn't catch that)
also, Temperature is not a major criterion for disk failures.
SMART disks…self monitoring. (!)
Even then, 56% of disks failing had no predictable behavior.
Well, more bad news: 70% of drives survive for 8 months. (So after 8 months, no predictability). So, SMART is not a great solution.”
So on stage, Luiz Barroso!
“Single fault will bring down the large scale computer systems that use shared memory programming model, and fault containment is complex. A difficult problem”
“The MHz race (Moore’s law) just makes the machines faster… the programs coded 10 yrs ago automatically run faster…
Additionally, power consumption increases and temperature management is a concern.
Ergo, cost increases with time.
So now, the equation becomes higher computing power = higher power bills= higher costs”
