You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "hirot (JIRA)" <ji...@apache.org> on 2007/08/01 04:39:53 UTC
[jira] Created: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
TimeLimitExceededException with the embedded ADS
------------------------------------------------
Key: DIRSERVER-1012
URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.0
Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
Reporter: hirot
I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
The environment is :
- Win XP SP2
- J2RE 1.5.0
- eclipse 3.2.0
- ADS 1.5.0
Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
When a same search takes less than 1 second, it successfully returns results.
I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
Is the server side timeout of ADS 1 second ?
Is there any measure to lengthen the timeout ?
(I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1012:
-----------------------------------------
Fix Version/s: 1.5.2
Should be investigated as soon as possible, after we have released 1.5.1 (I suspect that this issue is not very simple to fix...)
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "hirot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521911 ]
hirot commented on DIRSERVER-1012:
----------------------------------
I came up against TimeLimitExceededException again while the unit test was running.
The environment is :
- Linux 2.6.9-55.ELsmp
- J2RE 1.5.0
- JUnit 4.1
- ADS 1.5.0 (embedded for the unit test)
About one second after a search started, javax.naming.TimeLimitExceededException was thrown.
I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception was caused by the server side timeout, I suppose.
I added a part of the ADS' trace as follows :
2007-08-22 14:26:08 org.apache.directory.shared.ldap.codec.TwixTransformer::transform Thread-12
FINE [ Transformed message : LdapMessage
message Id : 2
Search Result Done
Ldap Result
Result code : (TIME_LIMIT_EXCEEDED) timeLimitExceeded
Matched DN : ''
Error message : 'failed on search operation:
SearchRequest
baseDn : 'o=hq,dc=myco,dc=com'
filter : '(& (2.5.4.50=uid=mdavis,ou=people,o=hq,dc=myco,dc=com)[9223372036854775807] (2.5.4.0=groupofuniquenames)[3] )[3] '
scope : whole subtree
typesOnly : false
no limit
Time Limit : 31
Deref Aliases : deref Always
attributes : 'cn'
:
org.apache.directory.shared.ldap.exception.LdapTimeLimitExceededException
at org.apache.directory.server.core.partition.PartitionNexusProxy$1.accept(PartitionNexusProxy.java:461)
at org.apache.directory.server.core.enumeration.SearchResultFilteringEnumeration.prefetch(SearchResultFilteringEnumeration.java:317)
at org.apache.directory.server.core.enumeration.SearchResultFilteringEnumeration.next(SearchResultFilteringEnumeration.java:204)
at org.apache.directory.server.ldap.support.SearchResponseIterator.<init>(SearchResponseIterator.java:97)
at org.apache.directory.server.ldap.support.SearchHandler.messageReceived(SearchHandler.java:334)
at org.apache.mina.handler.demux.DemuxingIoHandler.messageReceived(DemuxingIoHandler.java:144)
at org.apache.directory.server.ldap.LdapProtocolProvider$LdapProtocolHandler.messageReceived(LdapProtocolProvider.java:403)
at org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:703)
at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362)
at org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54)
at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800)
at org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimpleProtocolDecoderOutput.java:60)
at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:190)
at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362)
at org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54)
at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800)
at org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:243)
at org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:305)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:803)
'
]
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539578 ]
Emmanuel Lecharny commented on DIRSERVER-1012:
----------------------------------------------
I would suggest that another test is done using ADS 1.5.1, and providing a sample code to demonstrate the bug, instead of a 9 Mb long log which does not help a lot.
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543089 ]
Emmanuel Lecharny commented on DIRSERVER-1012:
----------------------------------------------
Hmmmm... I _may_ have a clue about what is going on. It may be a combinaison of two things :
- a misleading error message (timeout exception)
- a badly handled search on DistinguishedName values (like GroupOfNames)
We have fixed some issues in the way such DistinguishedNames were parsed and searched, which may have fixed such searches. It _may_ be related to https://issues.apache.org/jira/browse/DIRSERVER-923, for which I had to fix some bugs in DN searches.
The current trunk should be tested in order to check if the current issue is gone or not.
I will give it a try next week (sadly enough, I'm badly overwhelmed by many tasks atm ...)
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "Todd Kaplinger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543078 ]
Todd Kaplinger commented on DIRSERVER-1012:
-------------------------------------------
Problem still occurs after upgrading to ADS 1.5.1.
Unfortunately providing sample code is not possible since it would require more than a simple command line program and it also is intermittent. Can you tell us what we can provide in terms of trace or a possible debug module to help diagnose this issue. I would assume that you can debug issues without having to reproduce in your own environment for these types of issues. I know it would be ideal to have a testcase but we are not exactly sure what is triggering this issue.
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-1012) TimeLimitExceededException with the
embedded ADS
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-1012.
----------------------------------------
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "Todd Kaplinger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543091 ]
Todd Kaplinger commented on DIRSERVER-1012:
-------------------------------------------
Thanks for the quick response. I was not watching this bug so I was unaware that you had responded to the prior one so quickly. We use maven to resolve our projects so we would have to wait for an official release to validate the changes. Do you know when the current trunk will be considered finalized?
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-1012.
------------------------------------------
Resolution: Fixed
I _think_ this has been fixed a while back.
To be reopened if not.
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "Todd Kaplinger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584858#action_12584858 ]
Todd Kaplinger commented on DIRSERVER-1012:
-------------------------------------------
Just checking but do you have the bug id? I am thinking no based upon your comment
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543097 ]
Emmanuel Lecharny commented on DIRSERVER-1012:
----------------------------------------------
We don't have any fixed date for the 1.5.2 release. However, we have done a lot of modifications in a bigbang branch we want to inject into the trunk very shortly. This will be the perfect timing to have a 1.5.2 release, but as it will cost us at least one week to cut this release, and as we are really under heavy pressure right now, we can't guarantee that we will be able to do that before mid-december.
Here are the issues we have to work on for this release :
- we have no Unix installer currently
- the configuration format has changed, and we need to renew the documentation
- there are around 85 open bugs for 1.5.2, and even if we postpone some of them, we really want to fix some of them
- this is a terrible period to work on open source because we are all overhelmed with real life projects ...
I would like to be a little bit pessimistic in saying that we will release for the end of this year, the good news would be that we release earlier. Who knows ? ;)
Btw, any help on the installer would be very welcomed !
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1012) TimeLimitExceededException with
the embedded ADS
Posted by "Todd Kaplinger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539576 ]
Todd Kaplinger commented on DIRSERVER-1012:
-------------------------------------------
Can the owner of this bug provide a status update? I am aware that there may be other priorities regarding the next release of ADS but the bug has been opened for over 3 months.
> TimeLimitExceededException with the embedded ADS
> ------------------------------------------------
>
> Key: DIRSERVER-1012
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1012
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: Win XP SP2 / J2RE 1.5.0 / eclipse 3.2.0 / ADS 1.5.0
> Reporter: hirot
> Fix For: 1.5.2
>
> Attachments: trace-log-0(Includes Timout Failure).txt
>
>
> I'm using embedded Apache Directory Server for the unit testing with JUnit in eclipse.
> The environment is :
> - Win XP SP2
> - J2RE 1.5.0
> - eclipse 3.2.0
> - ADS 1.5.0
> Only when a search takes over around 1 second, javax.naming.TimeLimitExceededException is thrown as cited in the following :
> javax.naming.TimeLimitExceededException: [LDAP: error code 3 - failed on search operation]; remaining name 'o=hq,dc=myco,dc=com' at
> When a same search takes less than 1 second, it successfully returns results.
> I'm sure to set 30000 ms to the client side timeout using javax.naming.directory.SearchControls.setTimeLimits(int ms), so the exception is caused by the server side timeout, I suppose.
> Is the server side timeout of ADS 1 second ?
> Is there any measure to lengthen the timeout ?
> (I tried MutableServerStartupConfiguration.setMaxTimeLimit(int arg0). But I am not sure whether a parameter specifies ms or second, and it doesn't seem to work well in the embedded ADS at least because a search successfully returns results when I set 0 or 1 to "MaxTimeLimit".)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.