Bad file descriptor on iPad when I'm trying to log in bank app

bad file descriptor on iPad when I'm trying to log in bank app

Please report this to the app developer.

Similar Messages

Bad File Descriptor when I try to create an Tale

I am getting the following error when I execute the ./dbca on Red Hat Linux
java.io.IOException: Bad file descriptor
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:194)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:408)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:450)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:182)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at oracle.sysman.assistants.util.sqlEngine.SQLEngine$ErrorStreamReader.run(SQLEngine.java:1985)
at java.lang.Thread.run(Thread.java:534)

Hello Naveen,
I am experiencing exactly the same error message when trying to create a database through dbca(RH LInux). The assistant guides me through the process of locating the directories and naming the database but when I validate all choices and try to finish up the process I get the following error and dbca seem to enter some kind of loop. However nothing of the database is created. Did you manage to pass that stage if yes could you let me know how you went throught it. I am stuck to that point and no script was generated to manually create the DB.
If anyone else has a clue your advices are much awaited thanks in advance.
Nzavi
java.io.IOException: Bad file descriptor
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(Unknown Source)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(Unknown Source)
at sun.nio.cs.StreamDecoder.read(Unknown Source)
at java.io.InputStreamReader.read(Unknown Source)
at java.io.BufferedReader.fill(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at oracle.sysman.assistants.util.sqlEngine.SQLEngine$ErrorStreamReader.run(SQLEngine.java:1985)
at java.lang.Thread.run(Unknown Source)

"IOException: Bad file descriptor" thrown during readline()

I'm working on a system to send data to bluetooth devices. Currently I have a dummy program that "finds" bluetooth devices by listening for input on System.in, and when one is found, the system sends some data to the device over bluetooth. Here is the code for listening for input on System.in
InputStreamReader isr = new InputStreamReader(System.in);
BufferedReader br = new BufferedReader(isr);
boolean streamOpen = true;
while(streamOpen) {
     String next = "";
     System.out.println("waiting for Input: ");
     try {
          next = br.readLine();
           // other code here
      } catch (IOException ioe) {
           ioe.printStackTrace();
} // end of whileThis is running in it's own thread, constantly listening for input from System.in. There is also another thread that handles pushing the data to the bluetooth device. It works the first time it reads input, then the other thread starts running also, printing output to System.out. When the data has successfully been pushed to the device, the system waits for me to enter more information. As soon as I type something and press return, i get an endless (probably infinte if I don't kill the process) list of IOExceptions:Bad file descriptor exceptions that are thrown from the readline() method.
Here is what is being printed:
Waiting for Input: // <-- This is the thread listening for input on System.in
system started with 1 Bluetooth Chip // From here down is the thread that pushing data to the BT device
next device used 0
default device 0000000000
start SDP for 0000AA112233
*** obex_push: 00:00:AA:11:22:33@9, path/to/file.txt, file.txt
I'm not even sure which line it's trying to read when the exception gets thrown, whether it's the first line after "Waiting for Input: " or it's the line where I actually type something and hit return.
Any ideas why this might be happening? Could it have something to do with reading from System.in from a thread that is not the main thread?
Also, this is using java 1.6

Actually, restarting the stream doesn't work either..... here's a sample program that I wrote.
public class ExitListener extends Thread {
     private BufferedReader br;
     private boolean threadRunning;
     public ExitListener(UbiBoardINRIA ubiBoard) {
          super("Exit Listener");
          threadRunning = true;
          InputStreamReader isr = new InputStreamReader(System.in);
          br = new BufferedReader(isr);
     public void run() {
          while (threadRunning) {
               try {
                    String read = br.readLine();
                    if (read.equalsIgnoreCase("Exit")) {
                         threadRunning = false;
               } catch (IOException ioe) {
                    System.out.println("Can you repeat that?");
                    try {
                         br.close();
                         br = new BufferedReader(new InputStreamReader(System.in));
                    } catch (IOException ioe2) {
                         ioe2.printStackTrace();
                         System.out.println("Killing this thread");
                         threadRunning = false;
               } // end of catch
     } // end of run
}output:
I'm sorry, can you repeat that command? - Stream closed
Closed Stream
Ready?: false
I'm sorry, can you repeat that command? - Stream closed
Closed Stream
Ready?: false
I'm sorry, can you repeat that command? - Stream closed
Closed Stream
Ready?: false
I'm sorry, can you repeat that command? - Stream closed
Closed Stream
Ready?: false
I know that this is probably not enough code to really see the problem, but my main question is what could be going on somewhere else in the code that could cause this BufferedReader to not be able to re-open

System error 9 bad file descriptor

Hello. I am running system 10.3.9 and when I try to sync I get this error message, "system error 9 bad file descriptor." Needless to say I am unable to sync. Has anyone run into this problem? Are there any suggestions to fix it?

We have authorization problem, restric by OHD technical name.

Oracle Portal item cannot be deleted using dav (Bad File Descriptor)

I cannot delete an Oracle Portal item with webdav. I get an error 500 and the item is not deleted.
When this same user logs in as portal user with a browser, the item kan be deleted.
So the user permissions are probably not the problem.
What can be the problem?
How do I have to solve this?
<h1>Info found in log files</h1>
<h2>C:\OraHome_2\webcache\logs</h2>
Here I find an access.log file, but this one does not seem to contain anything useful.
<h2>C:\OraHome_2\Apache\Apache\logs\</h2>
Here I find two recent log files:
<h3>access_log.1340236800</h3>
HTTP/1.1" 207 3215
192.168.6.57 - - [21/Jun/2012:09:28:53 +0200] "DELETE /dav_portal/portal/Bibnet/Open_Vlacc_regelgeving/Werkgroepen/vlacc_wgCAT/fgtest.txt HTTP/1.1" 500 431
<h3>error_log.1340236800</h3>
[Thu Jun 21 09:28:53 2012] [error] [client 192.168.6.57] [ecid: 3781906711623,1] Could not DELETE /dav_portal/portal/Bibnet/Open_Vlacc_regelgeving/Werkgroepen/vlacc_wgCAT/fgtest.txt. [500, #0] [mod_dav.c line 2008]
[Thu Jun 21 09:28:53 2012] [error] [client 192.168.6.57] [ecid: 3781906711623,1] (9)Bad file descriptor: Delete unsuccessful. [500, #0] [dav_ora_repos.c line 8913]
In the error log, you also often find back message :
[Thu Jun 21 10:33:02 2012] [notice] [client 192.168.6.57] [ecid: 3421133404379,1] ORA-20504: User not authorized to perform the requested operation
This has probably nothing to do with it, you also have this message when the delete is successful.
<h1>Versions I have used</h1>
Dav client: I have tried with clients "Oracle Drive 10.2.0.0.27 Patch" and Cyberduck 4.2.1
Oracle Portal 10.1.4
In the errorX.log file, I find back these lines too:
[Thu Jun 21 09:53:17 2012] [notice] [client 192.168.6.57] [ecid: 4348843884218,1] OraDAV: Initializing OraDAV Portal Driver (1.0.3.2.3-0030) using API version 2.00
[Thu Jun 21 09:53:17 2012] [notice] [client 192.168.6.57] [ecid: 4348843884218,1] OraDAV: oradav_driver_info Name=interMedia Version=2.3

You may want to try a rebuild of the DAV tables in Oracle Portal. Before you do so, take a backup of the Portal repository database to ensure that you can revert back in case of disaster.
Rebuilding the DAV tables is done with the following instructions :
<li> Start SQL*PLUS and connect to the Portal metadata repository database as PORTAL user
<li> Execute wwdav_loader.create_dav_content :
SQL> exec wwdav_loader.create_dav_content();{code}
Thanks,
EJ

Installation:CSynEvent::~CSynEvent: an error occured;: Bad file descriptor

Hi,
CSynEvent::~CSynEvent: an error occured;: Bad file descriptor
I am getting the above error when I try installing SAP Netweaver 2004s SR1 on RedHat Linux 5.00
1. started ./sapinst in putty
2. started ./startInsGui.sh in HummingBird
Please help.
thanks,
Arun.

Dear Arun,
if you get the message
login timeout: unable to establish a valid connection
the sapinst GUI cannot connect to the sapinst server.
1) if you are using remote sapinst GUI
-> check if firewall is off via:
iptables -L
if your output is not like
# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
then the firewall is active. Please shut it down or open the port for sapinst GUI
2) if you are using local sapinst GUI
-> check if X forwarding works (e.g.) via calling xterm or xeyes
Thanks,
Hannes

Error : Bad file descriptor

Hi All,
I am getting Bad file descriptor error message while trying to run the below code :
try {
HSSFWorkbook wb = new HSSFWorkbook();
HSSFSheet sheet = wb.createSheet("Excel Sheet");
HSSFRow rowhead = sheet.createRow((short) 0);
rowhead.createCell((short) 0).setCellValue("Roll No");
rowhead.createCell((short) 1).setCellValue("Name");
rowhead.createCell((short) 2).setCellValue("Class");
rowhead.createCell((short) 3).setCellValue("Marks");
rowhead.createCell((short) 4).setCellValue("Grade");
int index = 1;
while (index<=110){
        HSSFRow row = sheet.createRow((short) index);
        row.createCell((short) 0).setCellValue(index);
        row.createCell((short) 1).setCellValue("Java");
        row.createCell((short) 2).setCellValue("Write to Excel");
        row.createCell((short) 3).setCellValue(index+15);
        row.createCell((short) 4).setCellValue("NA");
          index++;
       FileOutputStream fileOut = new FileOutputStream("\\\\remotepc1111\\C$\\test\\TestExcel.xls");
     wb.write(fileOut);
     fileOut.close();
catch (Exception e) {
System.out.println(e.getMessage());
}I read some where on the internet that this could be because of fileOut.close(). I tried after commenting that, but result was same.
Could some one point me what mistake I am making.
Thanks a lot.
AR

RAMJANE wrote:
As I am running this code through JSP file so printStackTrace() is not working for me. From Java standalone program it is working fine.The general strategy when doing old school JSP development is to use a servlet to do the business logic stuff and a JSP only to render the view. The strategy is basically to:
- enter in the Servlet which will do stuff and prepare data
- any data prudent to the view is put in the request scope using setAttribute()
- make the servlet forward to the JSP that renders the view (which does not always have to be the same one!)
- render the view using JSTL only - no Java code and/or scriptlets
that creates clean, easy to debug and maintain code. Of course that does mean that each 'page' has at least two resources, but that is true for most of any framework you can use too.
As for printStackTrace() "not working" - the output ends up in the server's log files. Check there.

Suse 10: Unable to release physical memory: Bad file descriptor

When I'm trying to run jrockit it prints the message "Unable to release
physical memory: Bad file descriptor":
stef@linux:~> export JAVA_HOME=/home/stef/progs/jrockit-jdk1.5.0_03
stef@linux:~> export PATH=/home/stef/progs/jrockit-jdk1.5.0_03/bin:$PATH
stef@linux:~> java -version
Unable to release physical memory: Bad file descriptor
[~38 time the same message]
Unable to release physical memory: Bad file descriptor
java version "1.5.0_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07)
BEA JRockit(R) (build dra-45238-20050523-2008-linux-ia32, R25.2.0-28)
The vm does work and the speed seems to be okay but this messages pops
up every time I try to run an application. (It's not specific to this
user it also happens for root)
What does it mean and what can I do about it?
Yours,
Stefan

You can safely ignore the messages. It is a result of changes in the implementation of madvise in the 2.6.13 kernel (which, needless to say, isn't supported with JRockit). We'll change our usage in a future release so that these messages don't show up.
Thanks for pointing it out,
/Staffan

Bad File Descriptor ERROR

Hi Friends,
Here is my scenario:
while (INFINITE_LOOP) {
     1. Create eraser.db DB with enabling environment & no transaction in dir: /DB_DIR
     2. Create expire.db DB without enabling environment & no transaction in same dir: /DB_DIR
     3. Perform add - remove record operations on both dbs.
     3. Close both dbs & environment
     4. Remove entire directory : /DB_DIR (using posix rmdir & unlink apis)
     5. sleep for 2 mins. (This is for stress testing... actual sleep value is 24 hrs)
This while loop works for few iterations. But after few iterations I start getting below errors:
seek: 0: (0 * 4096) + 0: Bad file descriptor
eraser.db: write failed for page 0
eraser.db: unable to flush page: 0
seek: 4096: (1 * 4096) + 0: Bad file descriptor
eraser.db: write failed for page 1
eraser.db: unable to flush page: 1
seek: 8192: (2 * 4096) + 0: Bad file descriptor
eraser.db: write failed for page 2
eraser.db: unable to flush page: 2
Once these errors start occuring. All the db operations start failing for all the following iterations.
Now I have to stop my program & restart, then only db starts working as expected.
Kindly suggest the root cause of the problem.
Regards,
~ Ashish K.

Hi Friends,
The above mentioned issues was not related to BDB. Finally I found "opened once, but closed twice" file descriptor issue in my multi threaded code.In our code a socket descriptor was getting closed twice. After few iterations of running, this problem was unintentionally leading to closing of one of the internal file descriptor of BDB. Once I fixed that problem. BDB started working as expected.
For those who are unfamiliar to closing twice issue in multi threaded code read below:
foo ()
    fd = open();
    // some processing.
    close (fd);
    // some processing.
    close (fd);
The above code will work smoothly for a single threaded application. But in our case of multithreading, if a thread "X" call open(), when thread "Y" is in between the two close() calls, then in that case, thread "X" will get the same fd for open which thread "Y" was using (since open always return the smallest unused descriptor). File descriptors are shared by all the threads. So when thread "Y" carries out its second close(), it actually closes the file descriptor of thread "X", which was valid & in use.
This is what precisely happening with my code.
TIP: Whenever your multi threaded code, starts giving BDB errors like "Bad file descriptor" first check if there is a place in code where you are "opening once but closing twice" any file descriptor.
Regards,
~ Ashish K.

Java.io.IOException: Bad file descriptor Jetty 9.2.10.v20150310

I started jetty in nonstop server on port 18095 and it was running fine, few days later suddenly noticed it consumes more CPU, when I check the log noticed the following log writing continiously
2015-07-08 13:25:48.606:WARN:oejs.ServerConnector:qtp26807578-18-acceptor-0@182e42f-ServerConnector@1f02fde {HTTP/1.1}{0.0.0.0:18095}:
java.io.IOException: Bad file descriptor (errno:4009)
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:241)
at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:377)
at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:500)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:724)
Can any one guess the root cause. Thanks.

I am using jdbc to connect the database. I want to update the blob fields that is picture into the database. Now i am using preparedstatement to update the fields. When it causes error, it will closed automatically. At that time, it causes bad file descriptor.

Mhddfs / FUSE 'Bad file descriptor' issue

Hi,
I have a Seagate Goflex Home running archlinuxarm. Everything is working fine other than an issue I'm having with mhddfs while unioning several hard drives. I seem to be able to write to any of the drives individually but when I use the union share via mhddfs, it always returned this error when writing a file: 'Bad file descriptor'.
When I try to do nano <new file name.txt>, it gives me the bad file descriptor error. However, if I persist after the initial error and try to save a second time it saves without any addition errors.
Also, if I try to copy a file over samba to the union share, I get the error 'Invalid file name'. This happens for all files whether they have special characters or not.
I'm a bit confused as to why this is happening. I've had mhddfs working well in the past. Does anyone know what could be causing this?
Last edited by LightC (2013-05-09 15:15:24)

Drawing Business wrote:
I then tried using "find" to look for single large files, using "sudo find / -size +94371840" (anything larger than 90Gb), and I get the following errors:
find: /dev/fd/3: Bad file descriptor
find: /dev/fd/4: Not a directory
find: /dev/fd/5: Not a directory
This is not an error and always happens with find unless you exclude the /dev hierarchy from the search. (Interestingly this seems to have gone away with 10.5??)
To locate your missing space, try WhatSize. Another alternative which I have not used personally is Disk Inventory X.
As an additional point, with 10.4 it is actually better to use Disk Utility, since it does more than fsck: Resolve startup issues and perform disk maintenance with Disk Utility and fsck, quote:
Note: If you're using Mac OS X 10.4 or later, you should use Disk Utility instead of fsck, whenever possible.

Can anyone tell me what "RUN-059008 ... Bad file descriptor"

The entire message is "2736 3052 RUN-059008 6/23/2010 12:54:16 PM Putting a row into a pageable cache failed with error <9> and error message <Db::put: Bad file descriptor>."
The person who got it was running a busObj data integrator job. The job was for a whole year. When she broke it down by quarter it ran fine.
I'm not familiar with the product, but are there cache settings or something I should look at?

if you are running the Dataflow is Pageable Mode, then for processing large volume data if caching is need instead of caching the Data in memory DI will cache this on the Disk. The cache file will be created in the Pageable Cache directory that is set from the server Manager.
check the size of PCache directory ?
since you are able to process the data in batches, could be related to volume of data and run time resource usage

Exfat bad file descriptor

Hi,
I formatted my external drive to exfat but i'm getting a bad file descriptor error when running:
sudo fsck_exfat -d disk1s2
It says read only and main boot region invalid jump
The external drive is a lacie d2 3tb thunderbolt.
I removed all partitions including the EFI partition.
used gpt to rebuild efi nothing worked.
I can access all files but i want to get rid of the error.

Please report this to the app developer.

Suddenly can't create dirs or files!? "Bad file descriptor"

Tearing my hair out...
Suddenly, neither root nor users can create files or directories in directories under /home. Attempting to do so gets: Error -51 in Finder, "Bad file descriptor" from command line, and "Invalid file handle" via SMB.
However, files and dirs can be: read, edited, moved, and occasionally copied. Rebooting made no difference.
Anyone have a clue on where to start on this?
Mac OS X 10.3.9. Dual G4 XServe with 2 x 7 x 250 G XRAID.
Many Mac OS X (10.3.9) Many
Many Mac OS X (10.3.9) Many

Indeed. This whole episode has exposed rather woeful lack of robustness on the part of the X Server and XRAID... various things failing and server hanging completely as a result of a few bad files on disk.. with lack of useful feedback as to what was happening.
Best I can tell, we had reached the stage where the next available disk location for directory or file was bad... blocking any further additions.
I've embarked on the process of copying everything off, remove crash-provoking files, replace one bad drive (hot swap didn't work), erase all, perform surface conditioning (bad-block finding) procedure, and maybe later this century will be copying all files back.
Looks to me like the bad block finding procedure is finding a few bad blocks on the supposedly good drives... presumably will isolate those, but maybe we need to get more new drives.
Many Mac OS X (10.3.9) Many

Bad File Descriptor in /dev/fd/3, and 94Gb of disk space missing

I noticed a few days ago, possibly as the result of a recent kernel panic, that I have a large chunk of hard drive space missing. The Finder reports that I have approximately 89Gb of free space, but using "df" reports that there is approximately 178Gb free. Using "du" doesn't report any unexpected huge files, so I tried running GrandPerspective. In addition to the usual file usage and free space, this shows a single 94Gb block of "miscellaneous used space".
I then booted into Single User mode to run fsck on the startup drive. This reported several errors, and took 3 passes to repair the directory structure, but didn't recover the missing space. I have subsequently run TechTool Pro and DiskWarrior on the startup drive (both of which found various minor errors), but the 94Gb still refuses to show itself.
I then tried using "find" to look for single large files, using "sudo find / -size +94371840" (anything larger than 90Gb), and I get the following errors:
find: /dev/fd/3: Bad file descriptor
find: /dev/fd/4: Not a directory
find: /dev/fd/5: Not a directory
After searching Google, a "Bad file descriptor" error points to an inode issue, that fsck cannot fix, but I don't know enough (read: anything) about inodes to risk running the clri command to zero the problem inode.
Short of blanking the startup disk and installing from scratch (not an attractive option), is there anything I can do to fix the broken inode and recover the missing space?
Any help appreciated.

Drawing Business wrote:
I then tried using "find" to look for single large files, using "sudo find / -size +94371840" (anything larger than 90Gb), and I get the following errors:
find: /dev/fd/3: Bad file descriptor
find: /dev/fd/4: Not a directory
find: /dev/fd/5: Not a directory
This is not an error and always happens with find unless you exclude the /dev hierarchy from the search. (Interestingly this seems to have gone away with 10.5??)
To locate your missing space, try WhatSize. Another alternative which I have not used personally is Disk Inventory X.
As an additional point, with 10.4 it is actually better to use Disk Utility, since it does more than fsck: Resolve startup issues and perform disk maintenance with Disk Utility and fsck, quote:
Note: If you're using Mac OS X 10.4 or later, you should use Disk Utility instead of fsck, whenever possible.

Bad file descriptor on iPad when I'm trying to log in bank app

Similar Messages

Maybe you are looking for