Cannot log into Web Manager when HTTP is disabled
Article ID: KB0083070
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | - |
Description
Cannot log into Web Manager when HTTP is disabled.
ERROR [DbChannel-RequestSelectThread] 2017-05-11 11:36:43.073 -0600 ServerChannelConnection - java.io.IOException: Failure with SSL engine 'CLOSED' indicates possible protocol corruption: cs.jdbc.driver.protocol.WireDecoder@43b3c67d
dbuf.position=37
sslUnwrapBuf.position=0
command=null
cmdbuf=
cmdValidated=false
rows=null
fields=null
readingRow=false
ftype=0
flen=-1
largeFieldBuffer=null
bytesRead=37
stringDateDecoding=false
protocolVersion=null
receiveByteEncodedDate=false
receiveTimezoneOffset=false
lastReceivedMessage=ping -1 -1
remote=/127.0.0.1:55465
local=/127.0.0.1:9403.[dbchannel-1908514]
at cs.jdbc.driver.protocol.WireDecoder.processInput(WireDecoder.java:290)
at cs.jdbc.driver.protocol.ChannelConnection.processInput(ChannelConnection.java:371)
at com.compositesw.server.dbchannel.RequestSelectThread.run(RequestSelectThread.java:424)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
DEBUG logs indicate:
(DEBUG [main] 2017-06-28 10:54:40.717 -0600 KeyStoreUtil - Loading keystore "C:\Program Files\Cisco Systems\CIS 7.0\conf\server\security\etringer.us.lmco.com.pfx
ERROR [DbChannel-RequestSelectThread] 2017-05-11 11:36:43.073 -0600 ServerChannelConnection - java.io.IOException: Failure with SSL engine 'CLOSED' indicates possible protocol corruption: cs.jdbc.driver.protocol.WireDecoder@43b3c67d
dbuf.position=37
sslUnwrapBuf.position=0
command=null
cmdbuf=
cmdValidated=false
rows=null
fields=null
readingRow=false
ftype=0
flen=-1
largeFieldBuffer=null
bytesRead=37
stringDateDecoding=false
protocolVersion=null
receiveByteEncodedDate=false
receiveTimezoneOffset=false
lastReceivedMessage=ping -1 -1
remote=/127.0.0.1:55465
local=/127.0.0.1:9403.[dbchannel-1908514]
at cs.jdbc.driver.protocol.WireDecoder.processInput(WireDecoder.java:290)
at cs.jdbc.driver.protocol.ChannelConnection.processInput(ChannelConnection.java:371)
at com.compositesw.server.dbchannel.RequestSelectThread.run(RequestSelectThread.java:424)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
DEBUG logs indicate:
(DEBUG [main] 2017-06-28 10:54:40.717 -0600 KeyStoreUtil - Loading keystore "C:\Program Files\Cisco Systems\CIS 7.0\conf\server\security\etringer.us.lmco.com.pfx
Issue/Introduction
Cannot log into Web Manager when HTTP is disabled
Resolution
Setup the below Debug Configuration to gather additonal logging:
1. Under Configuration-> Server->Communications
Set "Generate SSL Diagnostics" and "Generate SSL Diagnostics(On Server Restart)" to True
After the use case is tried again and the logs are collected, you can set them back to "False"
2. In the Server log4j.properties uncomment the following line:
log4j.logger.com.compositesw.server.security=DEBUG
As per the log, customer is using a pfx file as the keystore
(DEBUG [main] 2017-06-28 10:54:40.717 -0600 KeyStoreUtil - Loading keystore "<INSTALL>\conf\server\security\etringer.us.lmco.com.pfx
Converted pfx certificate to jks file by using the below command:
keytool -importkeystore -srckeystore mypfxfile.pfx -srcstoretype pkcs12 -destkeystore clientcert.jks -deststoretype JKS
Restarted TDV and customer to access the Web Manager successfully.
1. Under Configuration-> Server->Communications
Set "Generate SSL Diagnostics" and "Generate SSL Diagnostics(On Server Restart)" to True
After the use case is tried again and the logs are collected, you can set them back to "False"
2. In the Server log4j.properties uncomment the following line:
log4j.logger.com.compositesw.server.security=DEBUG
As per the log, customer is using a pfx file as the keystore
(DEBUG [main] 2017-06-28 10:54:40.717 -0600 KeyStoreUtil - Loading keystore "<INSTALL>\conf\server\security\etringer.us.lmco.com.pfx
Converted pfx certificate to jks file by using the below command:
keytool -importkeystore -srckeystore mypfxfile.pfx -srcstoretype pkcs12 -destkeystore clientcert.jks -deststoretype JKS
Restarted TDV and customer to access the Web Manager successfully.
Feedback
Yes
No
Powered by
