Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Soap Exceptions on 6.0.8_GA_2661.UBUNTU10_64

  1. #1
    Join Date
    Jun 2007
    Location
    Germany
    Posts
    16
    Rep Power
    8

    Default Soap Exceptions on 6.0.8_GA_2661.UBUNTU10_64

    Hey all. Im experiencing Problems with 6.0.8_GA_2661.UBUNTU10_64 UBUNTU10_64 NETWORK edition on Ubuntu 10.04.1 from time to time.

    Whenever i navigate the Backend (Administrative Console)
    and I click (e.g.) Aliases I get the Popup

    Servererror

    Mail: system failure: ZimbraLdapContext Errorcode: service.FAILURE
    Method: SearchDirectoryRequest Details:soap:Receiver
    Logfiles state:

    2010-10-03 02:17:40,206 INFO [btpool0-111://zimbra.hostname.tld:7071/service/admin/soap/SearchDirectoryRequest] [name=user@hostname.tld;mid=5;ip=93.196.221.251;ua= ZimbraWebClient - SAF3 (Mac);] soap - SearchDirectoryRequest
    2010-10-03 02:17:40,207 INFO [btpool0-111://zimbra.hostname.tld:7071/service/admin/soap/SearchDirectoryRequest] [name=user@hostname.tld;mid=5;ip=93.196.221.251;ua= ZimbraWebClient - SAF3 (Mac);] session - requested session no longer exists: 3422
    2010-10-03 02:17:40,210 INFO [btpool0-111://zimbra.hostname.tld:7071/service/admin/soap/SearchDirectoryRequest] [name=user@hostname.tld;mid=5;ip=93.196.221.251;ua= ZimbraWebClient - SAF3 (Mac);] SoapEngine - handler exception
    com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
    ExceptionId:btpool0-111://zimbra.hostname.tld:7071/service/admin/soap/SearchDirectoryRequest:1286065060209:1149f688c5469 eda
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:416)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:381)
    at com.zimbra.cs.account.ldap.LdapProvisioning.search Objects(LdapProvisioning.java:1263)
    at com.zimbra.cs.account.ldap.LdapProvisioning.search Objects(LdapProvisioning.java:1244)
    at com.zimbra.cs.account.ldap.LdapProvisioning.search Directory(LdapProvisioning.java:4713)
    at com.zimbra.cs.account.ldap.LdapProvisioning.search Directory(LdapProvisioning.java:4650)
    at com.zimbra.cs.session.AccountSearchParams.doSearch (AccountSearchParams.java:92)
    at com.zimbra.cs.session.AdminSession.searchAccounts( AdminSession.java:74)
    at com.zimbra.cs.service.admin.SearchDirectory.handle (SearchDirectory.java:162)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:420)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:274)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
    at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:181)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
    at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
    at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
    at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
    at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:418)
    at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
    at org.mortuserbay.jetty.HttpConnection$RequestHandle r.content(HttpConnection.java:939)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:413)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
    Caused by: javax.naming.CommunicationException: Bad file descriptor [Root exception is java.net.SocketException: Bad file descriptor]
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3213)
    at javax.naming.ldap.InitialLdapContext.extendedOpera tion(InitialLdapContext.java:164)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:406)
    ... 43 more
    Caused by: java.net.SocketException: Bad file descriptor
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutp utStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStre am.java:136)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.sun.jndi.ldap.Connection.writeRequest(Connecti on.java:396)
    at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient .java:1172)
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3160)
    ... 45 more
    Does anyone have an Idea on this?

    Thanks in advance!
    Patrick

  2. #2
    Join Date
    Jun 2007
    Location
    Germany
    Posts
    16
    Rep Power
    8

    Default

    More Errors on IMAP Connect...

    2010-10-03 04:59:10,925 WARN [ImapSSLServer-75] [name=user@host.tld;ip=93.196.221.251;] imap - Unable to get server attribute: zimbraImapExposeVersionOnBanner
    com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
    ExceptionId:ImapSSLServer-75:1286074750925:1149f688c5469eda
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:416)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:366)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getSer verByName(LdapProvisioning.java:2665)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getSer verByNameInternal(LdapProvisioning.java:2654)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getLoc alServer(LdapProvisioning.java:3265)
    at com.zimbra.cs.server.ServerConfig.getLocalServer(S erverConfig.java:165)
    at com.zimbra.cs.server.ServerConfig.getBooleanAttr(S erverConfig.java:157)
    at com.zimbra.cs.imap.ImapConfig.getServerVersion(Ima pConfig.java:46)
    at com.zimbra.cs.server.ServerConfig.getDescription(S erverConfig.java:90)
    at com.zimbra.cs.server.ServerConfig.getGoodbye(Serve rConfig.java:80)
    at com.zimbra.cs.imap.ImapHandler.sendBYE(ImapHandler .java:3728)
    at com.zimbra.cs.imap.ImapHandler.doLOGOUT(ImapHandle r.java:1064)
    at com.zimbra.cs.imap.ImapHandler.executeRequest(Imap Handler.java:446)
    at com.zimbra.cs.imap.TcpImapHandler.processCommand(T cpImapHandler.java:98)
    at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:196)
    at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:139)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: javax.naming.CommunicationException: Bad file descriptor [Root exception is java.net.SocketException: Bad file descriptor]
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3213)
    at javax.naming.ldap.InitialLdapContext.extendedOpera tion(InitialLdapContext.java:164)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:406)
    ... 17 more
    Caused by: java.net.SocketException: Bad file descriptor
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutp utStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStre am.java:136)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.sun.jndi.ldap.Connection.writeRequest(Connecti on.java:396)
    at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient .java:1172)
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3160)
    ... 19 more
    2010-10-03 04:59:10,925 WARN [ImapSSLServer-71] [name=user@host.tld;mid=5;ip=93.196.221.251;] imap - Unable to get server attribute: zimbraImapMaxRequestSize
    com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
    ExceptionId:ImapSSLServer-71:1286074750925:1149f688c5469eda
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:416)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:366)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getSer verByName(LdapProvisioning.java:2665)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getSer verByNameInternal(LdapProvisioning.java:2654)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getLoc alServer(LdapProvisioning.java:3265)
    at com.zimbra.cs.server.ServerConfig.getLocalServer(S erverConfig.java:165)
    at com.zimbra.cs.server.ServerConfig.getIntAttr(Serve rConfig.java:148)
    at com.zimbra.cs.imap.ImapConfig.getMaxRequestSize(Im apConfig.java:122)
    at com.zimbra.cs.imap.ImapRequest.getMaxRequestSize(I mapRequest.java:114)
    at com.zimbra.cs.imap.ImapRequest.incrementSize(ImapR equest.java:104)
    at com.zimbra.cs.imap.TcpImapRequest.continuation(Tcp ImapRequest.java:54)
    at com.zimbra.cs.imap.TcpImapHandler.processCommand(T cpImapHandler.java:83)
    at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:196)
    at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:139)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: javax.naming.CommunicationException: Bad file descriptor [Root exception is java.net.SocketException: Bad file descriptor]
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3213)
    at javax.naming.ldap.InitialLdapContext.extendedOpera tion(InitialLdapContext.java:164)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:406)
    ... 15 more
    Caused by: java.net.SocketException: Bad file descriptor
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutp utStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStre am.java:136)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.sun.jndi.ldap.Connection.writeRequest(Connecti on.java:396)
    at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient .java:1172)
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3160)
    ... 17 more

  3. #3
    Join Date
    May 2010
    Posts
    46
    Rep Power
    5

    Default

    Hi,

    I have the same problem. It's funnfy that all services specialy ldap is running. No evidence of crashing or other problem with LDAP. Just users can not connect to zimbra. And errors in mailbox.log same.

    Who can help? To solve this problem?

    version: Release 6.0.8_GA_2661.UBUNTU10_64 UBUNTU10_64 FOSS edition with patch zcs-patch-6.0.8_GA_2673

  4. #4
    Join Date
    May 2008
    Posts
    432
    Rep Power
    7

    Default

    Again: Searching the forums would have given the answer: See pm.zimbra.com Version 6.0.9 bugs. There is the Ldapcontext thing.

  5. #5
    Join Date
    May 2010
    Posts
    46
    Rep Power
    5

  6. #6
    Join Date
    Jun 2009
    Posts
    131
    Rep Power
    6

    Default

    Is there a way to fix this? Even a dirty hack for now?

    Thanks,

    iMx

  7. #7
    Join Date
    May 2010
    Posts
    46
    Rep Power
    5

    Default

    Hi,

    I think Zimbra Team will release new patch ex. P3 . After this I think will be OK with this problem.

    I'm waiting too

  8. #8
    Join Date
    Jun 2009
    Posts
    131
    Rep Power
    6

    Default

    Version Found: 7.0.0_ZCS_Helix

    From the bug - will they backport though?

  9. #9
    Join Date
    Jun 2007
    Location
    Germany
    Posts
    16
    Rep Power
    8

    Default

    And there we go - even more errors...

    2010-10-12 03:42:02,828 WARN [btpool0-123://zimbra.host.tldhost.tld/Microsoft-Server-ActiveSync?User=user@host.tld&DeviceId=Appl85939M643NP&DeviceType=iPhone&Cmd=Ping] [] misc - failed to get trusted IPs, only localhost will be trusted
    com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
    ExceptionId:btpool0-123://zimbra.host.tld/Microsoft-Server-ActiveSync?User=user@host.tld&DeviceId=Appl85939M643NP&DeviceType=iPhone&Cmd=Ping:1286847722828:08496e5b85cda740
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:416)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:366)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getSer verByName(LdapProvisioning.java:2665)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getSer verByNameInternal(LdapProvisioning.java:2654)
    at com.zimbra.cs.account.ldap.LdapProvisioning.getLoc alServer(LdapProvisioning.java:3265)
    at com.zimbra.cs.servlet.ZimbraServlet.getTrustedIPs( ZimbraServlet.java:486)
    at com.zimbra.cs.servlet.ZimbraServlet.getOrigIp(Zimb raServlet.java:475)
    at com.zimbra.zimbrasync.ZimbraSyncServlet.doPost(Zim braSyncServlet.java:315)
    at com.zimbra.zimbrasync.ZimbraSync$HttpHandler.doPos t(ZimbraSync.java:43)
    at com.zimbra.cs.extension.ExtensionDispatcherServlet .service(ExtensionDispatcherServlet.java:99)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
    at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
    at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
    at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
    at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:418)
    at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
    at org.mortbay.jetty.HttpConnection$RequestHandler.he aderComplete(HttpConnection.java:924)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:547)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:413)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
    Caused by: javax.naming.CommunicationException: Bad file descriptor [Root exception is java.net.SocketException: Bad file descriptor]
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3213)
    at javax.naming.ldap.InitialLdapContext.extendedOpera tion(InitialLdapContext.java:164)
    at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:406)
    ... 37 more
    Caused by: java.net.SocketException: Bad file descriptor
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutp utStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStre am.java:136)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.sun.jndi.ldap.Connection.writeRequest(Connecti on.java:396)
    at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient .java:1172)
    at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCt x.java:3160)
    ... 39 more

  10. #10
    Join Date
    Jun 2009
    Posts
    131
    Rep Power
    6

    Default

    http://www.zimbra.com/forums/adminis...tml#post198066

    Take a read of this post...potential fix in there

Similar Threads

  1. XSD/WSDL Files for the SOAP Server?
    By photoadrian in forum Developers
    Replies: 5
    Last Post: 12-23-2012, 01:32 AM
  2. Jar For Soap Client
    By wcameron in forum Developers
    Replies: 19
    Last Post: 06-03-2009, 02:04 PM
  3. SOAP Authentication Failure, but LDAP ok
    By scottp in forum Administrators
    Replies: 2
    Last Post: 01-20-2008, 08:53 PM
  4. Bug with preauth mechanism and SOAP headers?
    By Coilcore in forum Developers
    Replies: 3
    Last Post: 07-20-2006, 10:41 AM
  5. Soap Requests ...
    By ubumail in forum Developers
    Replies: 2
    Last Post: 04-26-2006, 06:39 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •