CipherException: Invalid padding length

Hello there,
I'm having problem to get our certifikates to work properly. I've been searching
BEA's newsgroups and found some things we've tried without any succes.
We have two certificates for our domain because we are using an load balancer(Local
Directory)infront of our two webservers. Our webservers have version 6.1 of WLS
and are managed from an ServerManager(also WLS 6.1).
We us the same ./config/mydomain directory on the ServerManager for both of our
webserver. The filenames for each server in ./config/mydomain are different ex:
my_domain_server1-key.der and my_domain_server2-key.der. We have also checked
that they are correct defind for both servers under each server SSL tag.
We have an newly fetched a CA-cert from Thawte and recived our certificates for
this domain during this week.
Could there be any problem with that we using the
same ./config/mydomain directory on the ServerManager for both of our webserver?
Or does anybody have any other suggestion of what more to check before we fetches
new certificates?
Regards
Lennart

If you are using password encryption, then please make sure KeyEncrypted field is
enabled and please make sure the password which you set for:
-Dweblogic.management.pkpassword is the same as value of the Private Key Password field
of the Certificate Request Generator servlet (please go through the documentation:
http://e-docs.bea.com/wls/docs61/adminguide/cnfgsec.html#1053930
for details).
Please inform whether the problem has been resolved with the above suggestions. Thank
you.
Lennart wrote:
Hello there,
I'm having problem to get our certifikates to work properly. I've been searching
BEA's newsgroups and found some things we've tried without any succes.
We have two certificates for our domain because we are using an load balancer(Local
Directory)infront of our two webservers. Our webservers have version 6.1 of WLS
and are managed from an ServerManager(also WLS 6.1).
We us the same ./config/mydomain directory on the ServerManager for both of our
webserver. The filenames for each server in ./config/mydomain are different ex:
my_domain_server1-key.der and my_domain_server2-key.der. We have also checked
that they are correct defind for both servers under each server SSL tag.
We have an newly fetched a CA-cert from Thawte and recived our certificates for
this domain during this week.
Could there be any problem with that we using the
same ./config/mydomain directory on the ServerManager for both of our webserver?
Or does anybody have any other suggestion of what more to check before we fetches
new certificates?
Regards
Lennart--
Developer Relations Engineer
BEA Support

Similar Messages

  • Weblogic.security.CipherException: Invalid padding length

    I am having some difficulties configuring SSL for WebLogic 6.0.2J (Japanese).
    Here is the history of my problem:
    1. A CSR was generated, but on a completely different platform (Windows) and
    for a slightly older version of WebLogic (6.0.1J)
    2. I was then brought in to install and configure WebLogic 6.0.2J on UNIX.
    3. I was then given the encrypted private key (security_net-chef_net-key.der),
    the CSR files, and the server cert from VeriSign Japan (cert.pem). I went to VeriSign
    Japan to get an intermediate CA cert (Server Chain Cert), which I saved as ca.pem.
    4. In the Admin Console, I configured the server in my target domain with: Server
    Certificate File Name = cert.pem, Trusted CA File Name = ca.pem, and Trusted CA
    File Name = security_net-chef_net-key.der.
    5. When I attempt to start my target server, I am seeing the following alert:
    ===========================================================
    <2001/08/07 13:22:25:JST> <Alert> <WebLogicServer> <&#35469;&#35388;&#12501;&#12449;&#12452;&#12523;
    config/net-chef
    /security_net-chef_net-key.der &#12395;&#12475;&#12461;&#12517;&#12522;&#12486;&#12451;
    &#12467;&#12531;&#12501;&#12451;&#12464;&#12524;&#12540;&#12471;&#12519;&#12531;&#19978;&#12398;&#21839;&#38988;&#12364;&#12354;&#12426;
    &#12414;&#12377;&#12290;java.io.IOException: weblogic.security.CipherException:
    Invalid padding le
    ngth 72>
    java.io.IOException: weblogic.security.CipherException: Invalid padding length
    7
    2
    at weblogic.security.RSAPrivateKeyPKCS8.input(RSAPrivateKeyPKCS8.java:15
    7)
    at weblogic.security.RSAPrivateKeyPKCS8.<init>(RSAPrivateKeyPKCS8.java:1
    25)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:387)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:297)
    at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:942)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:403)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    ===========================================================
    Please note that as I am doing this on a Japanese OS, some of the above messages
    may be rendered illegible.
    If anyone out there has a clue to why I am seeing the above error, I would greatly
    appreciate your help.
    Thanks and aloha in advance,
    Brooke

    See Posting 5457.

  • What cause this error: java.util.zip.ZipException: invalid literal/lengths?

    Hi all,
    Our application produces this error in the logs: (our JDEV is 11.1.1.4.0, WLS 10.3)
    org.apache.myfaces.trinidadinternal.renderkit.core.CoreResponseStateManager _restoreSerializedView
    SEVERE:
    java.util.zip.ZipException: invalid literal/lengths set
    at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:147)
    at java.util.zip.GZIPInputStream.read(GZIPInputStream.java:92)
    at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2266)
    at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2279)
    at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750)
    at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
    at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
    I have googled this error for hours and search the forum here, but no luck. Can someone please shed some light on this error? Thanks in advance!
    Shawn

    Hi Shawn,
    Please refer the below thing i found. Hope this may help you in moving forward in resolving. I hope this issue has occured when you are deploying your application WAR.
    ======================================================================================
    Method: read()
    Class: at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:147)
    The above class comes in your exception hierarchy above.
    Reads uncompressed data into an array of bytes. This method will block until some input can be decompressed.
    Throws:
    ZipException - if a ZIP format error has occurred
    ====================================
    This also points that your WAR file is corrupt.
    Class: GZIPInputStream
    IOException - if an I/O error has occurred or the compressed input data is corrupt
    Thanks,

  • Invalid key length on hard drive. Can this be fixed?

    Hello,
    I have a question about an error I am receiving with a hard drive I have been using for a few months on an imac G3 (the slot loading version). I bought this used 80 GIG hard drive on ebay for a friend of mine and I helped him transfer all his data from his older 9 GIG drive to this newer 80 GIG drive that I bought for him on ebay. I simply cloned the 9 GIG drive onto the new drive using Carbon Copy Cloner. There is not a lot of data on the drive - only about 3 GIGs of data.
    The drive is the only drive in the computer (an imac G3) and therefore it is the startup drive. The operating system on the drive is OS9. All was working fine for a few months until just last week. Now I am receiving this following error:
    error message:
    The disk "Macintosh HD" appears to be damaged. Use a disk repair utility to repair the disk.
    And so I used the disk utility built into OS9 to see if I could repair the problem. (I think OS9's disk utility is called "Disk First Aid")
    When using OS9s disk utility (I think it is called "Disk First Aid") the following report is issued:
    Problem: Invalid key length, 4,943
    Test done. Problems were found but Disk First Aid cannot repair them.
    My questions are:
    What is an "Invalid key length"?
    How serious is this?
    What would cause this?
    Could this have been caused by the physical condition of the disk or possibly by the software on the disk?
    Would re-formatting the drive fix it? (Of course I would try to save any data first onto another disk)
    Or is it risky to continue to use this disk even after reformatting it?
    I guess I have a lot of questions here and if anyone could make any suggestions or comment on why "Invalid key length" errors happen I would really appreciate it. Thanks:)
    Here are some details:
    When I bought the 80 GIG hard drive from ebay the first steps I took were to format the drive using OS9's "drive setup", load the OS9 drivers and then I verifed the disk. The disk seemed to be fine. Then I cloned his old drive onto this 80 GIG drive using Corbon Copy Cloner. I was sure the 80 GIG drive was in a healthy state at that time and I trusted it enough to give it to my friend for his startup drive. Now that the drive has failed with his data and programs, I feel pretty bad. How could this "Invalid key length" error occur?
    Should I go back to the person who sold me the drive on ebay and ask for a refund? Or are "Invalid key length" errors a common occurance with hard drives that should just be accepted? Or might it possibly be the contents (data) on my friend's disk that caused this error.
    It has been suggested to me to use "Tech Tools Pro" or "Disk Warrior" to repair the disk. Hopefully that might repair the disk. Unfortunately these programs are too expensive for this purpose because they would cost more than the computer actually costs (its an old imac G3 computer). I found a service that would run Disk Warrior on the disk to repair it for a $50 fee. Still, that is also not worth it as the computer may not even be worth $50.
    Here are some specifications:
    80 GIG drive specs: SEAGATE BARRACUDA 7200.7 80GB hard drive
    computer: imac G3 (slot loading version)
    OS: Mac OS9
    Thank you for any suggestions especially as to whether I should attempt to return the hard drive or look for a refund for this hard drive or attempt to reformat the drive and try again (backing up the data first).
    I also question the source of all the data on my friends computer. If he had the original operating system disks (which he said didn't come with his computer when he purchased it second-hand), I could have easily re-installed the OS and the applications. But he doesn't have any disks. That serves me right for having to deal with trying to help out someone who has software from a questionable source. I'm never doing that again. I guess that makes me guilty too as an accomplice. I don't feel very good about this
    I didn't know for sure - but I guess I should have assumed his software was illegal if he didn't have the disks - I was afraid to ask. I'm never putting myself in this possibly illegal situation again. Never again will I try to help someone out who doesn't clearly have the legal disks. Please forgive me and everyone else who reads this post. I feel shameful about this but somehow I must get myself out of this problem. I've learned a good lesson. Should I attempt to fix his computer? Or should I tell him to first buy a legal OS and software before I can help him out? You see I feel further guilt because I was the one who gave him the 80 GIG problematic hard drive that failed and I feel I should have to fix it. Can anyone offer me a bit of advice? What do I do?
    What's the right thing to do?

    Thank you Jim and Apple2Freak,
    I appreciate your comments. I am now suggesting to my friend to buy a legal OS and if that is the case I am suggesting to him to move to OSX instead of OS9. Luckily he let me know there wasn't much data on that drive that he needed to save. I am still trying to determine if I could still use this hard drive with the keylength errors if I erase it or if the hard drive has permanent damage. I am hoping that I could install OSX on it and erase the hard drive to start again.
    This imac (slot loading version) can support up to OS 10.3.9 however I might consider Xpostfacto to try to run 10.4. But then I would need to buy 10.3.9 as well as 10.4 and that would double my OS cost. I think I might just look for OS 10.3.9 only. Its not worth it for me to buy two OSes for it.
    Jim, your post was very interesting because it also pointed out that it could be an issue of bad RAM. A few months ago we installed some new second-hand RAM and I wonder if that is the cause of all these problems. I will have to check that first.
    Thanks again!

  • Weblogic upgrade 9.2 - 10.2: Could not perform unpadding: invalid pad byte

    While upgrading a domain from 9.2 to 10.2, I get the following error on running upgrade.sh:
    -bash-3.00$ ./upgrade.sh
    Warning: Cannot convert string "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1" to type FontStruct
    Calling Wizard framework for upgrade: args2: [-mode=gui, -file=wcf/plugin_gui_wizard.xml, -log=/app/bea/bea_10.2/user_projects/upgrade_logs/domain_04292008_152323_1, -p:plugin:plugin.executionPlan.file=resources/portal-upgrade.xml, -p:plugin:I18N_PLUGIN=weblogic/upgrade/i18n_upgrade, -p:plugin:TARGET_VERSION=10.0.1.0]
    weblogic.upgrade.domain.directoryselection.DomainDirectorySelectionPlugIn.validatePlatformDomain: Property set to skip platform domain validation. Skipping...
    <apr 29, 2008 3:23:56 PM CEST> <INFO> <Upgrade> <BEA-800000> <If not present, set the source WebLogic Configuration to:9.0>
    <apr 29, 2008 3:23:56 PM CEST> <INFO> <Upgrade> <BEA-800000> <If not present, set the source WebLogic Configuration to:9.0>
    <apr 29, 2008 3:23:56 PM CEST> <INFO> <Upgrade> <BEA-800000> <Domain directory selected: /app/bea_domains/portal>
    <apr 29, 2008 3:23:56 PM CEST> <INFO> <Upgrade> <BEA-800000> <Domain directory selected: /app/bea_domains/portal>
    <apr 29, 2008 3:24:16 PM CEST> <FATAL> <Upgrade> <BEA-800000> <Execute Exception ... weblogic.descriptor.DescriptorException: Unmarshaller failed>
    com.bea.plateng.plugin.PlugInException: Execute Exception ... weblogic.descriptor.DescriptorException: Unmarshaller failed
    at weblogic.upgrade.domain.directoryselection.DomainDirectorySelectionPlugIn.execute(DomainDirectorySelectionPlugIn.java:261)
    at com.bea.plateng.wizard.plugin.silent.tasks.ExecutePlugInTask.execute(ExecutePlugInTask.java:76)
    at com.bea.plateng.wizard.silent.tasks.AbstractSilentTask.run(AbstractSilentTask.java:28)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: weblogic.descriptor.DescriptorException: Unmarshaller failed
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
    at weblogic.management.provider.internal.DescriptorManagerHelper.loadDescriptor(DescriptorManagerHelper.java:58)
    at weblogic.upgrade.domain.directoryselection.DomainDirectorySelectionPlugIn.parseNewStyleConfig(DomainDirectorySelectionPlugIn.java:416)
    at weblogic.upgrade.domain.directoryselection.DomainDirectorySelectionPlugIn.execute(DomainDirectorySelectionPlugIn.java:226)
    ... 3 more
    Caused by: com.bea.xml.XmlException: weblogic.management.ManagementRuntimeException: weblogic.descriptor.DescriptorException: Unmarshaller failed: com.bea.xml.XmlException: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
    at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)
    at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:483)
    Caused by: weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
    at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:78)
    at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:94)
    at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:87)
    ... 55 more
    Caused by: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
    at com.rsa.jsafe.JA_PKCS5Padding.a(Unknown Source)
    at com.rsa.jsafe.JG_BlockCipher.decryptFinal(Unknown Source)
    at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:68)
    ... 57 more
    Before running upgrade.sh, all applications were undeployed from the domain and I've verified that config.xml is valid with no refs to previously installed apps.
    I've also removed refs to custom security providers in config.xml, but stil the same.
    Can anyone please help?
    Edited by mirzaei at 04/29/2008 7:18 AM

    Fixed.
    The xml-file for one of the jdbc-resources defined in config.xml was missing from DOMAIN_HOME/conf/jdbc. Adding the file fixed the problem.
    Edited by mirzaei at 04/29/2008 11:07 AM

  • Weblogic.security.CipherException: Incorrect block length 256 (modulus

    Hi,
    I have a stand alone java client which runs in the weblogic 8.1 server and when I tried to connect to the external site using the weblogic's HttpsURLConnection ,its throws the below exception.
    weblogic.security.CipherException: Incorrect block length 256 (modulus length 128)
    <Info> <Security> <BEA-090511> <The following exception has occurred:
    weblogic.security.CipherException: Incorrect encrypted block
         at weblogic.security.RSApkcs1.decrypt(RSApkcs1.java:205)
         at weblogic.security.RSAMDSignature.verify(RSAMDSignature.java:89)
         at weblogic.security.X509.verifySignature(X509.java:246)
         at weblogic.security.X509.verify(X509.java:176)
         at weblogic.security.SSL.SSLCertificate.verify(SSLCertificate.java:133)
         at weblogic.security.SSL.SSLCertificate.input(SSLCertificate.java:116)
         at weblogic.security.SSL.Handshake.input(Handshake.java:121)
         at weblogic.security.SSL.SSLSocket.getHandshake(SSLSocket.java:1117)
         at weblogic.security.SSL.SSLSocket.clientInit(SSLSocket.java:432)
         at weblogic.security.SSL.SSLSocket.initialize(SSLSocket.java:276)
         at weblogic.security.SSL.SSLSocket.<init>(SSLSocket.java:222)
         at weblogic.security.SSL.SSLSocketFactory.createSocket(SSLSocketFactory.java:213)
         at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:238)
         at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:389)
         at weblogic.net.http.HttpsClient.<init>(HttpsClient.java:209)
         at weblogic.net.http.HttpClient.New(HttpClient.java:228)
         at weblogic.net.http.HttpsURLConnection.getHttpClient(HttpsURLConnection.java:246)
         at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:217)
         at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:319)
         at HttpsConnect.main(HttpsConnect.java:13)
    <Info> <SSL> <000000> <weblogic.security.AuthenticationException: Incorrect encrypted block possibly incorrect SSLServerCertificateChainFileName set for this server certificate>
    java.io.IOException: weblogic.security.AuthenticationException: Incorrect encrypted block possibly incorrect SSLServerCertificateChainFileName set for this server certificate
    at weblogic.security.SSL.SSLCertificate.verify(SSLCertificate.java:172)
    at weblogic.security.SSL.SSLCertificate.input(SSLCertificate.java:116)
    at weblogic.security.SSL.Handshake.input(Handshake.java:121)
    at weblogic.security.SSL.SSLSocket.getHandshake(SSLSocket.java:1117)
    at weblogic.security.SSL.SSLSocket.clientInit(SSLSocket.java:432)
    at weblogic.security.SSL.SSLSocket.initialize(SSLSocket.java:276)
    at weblogic.security.SSL.SSLSocket.<init>(SSLSocket.java:222)
    at weblogic.security.SSL.SSLSocketFactory.createSocket(SSLSocketFactory.java:213)
    at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:238)
    at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:389)
    at weblogic.net.http.HttpsClient.<init>(HttpsClient.java:209)
    at weblogic.net.http.HttpClient.New(HttpClient.java:228)
    at weblogic.net.http.HttpsURLConnection.getHttpClient(HttpsURLConnection.java:246)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:359)
    at HttpsConnect.main(HttpsConnect.java:13)
    I verified the certifiate chain by using the weblogic's ValidateCertChain utility, and the output seems to be confusing for the intermediate site and the entity site.
    java utils.ValidateCertChain -pem inter.cerCert[0]: CN=VeriSign Class 3 International Server CA - G3,OU=Terms of use at https://www.verisign.com/r
    pa (c)10,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US
    Certificate chain is incomplete, can't confirm the entire chain is valid
    Certificate chain appears valid
    Any pointers will be appreciated.

    This might be because Verisign has included anadditional intermediate certificate in its chain
    You can find it here
    https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR657&actp=search&viewlocale=en_US
    Contact Verisign Support, u can chat with them even...
    Let me know if you have any doubt.
    Cheers!
    Faisal
    http://www.weblogic-wonders.com

  • ERROR com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.

              Hi,
              I am trying to setup cluster environment with weblogic7.0. I have two managed
              servers in my cluster. The first one I am able start without any problem(The first
              server and admin is on the same UNIX m/c). When I am trying to start the second
              server from different m/c(this is another UNIX m/c) it is giving the following
              error. I am not using default security realm.
              If anybody come across this error before,please reply me.
              Thanks
              Venkat
              com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad
              byte.
              at com.rsa.jsafe.JA_PKCS5Padding.performUnpadding(JA_PKCS5Padding.java:111)
              at com.rsa.jsafe.JG_BlockCipher.decryptFinal(JG_BlockCipher.java:1092)
              at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:67)
              at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
              at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
              at weblogic.management.commo.CommoModelMBean.getAttribute(CommoModelMBean.java:319)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              at $Proxy42.getCredential(Unknown Source)
              at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              --------------- nested within: ------------------
              weblogic.security.internal.encryption.EncryptionServiceException - with nested
              exception:
              [com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad
              byte.]
              at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:77)
              at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
              at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
              at weblogic.management.commo.CommoModelMBean.getAttribute(CommoModelMBean.java:319)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              at $Proxy42.getCredential(Unknown Source)
              at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              --------------- nested within: ------------------
              javax.management.RuntimeOperationsException: RuntimeException thrown by the getAttribute
              method of the DynamicMBean for the attribute Credential
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1185)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              at $Proxy42.getCredential(Unknown Source)
              at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              <Dec 7, 2002 8:57:33 PM EST> <Critical> <WebLogicServer> <000364> <Server failed
              during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
              Problem instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              attribute Credential
              weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              >
              <Dec 7, 2002 8:57:33 PM EST> <Emergency> <WebLogicServer> <000342> <Unable to
              initialize the server: Fatal initialization exception
              Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
              instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              attribute Credential
              weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              >
              The WebLogic Server did not start up properly.
              Exception raised:
              weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              Reason: Fatal initialization exception
              Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
              instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              attribute Credential
              weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              at weblogic.Server.main(Server.java:32)
              

    Venkat,
              I assume you are using symmetric ciphers. If soo make sure you
              generate the key for the admin server and copy that to all the managed
              servers in the cluster before you start each of the managed servers. I
              think you are generating keys for each server seperately (which might
              be the reason for the errors you got).
              Hope this helps.
              -Kiran
              "Venkat" <[email protected]> wrote in message news:<[email protected]>...
              > Hi,
              >
              > I am trying to setup cluster environment with weblogic7.0. I have two managed
              > servers in my cluster. The first one I am able start without any problem(The first
              > server and admin is on the same UNIX m/c). When I am trying to start the second
              > server from different m/c(this is another UNIX m/c) it is giving the following
              > error. I am not using default security realm.
              > If anybody come across this error before,please reply me.
              >
              > Thanks
              > Venkat
              >
              > com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad
              > byte.
              > at com.rsa.jsafe.JA_PKCS5Padding.performUnpadding(JA_PKCS5Padding.java:111)
              > at com.rsa.jsafe.JG_BlockCipher.decryptFinal(JG_BlockCipher.java:1092)
              > at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:67)
              > at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
              > at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
              > at weblogic.management.commo.CommoModelMBean.getAttribute(CommoModelMBean.java:319)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              > at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              > at $Proxy42.getCredential(Unknown Source)
              > at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              > at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              > at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > --------------- nested within: ------------------
              > weblogic.security.internal.encryption.EncryptionServiceException - with nested
              > exception:
              > [com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad
              > byte.]
              > at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:77)
              > at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
              > at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:53)
              > at weblogic.management.commo.CommoModelMBean.getAttribute(CommoModelMBean.java:319)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              > at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              > at $Proxy42.getCredential(Unknown Source)
              > at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              > at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              > at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > --------------- nested within: ------------------
              > javax.management.RuntimeOperationsException: RuntimeException thrown by the getAttribute
              > method of the DynamicMBean for the attribute Credential
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1185)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:844)
              > at weblogic.management.commo.CommoProxy.invoke(CommoProxy.java:330)
              > at $Proxy42.getCredential(Unknown Source)
              > at weblogic.security.providers.authentication.LDAPAtnDelegate.<init>(LDAPAtnDelegate.java:452)
              > at weblogic.security.providers.authentication.LDAPAuthenticationProviderImpl.initialize(LDAPAuthenticationProviderImpl.java:67)
              > at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > <Dec 7, 2002 8:57:33 PM EST> <Critical> <WebLogicServer> <000364> <Server failed
              > during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
              > Problem instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              > RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              > attribute Credential
              > weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              > Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              > thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > >
              > <Dec 7, 2002 8:57:33 PM EST> <Emergency> <WebLogicServer> <000342> <Unable to
              > initialize the server: Fatal initialization exception
              > Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
              > instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              > RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              > attribute Credential
              > weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              > Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              > thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > >
              > ***************************************************************************
              > The WebLogic Server did not start up properly.
              > Exception raised:
              > weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              > Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              > thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              > Reason: Fatal initialization exception
              > Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
              > instantiating Authentication Providerjavax.management.RuntimeOperationsException:
              > RuntimeException thrown by the getAttribute method of the DynamicMBean for the
              > attribute Credential
              > weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
              > Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
              > thrown by the getAttribute method of the DynamicMBean for the attribute Credential
              > at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:198)
              > at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:248)
              > at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1574)
              > at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1376)
              > at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
              > at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
              > at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
              > at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
              > at weblogic.Server.main(Server.java:32)
              

  • Invalid segment length (LL) of [1804] in input object-Using J2C Connector

    Hello,
    I have been struggling with this issue for the past 1 week .I am using J2C Connector tools to generate beans that lets us to communicate to cobol programs.
    In cobol code we have declared LL as like this.
    05 LL PIC S9(4) COMP.
    05 ZZ PIC XX.
    Using J2C Connector tools for this cobol programs(input and output records) total 5 fils are generated. Those are
    InputRecord.java,OutputRecord.java,
    java beans:Interface1.java,Interface1Impl.java
    Command Bean: RetrieveDetails.java.
    Here on i am setting all screen values and IMS related stuff in inputrecord
    and executing with this input on commandbean object,then we will get the output record contains all the output data.
    Here the problem is when i am setting the LL value like this and executing i am getting the follwing error.
    InputRecord inputRocord = InputRecord();
    inputrecord.setL1((short) 1804);
    RetrieveDetails commandBean= RetrieveDetails();
    commandBean.set(inputrecord);
    commandBean.execute();
    javax.resource.ResourceException: ICO0024E: [email protected]ldInputMsg(Record)
    error. Invalid segment length (LL) of 19200 in input object. [email protected](byte[):
    And one more quetion is in set() method which type of parameter we can set?
    what i think is , 1804 is total length of variables of cobol file.is it right or not?
    Could anyone help me out this problem.Help would be greatly appreciated.Its very urgent..please.......
    if you drop a mail also to [email protected] would be better.
    Thanks in advance.
    venkat.

    Hi Venkat
    Were you able to solve this issue ? I am having the same problem but could not find the answer.
    Please drop an email at [email protected] if you have any solution.
    Thanks

  • Unable to connect to ACE30 from 3845/2811 -ssh - Invalid modulus length

       Hi,
    I`ve seen quite a lot of posts regarding SSH issues and the above SSH error. However the fix mainly involves upgrading clients but in this instance the client is are Cisco routers 3845 / 2811 - which we use for out and inband management.
    Connectivity / routing etc is proven. Using SSH v2 the actual 6500 chassis where the ACE is physically located works fine. Configuring SSH v1 on the ACE module allows connections via the 3845/2811`s but we cannot use this.
    Both have the following IOS Version 12.4(24)T4. I have tried various key sizes on the ACE module.
    The SSH debug is :
    Aug  8 09:44:00.755: SSH2 CLIENT 2: SSH2_MSG_KEXINIT sent
    Aug  8 09:44:00.767: SSH2 CLIENT 2: ssh_receive: 536 bytes received
    Aug  8 09:44:00.767: SSH2 CLIENT 2: input: total packet length of 776 bytes
    Aug  8 09:44:00.767: SSH2 CLIENT 2: partial packet length(block size)8 bytes,nee                                                                                                                                                             ded 768 bytes,
                   maclen 0
    Aug  8 09:44:00.767: SSH2 CLIENT 2: ssh_receive: 240 bytes received
    Aug  8 09:44:00.767: SSH2 CLIENT 2: partial packet length(block size)8 bytes,nee                                                                                                                                                             ded 768 bytes,
                   maclen 0
    Aug  8 09:44:00.767: SSH2 CLIENT 2: input: padlength 10 bytes
    Aug  8 09:44:00.767: SSH2 CLIENT 2: SSH2_MSG_KEXINIT received
    Aug  8 09:44:00.767: SSH2:kex: server->client enc:aes128-cbc mac:hmac-sha1
    Aug  8 09:44:00.767: SSH2:kex: client->server enc:aes128-cbc mac:hmac-sha1
    Aug  8 09:44:00.767: SSH2 CLIENT 2: send:packet of  length 24 (length also inclu                                                                                                                                                             des padlen of 6)
    Aug  8 09:44:00.767: SSH2 CLIENT 2: SSH2_MSG_KEX_DH_GEX_REQUEST sent
    Aug  8 09:44:00.767: SSH2 CLIENT 2: Range sent- 1024  < 2048  < 4096
    Aug  8 09:44:00.859: SSH2 CLIENT 2: ssh_receive: 424 bytes received
    Aug  8 09:44:00.863: SSH2 CLIENT 2: input: total packet length of 424 bytes
    Aug  8 09:44:00.863: SSH2 CLIENT 2: partial packet length(block size)8 bytes,nee                                                                                                                                                             ded 416 bytes,
                   maclen 0
    Aug  8 09:44:00.863: SSH2 CLIENT 2: input: padlength 10 bytes
    Aug  8 09:44:00.863: SSH2 CLIENT 2: SSH2_MSG_KEX_DH_GEX_GROUP received
    Aug  8 09:44:00.863: SSH2 CLIENT 2:
    Invalid modulus length
    Is there a fix for this issue ?
    Many thanks for any tips/advise.

    I`ve now tried a new version of the code incase it was a bug. ( 12.4 (24) T6 ) and various key sizes ( 768, 1024,2048, 4096) but no avail.
    Oct 12 13:16:26.435: SSH CLIENT0: protocol version id is - SSH-2.0-OpenSSH_5.2
    Oct 12 13:16:26.435: SSH CLIENT0: sent protocol version id SSH-2.0-Cisco-1.25
    Oct 12 13:16:26.435: SSH CLIENT0: protocol version exchange successful
    Oct 12 13:16:26.435: SSH2 CLIENT 0: SSH2_MSG_KEXINIT sent
    Oct 12 13:16:26.447: SSH2 CLIENT 0: SSH2_MSG_KEXINIT received
    Oct 12 13:16:26.447: SSH2:kex: server->client enc:aes128-cbc mac:hmac-sha1
    Oct 12 13:16:26.447: SSH2:kex: client->server enc:aes128-cbc mac:hmac-sha1
    Oct 12 13:16:26.447: SSH2 CLIENT 0: SSH2_MSG_KEX_DH_GEX_REQUEST sent
    Oct 12 13:16:26.447: SSH2 CLIENT 0: Range sent- 1024  < 2048  < 4096
    Oct 12 13:16:26.535: SSH2 CLIENT 0: SSH2_MSG_KEX_DH_GEX_GROUP received
    Oct 12 13:16:26.535: SSH2 CLIENT 0:
    Invalid modulus length
    Oct 12 13:16:26.535: SSH CLIENT0: key exchange failure (code = 0)
    Oct 12 13:16:26.535: SSH CLIENT0: Session disconnected - error 0x00

  • Sparseimage Fails Verification with Invalid Key Length error.

    I recently have been having some trouble with my computer. Every time I log out of my account, all of my preferences reset. This just now started happening. It was working fine, then all of a sudden it started to do this. This only happens on my account and doesnt with the root account. On looking up solutions, I discovered that I should verify my home directory image. I logged in as a different user (root) and used disk utility to verify it. However it failed saying "invalid key length" and "Error: The underlying task reported failure on exit". When I try to repair it, it gives me the same error. I backed up my system using superduper to an external drive a while back and verified the sparseimage file that I backed up. It failed with the same error.
    When I verify my harddrive it passes with no problem. Only my sparseimage file is corrupted. I would try diskwarrior but I cant afford it right now.
    Any help would be greatly appreciated. Thanks.
    Macbook   Mac OS X (10.4.9)   100gb hd; 1gb ram; Triple-Boot(OSX-Linux-Vista)

    Would that mean that I can't turn off filevault? Way I see it is that since the image file is corrupted, I would try to have filevault unencrypt it and see if it somehow fixes it. (Since there will be no longer a filevaut image to be corrupted). All of my data in the image file seems to be fine. Everything is still there and I can access everything.
    I was also thinking that I might be able to just copy everything in the image to my external, then deleting the account and create a new one, coping everything back over when im done.
    I know I probably sound like a noob, but im really not. Ive had a lot of experience with my computer, just not this sorta thing. Thanks for your help.

  • Could not perform unpadding: invalid pad byte.

    Hello All
    In my config file I have 2 references to connection pool files.. In the files I have the following tag.
    <password-encrypted>{3DES}I8OqBHafh35fn6iVd6YXxw==</password-encrypted>
    When I try to run my connection pools are not getting initalized and the following error is displayed
    Could not perform unpadding: invalid pad byte.
    From my limitied knowledge I would just liek to change this to clear text or reencrypt the password. Can anyone help or send a link to an article that would help?
    I am running weblogic 9.2
    Thanks

    You can use the encrypt utility to reencrypt the password.
    http://edocs.bea.com/wls/docs90/admin_ref/utils.html#1209592
    D Walt wrote:
    Hello All
    In my config file I have 2 references to connection pool files.. In the files I have the following tag.
    <password-encrypted>{3DES}I8OqBHafh35fn6iVd6YXxw==</password-encrypted>
    When I try to run my connection pools are not getting initalized and the following error is displayed
    Could not perform unpadding: invalid pad byte.
    From my limitied knowledge I would just liek to change this to clear text or reencrypt the password. Can anyone help or send a link to an article that would help?
    I am running weblogic 9.2
    Thanks

  • Packaging error 2 (The media contains invalid NALU length)

    Hi,
    I am trying to publish live stream from Adobe Flash client that can be viewed on iOS device.  One known issue is that the Flash client does not support AAC audio encoder when it publishes a stream, but AAC is required for iOS viewing.  Thus I am using ffmpeg to transcode the audio to work around this issue.  The setup looks like following:
                                     Publish(h.264+Speex)      Pull               Re-Publish(h.264+AAC)
    Flash Client Publisher -------------------> AMS -----> ffmpeg ---------------------> AMS
    The command line I use for ffmpeg is like this:
    ffmpeg -re -i rtmp://xxx.xxx.xxx.xxx/livepkgr/orgstream -c:v copy -c:a aac -strict -2 -f flv rtmp://xxx.xxx.xxx.xxx/livepkgr/livestream
    This setup works perfectly if the original stream is published by Flash Media Live Encoder client.  However, if the stream is published by a web page using Flash ActionScript client, the iOS won't play the stream.  The root cause is that HLS module failed to generate the proper TS file. I get the following error in the Apache server log.
    [Sat Aug 17 15:56:50 2013] [error] mod_hlshttp [500]: Packaging error 2 (The media contains invalid NALU length) when processing /hls-live/streams/livepkgr/events/_definst_/livestream/livestreamNum0.ts
    I've tried various things to narrow down the possibilities regarding what could be wrong.  Here are some of my observations:
    1) The problem has nothing to do with audio.  If I do audio streaming only, it works well.  So in various experiement, I simplified the problem by doing video stream only.  When using ffmpeg to transcoding, I used '-an' to disable audio stream.
    2) If I use ffmpeg to save the stream into MP4 file first (say 1 minute long), and then publish that file, I got the same issue when iOS device is trying to retrieve content.  The MP4 file generated is fine though.  I can view it using VLC.
    3) If I use ffmpeg to transcode H.264 to H.264 (i.e. Not to use the "copy" transcoder), it then will work.  However, because of the CPU usage constraints in my requirement, I cannot adopt this approach. Here is the command line that works:
    ffmpeg -re -i rtmp://xxx.xxx.xxx.xxx/livepkgr/orgstream  -vcodec libx264 -b:v 1000k -c:a aac -strict -2 -f flv rtmp://xxx.xxx.xxx.xxx/livepkgr/livestream
    4) In all those experiments, the m3u8 file are generated correctly.  In the stream directory I always saw meaningful size for f4f and f4x files.
    5) The iOS client is able to view the original stream fine if the original stream is H.264 video only stream. (The 'orgstream', not the one republished by ffmpeg).
    6) In all those experiements, a regular Flash viewer client is able to play the live stream with no issue.
    Since I don't have access to source code to the Apache module for HLS (mod_hlshttp), I don't know how to proceed further. I appreciate any help from Adobe engineering team who have access to source code, and give me some hint what could go wrong.  I can also provide further information regarding the published stream, e.g. the generated MP4 if it can help.
    Thanks and best regards,
    Jason
    Message was edited by: Json

    The one thing you didn't do is reset your Photoshop preferences.
    Most likely the preferences got corrupted, and reference a corrupt preset.

  • Invalid key length - options

    A couple months ago I had issues installing Lion on my MBP. Upon installing, I was not able to mount the hard drive because of multiple errors. Disk repair eventually worked, I used my Time Machine backup to restore, and got Lion installed. After the installation, I went to make another TM backup and my external hard drive was corrupted to the point where I had to wipe everything on it - not sure what happened with it. Because I had so much trouble getting Lion installed, I didn't mess with creating a new TM backup and wanted to wait until I wasn't so busy at work to attempt it. I did however create a bootable Lion USB drive for emergencies.
    Long story short, the MBP froze the other day and would not boot properly. Clearing the PRAM/VRAM did not help, and when I try disk utility with the bootable USB drive, it is able to verify the drive itself, but unable to mount the startup volume. When I try to verify that volume, it stops and says to repair it. When I try to repair it, it stops and tells me the volume cannot be repaired and I need to back up my files.
    However, when I go into single user mode (running fsck gives me an invalid key length error), I can see the file structure of the drive, and all of my files in read only mode. My questions is, are those files recoverable? If so, how?
    Many thanks for an thoughts

    You have a failing internal hard drive, or some other hardware fault in the mass-storage subsystem. You must replace the drive, or otherwise determine the cause of the fault, immediately. But first you need to back up your data, if it's still possible.
    There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
    1. Boot from your recovery partition (10.7 or later), a local Time Machine backup volume (10.7.2 or later), or your installation disc (10.6.8 or earlier.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
    How to back up and restore your files
    2. If you have a working Mac, and both it and the non-working Mac have FireWire ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive.
    How to use and troubleshoot FireWire target disk mode
    3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

  • Invalid Key Length  Volume check failure

    I have a G4 with 768 Mb of Ram and originally ran as a dual boot system with OS9.2.2 and OSX 10.2. I attempted to upgrade to Tiger. The install kicked out twice. I then re-formatted the hard drive and installed again. I have tried running Disk First Aid, re-booting on Tiger CD, and it gives me an error message.
    Invalid Key Length
    Volume Check Failed
    ERROR: The underlying task reported failure on exit.
    1 HFS volume checked
    1 volume could not be repaired because of an error.
    HELP!!!
    Tried booting on a Norton Utilities disk but it repeatedly also locked on an error.
    Erased disk and attempted again, still no good.
    Finally went back to OS10.2.8 and am up but with still the same error if I run Disk First Aid.

    Welcome to Apple Discussions!
    Norton Utilities is not compatible with Mac OS X 10.2, and will actually cause these Invalid Keylength issues. They stopped supporting Mac OS X nearly two years ago, and even when they did it was Russian Roulette using their software.
    Remove it.
    The first utility software you should always use is a backup utility. Other utilities can supplement backups but should never be used instead of having a backup:
    http://www.macmaps.com/backup.html
    If erasing your hard drive and not installing any third party software upgrading back to 10.2.8 and not having any third party devices connected yielded an invalid keylength, either your 10.2 installation disk is damaged, or is the wrong 10.2 installation disk to use, or the hard drive or its connectors are bad. Try to determine which it is by process of elimination.
    Disclaimer: Reference to links I make to my Macmaps.com website are a for your information only type reference. I do not get any profit from this page, and it is open to the public.

  • "Invalid Key Length"

    Attempting to upgrade an iBook with 10.4.6 from 10.3.9 and getting an "Invalid Key Length" error during disk repair using Disk Utility.
    http://discussions.apple.com/thread.jspa?threadID=1042084
    Is there another way to get beyond this without erasing the HD?

    Yes, but you'll need DiskWarrior to fix the directory problem, since DU can't do it. Hopefully, you have a bootable backup/clone. If so, that allows you to revert to the previous good state without having to reinstall everything. Barring that, you'll have to erase the HD.
    Review these
    http://docs.info.apple.com/article.html?artnum=106941
    http://www.macmaps.com/upgradefaq.html
    http://www.thexlab.com/faqs/installswupdates.html
    http://www.thexlab.com/faqs/backuprecovery.html
    and adopt the necessary habits to mitigate what happened to you.

Maybe you are looking for