WebLogic Server 10.0 MP1: Error in resource adapter deployment

When I try to deploy our (own implemented) resource adapter into WebLogic Server 10.0 MP1, I get the following error message:
An error occurred during activation of changes, please see the log for details.
weblogic.security.service.InvalidParameterException: weblogic.security.service.SecurityServiceException: [Security:090198]No appropriate constructor for java.util.logging.LoggingPermission
java.util.logging.LoggingPermission.(java.lang.String)
The same adapter works flawless with Oracle AS/OC4J, JBoss 4.2 and Glassfish V2.
In the security-permission-spec element of our ra.xml file we use (beside others) the following permissions:
permission javax.management.MBeanTrustPermission "register";
permission java.util.logging.LoggingPermission "control";
When I delete this two lines from the security-permission-spec element, I can deploy the adapter in WebLogic.
For me this seems to be a bug in WebLogic 10.0MP1.
Best,
Manfred

Re: Installation error: Weblogic Server 10.0 MP2

Similar Messages

  • WebLogic Server 9.2 MP1

    Hello,
    I am trying to download/install WebLogic 9.2 MP1 (as it is required, and is a prerequestie). My OS is Solaris 10 x86 64-bit. On the Oracle download page, when I select my operating system corresponding to WebLogic Server 9.2 MP1, I am lead to a new page, on which the only choice for download I have is for SPARC 32-bit. My question is, if it leads me to SPARC download instead of x86, will it still work? If not, where can I get WebLogic 9.2 MP1 for my OS?
    We tried installing SPARC 32-bit and are getting an 'invalid argument' error everytime we try running the .bat file...
    Any suggestions? Your help is greatly appreciated!!!
    Svetlana

    Hi,
    Can you post the output of below commands from your OS?
    uname -a
    getconf LONG_BIT
    Do you want to download and install 64-bit WLS 9.2 on your OS?
    - - Tarun

  • Weblogic Server 10.0 MP1 while starting: Client VM not supported

    Dear All,
    Installation of Weblogic serever completed successfully but, while starting the weblogic server I am getting the following error/message: Client VM not supported.
    Please provide suggestion or an idea on what to do. The details are provided below.
    Processor: Intel Quad core 64bit
    OS: windows server 2008 R2 64 bit
    Java: JDK 1.5 update 21 64 bit
    Weblogic: Server 10.0 MP1 64 bit for windows
    Regards,
    Edited by: user4198347 on Feb 5, 2011 11:48 PM

    Re: Installation error: Weblogic Server 10.0 MP2

  • JCA Resource adapter deployment in Weblogic server

    Hi,
    I have deployed a resource adapter successfully in Weblogic server and works fine.My resource adapter has weblogic-ra.xml and ra.xml available under meta-inf folder.I have provided some properties in weblogic-ra.xml and ra.xml but unable to see the same properties when i open the resource adapter settings page in the the weblogic administration console
    I want to change resource adapter properties from weblogic adminstration console but dont see the properties which i used during deployment.
    Can someone help with identifying the issue or if i have to do something different.
    Appreciate any help.
    Thanks
    S

    Not sure what might be causing this behavior. Property values in ra/weblogic-ra.xml should be displayed on the console (http://machine:port/console). I think I have experienced similar issue only to realize that console only displays 10 properties and other properties are displayed after pressing Next link on the page.
    How many proprieties you have? What are getting displayed and what properties are not getting displayed?
    Manoj

  • Error in resource adapter cleanup.. javax.resource.ResourceException: java.

    Hi,
    I am getting the following error in my Oracle AS 10g R3 on Solaris .
    Error in resource adapter cleanup.. javax.resource.ResourceException: java.sql.SQLException: Closed Connection
    in log file:apps/oracle/oc4j_home/j2ee/homeMYAPP/log/homeMYAPP_default_group_1/oc4j/log.xml
    (Click on the log file link to download the log or view it as plain text)
    Can any one explain why this error comes.
    Regards,
    Kumar

    Hi,
    I am getting the following error in my Oracle AS 10g R3 on Solaris .
    Error in resource adapter cleanup.. javax.resource.ResourceException: java.sql.SQLException: Closed Connection
    in log file:apps/oracle/oc4j_home/j2ee/homeMYAPP/log/homeMYAPP_default_group_1/oc4j/log.xml
    (Click on the log file link to download the log or view it as plain text)
    Can any one explain why this error comes.
    Regards,
    Kumar

  • Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

    I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
    Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
    When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
    Any suggestion on resolving this problem?
    Thanks
    Ikad

    Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
    Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
    Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
    to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
    Ikad

  • Weblogic server failed to start errors BEA-000362 & BEA-000365

    Hi Friends,
    I'm trying to start weblogic server after starting admin server.I'm getting the below error after
    running the command:
    $ ./startManagedWebLogic.sh
    <Jul 29, 2011 10:09:54 AM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Jul 29, 2011 10:09:55 AM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Jul 29, 2011 10:09:57 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.1.3-11-141760-1.6.0_24-20110301-1430-linux-ia32 from Oracle Corporation>
    <Jul 29, 2011 10:09:58 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Jul 29, 2011 10:09:58 AM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: [Management:141247]The configuration directory /Middleware/SOASuite11gR1/wlserver_10.3/common/bin/config does not exist and the admin server is not available.
    at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:200)
    at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:115)
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:42)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:882)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:572)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
    at weblogic.Server.main(Server.java:71)
    >
    <Jul 29, 2011 10:09:58 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jul 29, 2011 10:09:58 AM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jul 29, 2011 10:09:58 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Do you have any idea how to resolve this error and start weblogic server succesfuly.
    Best regards,
    Edited by: user13311731 on Jul 28, 2011 10:45 PM

    Hi,
    Try starting the managed server with parameters:
    ./startManagedWebLogic.sh myManagedServerName http://serverName:7001
    Does that make a difference?
    Regards Peter

  • Weblogic server 10.3.5 error during SSL handshake

    Please some one help to figure the issue with following logs.
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 33092690>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 33095418>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <33092490 SSL Version data invalid>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Connection to SSL port from Sa-PC - 150.1.104.124 appears to be either unknown SSL version or maybe is plaintext>
    <16-Jan-2013 18:40:40 o'clock GMT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer Sa-PC - 150.1.104.124 during SSL handshake.>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 70
    java.lang.Exception: New alert stack
         at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
         at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
         at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
         at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
         at weblogic.server.channels.DynamicSSLListenThread$1.run(DynamicSSLListenThread.java:130)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33092490>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33092490>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 33092690>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <33095215 SSL Version data invalid>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Connection to SSL port from Sa-PC - 150.1.104.124 appears to be either unknown SSL version or maybe is plaintext>
    <16-Jan-2013 18:40:40 o'clock GMT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer Sa-PC - 150.1.104.124 during SSL handshake.>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 70
    java.lang.Exception: New alert stack
         at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
         at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
         at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
         at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
         at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
         at weblogic.server.channels.DynamicSSLListenThread$1.run(DynamicSSLListenThread.java:130)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33095215>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33095215>
    <16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 33095418>
    I just created domain with http and https ports. I installed an web app. When I am trying to access the app from browser through https the above error is occurring.
    Please somebody help me.
    Thanks in advance.
    SK

    This message indicates that the SSL connection is closed successfully. It is a warning message and normal to see in the logs when you enable the SSL debug flags. This is an expected behavior. If you see alerts when SSL debug is NOT ENABLED then it is a real alert and we need to take care of those issues. Also, it is not a real alert, it is a caught and handled exception from the certicom code which is not harmful and should be ignored, just because you have enabled the SSL debug flag. Once you turn it off, you won't see it in the logs.
    Edited by: sharmela on Jan 22, 2013 4:55 AM

  • Weblogic server 5.1 startup error

    I am using weblogic 5.1 on Solaris 8 (intel) for testing
    when I start up the server, the following error prompt out
    java.lang.UnsatisfiedLinkError: no jsafe in java.library.path
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Error.<init>(Error.java:50)
    at java.lang.LinkageError.<init>(LinkageError.java:43)
    at
    java.lang.UnsatisfiedLinkError.<init>(UnsatisfiedLinkError.java:42)
    at java.lang.ClassLoader.loadLibrary(Compiled Code)
    at java.lang.Runtime.loadLibrary0(Runtime.java:473)
    at java.lang.System.loadLibrary(Compiled Code)
    at COM.rsa.jsafe.JSAFE_DeviceBuilderNative.buildObjects(Compiled
    Code)
    at
    COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(JSAFE_AsymmetricCipher.java
    at COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(Compiled Code)
    at weblogic.security.RSA.performOPJSafe(Compiled Code)
    at weblogic.security.RSA.performOp(RSA.java:104)
    at weblogic.security.RSApkcs1.decrypt(Compiled Code)
    at weblogic.security.RSAMDSignature.verify(RSAMDSignature.java:87)
    at weblogic.security.X509.verifySignature(X509.java:223)
    at
    weblogic.t3.srvr.SSLListenThread.insertIntoCAChain(SSLListenThread.java:192)
    at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
    at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
    at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:140)
    at weblogic.Server.main(Compiled Code)
    at weblogic.Server.main(Server.java:58)
    The java.library.path is
    /usr/java/bin/../jre/bin/../lib/i386:/opt/weblogic/lib/solaris/oci815_8:/opt
    /weblogic/lib/solaris:/usr/lib
    and i am using JSK 1.2.2_07a
    Please help
    Fannie

    That's JVM crash, which is not supposed to happen ;-) You can try to search
    www.javasoft.com for answers, but it looks like Intel Solaris is not terribly
    popular or supported. Did you try to run WebLogic on Linux instead ?
    Fannie <[email protected]> wrote:
    After I add the command to startWebLogic.sh, the server can start up
    properly.
    When I try to test the jsp page through the browser
    The following error message prompt and the server shutdown
    Please help!
    Fannie
    SIGSEGV 11 segmentation violation
    si_signo [11]: SEGV
    si_errno [0]:
    si_code [1]: SEGV_MAPERR [addr: 0x2]
    stackpointer=D639E440
    "SSLListenThread" (TID:0x91a7d28, sys_thread_t:0x91a7c70, state:R, thread_t:
    t@30, threadID:0xd5f50d74, stack_bottom:0xd5f51000, stack_size:0x20000)
    prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
    [4] java.net.ServerSocket.accept(ServerSocket.java:223)
    [5]
    weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java
    :121)
    [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
    [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
    "ListenThread" (TID:0x9171528, sys_thread_t:0x9171470, state:R, thread_t:
    t@29, threadID:0xd5f80d74, stack_bottom:0xd5f81000, stack_size:0x20000)
    prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
    [4] java.net.ServerSocket.accept(ServerSocket.java:223)
    [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
    "ExecuteThread-14" (TID:0x867b8e8, sys_thread_t:0x867b830, state:CW,
    thread_t: t@24, threadID:0xd6320d74, stack_bottom:0xd6321000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-13" (TID:0x86810e8, sys_thread_t:0x8681030, state:CW,
    thread_t: t@23, threadID:0xd6370d74, stack_bottom:0xd6371000,
    stack_size:0x20000) prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2] weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:177)
    [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-12" (TID:0x872cd20, sys_thread_t:0x872cc68, state:R,
    thread_t: t@22, threadID:0xd63a0d74, stack_bottom:0xd63a1000,
    stack_size:0x20000) prio=5 current thread
    [1] weblogic.servlet.jsp.JspLexer.mPAGE_DIRECTIVE(JspLexer.java:3344)
    [2] weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3174)
    [3] weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1636)
    [4] weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1477)
    [5] weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1356)
    [6] weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:786)
    [7] weblogic.servlet.jsp.JspParser.doit(JspParser.java:57)
    [8] weblogic.servlet.jsp.JspParser.parse(JspParser.java:109)
    [9] weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
    [10] weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:235)
    [11] weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:198)
    [12] weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:174)
    [13]
    weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:16
    4)
    [14]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :99)
    [15]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :123)
    [16]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:742)
    [17]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:686)
    [18]
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:247)
    [19]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
    [20] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
    [21] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-11" (TID:0x86c80e8, sys_thread_t:0x86c8030, state:CW,
    thread_t: t@21, threadID:0xd63f0d74, stack_bottom:0xd63f1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-10" (TID:0x8745218, sys_thread_t:0x8745160, state:CW,
    thread_t: t@20, threadID:0xd6fb0d74, stack_bottom:0xd6fb1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-9" (TID:0x867bce8, sys_thread_t:0x867bc30, state:CW,
    thread_t: t@19, threadID:0xd6ff0d74, stack_bottom:0xd6ff1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-8" (TID:0x8742098, sys_thread_t:0x8741fe0, state:CW,
    thread_t: t@18, threadID:0xd7920d74, stack_bottom:0xd7921000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-7" (TID:0x8740ed8, sys_thread_t:0x8740e20, state:CW,
    thread_t: t@17, threadID:0xd7970d74, stack_bottom:0xd7971000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-6" (TID:0x86f40e8, sys_thread_t:0x86f4030, state:CW,
    thread_t: t@16, threadID:0xd79a0d74, stack_bottom:0xd79a1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-5" (TID:0x873dd58, sys_thread_t:0x873dca0, state:CW,
    thread_t: t@15, threadID:0xd79e0d74, stack_bottom:0xd79e1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-4" (TID:0x86ff4e8, sys_thread_t:0x86ff430, state:CW,
    thread_t: t@14, threadID:0xd86b0d74, stack_bottom:0xd86b1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-3" (TID:0x86ffce8, sys_thread_t:0x86ffc30, state:CW,
    thread_t: t@13, threadID:0xd8700d74, stack_bottom:0xd8701000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-2" (TID:0x87134e8, sys_thread_t:0x8713430, state:CW,
    thread_t: t@12, threadID:0xd8730d74, stack_bottom:0xd8731000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-1" (TID:0x8739c70, sys_thread_t:0x8739bb8, state:CW,
    thread_t: t@11, threadID:0xd8760d74, stack_bottom:0xd8761000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "ExecuteThread-0" (TID:0x8739a68, sys_thread_t:0x87399b0, state:CW,
    thread_t: t@10, threadID:0xd8790d74, stack_bottom:0xd8791000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
    [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
    "TimeEventGenerator" (TID:0x869a220, sys_thread_t:0x869a168, state:CW,
    thread_t: t@9, threadID:0xd87c0d74, stack_bottom:0xd87c1000,
    stack_size:0x20000) prio=5
    [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:249)
    [2]
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    :131)
    [3] java.lang.Thread.run(Thread.java:479)
    "SpinnerRandomSource" (TID:0x86e8218, sys_thread_t:0x86e8160, state:CW,
    thread_t: t@8, threadID:0xd87f0d74, stack_bottom:0xd87f1000,
    stack_size:0x20000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2]
    weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:10
    2)
    [3] weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:116)
    Exiting Thread (sys_thread_t:0xdfb7c29c) : no stack
    "Finalizer" (TID:0x81e3940, sys_thread_t:0x81e3888, state:CW, thread_t: t@6,
    threadID:0xdf4e0d74, stack_bottom:0xdf4e1000, stack_size:0x20000) prio=8
    [1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
    [2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
    [3]
    java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:1
    24)
    "Reference Handler" (TID:0x81da690, sys_thread_t:0x81da5d8, state:CW,
    thread_t: t@5, threadID:0xdf510d74, stack_bottom:0xdf511000,
    stack_size:0x20000) prio=10
    [1] java.lang.Object.wait(Object.java:424)
    [2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:130)
    "Signal dispatcher" (TID:0x81a0ea8, sys_thread_t:0x81a0df0, state:MW,
    thread_t: t@4, threadID:0xdf670d74, stack_bottom:0xdf671000,
    stack_size:0x20000) prio=10
    "main" (TID:0x8061728, sys_thread_t:0x8061670, state:CW, thread_t: t@1,
    threadID:0x804c178, stack_bottom:0x8048000, stack_size:0x848000) prio=5
    [1] java.lang.Object.wait(Object.java:424)
    [2] weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1784)
    [3] java.lang.reflect.Method.invoke(Native Method)
    [4] weblogic.Server.startServerDynamically(Server.java:148)
    [5] weblogic.Server.main(Server.java:66)
    [6] weblogic.Server.main(Server.java:58)
    "Dimitri Rakitine" <[email protected]> ¼¶¼g©ó¶l¥ó
    news:[email protected]...
    I do not think there are shared libs for WebLogic on Solaris/Intel.
    You can try disabling native SSL by adding this to WebLogic startup
    command line: -Dweblogic.security.SSL.useJava=true
    Fannie <[email protected]> wrote:
    I am using weblogic 5.1 on Solaris 8 (intel) for testing
    when I start up the server, the following error prompt out
    java.lang.UnsatisfiedLinkError: no jsafe in java.library.path
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Error.<init>(Error.java:50)
    at java.lang.LinkageError.<init>(LinkageError.java:43)
    at
    java.lang.UnsatisfiedLinkError.<init>(UnsatisfiedLinkError.java:42)
    at java.lang.ClassLoader.loadLibrary(Compiled Code)
    at java.lang.Runtime.loadLibrary0(Runtime.java:473)
    at java.lang.System.loadLibrary(Compiled Code)
    at COM.rsa.jsafe.JSAFE_DeviceBuilderNative.buildObjects(Compiled
    Code)
    at
    COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(JSAFE_AsymmetricCipher.java
    at COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(CompiledCode)
    at weblogic.security.RSA.performOPJSafe(Compiled Code)
    at weblogic.security.RSA.performOp(RSA.java:104)
    at weblogic.security.RSApkcs1.decrypt(Compiled Code)
    atweblogic.security.RSAMDSignature.verify(RSAMDSignature.java:87)
    at weblogic.security.X509.verifySignature(X509.java:223)
    at
    weblogic.t3.srvr.SSLListenThread.insertIntoCAChain(SSLListenThread.java:192)
    at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
    at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
    at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:140)
    at weblogic.Server.main(Compiled Code)
    at weblogic.Server.main(Server.java:58)
    The java.library.path is
    /usr/java/bin/../jre/bin/../lib/i386:/opt/weblogic/lib/solaris/oci815_8:/opt
    /weblogic/lib/solaris:/usr/lib
    and i am using JSK 1.2.2_07a
    Please help
    Fannie--
    Dimitri
    Dimitri

  • I can't install weblogic server 10.3 found error

    I have install to 65% and found error.
    i want to know why i can't install weblogic server 10.3 (may be error was create by jdk or anything else Please tell me! )
    and how many  problem  that can happen when install weblogic server 10.3
    ps. - OS that i install is windowsXP  sp2

    Without giving us any details about what error you got, or any circumstances of your environment (just the OS isn't enough), there is no way anyone could give you any help.

  • WebLogic Server 5.1 giving errors of code 500

    Hi,
              We have a system consisting of WebLogic Server 5.1 running on Sparc Solaris and
              JDK 1.2.2 that is going to go into production soon. It houses JSPs and some
              servlets (some of the servlets are JMS clients). The EJBs are kept on another
              Sparc Solaris machine with the same version of WebLogic Server and JDK.
              So far, the EJBs are running fine. However, it is noticed that after running for
              one or two days, the instance of WebLogic Server that houses JSPs would give
              the HTTP error code of 500 whenever it was contacted through a browser. The JMS
              clients in the instance appeared to have stopped, as they did not print out
              texts that were supposed to be shown whenver a message is received. The error
              code of 500 was given for both JSP and HTML accesses. The system would not
              recover from that condition even if it was left running for a few more hours.
              Attaching the WebLogic Server Console to the instance of WebLogic Server
              concerned did not reveal any possible cause, and the console appeared to
              function correctly by providing information on system threads and JSP names
              etc. weblogic.log, access.log and the console output (the messages written by
              WebLogic Server to the terminal where it was started) did not reveal anything
              unusual.
              Wondering if anyone has encountered the same problem. Will appreciate any
              help.
              Thanks in advance.
              Hann Wei
              

    Hann
              Before upgrading to service pack 6 for WebLogic Server 5.1. After first
              starting up the WLS, a user would see our index.html, but then would see
              error code 500 when trying to access the first JSP. A user would have to
              hit the browser back button and try again and the first JSP page would come
              up.
              I would suggest that you see if service pack 6 will have any impact on your
              problem, and see if that helps your situation.
              John J. Feigal Voice (651)766-8787 (main)
              Sr. Technical Consultant (651)766-7249 (direct)
              Ensodex, Inc. Fax (651)766-8792
              4105 N. Lexington Ave., Suite 150 email [email protected]
              Arden Hills, MN 55126 WebSite http://www.ensodex.com
              "Hann Wei Toh" <[email protected]> wrote in message
              news:[email protected]..
              > The systems have service pack 5 applied.
              >
              > Hann Wei
              

  • Weblogic Server 10.0 MP1 on RHEL5 StartUp Issues

    I am a newbie to Weblogic on RHEL. Havin issues with Weblogic to start up. I tried installing with root or a non root user but still the same result.
    Its get stuck at Initializing state and never move on from there.
    <BEA-000365> <Server state changed to STARTING>
    <BEA-002900> <Initializing self-tuning thread pool>
    Please let me know how to resolve this. I dunno if its a permission issue or not cos with root too its the same case .
    I tried to create a new domain with configure.sh, gave the user name and password too while startup but still it doesnt move from this line.
    Kindly let me know how to trace where n why its stuck .. or pls help me with the correct procedure to install

    Hi,
    Specially in Linux Environments sometimes we face issue of Locked Threads while starting some new processes...It happens many times because of less Entropy...Please refer to : http://weblogic-wonders.com/weblogic/2010/07/29/issues-relating-to-urandomrandom-on-weblogic-server-in-linux-environment/ for more details ....
    Above may be one of the reason.
    Thanks
    jay SenSharma
    http://weblogic-wonders.com/ /(Wonders Are Here)

  • Resource Adapter Deployment Error (Resolved)

    This Problem Has Been Resolved.
    I'm trying to develop an application using Inbound resource adapters on Weblogic 9.2.1 .
    I have the resource adapter and the MDB packaged separately. The MDB appears to deploy successfully, but the resource adapter does not.
    I get the following exception
    javax.naming.NamingException [Root exception is java.rmi.RemoteException: javax.naming.InitialContext; nested exception is:
         java.io.NotSerializableException: javax.naming.InitialContext]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:97)
         at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:421)
         at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:297)
         at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:389)
         at weblogic.connector.deploy.JNDIHandler.bindRA(JNDIHandler.java:575)
         at weblogic.connector.common.RAInstanceManager.putRAintoJNDITree(RAInstanceManager.java:1361)
         at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:432)
         A similar issues was referenced in this message :
         http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4330872
         It appears that the exception means the InitialContext is not serializable.
         This is my start(BootstrapContext) method in my resource adapter. If I DO NOT call new InitialContext(), or setMDBOnMessageMethod(), the exception does not occur.
    public void start(BootstrapContext ctx)
         this.ctx = ctx;
         System.out.println("entering AddScanResourceAdapterImpl start");
         logger.info("entering AddScanResourceAdapterImpl start");
         try
         this.JNDIContext = new InitialContext(); // This causes the exception.
         this.wm = this.ctx.getWorkManager(); // Calling this does not cause and exception.
         setMDBOnMessageMethod(); // This also appears to cause the same exception.
         catch (Exception e)
              System.out.println("AddScanRA start : Exception thrown: " + e);
         // TODO: Log problem.     
         logger.info("exiting AddScanResourceAdapterImpl start");
    private void setMDBOnMessageMethod()
    try
    Class socketListenerClass = com.fedex.ground.tms.mtms.server.addscan.connector.ra.AddScanSocketHandler.class;
    Class[] paramTypes      = { java.net.Socket.class };
    this.onMessageMethod      = socketListenerClass.getMethod("onMessage", paramTypes);
    catch (NoSuchMethodException ex)
    ex.printStackTrace();
    Thanks for your any help,
    John
    Edited by johnbrod20 at 04/17/2007 6:48 AM

    Hi John,
    One of my customer is facing the same error .
    Can you please share the resolution of this problem

  • Commit error of resource adapter in Application Resources of nwa

    Hi All,
    I am trying to configure SAP RFC with MII Message Listener XMIIRFC02
    While i am updating(XMIIRFC01) SAP details in Resource Adapter of Application Resource in nwa(SAP NetWeaver )
    And when i click the save button its showing below error.
    "Saving Resource Adapter: XMIIRFC02 failed due to: Configuration changes for resource adapter not committed"
    And if i check the Log Details, its showing below exception
    Exception: 
    [EXCEPTION]
    com.sap.engine.services.connector.exceptions.ConnectorException: Connector remote administration exception.
    Any idea regarding this error
    Thanks in advance
    Kind Regards,
    Praveen Reddy M
    Edited by: praveen2425 on Feb 27, 2012 1:57 PM

    Hi Michael,
    Thanks for your responses,
    Its showing for all and here i am trying to update SAP details in the XMIIRFC02 properties of Resource Adapters
    @Sarathi
    I have checked all the things, even i have reentered all the SAP details but no luck
    Before doing all this i have done in SAP netweaver for XMIIRFC02 in below navigation
    Configuration Management --> Infrastructure --> Application Resources --> select Resource Adapter --> select XMIIRFC02 --> go to properties and update all the details of SAP
    Is this process can work and update the message listener XMIIRRC02 with SAP server and client
    And while i am clicking update button of message listener XMIIRFC02 from MII Menu Screen, Its showing popup error message 
    "Cannot update Configuration; JRA XMIIRFC02 must be configured in SAP NetWeaver Administrator before it is used"
    Thanks,
    Kind Regards,
    Praveen Reddy M
    Edited by: praveen2425 on Feb 29, 2012 7:48 AM

  • Strange Lookup Error (SAP Resource Adapter)

    Hi all,
    I received a quite stange error (Below you can see the relavent part of the logfile).
    While the first attempt to get the ConnectionFactory of the SAP JRA succeeds, the second one fails. As you can see,  context and parameters of the lookup are exactly the same. Does anybody has experiences with this problem?
    Thanks a lot
    Nadine
    <b>1st attempt</b>
    DEBUG SAPEngine_Application_Thread[impl:3]_18 com.xxx.ik.ejb.srouter.util.SystemRouterUtil - return jca
    name: java:comp/env/SAPJCA
    INFO SAPEngine_Application_Thread[impl:3]_18 com.xxx.ik.ejb.sap.generic.bo.SAPGenericBO - search for
    JCA Adapter: java:comp/env/SAPJCA
    DEBUG SAPEngine_Application_Thread[impl:3]_18 com.xxx.ik.ejb.sap.generic.bo.SAPGenericBO -
    connectionfactory: com.sap.mw.jco.jra.JRA$ConnectionFactoryImpl@1d4445d
    <b>2nd attempt</b>
    DEBUG SAPEngine_Application_Thread[impl:3]_1 com.xxx.ik.ejb.srouter.util.SystemRouterUtil - return jca
    name: java:comp/env/SAPJCA
    INFO SAPEngine_Application_Thread[impl:3]_1 com.xxx.ik.ejb.sap.generic.bo.SAPGenericBO - search for JCA Adapter: java:comp/env/SAPJCA
    ERROR SAPEngine_Application_Thread[impl:3]_1 com.xxx.ik.ejb.sap.generic.bo.SAPGenericBO -
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/SAPJCA.

    Hi Vladimir,
    First of all, thanks a lot for your answer.
    I'm sure the application was not restarted or redeployed (as only about one minute has passed between the two attempts). During the processing of our application, this resource adapter (and the class that calls it) is used two times.
    I searched the JNDI tree as you recommended and found:
    * ejbContexts [Context]
        * t-systems.com [Context]
          * Integrationkernel [Context]
            * sap [Context]
              * generic [Context]
                * SAPGenericEJB [Context]
                  * java:comp [Context]
                    ORB
                    HandleDelegate
                    UserTransaction
                    * env [Context]
                      SAPJCA
    As I am only migrating this application, I just had a deeper look into method calls.
    The application consists of a web app which calls ejbs. The EJBs in turn are just Wrapper for the so called BusinessObjects (Beans). In the first attempt the SAPGenericEJB calls the SAPGenericBO which does the lookup. In the second attempt, the SAPGenericBO is called directly from a workflow-engine. Could it be, that this causes the problem? If so, what can I do? Define the resource reference in the WF-Module too? Thanks...
    Nadine
    Message was edited by: Nadine Kress

Maybe you are looking for