Multithreading - Keeping Data separated between threads

I am new to multithreading. I am taking some code that was created in CVI 6.0 (as a exe.). TestStand would call the wrappers which in turned call these functions. The CVI functions has several structures which are global. Now, if I call a teststep into several threads, will the data be separated between the threads, or would they be using the same data. I am trying to understand how the data is handled within the same DLL, but different threads. Each Thread is running the same function.

Hello James,
When you use DLLs, global variables or global structures are shared between all threads that call your DLL. On t he other hand, variables or structures you declare inside the function scope are not shared.
Regards,
Roberto P.
Applications Engineer
National Instruments
www.ni.com/support

Similar Messages

How to keep data integrity with the two business service in OSB 10.3.1.0

How to keep data integrity with the two business service in OSB 10.3.1.0
In our customer system, customer want to keep data integerity between two businness service. I thinks this is XA transaction issue.
Basing customer requirment, I created a testcase but I can't keep data integerity, For detail information, please refer the attached docs.

Can you please explain what you meant my data integrity in your use case?
Manoj

Transfering Data Between threads via Piped Streaming

Hi There
I want to send and recive objecs between threads this is just test class for this reson but it does not work and it throus this exception
NOTE : when I use PipedInputStream and PipedOutputStream with out ObjectOutputStream and ObjectInputStream it works fine
java.io.IOException: Write end dead
at java.io.PipedInputStream.read(PipedInputStream.java:244)
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2200)
at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2490)
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2500)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1267)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
at IOProblem.run(IOProblem.java:34)
And this is the test code
import java.io.*;
public class IOProblem extends Thread{
     private ObjectOutputStream out;
     private ObjectInputStream in;
     private PipedOutputStream pipeOut;
     private PipedInputStream pipeIn ;
     public IOProblem(){
          try{
               pipeOut = new PipedOutputStream();
               pipeIn = new PipedInputStream(pipeOut);
               out = new ObjectOutputStream(pipeOut);
               in = new ObjectInputStream(pipeIn);
          catch(Exception ex){
               ex.printStackTrace ();
               System.exit (1);
    public void run()
          try{
               System.out.println(in.readObject());
               out.writeObject("End");
               System.out.println(in.readObject());
          catch(Exception ioEx){
               ioEx.printStackTrace ();
          System.gc();
    }//End of Run
     public static void main(String []args)
          (new IOProblem()).start();
}Thanks In advance.

You only have one thread. Each end need its own. See this for examples:
http://www.google.com/search?q=java+pipe+tutorial
I would sugges that you instead use a circular buffer, it's an easier implementation:
http://www.google.com/search?q=ostermiller+circular+buffer

"Portable" way to do message passing between threads?

(I posted this on the Apple Developer Forums already, but since that forum is only accessible to registered and paid iPhone developers, I thought it would be nice to put it here as well so as to get some more potential eyeballs on it. I apologize if this kind of "cross-posting" is not kosher/is frowned upon around here.)
Hey everybody,
"Long-time listener, first-time caller," heh.
I've been working for the past 2-3 months on my very first iPhone app. Actually, what I've been working on is a framework that I plan to use in an iPhone app of my own but which I am also trying to write for the "lowest-common-denominator" so that I (and others) can use it in other apps written for both Mac and iPhone.
Not only is this my first time writing an iPhone app, it is my first time writing for any Apple platform. In fact, it is my first time using Objective-C, period. I cannot stress this enough: I am a "n00b." So go easy on me. I also have not worked with threading before this, either, on any platform, so the learning curve for me here is rather significant, I'm afraid. I am NOT afraid of either taking the time to learn something properly OR of rolling up my shirtsleeves and working. However, on account of my experiences so far, I am finding myself (not to flame or anything!) quickly becoming frustrated by and disillusioned with not so much Objective-C itself, but the Foundation frameworks.
So with that said, read on, if you dare...
The basic idea behind my project is that the framework I am writing will present an API to developers which will allow them to write client apps that interact with a particular network appliance or network-aware embedded system. I already have my basic set of classes up and functioning, and the framework works to my satisfaction both on MacOS and iPhoneOS. The platforms I am targeting are MacOS X Tiger 10.4 and later, and iPhoneOS, and up until this point, I've managed to keep a codebase that works on all of the above.
What I wanted to do next was add some multithreaded goodness to the mix. (Woe is me.) I have asynchronous network socket I/O working within the main thread, and it, in fact, works a treat. In my test app on the phone, I've managed to keep the UI nice and responsive by using the main thread's runloop efficiently. But even though TCP async I/O works fine within the main thread, I want to be able to split out and offload the processing of any data received by the app from the appliance to its own thread. (It is possible, and even desirable, for an application using this framework to be connected to multiple appliances simultaneously.)
My idea, in order to try to keep things as simple and as clean as possible, was to implement a wrapper class that presented my other main class as an "actor." So, rather than instantiating my main class, one would create an instance of the wrapper class which would in turn control a single instance of my main class and spawn its own thread that the network connection and all data processing for that particular connection would run within.
(I hope I'm making sense so far...)
Out of the gate, writing a subclass of NSThread sounds like the logical design choice for an "actor-type" thread, but because I was trying to maintain Tiger compatibility, I stuck with +detachNewThreadSelector:etc.
Once I decided to pursue the actor model, though, the main problem presented itself: how to best pass messages between the main thread and all of the "actor" threads that might be spawned?
I stumbled upon -performSelector:onThread:withObject:, and knew instantly that this was exactly what I was looking for. Unfortunately, it doesn't exist on Tiger; only its much more limited little brother -performSelectorOnMainThread:withObject: does. So I kept looking.
All of the pre-Leopard documentation, tutorials, and sample code that I read indicated that to pass messages between threads, I needed to basically pretend that the threads were separate processes and use the expensive Distributed Objects mechanism to get messages back and forth. Unfortunately, even if that WAS a desirable option, iPhoneOS does not have any support for DO! Grrr...
Finally, I thought I found the answer when I ran into a third-party solution: the InterThreadMessaging library from Toby Paterson (available @ http://homepage.mac.com/djv/FileSharing3.html). In this library, the author basically implemented his own version of -performSelector:onThread:withObject: called -performSelector:withObject:inThread:. Sounds close enough, right? And actually, it is pretty darn close. It's made to do exactly what it sounds like, and it does it in a platform-neutral way that works on pre-Leopard systems as well as iPhoneOS, using Mach ports instead of DO.
(...wellll, ALMOST. I discovered after I built a small test app around it that it actually isn't "iPhone-clean." The author used an NSMapTable struct and the NSMap*() functions, which don't exist in iPhoneOS, and he also implemented the handlePortMessage delegate method, but although iPhoneOS has NSPort, it DOESN'T have NSPortMessage. GAAARGH. So I took the time to replace the NSMapTable stuff with NSValue-wrapped objects inside of an NSMutableDictionary, and replaced the handlePortMessage method implementation with a handleMachMessage method, which took some doing because I had to figure out the structure of a Mach message, NO thanks to ANY of the available documentation...)
Once I started using it, though, I quickly discovered that this implementation wasn't up to snuff. My "actor" class and my main thread will be passing a ton of messages to each other constantly whenever there is network activity, and with InterThreadMessaging, I found that whenever activity started to ramp up, it would collapse on itself. This mostly took the form of deadlocks. I found a note that someone else wrote after experiencing something similar with this library (quoted from DustinVoss @ http://www.cocoadev.com/index.pl?InterThreadMessaging):
"It is possible to deadlock this library if thread A posts a notification on thread B, and the notification on B causes a selector or notification to be posted on thread A. Possibly under other circumstances. I have resolved this in my own code by creating an inter-thread communication lock. When a thread wants to communicate, it tries the lock to see if another thread is already using the InterThreadMessaging library, and if it can't get the lock, it posts a message to its own run-loop to try again later. This is not a good solution, but it seems to work well enough."
So I tried implementing what he described using a global NSLock, and it did help with some of the deadlocks. But not all. I believe the culprit here is the Mach ports system itself (from the NSPortMessage documentation for -sendBeforeDate:):
"If the message cannot be sent immediately, the sending thread blocks until either the message is sent or aDate is reached. Sent messages are queued to minimize blocking, but failure can occur if multiple messages are sent to a port faster than the portís owner can receive them, causing the queue to fill up."
InterThreadMessaging in fact calls -sendBeforeDate: and exposes the deadline option, so I tried setting a really short time-to-live on the Mach messages and then intercepted any NSPortTimeoutExceptions that were thrown; upon catching said exceptions, I would then re-queue up the message to be sent again. It worked, but Performance. Was. A. Dog. At least the message queue wouldn't be full indefinitely anymore, causing the main thread to block, but during the whole time that these messages were expiring because the queue was full and then being re-queued, either the main thread was trying to send more messages or the actor thread was trying to send more messages. And as far as I can tell, the Mach ports queue is global (at the very least, there is seemingly only one per process). The message would get through with this model...eventually.
JUST IN CASE the problem happened to be something I screwed up as I was rewriting portions of the InterThreadMessaging library so that it would compile and work on the iPhone SDK, I substituted in the original version of the library in my Mac test app to see if any of these problems became non-issues. I found that both versions of the library -- mine and the original -- performed identically. So that wasn't it.
Finally, in frustration I said, "screw it, I'm going to try it the Leopard way," and replaced all of the method calls I was making to InterThreadMessaging's -performSelector:withObject:inThread: with calls to Foundation's native -performSelector:onThread:withObject: instead, changing nothing else within my code in the process. And wouldn't you know: IT WORKED GREAT. Performance was (and is) fantastic, about on-par with the non-threaded version when only dealing with a single connection/instance of my class.
So, in the end, I was able to do nothing to salvage the InterThreadMessaging implementation of cross-thread method calling, and as far as I can tell, I'm out of (good) options. And thus my mind is filled with questions:
How is the Leopard -performSelector:onThread: method implemented? I'm guessing not using Mach ports, given that I didn't have the same blocking & deadlocking problems I had with InterThreadMessaging. Is it possible to re-implement this Leopard+ method in a similar manner as a category to NSObject under Tiger? Or is it possible, perhaps, to increase the size of the Mach ports queue so that InterThreadMessaging works at a sane level of performance? Or -- I'm getting desperate here -- is there any way that I could trick -performSelectorOnMainThread: to target a different thread instead? (I am assuming here that -performSelectorOnMainThread is implemented under-the-hood much like the new -performSelector:onThread: is implemented, but with a hard-coded NSThread pointer built-in to the code, and that the new method just exposes a more flexible interface to what is basically the same code. I'm probably wrong...) Is there another third-party library out there that I've missed that fits my requirements for being able to do message-passing between threads in an efficient and portable manner?
I refuse to believe that there is no way for me to maintain compatibility with all of the platforms I wish to support without having to resort to making preprocessor #ifdef spaghetti out of my code. And there SURELY has to be a better way of doing cross-thread message passing in Tiger without using Distributed Objects, for Pete's sake! Is this really how people did it for years-on-end since the dawn of NeXT up until the advent of Leopard? And if there really, genuinely wasn't another alternative, then what is up with the lack of DO in iPhoneOS?? Does Apple seriously intend for developers who have good, solid, tested and working code to just chuck it all and start over? What if there was some aspect of DO that previous implementations relied upon that cannot be recreated with simple -performSelector:onThread: calls? (I don't know what those aspects would be...just a hypothetical.) I mean, I can understand needing to write new stuff from scratch for your UI given how radically different the interface is between the Mac and iPhone, but having to reimplement back-end guts such as something as elemental as threads...really?!
I do laud the inclusion of the new method in Leopard as well as the new ability to subclass NSThread itself. But for those of us that need to support Tiger for one reason or another, some of these restrictions and omissions within iPhoneOS seem like rather pointless (and frustrating) roadblocks.
As I hope is obvious here, I have tried to do my homework before throwing up my hands and pestering y'all. If you have the patience to deal with me, please tell me what I am missing.
Thanks for taking the time to read,
-- Nathan

Thanks again for your patience. Comments below.
etresoft wrote:
It is pretty unusual that anyone would want to call perfomrSelector on any thread other than the main thread.
What I described in my original post was not a worker thread, but an "actor."
It is hard for me to answer this question because there are so many options available to do "message passing". The fact that you think there are so few tells me that you really aren't sure what you need to use.
I didn't say there were few options for message passing. I said there were few options for message passing that fit my criteria, which are that any potential solutions should both A) work efficiently and with good performance, and B) be available both pre-Leopard AND on the iPhone. -performSelector: ain't available before Leopard. Distributed Objects is overkill. Kernel Mach messages apparently have a high overhead, too, as my experience with the third-party library I wrote about in my original message shows.
...consider notifications.
I thought notifications couldn't be posted across threads, either. How do I post a notification to another thread's default notification center or notification queue from a different thread?
The notification center is owned by the process. Each run loop can listen for just the notifications it wants. You don't "pass" or "send" notifications, you run then up the flagpole for all to see.
I am aware of how to use notifications. The documentation for NSNotificationCenter clearly states that "In a multithreaded application, notifications are always delivered in the thread in which the notification was posted, which may not be the same thread in which an observer registered itself."
So, again, I don't see how one thread can post a notification in such a way that the observer's registered method is executed in another thread (posting notifications "across threads"). This probably isn't a big deal if you are using mutexes (assuming you don't actually care which thread carries out the task associated with the notification posting), but as I said before, this is not what I'm after.
I don't know what you are really after.
Allow me to attempt to explain a second time, in a more concise fashion.
My app will have multiple, persistent TCP connections open, one connection per remote device. The user will be able to select a task to execute on a particular device that we have a connection open to, and get back from the application real-time updates as to the progress or results of the execution of that task. In certain cases, the length of the task is infinite; it will keep executing forever and sending back results to my application which will update its display of the results every second that ticks by until the user STOPS that particular task.
This can be done simply using async I/O in the main runloop, sure. But if I were going to thread this so that I could be processing the results I've received back from one *or more* remote devices while also doing something else, given that I will only have one (persistent) connection open to any given remote device that I'm interacting with (that is to say, I won't be opening up a separate TCP session for every single task I want to execute on a single device simultaneously), it makes sense _to me_ to implement this as I've described: with every connection to each remote device getting its own thread that lasts for the lifetime of the TCP session (which could be the entire time the application is running, times however many devices the user wishes to be connected to while in the app). I won't be spawning a new thread for every task the user wishes to ask a remote device to do.
This is why (I think) I need bi-directional messaging between the main thread and each of these threads dedicated to a given remote device that we have an active session with/connection to. The main thread needs to be able to tell remote device X (which already has a running thread dedicated to it) to do task A, and then get real-time feedback from that remote device so that the main thread can be displaying it to the user as it is coming back. Same with remote device Y running task B, simultaneously. At any time during the execution of these tasks, the user needs to be able to tell my app to stop one of these tasks, and the main thread needs to send that message to one of the remote devices via that device's dedicated thread.
This is why I am talking about this in terms of the "actor model," and not the "worker thread model," because the former model seems to fit what I want to do.
-- Nathan

Data sync between exchange 2003 and exchange 2013

Need assistance on a general direction.
There is a 2003 domain with exchange 2003 currently in use. On this domain there is also a contact management application that is heavily integrated and cannot be update at this time. I would like to bring up a new 2013 exchange server.
Is there a method that I could have user data synchronized between the 2013 exchange data and the 2003 exchange? In this manner users could use the 2013 exchange as primary and the Contact manage application could use the sync copy of exchange 2003. For
now I am only concerned about he the calendar however I am sure the other information will need to be sync as well.
Please let me know. Thank you.

Hi There,
Once you install Exchange 2013 it will use the same data your Exchange 2003 is using \ seeing because both of them use Active directory for Directory information.
Exchange 2013 will see all the users that are 2003 without you needing to sync \ move data.
If you need to users to be on Exchange 2013 and keep Exchange 2003 all you need to do is move the mailboxes to Exchange 2013.
Cheers,
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Remote Desktop cannot verify the identity of the computer because there is a time or date diffrence between your computer and remote computer

Hello.....
I'm not able to log into Windows Server 2008 r2 server thorugh Remote Desktop connection, receiving below error message.
This issue is with only three servers in the environment
"Remote Desktop cannot verify the identity of the computer because there is a time or date diffrence between your computer and remote computer......"
The date/time is correct on the server when i checked in the console session of the server
Can see below messages in event logs
Event ID 1014:
"Name resolution for the name XYZdomain.com timed out after none of the configured DNS servers responded."
Event ID 1053:
The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
Any thoughts ....

Hi,
Have you tried to connect these three servers with IP address instead of computer name or DNS name?
Check Remote Desktop Connection settings: Option-->Advanced-->Connect from anywhere-->Settings-->Connection Settings-->Select “Do not user an RD Gateway server”
For more information please refer to following MS articles:
Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/c1f64836-5606-49b0-82eb-56be7f696520
Cannot connect via Remote Desktop
http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/5087e897-8313-468c-ad37-ef18b87d4dd6
Lawrence
TechNet Community Support

How to save an excel file as CSV with semi-colon as data separator?

We are creating a flat data file to load the flat file data to our BW system with Excel. When we save the file, there are three kinds of CSV types for selecting from the "Save as type" list box:
CSV (Comma delimited)
CSV (Macintosh)
CSV (MS-DOS)
There is no CSV (semi colon delimited) type. If we pick CSV (Comma delimted) as the type, then when clicking the "Preview ..." picture icon under the "DataSource/Trans. Structure" tab of the InfoSource for this flat file (with the CSV radio button checked the Data separator default is ";"), the File Upload Preview window shows the data is messed up that some columns of the excel flat file are combined into one column.
Since the save type we picked is "CSV (Comma delimited)", then we try to change the default Data separator from ";" to "," in the preview selection screen, but still not helpful!
How to resolve the above problem?
Thanks

Hi Kevin,
This "," is defined in your windows setting. If you want to have ";" as separator then go to control Panel, select Regional Options, go to Numbers Tab and define the List separator as ";". After that when you will save your excel file as CSV(MS-DOS) it will have ";" as separator. This will make sure that the amounts are not broken in to two different fields while loading.
Else if you keep "," as separator then you can also go into the Excel and define all number fields as Number without thousand separator.
Let me know if you have any doubts in this.
Regards,
Rohit

Sharing socket object between threads - Is any sync required?

For example, a thread receives (listens) datagram packets at incoming socket and forwards them downstream through another datagram socket. Another thread listens packets at this second socket and forwards the data via the first socket. It is possible that two threads invoke methods of the same socket (one is receiveng while another is sending). This situation is not described in the DatagramSocket manual. I beleive there is underlying synchronization at the OS kernel level. Can I relay on it? Thanks.

I expected some critics for using old plain sockets instead of nio :)You should use NIO if you have hundreds of connections. If you have a small number of connections and want a simple implementation use blocking IO as you have.
If you can have different
threads reading or writing at once eg two readingor
two writing then you need to use synchronisation.Shouldn't this be stated by the API designers somewhere?It is probibly covered in a tutorial or example somewhere.
You have a different input and output stream. There is a lock on each. This is your best hint.
Theoretically, nothing prohibits sending UDP packets in race conditions.
In fact, this is what my program
does - it respondes to different clients using one
(server) datagram socket. The responses are produced
by multiple threads. I suppose that java does not
involve any state variables; thus, beleive that the
system can accomplish the synchronisation unnecesary
at the application level.That depends on how you build and send your messages. If each part of the message can be sent in one hit and the order does not matter you are fine.
If you have a single object shared between threads, then all members are shared, not just static variables.

Data Separator

Hi gurus,
I want to upload a flat file in BW 7.0. I am creating the datasource, the problem I have is that the data separator and the thousands separator is the same (.) in the file. I cant upload the file correctly it keeps adding a new field thinking that the only thousands separator I use is a new data field.
Kind Regards
Points will be awarded

Hi John,
One more solution to ur problem:
As u r saying that dot is used as thousand seperator and aslo as a data seperator,
here make use of escape character (") to avoid ur problem.
For example to load 10.000 value as a single value put hat inside escape sigh i.e.., "10.000" so that it may not treat dot as data seperator here.
For more info go through [http://help.sap.com/saphelp_nw70/helpdata/EN/c2/678e3bee3c9979e10000000a11402f/content.htm]

I have problem with data transfer between Windows Server 2012RT and Windows7 (no more than 14kbps) while between Windows Sever 2012RT and Windows8.1 speed is ok.

I have problem with data transfer between Windows Server 2012RT and Windows7 (no more than 14kbps) while between Windows Sever 2012RT and Windows8.1 speed is ok.

Hi,
Regarding the issue here, please take a look at the below links to see if they could help:
Slow data transfer speed in Windows 7 or in Windows Server 2008 R2
And a blog here:
Windows Server 2012 slow network/SMB/CIFS problem
Hope this may help
Best regards
Michael
If you have any feedback on our support, please click
here.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Need charting help - multiple data points between major ticks

Hi,
I am trying to create an AreaChart in which the data shows a
consumption rate over the course of a week. The major points along
the x-axis will be Monday, Tuesday, ... , Sunday (the days of the
week). However, there are multiple data points between each day. I
only want the days of the week to show on the axis but I want to
plot all of the data points. How would I go about accomplishing
this task?
Thanks in advance,
Brent Schooley

Thanks, it is getting closer now. My only problem now is that
the data points do not line up correctly with the tick marks. I've
look through the documentation and I can't figure out what to do to
ensure this happens. Here are the relevant portions of my code:
[Bindable]
public var energyDataAC:ArrayCollection = new
ArrayCollection( [
{date: "2007, 7, 27, 0", saved: 0},
{date: "2007, 7, 27, 12", saved: 50},
{date: "2007, 7, 28, 0", saved: 35},
{date: "2007, 7, 28, 12", saved: 0},
{date: "2007, 7, 29, 0", saved: 0},
{date: "2007, 7, 29, 12", saved: 46},
{date: "2007, 7, 30, 0", saved: 39},
{date: "2007, 7, 30, 12", saved: 0},
{date: "2007, 7, 31, 0", saved: 0},
{date: "2007, 7, 31, 12", saved: 44},
{date: "2007, 8, 1, 0", saved: 45},
{date: "2007, 8, 1, 12", saved: 0} ]);
public function myParseFunction(s:String):Date {
// Get an array of Strings from the comma-separated String
passed in.
var a:Array = s.split(",");
// Create the new Date object.
var newDate:Date = new Date(a[0],a[1],a[2],a[3]);
return newDate;
<mx:AreaChart id="Areachart" height="100%" width="100%"
paddingLeft="5" paddingRight="5"
showDataTips="true" dataProvider="{energyDataAC}" >
<mx:horizontalAxisRenderer>
<mx:AxisRenderer styleName="myAxisStyle"/>
</mx:horizontalAxisRenderer>
<mx:horizontalAxis>
<mx:DateTimeAxis alignLabelsToUnits="true"
dataUnits="hours" labelUnits="days" dataInterval="12" interval="1"
parseFunction="myParseFunction"/>
</mx:horizontalAxis>
<mx:series>
<mx:AreaSeries yField="saved" xField="date"
form="segment" displayName="Energy Saved"/>
</mx:series>
</mx:AreaChart>
<mx:Legend dataProvider="{Areachart}"/>
Any ideas?
Thanks,
Brent

The DATA CAP MEGA THREAD....post data cap questions or comments here.

In the interest of keeping things orderly....This is the DATA CAP MEGA THREAD....post data cap questions or comments here.
Please keep it civil.
Comcast is testing usage plans (AKA "data caps") in certain markets.
The markets that are currently testing usage plans are:
Nashville, Tennessee market: 300 GB per month and additional gigabytes in increments/blocks ( e.g., $10.00 per 50 GB ).
Tucson, Arizona market: Economy Plus through Performance tiers receive 300 GB. Those customers subscribed to the Blast! Internet tier receive 350 GB; Extreme 50 customers receive 450 GB; Extreme 105 customers receive 600 GB. Additional gigabytes in increments/blocks of 50 GB for $10.00 each in the event the customer exceeds their included data amount.
Huntsville and Mobile, Alabama; Atlanta, Augusta and Savannah, Georgia; Central Kentucky; Maine; Jackson, Mississippi; Knoxville and Memphis, Tennessee and Charleston, South Carolina: 300 GB per month and additional gigabytes in increments/blocks ( e.g., $10.00 per 50 GB ) Economy Plus customers have the option of enrolling in the Flexible-Data plan.
Fresno, California, Economy Plus customers also have the option of enrolling in the Flexible-Data plan.
- If you live outside of these markets you ARE NOT currently subject to a data plan.
- Comcast DOES NOT THROTTLE your speed if you exceed your usage limits.
- You can check out the Data Usage Plan FAQ for more information.

I just got a call today that I reached my 300GB limit for the month. I called and got a pretty rude response from the security and data usage department. The guy told me in so many words that if I do not like or agree with the policy that I should feel free to find another service provider.!!! I tried to explain that we watch Netflix and XFinity on-demand alot and I was told that that can not be anywhere close to the data usage. I checked my router and watching a "super HD, dolby 5.1" TV show on Netflix will average about 5-6 GB per hour (1.6MB/s) ... sp this means that I can only watch no more than 1-2 Super HD TV shows a day via Netflix before I run out of my data usage. This seems a bit redicilous doesn't it? Maybe the TV ads about the higher speed than the competition should be accompanied with "as long as you don't use it too often" Not a good experience ...

Dbx collector not collecting data for all threads

Hi, I am having problem with the dbx collector when I collect data from a multithreaded application. Data seems to be collected only from the first threads. Sun Studio 11
(dbx) attach -p 5501 my_proc
(dbx) threads
> t@2 a l@2 SI_SigThr() running in ___sigtimedwait()
t@3 a l@3 SF_autoReInit() running in ___nanosleep()
t@4 b l@4 SF_sendHeartBeats() running in ___nanosleep()
t@5 a l@5 SF_Main() running in ___nanosleep()
t@6 a l@6 MSI_TimerThread() running in ___nanosleep()
t@7 b l@7 HbtMonitor() running in ___nanosleep()
t@20 b l@20 umem_update_thread() sleep on 0xfe803ea8 in __lwp_park()
t@22 a l@22 FXI_SorterSpooler() sleep on 0xbd418 in __lwp_park()
t@23 a l@23 XCI_ReaderThread() running in __pollsys()
t@24 a l@24 MSI_ListenerThread() running in soaccept()
t@25 a l@25 MSI_ListenerThread() running in soaccept()
... and so on.... (sever hundred threads)
t@33 a l@33 ReconnectingThread() sleep on 0xc55f8 in __lwp_park()
... and so on.... (sever hundred threads)
(dbx) collector limit unlimited
(dbx) collector enable
(dbx) cont
^C
(dbx) collector show
collector enable
collector profile timer 10.007
collector profile on
collector synctrace threshold calibrate
collector synctrace off
collector hwprofile counter insts
collector hwprofile off
collector heaptrace off
collector mpitrace off
collector store directory "."
collector store experiment "test.3.er"
collector sample periodic
collector dbxsample on
collector sample period 1
collector limit none
collector archive on
(dbx) collector disable
When viewing the experiment only the t@2,t@3,t@4 and t@33 are seen!?
What

I had a few other questions in my earlier post.
During the time that data collection was running, how active (w.r.t. CPU time) should those threads be? When you run collect (instead of DBX) and look at timeline, how much activity do you see activity on the 'missing' threads during the similar segment (and loading) of the program's operation ? (I believe the collector won't record data if a thread does not get sufficient CPU time during the data collection period. )
Also, please post which OS version you are using and which version of collect & dbx. Thanks!

RECOVERY OF PASSWORD KEEPER DATA

Have Bold 9700 and got JVM Error 102 message. Had backed up couple days ago. Was my Password Keeper data backed up and will it be recoverable? This is tragic. Any thoughts welcome regarding any aspect of dealing with this error message. HOW do you talk to a tech person at RIM? Thanks.

Hi and Welcome to the Forums!
There are several threads throughout these forums about the JVM 102 error. Many claim to have workarounds that recover without losing data. I've not idea if they are valid or not. There is a formal RIM KB on the matter here, which includes what I was going to advise...reload your OS and restore from the backup. The backup should contain all of the databases on the BB...which are listed in this KB. Good job on taking a recent backup, though...many don't bother, and wind up in much more pain than you.
bbrown4u wrote:
HOW do you talk to a tech person at RIM?
Front line support for BB's is, by contract, not provided by RIM. The carriers and authorized resellers are responsible for front line formal support to end users. It is possible to bypass your carrier and seek assistance direct from RIM, but such involves fees since you are bypassing your support agreement with your carrier. The "Support and Services" tab toward the top of these forum pages provide information about that. But, if you do go through your carrier for support, they can escalate into RIM at no fee to you if they so choose to.
Good luck!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

What is the difference between thread and task

hi ,this is guruvulu bojja
what is the diff between thread and task .
can u give me the example for distinguish a thread and a task .
How can i know thread is better than a task .
please tell me what is the task in o/s level and task.
how the o/s distinguish a therad and task.

Hi Guruvulu,
Threads enhance performance and functionality by allowing a program to efficiently perform multiple tasks simultaneously.
In the case of common memory threads naturally have shared data regions while it has to be specially created and initialized for tasks.
Simply put, a thread is a program's path of execution. It allows execution of two or more sections of a program at the same time.
Regards,
Pooja.

Multithreading - Keeping Data separated between threads

Similar Messages

Maybe you are looking for