You can change the number of file descriptors using the ulimit
command.

Right now the number of sockets should be unlimited because that's
what I can see on the emulator

ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        8192
coredump(blocks)     0
memory(kbytes)       unlimited
locked memory(kbytes) 32
process(processes)   768
nofiles(descriptors) 1024

You could modify the number of fd with using "ulimit -n" and set it to
a very low number (for example 5). Try to check out whether you run in
any issues.

I assume that the sigfault is not because of a limitation of sockets.

--
Roman Baumgaertner
Sr. SW Engineer-OSDC
·T· · ·Mobile· stick together
The views, opinions and statements in this email are those of the
author solely in their individual capacity, and do not necessarily
represent those of T-Mobile USA, Inc.


On Jul 29, 6:31 pm, Rich <[email protected]> wrote:
> I've posted this already but I think Google Groups was throwing a
> wobbly cause it ended up in a group called AA-CCNA-O05..
>
> Anyway, output:
>
> D/libc-abort( 1180): abort() called in pid 1180
> I/DEBUG   (  551): *** *** *** *** *** *** *** *** *** *** *** *** ***
> *** *** ***
> I/DEBUG   (  551): Build fingerprint: 'generic/google_sdk/generic/:1.5/
> CUPCAKE/148875:eng/test-keys'
> I/DEBUG   (  551): pid: 1180, tid: 1190  >>> org.ale.abtc <<<
> I/DEBUG   (  551): signal 11 (SIGSEGV), fault addr deadbaad
> I/DEBUG   (  551):  r0 00000003  r1 deadbaad  r2 00000027  r3 ffff6150
> I/DEBUG   (  551):  r4 ffff6128  r5 afe2fef8  r6 afe39dd0  r7 80000088
> I/DEBUG   (  551):  r8 44d23da0  r9 42397eb8  10 42397ea8  fp 00000001
> I/DEBUG   (  551):  ip 0000001b  sp 44d23ce8  lr afe1ff33  pc
> afe1066a  cpsr 20000030
> I/DEBUG   (  551):          #00  pc 0001066a  /system/lib/libc.so
> I/DEBUG   (  551):          #01  pc 0000afae  /system/lib/libc.so
> I/DEBUG   (  551):          #02  pc 0001293a  /system/lib/
> libnativehelper.so
> I/DEBUG   (  551):          #03  pc 0000e3b4  /system/lib/libdvm.so
> I/DEBUG   (  551): stack:
> I/DEBUG   (  551):     44d23ca8  01c84282
> I/DEBUG   (  551):     44d23cac  007076e0
> I/DEBUG   (  551):     44d23cb0  afe39f90
> I/DEBUG   (  551):     44d23cb4  afe39fe4
> I/DEBUG   (  551):     44d23cb8  00000000
> I/DEBUG   (  551):     44d23cbc  afe13e4d  /system/lib/libc.so
> I/DEBUG   (  551):     44d23cc0  ad084a98
> I/DEBUG   (  551):     44d23cc4  3ac170c5
> I/DEBUG   (  551):     44d23cc8  ad084a98
> I/DEBUG   (  551):     44d23ccc  ffff6128
> I/DEBUG   (  551):     44d23cd0  afe2fef8  /system/lib/libc.so
> I/DEBUG   (  551):     44d23cd4  afe39dd0
> I/DEBUG   (  551):     44d23cd8  80000088  /system/lib/libicudata.so
> I/DEBUG   (  551):     44d23cdc  afe10663  /system/lib/libc.so
> I/DEBUG   (  551):     44d23ce0  df002777
> I/DEBUG   (  551):     44d23ce4  e3a070ad
> I/DEBUG   (  551): #00 44d23ce8  0018c5f8  [heap]
> I/DEBUG   (  551):     44d23cec  afe0e940  /system/lib/libc.so
> I/DEBUG   (  551):     44d23cf0  0018c5f8  [heap]
> I/DEBUG   (  551):     44d23cf4  afe3c980
> I/DEBUG   (  551):     44d23cf8  00002bb0
> I/DEBUG   (  551):     44d23cfc  fffffbdf
> I/DEBUG   (  551):     44d23d00  afe39dd0
> I/DEBUG   (  551):     44d23d04  0018c5f0  [heap]
> I/DEBUG   (  551):     44d23d08  8018c678  /system/lib/libicudata.so
> I/DEBUG   (  551):     44d23d0c  afe0afb3  /system/lib/libc.so
> I/DEBUG   (  551): #01 44d23d10  001ad668  [heap]
> I/DEBUG   (  551):     44d23d14  ad03475d  /system/lib/libdvm.so
> I/DEBUG   (  551):     44d23d18  afe3c980
> I/DEBUG   (  551):     44d23d1c  afe39dd0
> I/DEBUG   (  551):     44d23d20  0000a000  [heap]
> I/DEBUG   (  551):     44d23d24  4384d668
> I/DEBUG   (  551):     44d23d28  0018c5f8  [heap]
> I/DEBUG   (  551):     44d23d2c  ad0346c9  /system/lib/libdvm.so
> I/DEBUG   (  551):     44d23d30  001ad668  [heap]
> I/DEBUG   (  551):     44d23d34  0000030c
> I/DEBUG   (  551):     44d23d38  0018c5f8  [heap]
> I/DEBUG   (  551):     44d23d3c  ad21293f  /system/lib/
> libnativehelper.so
> I/WindowManager(  581): WIN DEATH: Window{43729d28 org.ale.abtc/
> org.ale.abtc.dl paused=false}
> I/ActivityManager(  581): Process org.ale.abtc (pid 1180) has died.
> D/Zygote  (  553): Process 1180 terminated by signal (11)
> W/InputManagerService(  581): Got RemoteException sending setActive
> (false) notification to pid 1180 uid 10020
>
> Running on the emulator.
>
> On Jul 29, 8:25 pm, Roman <[email protected]> wrote:
>
> > There is no precised answer possible to your question about speed and
> > stability of your connection. My comments below are only looking at
> > the usage of the radio interface itself. I have no real information
> > about how many sockets your device can handle.
>
> > It depends on a lot of factors ....
>
> > 1. Which radio interface are you using? Wifi is faster than Edge/3G
> > but signal strength could drop very fast when you move away from the
> > AP.
> > 2. In case of Wifi how crowded is your network? If you have a lot of
> > user than Wifi gets congested
> > 3. Which kind of traffic are you looking at? Streaming on Wifi has
> > different requirements than browsing the web. Mixing both type of
> > traffics impacts stability.
> > 4. In cellular networks the bandwidth you are getting depends on the
> > number of users in a cell
> > 5. Speed of your cellular data connection depends on the distance to
> > the BS
>
> > It would be also helpful to find out about when exactly you run in the
> > seg fault.
>
> > --
> > Roman Baumgaertner
> > Sr. SW Engineer-OSDC
> > ·T· · ·Mobile· stick together
> > The views, opinions and statements in this email are those of the
> > author solely in their individual capacity, and do not necessarily
> > represent those of T-Mobile USA, Inc.
>
> > On Jul 29, 10:10 am, Rich <[email protected]> wrote:
>
> > > Hello!
>
> > > I've written an application which involves a lot of simultaneous
> > > connections to different servers. I've noticed some big stability
> > > issues with this as sometimes the program crashes totally (not just
> > > ANR, but a segfault type thing). What's the recommended number of
> > > maximum simultaneous connections for speed and stability?
>
> > > Rich
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to