Receiving Error "DPR-ERR-2202" when testing JDBC connections Cognos 11.0.13

[plip]

Hello everyone, I am new to the forums here but hoping someone can point me in the right direction.  We have just recently installed Cognos 11.0.13 on a Linux (RHEL7) server and are having some issues making jdbc connections.  Our Cognos installation is a (single-server, everything on one box) setup and our database (DB2) is on a separate server.  When we have all of our URIs inside 'cogconfig' set to 'http' we are able to connect un-securely to our unsecure database port as well as securely (using ssl and certs) to our secure database port.  However, if we change our URIs to 'https' the un-secure and secure connection tests fail with the error listed below.  The jdbc connection string and certs are the same, the only thing that is changing is the URI.  I've also noticed that when we have everything set to 'https' the parameters that I add to our jdbc connection string don't get picked up.  For instance I can add random characters to our connection string but I don't get any syntax error but just get the error below. 

Error:  "DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit"

I've googled this error quite a bit and seen some info on modifying the jvm heap size which I have done but have not seen any affect from that. 

Has anyone else seen this behavior?  Any advice on how to resolve this would be much appreciated.  Thanks!!

Patrick

[MFGF]

Hello everyone, I am new to the forums here but hoping someone can point me in the right direction.  We have just recently installed Cognos 11.0.13 on a Linux (RHEL7) server and are having some issues making jdbc connections.  Our Cognos installation is a (single-server, everything on one box) setup and our database (DB2) is on a separate server.  When we have all of our URIs inside 'cogconfig' set to 'http' we are able to connect un-securely to our unsecure database port as well as securely (using ssl and certs) to our secure database port.  However, if we change our URIs to 'https' the un-secure and secure connection tests fail with the error listed below.  The jdbc connection string and certs are the same, the only thing that is changing is the URI.  I've also noticed that when we have everything set to 'https' the parameters that I add to our jdbc connection string don't get picked up.  For instance I can add random characters to our connection string but I don't get any syntax error but just get the error below. 

Error:  "DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit"

I've googled this error quite a bit and seen some info on modifying the jvm heap size which I have done but have not seen any affect from that. 

Has anyone else seen this behavior?  Any advice on how to resolve this would be much appreciated.  Thanks!!

Patrick

Hi,

When you enabled ssl in your instance, did you also amend the JDBC URL to add the ':sslConnection=true;' clause? I also assume the ssl connection to your Db2 instance is open on a different port to the non-ssl connection - did you change the port accordingly in the URL?

Cheers!

MF.

[plip]

Hello,

> When you enabled ssl in your instance, did you also amend the JDBC URL to add the ':sslConnection=true;' clause?

Yes, when I have everything set to 'http' I have to add that parameter to the string in order to connect to our secure port.  If I add that parameter when everything is set to 'https' it has no effect.  I can literally put something like "sslConnection=!@#$%%" and I still get the same error listed.  No syntax error or anything. 

> I also assume the ssl connection to your Db2 instance is open on a different port to the non-ssl connection - did you change the port accordingly in the URL?

Yes, I have changed the port setting accordingly.

Thanks!!

Patrick

[MFGF]

Hello,

> When you enabled ssl in your instance, did you also amend the JDBC URL to add the ':sslConnection=true;' clause?

Yes, when I have everything set to 'http' I have to add that parameter to the string in order to connect to our secure port.  If I add that parameter when everything is set to 'https' it has no effect.  I can literally put something like "sslConnection=!@#$%%" and I still get the same error listed.  No syntax error or anything. 

> I also assume the ssl connection to your Db2 instance is open on a different port to the non-ssl connection - did you change the port accordingly in the URL?

Yes, I have changed the port setting accordingly.

Thanks!!

Patrick

Hmmm, ok. That all sounds fine. Where are you defining the connection - is it a new Data Server connection defined in the CA UI or are you using the old Data Source connection URL from within the Admin Console?

Cheers!

MF.

[plip]

Hi,

>Where are you defining the connection - is it a new Data Server connection defined in the CA UI or are you using the old Data Source connection URL from within the Admin Console?

Yes, I'm defining the connection in the admin console (manage tab - content admin - data source connections)

Thanks!

[MFGF]

Hi,

>Where are you defining the connection - is it a new Data Server connection defined in the CA UI or are you using the old Data Source connection URL from within the Admin Console?

Yes, I'm defining the connection in the admin console (manage tab - content admin - data source connections)

Thanks!

Just as a sanity check, do you see the same issue if you define the connection as a Data Server from the Manage menu?

MF.

[plip]

Thanks for the suggestion MF

>Just as a sanity check, do you see the same issue if you define the connection as a Data Server from the Manage menu?

I tried creating/testing the connection from that Data Server section with same results and same error... :<

Thanks!

Patrick

[MFGF]

Thanks for the suggestion MF

>Just as a sanity check, do you see the same issue if you define the connection as a Data Server from the Manage menu?

I tried creating/testing the connection from that Data Server section with same results and same error... :<

Thanks!

Patrick

It sounds like it's time to dig a little deeper. The next thing I'd check is if you are seeing any further related error message in cogserver.log - these might give a pointer to what is causing the issue if they are in there.

Cheers!

MF.

[plip]

Hi,

> It sounds like it's time to dig a little deeper. The next thing I'd check is if you are seeing any further related error message in cogserver.log - these might give a pointer to what is causing the issue if they are in there.

Yes, I am seeing an error in the cognos server log.  Seems to be an issue starting the query service (stack trace listed below if you're interested).  I'm sure this error is not a good thing but I'm not sure if this is directly tied to the jdbc connection issue.  As far as the query service goes, I'm a bit lost.  It's complaining about a null pointer but I have no idea where that pointer would be.  From a logic perspective it just doesn't make sense that the connections work with 'http' URIs but fail with 'https' URIs. 

Stack Trace for the query service issue follow:

2021-05-26T08:11:16.367-0400    ERROR   com.cognos.pogo.services.DispatcherServices     [Timer-46]                              NA                                                              LinkageError in start of service queryService
java.lang.ExceptionInInitializerError: null
        at java.lang.J9VMInternals.ensureError(J9VMInternals.java:147) ~[?:2.9 (09-01-2020)]
        at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:136) ~[?:2.9 (09-01-2020)]
        at org.apache.commons.httpclient.protocol.Protocol.lazyRegisterProtocol(Protocol.java:143) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.protocol.Protocol.getProtocol(Protocol.java:117) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.HttpHost.<init>(HttpHost.java:107) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.HttpMethodBase.setURI(HttpMethodBase.java:280) ~[commons-httpclient-3.1.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesComponentFactory$V5DataServerProcess.waitForRemoteInformation(CubingServicesComponentFactory.java:900) ~[xqeService.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesComponentFactory$V5DataServerProcess.start(CubingServicesComponentFactory.java:846) ~[xqeService.jar:?]
        at com.cognos.pogo.reportservice.ProcessFacade.createServerProcess(ProcessFacade.java:303) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:163) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:122) ~[p2pd.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesComponentFactory$V5DataServerProcessFacade.<init>(CubingServicesComponentFactory.java:382) ~[xqeService.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesComponentFactory.newProcessFacade(CubingServicesComponentFactory.java:329) ~[xqeService.jar:?]
        at com.cognos.pogo.reportservice.ProcessManager.createProcessFacade(ProcessManager.java:521) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessManager.startProcess(ProcessManager.java:497) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessManager.startInitialProcesses(ProcessManager.java:371) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessManager.start(ProcessManager.java:302) ~[p2pd.jar:?]
        at com.cognos.pogo.async.service.connection.bibustkserver.BIBusTKServerConnectionFactory.startProcessManager(BIBusTKServerConnectionFactory.java:456) ~[p2pd.jar:?]
        at com.cognos.pogo.async.service.connection.bibustkserver.BIBusTKServerConnectionFactory.start(BIBusTKServerConnectionFactory.java:578) ~[p2pd.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesConnectionFactory.start(CubingServicesConnectionFactory.java:1398) ~[xqeService.jar:?]
        at com.cognos.pogo.async.service.AsyncRequestHandler.start(AsyncRequestHandler.java:281) ~[p2pd.jar:?]
        at com.cognos.pogo.services.DefaultHandlerService.start(DefaultHandlerService.java:88) ~[p2pd.jar:?]
        at com.cognos.pogo.services.DispatcherServices.start(DispatcherServices.java:218) [p2pd.jar:?]
        at com.cognos.pogo.services.DispatcherServices.continueStartup(DispatcherServices.java:475) [p2pd.jar:?]
        at com.cognos.pogo.services.DispatcherServices.configure(DispatcherServices.java:164) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.RefreshController.composeAndConfigureServices(RefreshController.java:122) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.RefreshController.run(RefreshController.java:82) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.startConfiguration(BootstrapConfigurePublish.java:170) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.checkConfiguration(BootstrapConfigurePublish.java:149) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.access$000(BootstrapConfigurePublish.java:34) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish$ConfigurationCheckTask.safeRun(BootstrapConfigurePublish.java:141) [p2pd.jar:?]
        at com.cognos.pogo.util.threads.SafeTimerTask.run(SafeTimerTask.java:40) [p2pd.jar:?]
        at java.util.TimerThread.mainLoop(Timer.java:566) [?:1.8.0]
        at java.util.TimerThread.run(Timer.java:516) [?:1.8.0]
Caused by: java.lang.NullPointerException
        at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.<init>(SSLProtocolSocketFactory.java:124) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.<init>(SSLProtocolSocketFactory.java:116) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.<init>(SSLProtocolSocketFactory.java:112) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.<clinit>(SSLProtocolSocketFactory.java:97) ~[commons-httpclient-3.1.jar:?]
        ... 32 more

Thanks!

Patrick

[MFGF]

Hi,

> It sounds like it's time to dig a little deeper. The next thing I'd check is if you are seeing any further related error message in cogserver.log - these might give a pointer to what is causing the issue if they are in there.

Yes, I am seeing an error in the cognos server log.  Seems to be an issue starting the query service (stack trace listed below if you're interested).  I'm sure this error is not a good thing but I'm not sure if this is directly tied to the jdbc connection issue.  As far as the query service goes, I'm a bit lost.  It's complaining about a null pointer but I have no idea where that pointer would be.  From a logic perspective it just doesn't make sense that the connections work with 'http' URIs but fail with 'https' URIs. 

Stack Trace for the query service issue follow:

2021-05-26T08:11:16.367-0400    ERROR   com.cognos.pogo.services.DispatcherServices     [Timer-46]                              NA                                                              LinkageError in start of service queryService
java.lang.ExceptionInInitializerError: null
        at java.lang.J9VMInternals.ensureError(J9VMInternals.java:147) ~[?:2.9 (09-01-2020)]
        at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:136) ~[?:2.9 (09-01-2020)]
        at org.apache.commons.httpclient.protocol.Protocol.lazyRegisterProtocol(Protocol.java:143) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.protocol.Protocol.getProtocol(Protocol.java:117) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.HttpHost.<init>(HttpHost.java:107) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.HttpMethodBase.setURI(HttpMethodBase.java:280) ~[commons-httpclient-3.1.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesComponentFactory$V5DataServerProcess.waitForRemoteInformation(CubingServicesComponentFactory.java:900) ~[xqeService.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesComponentFactory$V5DataServerProcess.start(CubingServicesComponentFactory.java:846) ~[xqeService.jar:?]
        at com.cognos.pogo.reportservice.ProcessFacade.createServerProcess(ProcessFacade.java:303) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:163) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessFacade.<init>(ProcessFacade.java:122) ~[p2pd.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesComponentFactory$V5DataServerProcessFacade.<init>(CubingServicesComponentFactory.java:382) ~[xqeService.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesComponentFactory.newProcessFacade(CubingServicesComponentFactory.java:329) ~[xqeService.jar:?]
        at com.cognos.pogo.reportservice.ProcessManager.createProcessFacade(ProcessManager.java:521) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessManager.startProcess(ProcessManager.java:497) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessManager.startInitialProcesses(ProcessManager.java:371) ~[p2pd.jar:?]
        at com.cognos.pogo.reportservice.ProcessManager.start(ProcessManager.java:302) ~[p2pd.jar:?]
        at com.cognos.pogo.async.service.connection.bibustkserver.BIBusTKServerConnectionFactory.startProcessManager(BIBusTKServerConnectionFactory.java:456) ~[p2pd.jar:?]
        at com.cognos.pogo.async.service.connection.bibustkserver.BIBusTKServerConnectionFactory.start(BIBusTKServerConnectionFactory.java:578) ~[p2pd.jar:?]
        at com.cognos.xqebifw.cubingservices.CubingServicesConnectionFactory.start(CubingServicesConnectionFactory.java:1398) ~[xqeService.jar:?]
        at com.cognos.pogo.async.service.AsyncRequestHandler.start(AsyncRequestHandler.java:281) ~[p2pd.jar:?]
        at com.cognos.pogo.services.DefaultHandlerService.start(DefaultHandlerService.java:88) ~[p2pd.jar:?]
        at com.cognos.pogo.services.DispatcherServices.start(DispatcherServices.java:218) [p2pd.jar:?]
        at com.cognos.pogo.services.DispatcherServices.continueStartup(DispatcherServices.java:475) [p2pd.jar:?]
        at com.cognos.pogo.services.DispatcherServices.configure(DispatcherServices.java:164) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.RefreshController.composeAndConfigureServices(RefreshController.java:122) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.RefreshController.run(RefreshController.java:82) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.startConfiguration(BootstrapConfigurePublish.java:170) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.checkConfiguration(BootstrapConfigurePublish.java:149) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish.access$000(BootstrapConfigurePublish.java:34) [p2pd.jar:?]
        at com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish$ConfigurationCheckTask.safeRun(BootstrapConfigurePublish.java:141) [p2pd.jar:?]
        at com.cognos.pogo.util.threads.SafeTimerTask.run(SafeTimerTask.java:40) [p2pd.jar:?]
        at java.util.TimerThread.mainLoop(Timer.java:566) [?:1.8.0]
        at java.util.TimerThread.run(Timer.java:516) [?:1.8.0]
Caused by: java.lang.NullPointerException
        at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.<init>(SSLProtocolSocketFactory.java:124) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.<init>(SSLProtocolSocketFactory.java:116) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.<init>(SSLProtocolSocketFactory.java:112) ~[commons-httpclient-3.1.jar:?]
        at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.<clinit>(SSLProtocolSocketFactory.java:97) ~[commons-httpclient-3.1.jar:?]
        ... 32 more

Thanks!

Patrick

Hi,

It does look like there are issues with your Query Service. What min and max memory settings are currently applied to your Query Service?

MF.

[plip]

> It does look like there are issues with your Query Service. What min and max memory settings are currently applied to your Query Service?

Yes, this is something I changed based on some googling.  My 'initial jvm heap size' is 6064.  The limit is set to 16,000.  I think initially I had the limit set to 6064.  After I made those changes and restarted everything I didn't notice any difference.  I do notice when I look at the status of the query service inside the admin console it shows 'partially available.'  If I right click and force it to start it will show as 'available' but jdbc connections are still failing though. 

[MFGF]

> It does look like there are issues with your Query Service. What min and max memory settings are currently applied to your Query Service?

Yes, this is something I changed based on some googling.  My 'initial jvm heap size' is 6064.  The limit is set to 16,000.  I think initially I had the limit set to 6064.  After I made those changes and restarted everything I didn't notice any difference.  I do notice when I look at the status of the query service inside the admin console it shows 'partially available.'  If I right click and force it to start it will show as 'available' but jdbc connections are still failing though.

So your min heap size is 6Gb and max is 16Gb (roughly). Does your server have enough free memory to support this?

Cheers!

MF.

[plip]

> So your min heap size is 6Gb and max is 16Gb (roughly). Does your server have enough free memory to support this?

Yes, we have 32 GB on that server and Cognos is the only application that is running there.  Also even when I had the default settings there I was still getting the error.