EJB Timer Service

I've been trying to get the javax.ejb.TimerService working. As stated in the J2EE 1.4 tutorial, it is possible to use the TimerService in an entity bean. In fact, it states that if I wanted a timer for each instance of an entity bean, to create the timer in the entity bean's ejbCreate(). However, I keep getting an IllegalStateException when attempting to do so. I have implemented TimedObject in the entity bean, so I'm a little confused. Here's my ejbCreate:
public String ejbCreate(String clientID, long timeout) throws CreateException {
setClientID(clientID);
TimerService timerService = context.getTimerService();
//dies on next line
Timer timer = timerService.createTimer(getTimeout(), "state 1");
return clientID;
Any help is appreciated....
Thanks
Raj

getTimerService is allowed in ejbCreate but Timer Service Methods are not . You can use Timer Service methods in ejbPostCreate(), though.

Similar Messages

EJB Timer Services - timeout overlapping

Hi,
I have this question:
What should happen if the @Timeout method spends more time in working
something than the timer expiration time?
For example:
EJB timer is created with interval (expiration time) every 3 minutes. But for some reason the EJB binded to this timer is spending 4 minutes to process a timer notification. What happens with the next incoming timer notification?
Is it skipped or blocked? What happens with the method annotated as @Timeout?
Thanks!

Hi Fellipe,
This case isn't explicitly mentioned in the spec since the expectation is that the processing
time for the timeout would be much shorter than the interval itself. The design center for the
EJB Timer Service is to handle long-lived business processes so the spec examples for
timeouts are on the order of hours or days, even though the actual type in the API is
milliseconds. Many developers have expressed interest in support for finer-grained
timeouts and even cron-like functionality. The issue you raise would be an important one
to address in the scope of those EJB Timer Service additions.
Having said all that, the implementation in the Java EE SDK will not deliver a subsequent
timeout for the same timer until the previous one has completed.
--ken

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

The EJB 2.1 Timer Service & Clustering Behavior

With respect to WebLogic Server 9.0, does anyone know if The EJB 2.1 Timer Service will automatically restart a timer in the event of an entire cluster failure? Thanks,
          -Matt

Tim Farrell <> writes:
          > Good question. Since theres little to no documentation on the new EJB Timer or the TimerService implemented in 9.0 I would also like to know this.
          >
          > In fact, drilling down further, I want to understand what happens in a cluster when one of the servers fails with Timers scheduled.
          >
          > 1. Do they migrate to other servers ?
          No
          > 2. How do they migrate ?
          > 3. Will they migrate back to the original server when it comes back up ?
          > 4. When will the docs get completed for this feature ?
          Its possible that if you mark the server as migratable and have your
          store using HA then migration would work, although I'm certain that
          this has been tested.
          andy

Stateless Bean - scope of instance variable in EJB Timer call back function

Hi,
I would like to know on the scope of an instance variable of a Stateless Bean object,
when used in a EJB Timer call back.Let me explain this in more detail below.
I have a requirement to use a EJB Timer.
For this, I have created a stateless object since Timer creation needs to be done
from a stateless bean. I have a member variable "count" of the stateless bean class.
In the timer call back(ejbTimeout), I am able to use this count variable during
each time of the call back, and the value of this variable is also updated properly.
I have a few queries with respect to the above behaviour:
1) Does stateless bean object not get destroyed once the Timer is created from the Bean?
2) If the Bean object is not destroyed, then when does the bean object get destroyed?
3) If both (1) and (2) are not true, then can anyone explain on how the above behaviour is possible?
Thanks in advance,
Ulrich

Hi Ulrich,
The ejb timer is associated with the stateless session bean component, not with a particular bean instance. There is no formal relationship between the bean instance that called createTimer() and the bean instance on which the timer callback happens. If they're the same in your test run that's just a coincidence and not something your application should be depending on.
In the stateless session bean model, the container can create and destroy stateless session bean instances at any time. The container is free to pick any stateless session bean instance to service any client invocation or timer callback. If you need to pass context into a timer callback, one way to do it is via the timer "info" object. However, the info object is immutable so it wouldn't be a good match for a counter. You could of course always just use a database for any necessary coordinated state.
--ken

Does WebLogic Server 8.1 supports ejb2.1(timer service)

1.does WebLogic Server 8.1(SP5) supports ejb2.1 (timer service)?
2. does ejb 2.0 support timer service?

Hi,
1. No, EJB Timer support was added in WLS 9.0.
2. No, EJB Timers were introduced in EJB 2.1.
- Matt

Time service clustering in WLS8

          Hi
          Our product uses timer service on WLS 6.1, and timer is started by startup class.
          Now we need to move our product to WLS8 cluste. My question is: although startup
          class is clusterable, can timer service be clustered on WLS8? Or I can only start
          the timer in one server instance? If the timer is implemented using a stateless
          session bean which is deployed in the cluster, and one client in one managed server
          in the cluster starts the timer by calling the stateless session bean, will WLS
          support failover and load balancing of timer service?
          Thanks
          Chun


As Emily Lutella used to say: never mind!
It turns out the time service is simple, as we originally thought, and does
not distribute threads over scheduled trigger actions.
The mystery thread was started by a second server in the cluster going over
the wire to get to a bean on the first server.
---Paul O
Paul O'Rorke wrote:
We use the time service to schedule and process events at set times.
I just recently reviewed the documentation on this but still need a bit
more detail than I have seen, for example at
http://www.weblogic.com/docs51/classdocs/API_time.html
I am curious how multiple JVMs and threads may impact our scheduled
events.
We seem to have a situation where, when several events are scheduled to
occur at the same time, the first one waits on some resource such as an
EJB, possibly even getting into a deadlock with another thread that may
access the same resource(s), which may be running a JSP. But the time
service seems to move on, to process a second event scheduled for the
same time.
I would like to know more about how the time service allocates threads
to execute scheduled actions. For example, does it create a thread for
each action scheduled for a given time, or allocate a thread pool over
those actions?
If this is documented somewhere, I'd appreciate a pointer, otherwise
hopefully someone can provide more info here.
Thanks!
---Paul O

EJB Timer stops when database connection lost

G'day.
We use EJB Timers quite successfully in stateless session beans under Sun Java System Application Server 8.1 on Windows Server 2003.
We start and stop the timers for specific session beans using public intefaces on their respective beans. This works fine.
The problem we have is when the JDBC connection used by the EJBTimer service is dropped, such as when the remote database / machine falls over or (probably) when the network is lost. All the timers stop working at this point.
The timers do not restart when the database connection is restored either, despite the entries still being in the ejb__timers__tbl table.
If we stop and start the application server instance then they do restart.
We've looked at the setup of the timers but this seems to be pretty straightforward with no options that seem to influence this.
We've tried altering the JDBC connection validation settings but this doesn't seem to have made any difference.
Anyone have any ideas?
Robski!

There are no special options to handle this case in the current timer service implementation. Please file an issue describing the scenario here :
https://glassfish.dev.java.net/servlets/ProjectIssues
--ken

Timer Services

Hi All,
EjbTimerService in 2.1 says that Timers are persistent. If the server is shut down (or even crashes), timers are saved and will become active again when the server is restarted. If a timer expires while the server is down, the container will call ejbTimeout when the server is restarted.
I need to know that what feature we are supposed to add in order to allow undeployment to treat persisted timers as entities that exist beyond the lifetime of the ejb deployment.
I could not find any article for same. Please tell me, where i can get the documentation in details about how Jboss handles the Timer services especially when such condition occurs.
All suggestions are welcome.
Thanks.

I am not sure I completely understand your question, but this might help...
JBoss stores the timers in a database table named TIMER. When undeploying an EJB-JAR containing an EJB for which there is an active timer, JBoss removes the correponding row from the TIMER table. So it is not possible that a timer is triggered for an EJB that is not deployed anymore.
But I am not sure how JBoss handles this if you simply deletes the EJB-JAR file from the deploy folder when JBoss is not running.
Also, there is a timer section in the J2EE tutorial at http://java.sun.com/j2ee/1.4/docs/tutorial/doc/Session5.html
Bruno
http://www.practicalsoftwarearchitect.com

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

QuartzPublisher::execute ERROR message ejb/bpel/services/notification/Noti

Hello
I am getting the following error.
There are no instances in execution at this point in time but I still get this error.
<2008-05-23 14:10:23,648> <ERROR> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> ERROR message : javax.nam
ing.NameNotFoundException: ejb/bpel/services/notification/NotificationServiceBean not found
<2008-05-23 14:10:23,678> <ERROR> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> at com.evermind.serve
r.rmi.RMIServerContext.lookup(RMIServerContext.java:207)
<2008-05-23 14:10:23,678> <ERROR> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> at com.evermind.serve
r.ApplicationContext.unprivileged_lookup(ApplicationContext.java:257)
<2008-05-23 14:10:23,678> <ERROR> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> at com.evermind.serve
r.ApplicationContext.lookup(ApplicationContext.java:197)
<2008-05-23 14:10:23,678> <ERROR> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> at javax.naming.Initi
alContext.lookup(InitialContext.java:351)
<2008-05-23 14:10:23,678> <ERROR> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> at oracle.bpel.servic
es.notification.NotificationUtil.lookupRemoteBean(NotificationUtil.java:420)
<2008-05-23 14:10:23,678> <ERROR> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> at oracle.bpel.servic
es.notification.queue.sender.QuartzPublisher.execute(QuartzPublisher.java:92)
<2008-05-23 14:10:23,678> <ERROR> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> at org.quartz.core.Jo
bRunShell.run(JobRunShell.java:191)
<2008-05-23 14:10:23,678> <ERROR> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> at org.quartz.simpl.S
impleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
Regards
Kalidass

Hi,
Please read Metalink Note:563321.1
Thanks,
Vijay

Time Service Panasonic PBX

All work I've done using our PBX has been touch and go.Two users have complained that their time service keeps switching on it's own (on their phones). Employee A defaults their time service to "Lunch Mode" while employee B uses "Day Mode". I know that the different setting will dictate where calls go at different times of the day. My thought is they are switching it back and forth between each other.
I can't imagine the time-service is switched globally as people don't go on lunch at the same time typically. Is this setting set by group of extensions maybe? For exampleGroup Agoes to lunch at the same time so one person can change the time service for all of them via their phone?I don't understand the working of this function a whole lot and troubleshooting is difficult because of this.All help is appreciated.*I apologize if this is in...
This topic first appeared in the Spiceworks Community

As Emily Lutella used to say: never mind!
It turns out the time service is simple, as we originally thought, and does
not distribute threads over scheduled trigger actions.
The mystery thread was started by a second server in the cluster going over
the wire to get to a bean on the first server.
---Paul O
Paul O'Rorke wrote:
We use the time service to schedule and process events at set times.
I just recently reviewed the documentation on this but still need a bit
more detail than I have seen, for example at
http://www.weblogic.com/docs51/classdocs/API_time.html
I am curious how multiple JVMs and threads may impact our scheduled
events.
We seem to have a situation where, when several events are scheduled to
occur at the same time, the first one waits on some resource such as an
EJB, possibly even getting into a deadlock with another thread that may
access the same resource(s), which may be running a JSP. But the time
service seems to move on, to process a second event scheduled for the
same time.
I would like to know more about how the time service allocates threads
to execute scheduled actions. For example, does it create a thread for
each action scheduled for a given time, or allocate a thread pool over
those actions?
If this is documented somewhere, I'd appreciate a pointer, otherwise
hopefully someone can provide more info here.
Thanks!
---Paul O

How to create secure EJB web service in Oc4J using JDeveloper?

We are going to develop a EJB web service running in OC4J using JDeveloper 10.1.3.3.
By using the JDeveloper feature, we can simply create the web service by using the "Web Service Endpoint Interface" in the session bean.
However, unlike the web service created from Java class, I can't find any option to change the security setting of this web service. We tried adding annotation like @DenyAll for testing, but there has no effect and related method can still be called without WS-Security header.
Now, we can only change the security setting via the web console after deployment (select the web service, then enable security in administration page, and then edit security configuration to change the inbound policies for authentication). It works in our local machine, but it may not work in the production environment as we cannot touch the em console.
May I know if there has any way to include the security setting inside the project?
Thanks in advance.

If I am not wrong, you might be probably talking about this :
http://docs.oracle.com/cd/B40099_02/books/EAI2/EAI2_WebServices33.html#wp179056
In order to implement the SOAP header, you would have to :
(1) Define SOAP header in the wsdl of the service.
(2) Add a new soap binding in the wsdl, which contains soap header and soap body.
I think, this should get you going..

Sharepoint 2013 search error - The search application 'Search Service Application 1' on server is not provisioned.Confirm that the Microsoft SharePoint Foundation Timer service and Central Administration service are running on the server.

Hi All,
I'm getting the below error in My SHarepoint 2013 search Administration page.
Crawler background activity - The search application 'Search Service Application 1' on server "" is not provisioned. Confirm that the Microsoft SharePoint Foundation Timer service and Central Administration service are running
on the server.
and when i click on Crawl Log and content source
it throws the below error
The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether
the service is enabled. This might also be because an indexer move is in progress
When i check the search status
Get-SPEnterpriseSearchServiceInstance, it shows all the components are online.
As of now search service application is online and search is working.But not sure why it throws the above error.
I have restarted timer service,search service in services.msc and cleared the sharepoint cache as well.
But no luck,This is happening in my prodcution environment.
Any help will be greatly appreciated.
There are the logs i have found
05/23/2014 13:03:22.71 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3%2Dc3e4%2D4097%2D85fd%2Daa5248346d2e) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.71 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.73 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.79 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djs2 High [Forced due to logging gap, cached @ 05/23/2014 13:03:22.76, Original Level: VerboseEx] {0} d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.79 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.80 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djj1 High Unable to find application 'b9c8106c-c7ed-4eb3-96c9-ae1881ffb695' d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djj1 High Unable to find application 'b9c8106c-c7ed-4eb3-96c9-ae1881ffb695' d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General 8nca Medium Application error when access /_admin/search/listcontentsources.aspx, Error=The search service is currently offline. Visit the Services
on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.   at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object
sender, EventArgs e)     at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Runtime tkau Unexpected Microsoft.SharePoint.SPException: The search service is currently offline. Visit the Services on Server page in SharePoint Central
Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.    at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General ajlz0 High Getting Error Message for Exception Microsoft.SharePoint.SPException: The search service is currently offline. Visit the Services on
Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.     at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object
sender, EventArgs e)     at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General aat87 Monitorable  d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation DistributedCache ah24q Unexpected SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts are present in the farm. d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation DistributedCache ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedViewStateCache'
- Exception 'System.InvalidOperationException: SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.     at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'. d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General ajb4s Monitorable ViewStateLog: Failed to write to the velocity cache:
http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3-c3e4-4097-85fd-aa5248346d2e d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3%2Dc3e4%2D4097%2D85fd%2Daa5248346d2e)).
Execution Time=109.695855199474 d4c6939c-b10d-4000-6d95-14caeefe67df
Anil Loka

Please try below mentioned steps:
1. Central Administration > Monitoring > Review job definitions > Look for following timer job "Application Server Administration Service Timer Job" > Disable
2. Then open windows administrative services (services.msc), stop SharePoint Timer Service
3. Clear SharePoint Timer configuration cache by following steps mentioned in below blog:
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
4. Start SharePoint Timer Service and give it a few seconds so that the new XML files from the location you deleted then are re-populated.
5.Central Administration > Monitoring > Review job definitions > Look for following timer job "Application Server Administration Service" Timer Job > Enable
Please ensure that you mark a question as Answered once you receive a satisfactory response.

EJB Timer problem

Hi all, I'm trying to run the J2EE Tutorial EJB Timer sample, but I keep getting an exception:
Errors while obtaining information about the database. Got the following exception:
java.sql.SQLException: Error in allocating a connection. Cause:
Connection could not be allocated because: Connection does not exist.
com.sun.jdo.api.persistence.support.JDOFatalInternalException:
JDO76519: Failed to identify vendor type for the data store.
NestedException: java.sql.SQLException: Error in allocating a connection.
Cause: Connection could not be allocated because: Connection does not exist. .The tutorial says that I should start the PointBase database first, and I did; but there seems to be something missing, like the server is trying to lookup some datasource and it can't find it.
Any ideas?

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

EJB Timer Service

Similar Messages

Maybe you are looking for