BLS Read Timeout

I am creating a transactions that joins results from three separate xMII documents (two SQL queries and one xMII document built from an external xml file). The three documents each have five columns and approximately 4000 rows. When I execute the transaction with ROWCOUNT set to 100 it works fine. When I set the ROWCOUNT to 5000 to accommodate all of my data, it crashes with the following error:
[ERROR]: Error executing transaction: java.net.SocketTimeoutException: Read timed out
No other tracing is provided.
After playing around with the logic, I have determined that the crash occurs at the first joiner.
Any thoughts??

Udayan -
The sequence of operations is as follows:
Sequence 1:
- Execute SQL select query against DB1
- Execute SQL select query against DB2
- Create An XML document to hold static xml
Sequence 2:
- Read static XML file
Sequence 3:
- Repeat through row elements of Static XML
Sequence 4:
- Append Repeater output to XML document
Sequence 5: ( this branch is independant of the repeater. It is a right branch off of sequence 1)
- Join XML Document with First SQL query
<CRASH OCCURS HERE>

Similar Messages

Read Timeout is not working with business service in OSB 11.6

HI All,
We have set below configuration in "Http Transport Configuration" of a business service.
Read Timeout- 8
Connection Timeout - 8
Authentication - None
Proxy Serve
Follow HTTP redirects - Disable
Use Chunked Streaming Mode - Enable
Even though backend is taking more than the configured value in Read Timeout but timeout is not happening in OSB, Connection time out also not worked, when we tested with wrong backend URL.
Any help for this configuration would appreciated.
Thanks,.

Hi,
Have you invoked any Services before calling the Business Service.
If Yes, then the problem with the Invoked service.In this scenario even if you set the time out period it will not work..
If No, your request payload is high
Regards,
Kiran

RT FIFO Read timeout

I have a timeout question about RT FIFO Read in Producer/Consumer system. Here is the scenario.
Producer writes data to RT FIFO via RT FIFO Write;
Consumer read data from RT FIFO via RT FIFO Read with timeout 100ms;
If RT FIFO is empty, returns 100ms timeout and stops Producer and Consumer.
If RT FIFO is not empty, process the data from FIFO and continue Producer/Consumer.
As I understand, RT FIFO empty means 100ms timeout. But the 100ms timeout condition does not behave properly as expected.
Am I understanding the FIFO Read timeout correctly?
Thanks!

MileP,
I find the best way to learn about Real-Time FIFOs is to run some examples of them, check these out and let me know what you think:
https://decibel.ni.com/content/docs/DOC-2303
https://decibel.ni.com/content/docs/DOC-9893
http://zone.ni.com/devzone/cda/tut/p/id/3934
I hope this helps get you going
Sam S
Applications Engineer
National Instruments

OSB Business Service is not timing out on Connection/Read timeout

I have a weird problem with my business service in OSB. I have set the read timeout value as 1 sec and Connection timeout value as 1 sec. The response from backend is taking more than 2 seconds or even 3 seconds but still my business service is not timing out..! My service is still listening to the response from backend even if it comes after 3 seconds. I expect it to timeout after 2 seconds. Any ideas?
Business Service Configurations:
Service Type: Any type
Protocol: http
Retry count : 0
Retry Application Errors: No
Read Timeout: 0
Connection Timeout: 0
HTTP Request Method: POST
Result Caching: No
Let me know if you need any more information. Thanks in Advance.
Regards
Kaleem

AbhishekJ wrote:
Maximum possible successful response time of the service will be less than Read TO + Connection TO.
Alas, this is not true.
Maximum possible response time is infinity.
There are two reasons for that.
1. Read timeout is not counted as time from the successful connection establishing to the current moment. It is measured as time from the last received byte to now. Imagine a backend service that sends a single byte in a data packet every 500ms. Despite you have read timeout set to 1, the receiving of 3K message will take 25 minutes, and yet your Biz service will not timeout.
2. In HTTPS, handshake is handled by a separate library which has its own quirks. Specifically, if the key exchange is broken at particular point of handshake, the library re-establishes the connection and does it few times; in my experiements, the largest I could delay the eventual fault was about 3 minutes.
Having said that, in the OP message the configuration is Read=0, Connect=0, so I wonder why the timeout is expected.

Read Timeout on non-blocking sockets

Hi,
I was wondering if there is a way to specify a read timeout (like setSoTimeout for synchronous sockets) when using a non-blocking socket.
I'd like to have the select() method return is a sockets timeout expires, puting in the selected key set the timedout socket and have it's read operation return -1, something like what happens when a socket is closed by the other side.
The thing is I need this to be a timeout specific to each socket, thus the select(millis) isn't apropriate.
Anyone knows of something like this?
Thanks....

Yeah, select() is the only thing built in for that, and you have to do the bookkeeping yourself. You would start something like forming the disjunction of the ready keys and the registered keys after each select, to get the unready keys, and then looking at their history to see how long they have been unready via a Map{key,Long(time)).

SMTP postfix crashing - network_biopair_interop read timeout

Periodically, my mail server goes into a crash cycle. Error messages like those below appear, and very quickly, the machine becomes unresponsive (I believe because it can't fork any more process - so OD won't authenticate, and any command which requires authentication (like a restart or service restart) hangs indefinitely).
The machine will crash every ~12 hours after being rebooted, for maybe 2-3 days before the problem mysteriously goes into remission. I don't know what confluence of events causes this, or how to see it coming sooner so I can stop and restart the mail service.
Any insight or solutions would be greatly appreciated.
/var/log/system.log:
Apr 25 07:37:43 mercury postfix/smtpd[8213]: warning: Read failed in networkbiopairinterop with errno=0: num_read=0, want_read=5
Apr 25 07:48:39 mercury postfix/smtpd[8475]: warning: Read failed in networkbiopairinterop with errno=0: num_read=0, want_read=5
Apr 25 07:50:06 mercury postfix/master[51]: warning: unixtriggerevent: read timeout for service public/flush
Apr 25 07:55:50 mercury postfix/pipe[8467]: warning: pipecommandwrite: write time limit exceeded
Apr 25 07:55:50 mercury postfix/pipe[8470]: warning: pipecommandread: read time limit exceeded
Apr 25 07:57:08 mercury postfix/pipe[8479]: warning: pipecommandread: read time limit exceeded

The output of postconf -n:
mercury:/ root# postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
mail_owner = postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
messagesizelimit = 15728640
mydestination = $myhostname,localhost.$mydomain,tjs.org,staff.tjs.org,mercury.tjs.org,info.tjs. org
mydomain = tjs.org
mydomain_fallback = localhost
myhostname = mail.tjs.org
mynetworks = 127.0.0.1/32,10.1.1.0/24,66.148.181.0/24,66.90.0.0/16,192.168.1.0/24,66.93.192. 247/32,66.93.193.247/32
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdpw_server_securityoptions = cram-md5,gssapi
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtls_certfile = /etc/certificates/*.tjs.org.crt
smtpdtls_keyfile = /etc/certificates/*.tjs.org.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
And here's a more full version of the logs. I think the increasing pids is a symptom of the problem:
Apr 27 10:34:58 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:34:58 mercury pop3[7369]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:35:18 mercury pop3[7164]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits new) no authentication
Apr 27 10:35:19 mercury pop3[7164]: login: ppp-70-245-234-7.dsl.stlsmo.swbell.net [70.245.234.7] YYY APOP+TLS User logged in
Apr 27 10:35:28 mercury pop3[7369]: login: c-69-241-232-137.hsd1.mi.comcast.net [69.241.232.137] XXX APOP User logged in
Apr 27 10:35:59 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:36:10 mercury pop3[7369]: login: dsl093-192-247.stl1.dsl.speakeasy.net [66.93.192.247] XXX APOP User logged in
Apr 27 10:36:11 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:01 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:01 mercury pop3[7369]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:01 mercury pop3[7833]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:07 mercury ctl_cyrusdb[7836]: checkpointing cyrus databases
Apr 27 10:37:08 mercury ctl_cyrusdb[7836]: done checkpointing cyrus databases
Apr 27 10:37:15 mercury pop3[7164]: login: dsl093-192-247.stl1.dsl.speakeasy.net [66.93.192.247] XXX APOP User logged in
Apr 27 10:37:26 mercury pop3[7833]: login: dsl093-192-247.stl1.dsl.speakeasy.net [66.93.192.247] XXX APOP User logged in
Apr 27 10:37:38 mercury pop3[7369]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:52 mercury imap[7842]: login: localhost [::1] jroth CRAM-MD5 User logged in
Apr 27 10:37:52 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:38:03 mercury imap[7842]: login: localhost [::1] XXX CRAM-MD5 User logged in
Apr 27 10:38:13 mercury imap[7842]: login: localhost [::1] XXX CRAM-MD5 User logged in
Apr 27 10:38:15 mercury imap[7842]: login: localhost [::1] XXX CRAM-MD5 User logged in
Apr 27 10:38:26 mercury pop3[7833]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:38:30 mercury imap[7842]: login: localhost [::1] XXX CRAM-MD5 User logged in
Apr 27 10:40:18 mercury pop3[7871]: TLS server engine: cannot load CA data
Apr 27 10:40:19 mercury pop3[7871]: TLS server engine: No CA file specified. Client side certs may not work
Apr 27 10:40:19 mercury pop3[7871]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits new) no authentication
Apr 27 10:41:41 mercury postfix/master[51]: warning: unixtriggerevent: read timeout for service public/flush
Apr 27 10:50:18 mercury pop3[7913]: TLS server engine: cannot load CA data
Apr 27 10:50:18 mercury pop3[7913]: TLS server engine: No CA file specified. Client side certs may not work
Apr 27 10:50:18 mercury pop3[7913]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits new) no authentication
And then the crash. Note this is a more recent crash cycle than the last one which I posted logs from.
Interesting that SSL certificates might be the issue. The one user, shown above as YYY, always triggers the log messages about TLS, which none of the other users seem to use. I haven't enabled SSL for email, but I wouldn't mind doing it to fix this problem.
Thanks for your thoughts and time.
Brian Howard

read-timeout-seconds not working

(WL 5.1, SP 11)
Hi all,
I'm playing around with Read-Only entity beans, and I get a problem
with the read-timeout-seconds property. I've set my
weblogic-ejb-jar.xml like this:
<ejb-name>product.entity</ejb-name>
<caching-descriptor>
<max-beans-in-cache>1000</max-beans-in-cache>
<cache-strategy>Read-Only</cache-strategy>
<read-timeout-seconds>60</read-timeout-seconds>
</caching-descriptor>
The first call to the EJB caches the database record, and subsequent
calls use the cache. My problem: Even if I delete the database record
directly (I know, I shouldn't do that... but like I said, I'm playing
around here... ;)) and wait for more than 60 seconds, the next call to
the bean still returns the same cached entry.
I tried with <idle-timeout-seconds> set to 60, and it doesn't work
neither.
I've seen in previous messages that this problem (or similar) was
fixed in SP4, but I use SP11, so it shouldn't be the problem.
Thanks for your help!
Phil

Hi,
Have you invoked any Services before calling the Business Service.
If Yes, then the problem with the Invoked service.In this scenario even if you set the time out period it will not work..
If No, your request payload is high
Regards,
Kiran

Modbus TCP/IP read timeout

The code below was taken from the NI Modbus library:
The first TCP Read VI, reads 7 bytes as a binary string. The data string is then cast to the MBAP_Header data type.
The MBAP header contains a length field, that is used to determine the length of the Modbus PDU (i.e. remaining part of the TCP message)
The second TCP Read VI then gets the remaining part of the message.
Can I set the second read timeout to 0?
For reqular Ethernet, the maximum packet payload is 1500 bytes.
1500 bytes is larger than any Modbus message, so I would not expect segmentation of Modbus messages.
Is this correct?
In general, if the application data is less than 1500 bytes (on regular Ethernet) and data is read in two parts, is it a good idea to set the second read timeout to 0.
Is there any other reason why I should not do this?
Thanks.
Message Edited by sparkymark567 on 01-28-2010 03:59 AM
Message Edited by sparkymark567 on 01-28-2010 04:01 AM

Hey,
The second read should not have a time out of 0. The first read only gets the first 8 bits of data, it does not buffer the rest of the package so the second read still needs time to receive the remaining data and hence will need at least some sort of time out value.
On the subject of segmentation, I believe you are correct. As long as your message doesn't excede 1492 bytes (I think the 1500 includes the overhead of the Ethernet package), it should come down in one package.
The best thing you can do is to try it out.
Kind regards,
Dominic Walker
Cardiff University
Electrical and Electronic Engineering Student

How to run vi continuously when VISA read timeout happens

Hello,
I am using LabView 2010 to read an Agilent 6000 series Oscilloscope. The Oscilloscope reads data from another experimental machine which fails occasionally due to sample failure. When the machine fails, it stops sending signal to the oscilloscope and leads to the VISA read timeout error and the whole vi is terminated. Is there a way that I can continuously run the vi when the error happens? For example, when the error happens, it stores the error in the error wire. When the vi read the error code from the wire, it sends a command to stop my experimental machine then stop the vi.
So far, it just simply stops during executing the visa read function. In this case, why do we have error in and out? The vi simply stops when the error happens.
Thanks
Lawrence
Solved!
Go to Solution.

I'll start of with automatic error handling. By default, LabVIEW enables the automatic error handling. So consider the case like the one below,
If let's say the VISA Read returns an error, but you did you pass the error information to VISA Close, what will happen is that LabVIEW will highlight the VISA Read (since the error comes from that function), pause the execution at the VISA Read and an error dialog box will appear. From the dialog box, it will prompt to either continue (Move on to the VISA Close) or stop (LabVIEW will stop the VI at VISA Read)
Now, consider another scenario like this,
By passing the error information from one function to another, let's say if VISA Read returns an error, that error will pass to VISA Close and finally to Simple Error Handler.vi. So Simple Error Handler will generate error dialog box after all the VISA operation is completed. This is called manual error handling (It can be enabled by just wiring the error information from one function to another and terminates at Simple Error Handler).
http://www.ni.com/gettingstarted/labviewbasics/handlingerrors.htm
As for VISA Close, here is the information about VISA Close.
http://zone.ni.com/reference/en-XX/help/371361K-01/lvinstio/visa_close/
See that button on the left side of this post...
If you feel my post is helpful, all you need is just (at most) 2 seconds to click that button, to show your appreciation. Thank you~~

Read-timeout-seconds

Hi!
What happens if I set <read-timeout-seconds> to some value
for a read only bean, according to bea's docs the ejbLoad() is called initially when the EJB is created and afterwards, WebLogic Server calls ejbLoad() only at intervals defined by the read-timeout-seconds. Does this mean that Weblogic always runs ejbLoad() every x seconds or ONLY if some client runs findByPrimaryKey() and the interval has expired?
Thanks,
A.

It's done lazily. When you access the bean, WLS checks if currentTime -
lastLoadedTime is > read-timeot-seconds. If so, it calls ejbLoad.
-- Rob
bnmbn ghjhg wrote:
Hi!
What happens if I set <read-timeout-seconds> to some value
for a read only bean, according to bea's docs the ejbLoad() is called initially when the EJB is created and afterwards, WebLogic Server calls ejbLoad() only at intervals defined by the read-timeout-seconds. Does this mean that Weblogic always runs ejbLoad() every x seconds or ONLY if some client runs findByPrimaryKey() and the interval has expired?
Thanks,
A.

SerialPort Read Timeout

Anyone knows how to achieve SerialPort Read Timeout? Or in another way to say it, stop reading from the SerialPort.

Remove the Serialport listener Maybe !

_setProperty weblogic.wsee.transport.read.timeout in weblogic 8.1

I need to set the timeout in the client deployed in weblogic 8.1 when making a call to a webservice.
I have tried the following code:
((ManagePrepaidCardRegistrationPort_Stub) managePrepaidCardRegistrationPort)._setProperty("weblogic.wsee.transport.read.timeout","10");
and get the following error:
java.lang.UnsupportedOperationException: unknow property:weblogic.wsee.transport.read.timeout
at weblogic.webservice.core.rpc.StubImpl._setProperty(StubImpl.java:146)
How do I do set the timeout property in the client deployed on weblogic 8.1 sp4 when making a call to a webservice?
I would appreciate any pointers?
Cheers
Charlie

Hi,
WLS 10.3 documentation
=======================
http://download.oracle.com/docs/cd/E13222_01/wls/docs103/webserv_ref/anttasks.html
<taskdef name="clientgen"
classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
once you generate client stubs you can use below options
The below options are for timeout only for JAX-RPC Webservice clients generated from clientgen:
import javax.xml.rpc.Stub;
((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
how are you running your client what are jar files are there in the classpath when running the client
http://docs.oracle.com/cd/E13222_01/wls/docs103/webserv/client.html#standalone_invoke
Regards,
Sunil P

Is there any way to set read timeout on JDBC connection?

When the network connectivity between the machine
where Database is running and where the application is running breaks,
the query executed using the old connection handle is not timing out.
Is there any way to set read timeout on JDBC connection. ?
FYI, Oracle JDBC thin Driver is used in our application.

Set the tuning parameters with Embedded OC4J Server Preferences>Current Workspace>Data Sources>jdev-connection-DBConnection1 node.
Select the Tuning tab.
The Inactivity Timeout parameter specifies the number of secs of inactivity after which a connection gets disconnected.

IRM LDAP Read timeout

Good day everyone!
We are facing problem when LDAP read procedure takes too long
Environment is: IRM + OVD as user repository (many AD domains behind it)
When we search for users in IRM we get exception:
<05.07.2011 14:08:36 MSD> <Warning> <oracle.irm.web> <IRM-03012> <Исключение при извлечении сведений о пользователе.
oracle.irm.jps.exception.JpsIdentityStoreFailureException: oracle.security.idm.OperationFailureException: javax.naming.NamingException: [LDAP: error code 1 - LDAP Error 1 : LDAP response read timed out, timeout used:15000ms.]; remaining name 'dc=ovd'
     at oracle.irm.jps.util.Store.searchIdentities(Store.java:404)
     at oracle.irm.web.services.IrmCommonUtil.searchByUserOrGroup(IrmCommonUtil.java:131)
     at oracle.irm.web.backing.common.CommonUserSearch.searchAction(CommonUserSearch.java:169)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.el.parser.AstValue.invoke(Unknown Source)
     at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
     at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodExpression(UIXComponentBase.java:1300)
     at oracle.adf.view.rich.component.UIXQuery.broadcast(UIXQuery.java:116)
     at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
     at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96)
     at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96)
     at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:902)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:313)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:186)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
is there anyway to increase ldap read timeout? We tried to change OVD Authenticator properties, but it seems that IRM doesn't bother to look at them =(

Hi,
This problem is caused by the type of search IRM makes when searching for users. By default, if you specify 'ran' as a search parameter, then we search for \*ran\* and so Frank would be returned. The problem is that very large LDAP repositories can take a long time to return when performing this kind of search unless they're setup appropriately. So you have two options:
1. Implement Medial (also known as Tuple) Indexing in your LDAP. This builds a larger less efficient index but gives much faster responses on substring searches.
2. As of 11.1.1.3 we have a patch (patch number 10354979) which allows you to refine the type of search to 'begins', 'ends' or 'exact match'. For example, you can do prefix searching. So 'ran' would not find 'Frank' but it would find 'Randolph'. If you are running 11.1.1.3, you need to apply the patch. If you are running a later version you just need to switch on the parameter defined in the patch readme. You cannot apply the patch to 11.1.1.2.1; in this case you have to upgrade to the latest version.
You should refer to KM note 1272153.1 which tells you more about this.
Regards,
Frank.

HTTP Jar Download Read Timeout

For some reason I've been having a hard time finding the setting which controls the read timeout for JAR downloads. At the moment it looks like it will never timeout such that if I am about to download a jar and the server goes down, the read will never timeout.
TIA

Yeah, jar downloading will use URLConnection and HTTP by default. What is not clear to me is if you can set the read timeout value in 1.4.2 and if my presumption is correct that if one does not set a read timeout value that a client could hang on a read indefinitely. I don't have the source to any concrete subclass of HttpUrlConnection that has a settable read timeout value.

BLS Read Timeout

Similar Messages

Maybe you are looking for