- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - NonStop OS
- >
- Tandem enscribe file hit error 28.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2013 02:37 AM - last edited on 06-17-2013 02:47 AM by JinJing1
06-17-2013 02:37 AM - last edited on 06-17-2013 02:47 AM by JinJing1
Tandem enscribe file hit error 28.
Recently my java socket hit error 28 when try to write record in tandem enscribe file.
Look like i have issue with concurrent situation.
com.tandem.ext.enscribe.EnscribeFileException: File write error. File error 28
To solve it, i increase its syndepth to max to allow more transaction to write into the file.
But, while performing stress testing by sent in 300 trx simulataneously,
about 12 of this errors occur. I made up some solutions for this issue by :-
- add more opener to the enscribe file. When hit err 28,
use another opener to write. Not likely to solve the issue,
it just reduce the possibility to hit error 28.
- suspend, delay and wait availabilty of enscribe file to
be written. This method so risk, bcoz the socket have process timeout
can cause trx to abort.
Is there any permanent solution to not hit error 28? Any idea or suggestion?
Thanks.
P.S. This thread has been moved from Welcome to the Community > Community Feedback & Suggestions to Operating Systems > NonStop OS. -HP Forum moderator