Persisting a trigger with weblogic time services

Hello,
I'm using Weblogic v4.51
Does weblogic provide a way to persist triggerable events so that if the
server is shut down and restarted, the triggerable events are still
scheduled?
Or do I have to write my own persistence system for scheduled events?
any comments are appreciated,
thanks,
Tom

Yes, you are in true.
But, I can't understand it. Weblogic allow to execute a number of threads that
couldn't go far in execution (they haven't resources) ... and maintains them runnable.
But, the thread that could progress in their execution (they have the resources)
aren't runnables ...
The only solution is the one you say ... but I think the way weblogic schedules
the execute threads isn't a good way.
Thanks
"Adam Messinger" <[email protected]> wrote:
>
"jlglez" <[email protected]> wrote in message
news:3b9899a4$[email protected]..
Ok. I have a problem with concurrency and locks with weblogic ... hereis
my thread
dump:
Number of Threads of my Server: 15
Number of Threads of my Application: 25
LDAPPool: 5
Yes, I know the second is bigger than the first. I try to create anscenario of
a number of apps over the same server.It looks like the majority of your threads are waiting while attempting
to
get an LDAP connection. Make that pool bigger (same size as number of
execute threads).
Cheers!
Adam

Similar Messages

WebLogic Time Service

Hi,
I've created a time service on the server, which gets activated on
startup and repeatly occurs at some given interval. However, I need to
stop the timer and restart it again when the time interval is changed.
Is it possible to do that without bringing down the server?
Thanks,
TomyD

Mario -
I believe the way it works is you call the schedule () method of your WL
Time Services implementing object first. For example:
// Obtain a T3Services factory
T3ServicesDef t3 = getT3Services ();
// Request a ScheduledTrigger from the factory. Use
// this class for scheduling and execution
std = t3.time().getScheduledTrigger(this, this);
// Start the ball rolling
std.schedule();
Your schedule method would specify the point of time in the future in
which you are interested.
Your trigger method, when invoked, should set some instance variable in
your class. Your schedule method will be invoked after your trigger
method completes. When your schedule method is invoked, it should check
the instance variable and if it has been set, the schedule method should
return 0 to prevent the trigger from being called again.
Make sure that the schedule method is correctly setting the returned
long.
Oh --- your class should be implementing the Schedulable and Triggerable
interfaces, in case you were using something else. I agree that the
documentation for this feature seems pretty confusing.
Peter
"Mario B. Jones" wrote:
>
List,
As you can tell, I've been spending alot of time playing with Weblogic
time service lately, and needless to say, I've been running into alot of
roadblocks.
Question.
How in the heck do you implement the time api to perform a "one-time"
trigger for some point of time in the future? All of the examples, api
documentation, etc talks you through the necessary to perform
"recurring" actions. But nothing on one time actions. I have tried
several different variations but cannot get it done. Seems like the
trigger will immediately fire the first time but can be delayed for
future iterations till a specified point of time in the future using
java.util.Date methods.
Help!
Thanks in advance...

WebLogic Timer services.

WebLogic has deprecated Timer services with version 6.1 and recommend using Flux.
What is the rationale behind that? What do other scheduling services offer over the
standard JDK java.util.Timer class where I can kick of scheduled tasks?
Thanks ahead of time for your response.
Regards,
Amit

.... but if done from startup, a timer is not in an app and thus can't see
the app's environment?
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]..
Yes, that should work fine. What is the error?
-- Rob
Satish Yellanki wrote:
Hi,
I am trying to use the weblogic timer services.
I implemented the TriggerDef interface and deployed
the trigger using "Scheduler" and "Trigger" classes.
(Server-side triggers.)
However, when the trigger is run, will I be able to
do a InitialContext() without any parameters and use
it to do JNDI lookup? I am running into an error doing
that and am not sure if I am doing the right thing.
Thanks,
Satish--
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com

Best practice using Using the WebLogic Timer Service

Hi,
We have a stateless session bean having a method which needs to be called lezs
say every 10 Seconds. I think the WebLogic Timer Service (JMX) should exactly
fit in this problem. So I would write a small class implementing the interface
NotificationListener which will receive the notification. The listener I would
register in my startup class.
This brings up some questions:
Could this class be a inner class of the SessionBean and directly calling the
method on the bean ?
Has it to be a more independent class gettting an initiali context, getting local
home, etc. etc. and then executing the method on the received Stub ? If yes can
it keep the Stub betwean the interval without releasing ?
Has someone experiance in this area ?
Regards
Tomy

Actually, it's bad practice to use break anywhere other than in conjunction with a switch statement.Presumably, if you favour:
boolean test = true;
while (test)
test = foo && bar;
if (test)
}overfor (;;)
if (! ( foo && bar) ) break;
}then you also favour
boolean test = foo && bar;
if (test)
}overif (foo && bar)
}Or can you justify your statement with any example which doesn't cause more complexity, more variables in scope, and multiple assignments and tests?

Monitoring Weblogic Time Service

Hello
I built a number of java classes that implemented ScheduleDef and
Triggerdef.
Then these classes are scheduled using WebLogic Time Service.
The question is :
Is there a way to query WLS to find out how many of these classes are
currently
being scheduled? We need to find out which one are no longer running in the
system
so we can reschedule them. But we also need to know if one is already
scheduled and
therefore disallow the ability to schedule a 2nd instance in the server.
Thanks

They did state a reason. They expect these services to become part of J2EE.
You can still use them, or check out something like Flux from Sims
Computing.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"James McGovern" <[email protected]> wrote in message
news:[email protected]..
BEA has deprecated the time services classes without stating any reason.
Hopefully they will step up and come up with a replacement.

Weblogic singleto with weblogic timer

Pls give some sample for using both weblogic singleton and weblogic timer.

weblogic sibgleton should invoke weblogic timer service?

Storing by trigger with pre time and post time

hi,
I am acquiring sample rate of 1000 samples/sec. i am using digital inputs for storing start and stop. when the digital input is high it should start storing and accordingly user has to specify the number of samples or time and data appended before storing starting. i.i pre time or pre samples has to be added before start storing the data. also for stop storing the data post time or samples has to be added.
how to do this..? can i have a sample vi?
Regards,
Balaji DP

may be its helpful to you,By using value signaling we can generate the event whenever true occur in Digital input channel (daq),in that particula event case we can append the old data from file like tdms etcc.
Attachments:
1.png ‏14 KB

WL Time Service Questions

Hello -
A few questions about Weblogic Time Services:
1. What is BEA's policy on supporting this functionality for future
Weblogic releases?
2. Will BEA be supporting the JMX javax.management.timer functionality
as a replacement in future releases?
3. What happens if an EJB schedules a trigger and the application
containing the EJB is not deployed at the time of the trigger (or has
been redeployed in between)?
4. Any suggestions for persistence of scheduled triggers between
application deployments?
Can anyone suggest a J2EE-compliant alternative to these services?
Thanks
Peter

Peter Mularien wrote:
1. What is BEA's policy on supporting this functionality for future
Weblogic releases?I believe it will be deprecated in the next major release (although it
will remain around for at least 2 releases after deprecation).Do you all have anything planned yet to replace it?There is an internal proposal for "TimerDrivenBeans". I wish JavaSoft would
just define an appropriate J2EE API for this, and be done with it.
>
>
2. Will BEA be supporting the JMX javax.management.timer functionality
as a replacement in future releases?This is a possibility. In fact, it probably works today. There is
also the java.util.Timer API. I'm not too keen on it, as it spawns a
thread, rather than having an ability to use a thread pool.I note that JBoss is one app server which does support the
javax.management.timer functionality. But they seem to have embraced JMX
even more fully than Weblogic did in 6.x.Yes, I noticed that too.
>
>
>>>
3. What happens if an EJB schedules a trigger and the application
containing the EJB is not deployed at the time of the trigger (or
has been redeployed in between)?If the bean is not present, I suppose the timer will receive an
exception (and if it's not caught, I believe the timer will be
cancelled). If it's redeployed, it should just work, but I'm not 100%
sure.I suppose I'll try it out and report back here.
4. Any suggestions for persistence of scheduled triggers between
application deployments?You'd have to have your own persistence mechanism... we don't have a
solution for this. Except for using JMS messages with birth times.I noticed that JMS birth times was a new feature in 6.1. That is a
Weblogic-specific feature, though, and not covered in the JMS spec,
correct?Yes, WebLogic specific.
It wouldn't be terribly difficult for us to wrap the WL Time Service
functionality with a persistence layer, either.I think that would be a really nice feature.
>
Can anyone suggest a J2EE-compliant alternative to these services?Our JMS service has an ability to have a cron-like message which can
drive a MessageDrivenBean, or, I believe, a message that has a "birth
time" which will cause the message to be delivered at a particular time
in the future.I'll explore that option as well. Thanks for your detailed responses.
Peter

Unable to pass xmlbeans object in weblogic web services using OEPE

Migrating Weblogic web services from Weblogic Workshop 10.3 to Oracle Enterprise for Eclipse...Passing xmlbean generated types in arguments of webservice call
How to work around the following errors? I do not have this error when in workshop 10.3 only in OEPE eclipse
"oracle.eclipse.tools.webservices.compiler.CompilationException: Errors: JAX-WS web services must not have xmlBean parameter or return type"
PLease note that I want DocType to be xmlbeans generated or inherited from org.apache.xmlbeans.XmlObject....
@WebMethod
     public void upload(String filename, DocType doc) {
Hi, I have legacy codes from Weblogic workshop 10.1 and 10.3.....
I am able to compile and run in Weblogic workshop 10.3 by passing the xmlbean generated DocType as arguments in the web services call.... but why am I not able to do this in Oracle Enterprise for Eclipse OEPE......
If I were to generate the web service from teh wsdl...it will generate it's own DocType.class in the jar files and not use the xmlbean generated class one....
How to get iOEPE to generate the classes in build\jws\ for
testWSService-annotation.xml
weblogic-webservices.xml etc like in workshop
How can I resolve this??? Am I stuck with Workshop on this?? How to work around??
Any help or clarifications would be much appreciated.
Inside testWS.java,
package ws;
import java.io.File;
import javax.jws.*;
import org.example.doc.DocType;
@WebService
public class testWS {
     @WebMethod
     public void upload(String filename, DocType doc) {
          try {
               doc.save(new File(filename));
          catch(Exception e) {
               System.out.println(e);
Inside xmlbeans generated DocType.java.....and DocTypeDocuments.java
* XML Type: DocType
* Namespace: http://www.example.org/doc
* Java type: org.example.doc.DocType
* Automatically generated - do not modify.
package org.example.doc;
* An XML DocType(@http://www.example.org/doc).
* This is a complex type.
public interface DocType extends org.apache.xmlbeans.XmlObject
public static final org.apache.xmlbeans.SchemaType type = (org.apache.xmlbeans.SchemaType)
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(DocType.class.getClassLoader(), "schemaorg_apache_xmlbeans.system.testWSTypeSystem").resolveHandle("doctypec217type");
* Gets the "element1" element
java.lang.String getElement1();
* Gets (as xml) the "element1" element
org.apache.xmlbeans.XmlString xgetElement1();
* Sets the "element1" element
void setElement1(java.lang.String element1);
* Sets (as xml) the "element1" element
void xsetElement1(org.apache.xmlbeans.XmlString element1);
* Gets the "element2" element
java.lang.String getElement2();
* Gets (as xml) the "element2" element
org.apache.xmlbeans.XmlString xgetElement2();
* Sets the "element2" element
void setElement2(java.lang.String element2);
* Sets (as xml) the "element2" element
void xsetElement2(org.apache.xmlbeans.XmlString element2);
* A factory class with static methods for creating instances
* of this type.
public static final class Factory
public static org.example.doc.DocType newInstance() {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance( type, null ); }
public static org.example.doc.DocType newInstance(org.apache.xmlbeans.XmlOptions options) {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance( type, options ); }
/** @param xmlAsString the string value to parse */
public static org.example.doc.DocType parse(java.lang.String xmlAsString) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xmlAsString, type, null ); }
public static org.example.doc.DocType parse(java.lang.String xmlAsString, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xmlAsString, type, options ); }
/** @param file the file from which to load an xml document */
public static org.example.doc.DocType parse(java.io.File file) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( file, type, null ); }
public static org.example.doc.DocType parse(java.io.File file, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( file, type, options ); }
public static org.example.doc.DocType parse(java.net.URL u) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( u, type, null ); }
public static org.example.doc.DocType parse(java.net.URL u, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( u, type, options ); }
public static org.example.doc.DocType parse(java.io.InputStream is) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( is, type, null ); }
public static org.example.doc.DocType parse(java.io.InputStream is, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( is, type, options ); }
public static org.example.doc.DocType parse(java.io.Reader r) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( r, type, null ); }
public static org.example.doc.DocType parse(java.io.Reader r, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( r, type, options ); }
public static org.example.doc.DocType parse(javax.xml.stream.XMLStreamReader sr) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( sr, type, null ); }
public static org.example.doc.DocType parse(javax.xml.stream.XMLStreamReader sr, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( sr, type, options ); }
public static org.example.doc.DocType parse(org.w3c.dom.Node node) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( node, type, null ); }
public static org.example.doc.DocType parse(org.w3c.dom.Node node, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( node, type, options ); }
/** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
public static org.example.doc.DocType parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xis, type, null ); }
/** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
public static org.example.doc.DocType parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xis, type, options ); }
/** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
public static org.apache.xmlbeans.xml.stream.XMLInputStream newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream xis) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
return org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newValidatingXMLInputStream( xis, type, null ); }
/** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
public static org.apache.xmlbeans.xml.stream.XMLInputStream newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream xis, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
return org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newValidatingXMLInputStream( xis, type, options ); }
private Factory() { } // No instance of this class allowed
Edited by: user11079482 on Jan 1, 2010 2:09 AM

Ok just as I expected. So I guess I am left with the following two options
1) either I switched to using JAXB in my apps instaed of xmlbeans....
2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
Programming Web Services for WebLogic Server (ant tasks)
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
Getting Started With WebLogic Web Services Using JAX-RPC
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

Problem in using EJB 2.1 Timer Service

Hi all,
I need a method in my EJB to be called by the EJB container at regular intervals. For this I plan to use the EJB 2.1 Timer Service.
I did the following for implementing the Timer Service.
1. My bean class implements the TimedObject interface. Thus the method ejbTimeout(Timer t) will be called by the container according to the interval I define in the timer.
2. For defining a timer, I have created a business method in the EJB which creates a Timer object with the timer service.
public void registerTimer(){
     // getting the timerService from the EJBContext
     timerService = myContext.getTimerService();
     // create a timer which times out after 5 seconds, and subsequently after every 10 seconds
     t = timerService.createTimer(5000,10000,"my timer");
Q: Is this enough or do we have to configure the engine in some way, so that it calls the ejbTimeout() method ? Maybe I am missing out something.
If the above tasks are enough then according to my understanding, the timer is created and then the ejbTimeout(Timer arg0) should be called first after 5 seconds and then after every 10 seconds.
I have created a servlet which acts as a client to this EJB, by which I can see that the Timer object is created, but the ejbTimeout() is never fired .
What could be the reason behind this? Am I missing something? Do I need to configure the engine in some way?
Any input on the above will be most valuable.
Thanks and Regards,
Gagan Parhar.

Hi ,,
    Go THru this article, sure it helps .
http://www.oracle.com/technology/sample_code/tutorials/fbs10g/fbs10gtoc.htm
Reg
VArun CN

Stateful WebLogic Web Services using cookie

Hi all,
How do I configure WebLogic Web Services to return cookie in the HTTP header?
In my weblogic.xml I included the following attributes but no cookie is returned in the HTTP header.
<session-descriptor>
<cookie-http-only>false</cookie-http-only>
     <tracking-enabled>true</tracking-enabled>
     <cookies-enabled>true</cookies-enabled>
     <cookie-name>JSESSION_ID</cookie-name >
</session-descriptor>
Thanks
SMT

Ok just as I expected. So I guess I am left with the following two options
1) either I switched to using JAXB in my apps instaed of xmlbeans....
2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
Programming Web Services for WebLogic Server (ant tasks)
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
Getting Started With WebLogic Web Services Using JAX-RPC
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

SharePoint timer service getting terminated after I joined a new server to an existing farm.

Hello guys, hope you are doing well.
I recently added a new server to my existing server farm set up containing 2 servers. In all, I now have three servers in my farm.
I am observing an System event error related with SharePoint timer service getting unexpectedly terminated. Event ID - 7031.
I have read a lot of blogs around this issue and I believe that the probable solution could be to try clearing SharePoint Configuration Cache and see if that resolves the issue.
I am going to try to soon but in the meanwhile I would like to know if anyone has any other suggestions to resolve this or if there is anything else that I can consider checking? ULS logs did not help much in my case.
On a side note, I have also observed that if I stop the user profile service on the newly added server, the event error stops getting logged in the new server but at the same time the event error can be seen on the other server where the User profile synchronization
service is running.
Any help is welcome!!
Thanks!

"ULS logs did not help much in my case."ULS log is more reliable for us to get the root cause of the issue, please do check it on the server when the service stopped.
From your description, it may be related to the user profile service, check the below article, whether you have tried this way:
http://www.darkomilevski.info/blog/?p=19
another situation:
http://blogs.technet.com/b/sowmyaa/archive/2013/07/16/sp2010-timer-service-crash.aspx
Qiao Wei <br/> My blog:<a href="http://blog.goobol.com">http://blog.goobol.com</a>

How to implement the security in web service with Weblogic 9.2

I've generated web service by Web Logic 9.2 using existing WSDL (as per client requirement) and want to add security policy for authentications.
I have used following annotation in service class.
@Policies({
@Policy(uri="policy:Auth.xml" , direction=Policy.Direction.inbound)
But it gives compilation time error with following message.
The Policy and Policies annotations are not allowed on jws file when compiledWsdl option is specified
I've also tried to modify the WSDL to accommodate policy configuration and again generate the web service but problem is being as it is.
If anybody has solution of this issue then please let me know ASAP.

Did you get an answer to your question? I have the same problem with WebLogic 10.0.

I have a 6 week old 4s running 5.1.1 Just started recieving "failed sim" message the other day. This leaves me with no cell service . Service comes back after shutting down and restarting. at least until message reaapears. Has happened three times in two

I have a 6 week old 4s running 5.1.1. Started recieving "failed sim" message yesterday. this leaves me with no cell service. Shutting down and turning back own seems to alleviate problem temporarily. It has happened three times now. Help.

Sounds like you have a battry issue but don't want to believe it.
If a car was running fine on one tank of gas, then you filled it up with another tank of gas and it began to run funny, one might suspect that tank of gas. But let's just say coincidence blew a valve-- would you think the new tank of gas was the culprit?
BUT WAIT!! It just might have been! The gas could have been of higher octane and put more more strain on the valves; you know, like going from 87 octane (OS6) to 93 octane (OS7) and showing you the engine was on the edge of compromise.
Sometimes you have to go with common sense. If everything else is ruled out, it must be the battery. And if it runs fine one moment in OS6 but immediately ***** in OS7, I'd believe my battery was suspect-- though comfy-- in OS6 but the OS7 showed its true power.
Moreover, if you had the answer-- or didn't want to believe someone's more competent advice-- why did you even call? You've already shown that you don't know much when you asked if you could go backwards after setting up the new OS as a new phone.
Additonally, if you're such the know-it-all, but yourself the $29 battery and put it in yourself. It's a piece of cake.
<Edited By Host>

Issue with Weblogic services in Linux OBIEE 11G

Hello All,
I have a OBI 11G set up on a linux OS.I am facing a issue with weblogic service.
Whenever I am trying to start the Admin server from command line using its .sh , it is starting successfully.
But whenever I am closing that Linux session or coming out of the Admin server log , this service is getting stopped on its own.
OBI is working perfectly when that Linux session and Admin server log is intact, but as soon as i close either of them Admin server shut itself down.
Please any help on this will be appreciated.
Thanks,
Bhavnesh

Hi Bhavnesh.
Try this way and let me know the outcome.
nohup ./startWeblogic.sh -Dweblogic.management.username=Username -Dweblogic.management.password=password & tail -f nohup.out
Mark if helps,
Thanks,

Persisting a trigger with weblogic time services

Similar Messages

Maybe you are looking for