BEA Guardian Support for WLS 10

I am running Weblogic Server 10 and was wondering if Guardian supports it. I read in one FAQ that Guardian supports WLS 8.1 and up, but cannot get it to work with 10.
I tried to manually deploy the Agent to my local server, but I do not see a supported *.jar file for weblogic10. I attempted to deploy the Agent using the jar for weblogic9, but continue to get an error message stating that "Guardian is unable to verify that the agent has been properly deployed to all running servers..."
Any help is appreciated.

Hi, the latest version of OCCAS (formerly known as WLSS) 4.0 is based on WLS 10.3 and Java 1.6.
Regards
Graham Pearce
Senior Manager, Oracle Support

Similar Messages

  • Platform Support for WLS 5.1 SP9 and / or WLS 6.x

    When will BEA support WLPS with either WLS 5.1 SP9 or WLS 6.x?

    Should have been more specific:
    When will BEA support WLPS __3.2__ with either WLS 5.1 SP9 or WLS 6.x? The
    docs say it currently only supports WLS 5.1 sp6/sp8, depending on platform.
    Are there plans for BEA to support WLPS __3.5__ with WLS 5.1 SP9? The doc
    says it currently only supports WLS 6.x
    Jesus M. Salvo Jr. wrote:
    >
    When will BEA support WLPS with either WLS 5.1 SP9 or WLS 6.x?

  • Apache plugin support for WLS  6.1 is not working for me.

    Following are the additional configurations I used in httpd.conf after doing LoadModule
    & AddModule
    Alias /weblogic "/opt/BEA/wlserver6.1/config/petstore/applications"
    <Location /weblogic>
    SetHandler weblogic-handler
    </Location>
    <IfModule mod_weblogic.c>
    WebLogicHost localhost
    WebLogicPort 7003
    </IfModule>
    I get Permission denied & not even 403/forbidden for Petstore example jsps. I
    am trying
    to proxy it by URL basis not on mime type. I tried doing same thing for one of
    my own domains
    & server. The results were same. Now, If I try to comment out the Alias line from
    my httpd.conf
    file, it gives me 404 error. Can anyone help me out in this regard? I doubt my
    configurations
    in my weblogic's config.xml file.
    Thanks,
    Naveen

    Hi.
    I'm not clear on what you are trying to accomplish with the alias pointing to the absolute
    path of your WLS applications directory. This is not how the plugin works. As you have it
    set up now the plugin looks for URLs with /weblogic in them and proxies those requests to a
    running instance of WLS.
    For example, the plugin will accept the following URL and forward it to WLS:
    http://host:port/weblogic/index.html
    WLS will respond IF you have a webapp named weblogic. From your example it looks like you
    are trying to proxy to the petstore example. The URL to access the petstore example that
    ships with wls is something like: http://localhost:7003/estore/control/main so if you want
    to proxy by path you may want to proxy when the path contains /estore instead of /weblogic.
    Hope this helps.
    Michael
    Naveen wrote:
    Following are the additional configurations I used in httpd.conf after doing LoadModule
    & AddModule
    Alias /weblogic "/opt/BEA/wlserver6.1/config/petstore/applications"
    <Location /weblogic>
    SetHandler weblogic-handler
    </Location>
    <IfModule mod_weblogic.c>
    WebLogicHost localhost
    WebLogicPort 7003
    </IfModule>
    I get Permission denied & not even 403/forbidden for Petstore example jsps. I
    am trying
    to proxy it by URL basis not on mime type. I tried doing same thing for one of
    my own domains
    & server. The results were same. Now, If I try to comment out the Alias line from
    my httpd.conf
    file, it gives me 404 error. Can anyone help me out in this regard? I doubt my
    configurations
    in my weblogic's config.xml file.
    Thanks,
    Naveen--
    Michael Young
    Developer Relations Engineer
    BEA Support
    [att1.html]

  • Workshop Support for WLS 9.0

    I have been trying to evaluate the potential of WLS 9.0 using Beehive and Pollinate, only to discover that BEA may be developing the Workshop plugin for Eclipse themselves, and that the Pollinate project is dead.
    Could somebody from BEA please give the official word on their plans to support Workshop in WLS 9.0.
    Thanks,
    Neil

    Our sales rep told us yesterday that Workshop for WLS9 will be available around the end of the year.
    Until then there is no upgrade path for current workshop apps either. That means that apps developed in Workshop 8.1 won't run in WLS9 apparently.

  • Oracle 11g Support For WLS 10 and WLS 9.2

    Hi,
    Does anyone know where I can find out definatively when Weblogic 10 and 9.2 will officially support Oracle 11g ?
    Any official BEA sources here.
    Cheers
    Simon

    There is only one real answer here: test it and test it thoroughly. Asking this question here is pointless, you cannot trust anyone here to give you advice you can rely on. Whatever is said, you have to validate the claims anyway.
    Or did you think that Oracle employees were going to answer your question? If so, you are sadly mistaken. Oracle charges money for giving technical support.

  • Support for 'rport' parameter

    RFC3581 specifies that if a client sends 'rport' parameter in the 'Via' header, the server will issue response to the client from the source port rather than to the port written in the Via header.
    Despite BEA mentioning support for the rfc [url http://e-docs.bea.com/wlcp/wlss30/confignetwork/network_ex.html#wp1084515]here, I cannot get weblogic to return responses to a different port.
    I am not working with any type of proxy between the client and the server.
    What can I do to solve this problem?

    Hi Dan,
    I assume that you have a NAT between your client and server. Is that true? If not, the server shouldn't change the port when replying. 'rport' is there to instruct the server to reply to the actual physical address/port from which the request was sent instead of the 'From' address. Without a NAT between your client and server, those 2 addresses/ports are the same. I'm working in a similar area, but with a NAT in the picture. The SIP server does indeed honor the 'rport' parameter.
    Regards,
    Brian.

  • Commercial support for OpenJPA in Weblogic 10

    Hello,
    We are evaluvating OpenJPA available on Weblogic 10 (not KODO) & are very keen in using the same in future projects. We were interested to know whether the BEA commercial support for Weblogic platform also extends to OpenJPA. i.e. do we need to purchase support for our production environment from a separate commercial vendor or does BEA provide support for OpenJPA too.
    regards
    Vikram Karinje

    At moment there is no support for OAuth in OSB.
    Ni pedo k...

  • WLS support for SC_NOT_MOFIDIED (304) status code

    Hi all,
    We are using WLS 7.0 and noticed that it does not support the conditional retrieval
    of URL for static content (ie html pages and gif files etc). This is true at least
    for web application deployed with either a war file or "exploded" directory structure.
    For those of you who not familiar with this status code, it basically enables
    browser to send IF-MODIFIED-SINCE header with a http request. The server is supposed
    to check if a new version exisits and if not, returns status code 304. This would
    speed up things for an application with large number of static images, css or
    html files. We are quite surprised that a leading product like WLS would omit
    somthing so basic. So we are not sure if there is a place to turn it on or off?
    If there is simply no support for this feature, can someone provide some explaination
    as to the rationale behind it? We have some idea, but would rather hear it directly
    from BEA. Thanks.

    No, we have consolidated on the Apache XML/XSL stuff. You are free to use
    whatever other parser you would like however. The Sun XML pkg should work
    fine.
    Thanks,
    Michael
    Michael Girdley
    BEA Systems Inc
    "Boris Tabenkin" <[email protected]> wrote in message
    news:[email protected]..
    Are you still including the sun XML package, and if so which version?
    "Toby Allsopp" <[email protected]> wrote in message
    news:[email protected]..
    Hi, Craig.
    Craig Macha wrote:
    Our company typically does NOT use Open Source products. We can't
    risk
    not having support.
    I think you're a little confused about what "Open Source" means. Itdoesn't mean "unsupported." If you want support then you need to pay forit,
    just like any software. One of the advantages of open source software is
    that you aren't tied to a single vendor for your support - anyone with the
    appropriate skills can take the source code and
    provide support, as BEA have chosen to do in this case.
    Regards,
    Toby Allsopp.

  • Clustering support for BEA Weblogic Enterprise for Solaris/SUN HA

              Hi,
              Does BEA WLE 5.0.1/5.1 support SUN's SunCluster 2.X HA Framework for the Sun
              Enterprise set of Hardware?
              If not - do you plan to provide support for it in any future releases?
              Thanks and regards
              Mark O'Brien
              

    Look for WLS 10.3 under Oracle rather than BEA group.
    Konstantin

  • Support for the creation of a new BEA WebLogic Application Server v10.3

    To All,
    After downloading and installing the Enterprise Pack for Eclipse (Ganymede: http://download.oracle.com/otn_software/oepe/ganymede) I attempted to create a new BEA WebLogic 10.3 server - since that is the version of the application server that I have installed on my machine.
    I went to create the new server and selected "BEA WebLogic Server v10.0", since there was no option to select a WebLogic 10.3 server. I selected as the WebLogic Home directory "D:\BEA_HOME\wlserver_10.3" and received the error message: "The path "D:\BEA_HOME\wlserver_10.3" contains the wrong version of WebLogic Server. Expected version 10.0. Found version 10.3."
    Is there some way that I can create a new WLS v10.3 in Eclipse Ganymede? Do I need to download an additional plugin?
    Thanks in advance for your help on this,
    John Livingstone

    Look for WLS 10.3 under Oracle rather than BEA group.
    Konstantin

  • Does the JRE 1.5 is supported for the WLS 8.1SP3 client

    Hi,
    Does the JRE 1.5 is supported for the WLS 8.1SP3 client
    Regards,
    Ahamad

    Hi,
    Does the JRE 1.5 is supported for the WLS 8.1SP3 client
    Regards,
    Ahamad

  • Full servlet 2.3 support in WLS 6.1 available?

              Hi,
              I have succeffully ported a servlet 2.3 based web app to WLS 7.0. The same code
              generates compile errors when compiling against WLS 6.1 sp4 jar.
              Here is the list of inconsistencies as documented in 6.1 notes - go to http://edocs.bea.com/wls/docs61/notes/new.html
              and search for "Servlet API Classes" you should see table with the following classes
              that are not fully 2.3 compatible.
              javax.servlet.Filter
              javax.servlet.ServletContext
              javax.servlet.ServletContextAttributesListener
              javax.servlet.http.HttpServletResponse
              javax.servlet.http.HttpSession
              javax.servlet.http.HttpSessionAttributesListener
              For some classes I a rename works fine, however other are more problematic.
              Is there a patch for WLS 6.1 that fully supports servlet 2.3 specification? Or,
              what else would you suggest?
              Thanks,
              Radu
              

              WLS6.1 supports Public Final Draft 1 of Servlet 2.3 specification, not the Servlet
              specification 2.3.
              Refer to
              http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_clfydoc&answerpage=solution&page=wls%2FS-10618.htm
              thanks,
              Deepak
              "Radu" <[email protected]> wrote:
              >
              >Hi,
              >
              >I have succeffully ported a servlet 2.3 based web app to WLS 7.0. The
              >same code
              >generates compile errors when compiling against WLS 6.1 sp4 jar.
              >
              >Here is the list of inconsistencies as documented in 6.1 notes - go to
              >http://edocs.bea.com/wls/docs61/notes/new.html
              >and search for "Servlet API Classes" you should see table with the following
              >classes
              >that are not fully 2.3 compatible.
              >
              >javax.servlet.Filter
              >javax.servlet.ServletContext
              >javax.servlet.ServletContextAttributesListener
              >javax.servlet.http.HttpServletResponse
              >javax.servlet.http.HttpSession
              >javax.servlet.http.HttpSessionAttributesListener
              >
              >For some classes I a rename works fine, however other are more problematic.
              >
              >Is there a patch for WLS 6.1 that fully supports servlet 2.3 specification?
              > Or,
              >what else would you suggest?
              >
              >Thanks,
              >Radu
              >
              >
              >
              

  • (268625273) Q WSI-29 Can you give any performance benchmarks for WLS web services?

    Q<WSI-29> Can you give any performance benchmarks for WLS web services?
    A<WSI-29>: It is very difficult to quantify performance aspects of web services
    since they depend on so many variables including but not limited to: backend system
    processing by stateless session beans and message driven beans, size of XML SOAP
    message sent, system hardware (CPU speed, parallel processing, RAM speed) and
    system software (JVM type and version of WebLogic server). However, let me point
    out that the EJB backend processing of requests both have the best possible scalability
    within the EJB2.0 specification (both stateless session and message driven beans
    can be pooled) and servlets have a proven scalable track record. Thus it should
    be possible to scale your web service deployment to meet demand. The overhead
    in processing XML within the servlet can be significant depending on the size
    of XML data (either as a parameter or a return type). While WLS6.1 does not have
    any features to address this performance concern, WLS7.0 will feature Serializer
    and Deserializer classes which can be dedicated to the XML to Java and Java to
    XML translation (they can also be automatically be generated from a DTD, XML Schema
    or regular JavaBean).
    It is true that web services are not the fastest way to process client requests
    but BEA is committed to making WebLogic server the fastest possible service provider.
    Adam

    see http://www.oracle.com/support/products/oas/sparc30/html/ows08811.html

  • Oracle support for Weblogic 7 under LINUX

    Hi,
    Does anyone know what happened to oracle support in weblogic 7.0 for linux platform,
    as it seems that the drivers are not included? Are there any discussions on that
    topic anywhere?
    thanks.
    Zlatko

    It DOES appear that there is support for WebLogic jDriver for Oracle on Linux:
    see http://e-docs.bea.com/wls/certifications/certifications/redhat_linux.html#39532
    The strange thing here is that, apparently, the Oracle drivers located @ lib/linux/i686/oci817_8/libweblogicoci38.so
    and lib/linux/i686/oci817_8/libweblogicoxa38.so are "Type 2" ODBC drivers which
    require an Oracle client to be installed on the WebLogic machine, but Oracle doesn't
    support installation of the client on RedHat 7.2, which is required (according
    BEA's doc) for installation of WebLogic 7.0. Can someone reconcile this apparent
    conflict?
    Laurent Goldsztejn <[email protected]> wrote:
    Hi,
    There is currently no support for WebLogic jDriver for Oracle on Linux
    with WLS 7.0. Please check the following page for update on this topic.
    http://www.weblogic.com/platforms/index.html#jdbc
    Zlatko Mesaros wrote:
    Hi,
    Does anyone know what happened to oracle support in weblogic 7.0 forlinux platform,
    as it seems that the drivers are not included? Are there any discussionson that
    topic anywhere?
    thanks.
    Zlatko
    Thank you,
    Laurent Goldsztejn
    Developer Relations Engineer
    BEA Support

  • KDC has no support for encryption type (14)

    I have come across a posting on "KDC has no support for encryption type (14)" - " http://www.webservertalk.com/message1277232.html"
    and believe that I am hitting the same problem. However, there is no solution. Can anybody help?
    I have done all the necessary steps suggested, including changing the registry and removing the unwanted SPN, but the error still there. The only different is probably I combined WebLogic and AD in one machine. But, does that make any difference?
    Client
    ====
    Name: ssoclient.ssow2k.com
    OS: Win XP SP2
    Server
    =====
    Name: ssow2kserver.ssow2k.com
    OS: Windows 2000 Advanced Server SP4
    WLS: BEA WebLogic 8.1.4
    <<Registry>>
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters
    Value Name: allowtgtsessionkey
    Value Type: REG_DWORD
    Value: 0x01
    The following is the WebLogic myserver log for your reference:
    ========================================================================================
    ####<Apr 6, 2006 2:55:20 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): Resource: type=<url>, application=console, contextPath=/console, uri=/*>
    ####<Apr 6, 2006 2:55:20 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): Role:>
    ####<Apr 6, 2006 2:55:20 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> < roleName: Admin>
    ####<Apr 6, 2006 2:55:20 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> < roleName: Operator>
    ####<Apr 6, 2006 2:55:20 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> < roleName: Deployer>
    ####<Apr 6, 2006 2:55:20 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> < roleName: Monitor>
    ####<Apr 6, 2006 2:55:20 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): Built role expression of {Rol(Admin,Operator,Deployer,Monitor)}>
    ####<Apr 6, 2006 2:55:20 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): policy {Rol(Admin,Operator,Deployer,Monitor)} successfully deployed for resource type=<url>, application=console, contextPath=/console, uri=/*>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): Resource: type=<url>, application=mySampleWebApp, contextPath=/mysamplewebapp, uri=/*, httpMethod=GET>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): Role:>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> < roleName: DCMS_ROLE>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): Built role expression of {Rol(DCMS_ROLE)}>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): policy {Rol(DCMS_ROLE)} successfully deployed for resource type=<url>, application=mySampleWebApp, contextPath=/mysamplewebapp, uri=/*, httpMethod=GET>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): Resource: type=<url>, application=mySampleWebApp, contextPath=/mysamplewebapp, uri=/*, httpMethod=POST>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): Role:>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> < roleName: DCMS_ROLE>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): Built role expression of {Rol(DCMS_ROLE)}>
    ####<Apr 6, 2006 2:55:22 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <main> <<WLS Kernel>> <> <000000> <Default Authorization deployPolicy(): policy {Rol(DCMS_ROLE)} successfully deployed for resource type=<url>, application=mySampleWebApp, contextPath=/mysamplewebapp, uri=/*, httpMethod=POST>
    ####<Apr 6, 2006 3:02:07 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <000000> < PrincipalAuthenticator.assertIdentity - Token Type: Authorization>
    ####<Apr 6, 2006 3:02:07 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <ExecuteThread: '14' for queue: ' weblogic.kernel.Default'> <<WLS Kernel>> <> <000000> <Found Negotiate with SPNEGO token>
    ####<Apr 6, 2006 3:02:08 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <ExecuteThread: '14' for queue: ' weblogic.kernel.Default'> <<WLS Kernel>> <> <000000> <GSS exception GSSException: Failure unspecified at GSS-API level (Mechanism level: KDC has no support for encryption type (14))
    GSSException: Failure unspecified at GSS-API level (Mechanism level: KDC has no support for encryption type (14))
    at sun.security.jgss.krb5.Krb5Context.acceptSecContext(Krb5Context.java:734)
    at sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:300)
    at sun.security.jgss.GSSContextImpl.acceptSecContext (GSSContextImpl.java:246)
    at weblogic.security.providers.utils.SPNEGONegotiateToken.getUsername(SPNEGONegotiateToken.java:371)
    at weblogic.security.providers.authentication.SinglePassNegotiateIdentityAsserterProviderImpl.assertIdentity (SinglePassNegotiateIdentityAsserterProviderImpl.java:201)
    at weblogic.security.service.PrincipalAuthenticator.assertIdentity(PrincipalAuthenticator.java:553)
    at weblogic.servlet.security.internal.CertSecurityModule.checkUserPerm (CertSecurityModule.java:104)
    at weblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.java:199)
    at weblogic.servlet.security.internal.CertSecurityModule.checkA(CertSecurityModule.java:86)
    at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:145)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3685)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Apr 6, 2006 3:02:08 PM GMT+08:00> <Debug> <SecurityDebug> <ssow2kserver> <myserver> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <000000> <Exception weblogic.security.providers.utils.NegotiateTokenException: GSSException: Failure unspecified at GSS-API level (Mechanism level: KDC has no support for encryption type (14))
    weblogic.security.providers.utils.NegotiateTokenException : GSSException: Failure unspecified at GSS-API level (Mechanism level: KDC has no support for encryption type (14))
    at weblogic.security.providers.utils.SPNEGONegotiateToken.getUsername(SPNEGONegotiateToken.java:419)
    at weblogic.security.providers.authentication.SinglePassNegotiateIdentityAsserterProviderImpl.assertIdentity(SinglePassNegotiateIdentityAsserterProviderImpl.java:201)
    at weblogic.security.service.PrincipalAuthenticator.assertIdentity (PrincipalAuthenticator.java:553)
    at weblogic.servlet.security.internal.CertSecurityModule.checkUserPerm(CertSecurityModule.java:104)
    at weblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.java :199)
    at weblogic.servlet.security.internal.CertSecurityModule.checkA(CertSecurityModule.java:86)
    at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:145)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3685)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
    at weblogic.kernel.ExecuteThread.execute (ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    ========================================================================================
    The following are some krb5 packets captured. I suspected it is due to the encryption type used - RC4-HMAC:
    ========================================================================================
    KRB5 (AS-REQ)
    ============
    No. Time Source Destination Protocol Info
    125 10.301166 10.122.1.2 10.122.1.200 KRB5 AS-REQ
    Frame 125 (345 bytes on wire, 345 bytes captured)
    Arrival Time: Apr 6, 2006 13:49:54.848903000
    Time delta from previous packet: 0.008330000 seconds
    Time since reference or first frame: 10.301166000 seconds
    Frame Number: 125
    Packet Length: 345 bytes
    Capture Length: 345 bytes
    Protocols in frame: eth:ip:udp:kerberos
    Ethernet II, Src: 10.122.1.2 (00:0c:29:17:9a:be), Dst: Vmware_59:2c:e6 (00:0c:29:59:2c:e6)
    Destination: Vmware_59:2c:e6 (00:0c:29:59:2c:e6)
    Source: 10.122.1.2 (00:0c:29:17:9a:be)
    Type: IP (0x0800)
    Internet Protocol, Src: 10.122.1.2 (10.122.1.2), Dst: 10.122.1.200 (10.122.1.200)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
    0000 00.. = Differentiated Services Codepoint: Default (0x00)
    .... ..0. = ECN-Capable Transport (ECT): 0
    .... ...0 = ECN-CE: 0
    Total Length: 331
    Identification: 0x0158 (344)
    Flags: 0x00
    0... = Reserved bit: Not set
    .0.. = Don't fragment: Not set
    ..0. = More fragments: Not set
    Fragment offset: 0
    Time to live: 128
    Protocol: UDP (0x11)
    Header checksum: 0x208d [correct]
    Source: 10.122.1.2 (10.122.1.2 )
    Destination: 10.122.1.200 (10.122.1.200)
    User Datagram Protocol, Src Port: 1075 (1075), Dst Port: kerberos (88)
    Source port: 1075 (1075)
    Destination port: kerberos (88)
    Length: 311
    Checksum: 0x1133 [correct]
    Kerberos AS-REQ
    Pvno: 5
    MSG Type: AS-REQ (10)
    padata: PA-ENC-TIMESTAMP PA-PAC-REQUEST
    Type: PA-ENC-TIMESTAMP (2)
    Type: PA-PAC-REQUEST (128)
    KDC_REQ_BODY
    Padding: 0
    KDCOptions: 40810010 (Forwardable, Renewable, Canonicalize, Renewable OK)
    Client Name (Principal): ssouser
    Realm: SSOW2K.COM
    Server Name (Service and Instance): krbtgt/SSOW2K.COM
    till: 2037-09-13 02:48:05 (Z)
    rtime: 2037-09-13 02:48:05 (Z)
    Nonce: 1870983219
    Encryption Types: rc4-hmac rc4-hmac-old rc4-md4 des-cbc-md5 des-cbc-crc rc4-hmac-exp rc4-hmac-old-exp
    Encryption type: rc4-hmac (23)
    Encryption type: rc4-hmac-old (-133)
    Encryption type: rc4-md4 (-128)
    Encryption type: des-cbc-md5 (3)
    Encryption type: des-cbc-crc (1)
    Encryption type: rc4-hmac-exp (24)
    Encryption type: rc4-hmac-old-exp (-135)
    HostAddresses: SSOCLIENT<20>
    KRB5 (AS-REP)
    ============
    No. Time Source Destination Protocol Info
    126 10.303156 10.122.1.200 10.122.1.2 KRB5 AS-REP
    Frame 126 (1324 bytes on wire, 1324 bytes captured)
    Arrival Time: Apr 6, 2006 13:49:54.850893000
    Time delta from previous packet: 0.001990000 seconds
    Time since reference or first frame: 10.303156000 seconds
    Frame Number: 126
    Packet Length: 1324 bytes
    Capture Length: 1324 bytes
    Protocols in frame: eth:ip:udp:kerberos
    Ethernet II, Src: Vmware_59:2c:e6 (00:0c:29:59:2c:e6), Dst: 10.122.1.2 (00:0c:29:17:9a:be)
    Destination: 10.122.1.2 (00:0c:29:17:9a:be)
    Source: Vmware_59:2c:e6 (00:0c:29:59:2c:e6)
    Type: IP (0x0800)
    Internet Protocol, Src: 10.122.1.200 (10.122.1.200), Dst: 10.122.1.2 (10.122.1.2)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
    0000 00.. = Differentiated Services Codepoint: Default (0x00)
    .... ..0. = ECN-Capable Transport (ECT): 0
    .... ...0 = ECN-CE: 0
    Total Length: 1310
    Identification: 0x0a0f (2575)
    Flags: 0x00
    0... = Reserved bit: Not set
    .0.. = Don't fragment: Not set
    ..0. = More fragments: Not set
    Fragment offset: 0
    Time to live: 128
    Protocol: UDP (0x11)
    Header checksum: 0x1403 [correct]
    Source: 10.122.1.200 (10.122.1.200)
    Destination: 10.122.1.2 (10.122.1.2)
    User Datagram Protocol, Src Port: kerberos (88), Dst Port: 1075 (1075)
    Source port: kerberos (88)
    Destination port: 1075 (1075)
    Length: 1290
    Checksum: 0xb637 [correct]
    Kerberos AS-REP
    Pvno: 5
    MSG Type: AS-REP (11)
    Client Realm: SSOW2K.COM
    Client Name (Principal): ssouser
    Ticket
    enc-part rc4-hmac
    Encryption type: rc4-hmac (23)
    Kvno: 1
    enc-part: E3610239EACDD0E6D4E89AA7D81A355F6C93B95D95B13B56...
    KRB5 (TGS-REQ)
    ============
    No. Time Source Destination Protocol Info
    127 10.309350 10.122.1.2 10.122.1.200 KRB5 TGS-REQ
    Frame 127 (1307 bytes on wire, 1307 bytes captured)
    Arrival Time: Apr 6, 2006 13:49:54.857087000
    Time delta from previous packet: 0.006194000 seconds
    Time since reference or first frame: 10.309350000 seconds
    Frame Number: 127
    Packet Length: 1307 bytes
    Capture Length: 1307 bytes
    Protocols in frame: eth:ip:udp:kerberos
    Ethernet II, Src: 10.122.1.2 (00:0c:29:17:9a:be), Dst: Vmware_59:2c:e6 (00:0c:29:59:2c:e6)
    Destination: Vmware_59:2c:e6 (00:0c:29:59:2c:e6)
    Source: 10.122.1.2 (00:0c:29:17:9a:be)
    Type: IP (0x0800)
    Internet Protocol, Src: 10.122.1.2 (10.122.1.2), Dst: 10.122.1.200 (10.122.1.200)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
    0000 00.. = Differentiated Services Codepoint: Default (0x00)
    .... ..0. = ECN-Capable Transport (ECT): 0
    .... ...0 = ECN-CE: 0
    Total Length: 1293
    Identification: 0x0159 (345)
    Flags: 0x00
    0... = Reserved bit: Not set
    .0.. = Don't fragment: Not set
    ..0. = More fragments: Not set
    Fragment offset: 0
    Time to live: 128
    Protocol: UDP (0x11)
    Header checksum: 0x1cca [correct]
    Source: 10.122.1.2 (10.122.1.2)
    Destination: 10.122.1.200 ( 10.122.1.200)
    User Datagram Protocol, Src Port: 1076 (1076), Dst Port: kerberos (88)
    Source port: 1076 (1076)
    Destination port: kerberos (88)
    Length: 1273
    Checksum: 0xd085 [correct]
    Kerberos TGS-REQ
    Pvno: 5
    MSG Type: TGS-REQ (12)
    padata: PA-TGS-REQ
    Type: PA-TGS-REQ (1)
    KDC_REQ_BODY
    Padding: 0
    KDCOptions: 40800000 (Forwardable, Renewable)
    Realm: SSOW2K.COM
    Server Name (Service and Instance): HTTP/ssow2kserver.ssow2k.com
    till: 2037-09-13 02:48:05 (Z)
    Nonce: 1871140380
    Encryption Types: rc4-hmac rc4-hmac-old rc4-md4 des-cbc-md5 des-cbc-crc rc4-hmac-exp rc4-hmac-old-exp
    Encryption type: rc4-hmac (23)
    Encryption type: rc4-hmac-old (-133)
    Encryption type: rc4-md4 (-128)
    Encryption type: des-cbc-md5 (3)
    Encryption type: des-cbc-crc (1)
    Encryption type: rc4-hmac-exp (24)
    Encryption type: rc4-hmac-old-exp (-135)
    KRB5 (TGS-REP)
    ============
    No. Time Source Destination Protocol Info
    128 10.310791 10.122.1.200 10.122.1.2 KRB5 TGS-REP
    Frame 128 (1290 bytes on wire, 1290 bytes captured)
    Arrival Time: Apr 6, 2006 13:49:54.858528000
    Time delta from previous packet: 0.001441000 seconds
    Time since reference or first frame: 10.310791000 seconds
    Frame Number: 128
    Packet Length: 1290 bytes
    Capture Length: 1290 bytes
    Protocols in frame: eth:ip:udp:kerberos
    Ethernet II, Src: Vmware_59:2c:e6 (00:0c:29:59:2c:e6), Dst: 10.122.1.2 (00:0c:29:17:9a:be)
    Destination: 10.122.1.2 (00:0c:29:17:9a:be)
    Source: Vmware_59:2c:e6 (00:0c:29:59:2c:e6)
    Type: IP (0x0800)
    Internet Protocol, Src: 10.122.1.200 (10.122.1.200), Dst: 10.122.1.2 (10.122.1.2)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
    0000 00.. = Differentiated Services Codepoint: Default (0x00)
    .... ..0. = ECN-Capable Transport (ECT): 0
    .... ...0 = ECN-CE: 0
    Total Length: 1276
    Identification: 0x0a10 (2576)
    Flags: 0x00
    0... = Reserved bit: Not set
    .0.. = Don't fragment: Not set
    ..0. = More fragments: Not set
    Fragment offset: 0
    Time to live: 128
    Protocol: UDP (0x11)
    Header checksum: 0x1424 [correct]
    Source: 10.122.1.200 (10.122.1.200)
    Destination: 10.122.1.2 (10.122.1.2)
    User Datagram Protocol, Src Port: kerberos (88), Dst Port: 1076 (1076)
    Source port: kerberos (88)
    Destination port: 1076 (1076)
    Length: 1256
    Checksum: 0x1318 [correct]
    Kerberos TGS-REP
    Pvno: 5
    MSG Type: TGS-REP (13)
    Client Realm: SSOW2K.COM
    Client Name (Principal): ssouser
    Ticket
    enc-part rc4-hmac
    Encryption type: rc4-hmac (23)
    Kvno: 1
    enc-part: 4D2A9E8590CC716EA6571B093B6FAF89537B0B89F832C073...
    ========================================================================================
    Can anybody enlighten me on how you solve this problem? Thanks.

    I ran into this error and caught the error code to remind me to edit the registry.
    if (sError.contains("KDC has no support for encryption type (14)")){
                        JOptionPane.showMessageDialog(null,"Error " + ThisErrorCode.myErrorCode() + '\n' +
                        " http://support.microsoft.com/default.aspx?scid=kb;en-us;308339" + '\n' + '\n' +
                        "There is a known issue involving Windows clients running Windows 2000 SP4, XP SP2." + '\n' +
                        "To avoid the error, administrators need to update the Windows registry." + '\n' +
                        "The registry key, allowtgtsessionkey, should be added, and its value set correctly" + '\n' +
                        "to allow session keys to be sent in the Kerberos Ticket-Granting Ticket." + '\n' + '\n' +
                        "Windows XP SP2, add the registry entry:" + '\n' +
                        "HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Lsa\\Kerberos\\" + '\n' +
                        "Value Name: allowtgtsessionkey" + '\n' +
                        "Value Type: REG_DWORD" + '\n' +
                        "Value: 0x01" ,null, JOptionPane.ERROR_MESSAGE);
                        System.exit(-1);

Maybe you are looking for