Error starting wl61 on a new install
Ravindra Sahasrabudhe
I have installed wl61sp2 on my windows nt box. It gives following exception
when I start the server. Its working on my other machine. What could be
different on this machine?
Thanks
-Ravi
Starting WebLogic Server ....
<Jan 17, 2002 4:13:33 PM PST> <Notice> <Management> <Loading configuration
file .\config\webango\config.xml ...>
***************************************************************************
The WebLogic Server did not start up properly.
Exception raised:
COM.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid
pad byte.
at
COM.rsa.jsafe.JA_PKCS5Padding.performUnpadding(JA_PKCS5Padding.java)
at COM.rsa.jsafe.JG_BlockCipher.decryptFinal(JG_BlockCipher.java)
at
weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptByte
s(JSafeEncryptionServiceImpl.ja
:68)
at
weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptStri
ng(JSafeEncryptionServiceImpl.j
a:94)
at
weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearO
rEncryptedService.java:53)
at
weblogic.management.internal.EncryptedData.decrypt(EncryptedData.java:45)
at
weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.pa
rseMBeanAttributes(Configuratio
arser.java:360)
at
weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.st
artElement(ConfigurationParser.
va:188)
at
weblogic.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1340)
at
weblogic.apache.xerces.validators.common.XMLValidator.callStartElement(XMLVa
lidator.java:1183)
at
weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentS
canner.java:1876)
at
weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(XMLDocumentScanner.java:1252
at
weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:381)
at
weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
at
weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationPars
er.java:105)
at
weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFileReposit
ory.java:261)
at
weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFileReposit
ory.java:223)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy1.loadDomain(Unknown Source)
at
weblogic.management.AdminServer.configureFromRepository(AdminServer.java:188
)
at weblogic.management.AdminServer.configure(AdminServer.java:173)
at weblogic.management.Admin.initialize(Admin.java:239)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Michael Young
This could possibly be the result of corruption of the installation file. Try
downloading WLS and reinstalling again.
Thanks,
Michael
Ravindra Sahasrabudhe wrote:
--
Michael Young
Developer Relations Engineer
BEA Support
Ravindra Sahasrabudhe
Some how it started working . Still don't know why it was not working.
But now I am having same problem with the same instance of weblogic
appserver but different instance of our application.
What could be the reason?
-Ravi
"Michael Young" <Re...@ToNewsgroup.Only> wrote in message
news:3C4C848D...@ToNewsgroup.Only...
Gwyn Evans
>
> Some how it started working . Still don't know why it was not working.
>
> But now I am having same problem with the same instance of weblogic
> appserver but different instance of our application.
>
> What could be the reason?
I had that problem and for me, it appeared to be removed when I
editted the config.xml and replaced the {3DES} password strings
by the cleartext passwords. See
http://groups.google.com/groups?hl=en&selm=3C1DFFD0.657702%40strong-funds.com
for where I saw this fix.
Gwyn