On-premise '23 Pega platform does not start with Tomcat
After installed '23 successfully, we failed to start Pega as Stream node.
Also we failed to start WebUser node.
I already looked through this Configuring an embedded stream service
There are some messages in PegaRULE.log related to failing to start, below.
After installed '23 successfully, we failed to start Pega as Stream node.
Also we failed to start WebUser node.
I already looked through this Configuring an embedded stream service
There are some messages in PegaRULE.log related to failing to start, below.
2023-11-08 08:47:32,602 [ALIZE_STREAM_SERVICE] [ STANDARD] [ ] [ ] (prpc.service.ServiceDefinition) ERROR - Unable to create DSM service DATA-DECISION-SERVICE-STREAMSERVER DEFAULT
java.lang.reflect.InvocationTargetException: null
2023-11-08 08:47:32,754 [eue301z.dev.jp.local] [ STANDARD] [ ] [ ] (.internal.GenericErrorAnalyzer) ERROR - Health monitor received critical error notification from:
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
Caused by: com.pega.pegarules.pub.PRRuntimeException: Startup Task: [INITIALIZE_STREAM_SERVICE] has failed after retries or with error
Caused by: com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
Caused by: java.lang.reflect.InvocationTargetException
Caused by: com.pega.platform.stream.StreamServiceException: Failed to configure StreamAPI provider
Caused by: com.pega.platform.stream.StreamServiceException: 'services/stream/broker/url' isn't provided.
2023-11-08 10:25:23,298 [gaRULES-ShutDownTask] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) ERROR - Failed to execute task:class com.pega.pegarules.session.internal.engineinterface.shutdown.shutdowntasks.StopIndexingTask
java.lang.IllegalStateException: Calling a method from NodeLifecycle, before initializing it!
Why do we fail like this ?
we want to use embedded kafka because we can't provision external kafka.
Is there any configuration for stream node ?
***Edited by Moderator Marije to add Support Case ID**
Accepted Solution
Updated: 17 Nov 2023 7:06 EST
Pegasystems Inc.
GB
@MasashiY I can see that INC-A23747 has been closed following a successful conclusion:
The issue came down to the fact that the prconfig.xml. file was set incorrectly and you were not using External Stream.
This is the point which @SUMAN_GUMUDAVELLY correctly highlighted - many thanks for that!
Starting infinity, the use of embedded Kafka is not encouraged and thus the default configuration looks for external kafka connection for stream service. If the requirement is to use embedded Kafka then please add the below prconfig.xml setting,
<env name="services/stream/provider" value="Internal"/>
You confirmed yesterday that adding config below "internal kafka" to prconfig.xml allowed Stream node to correctly start.
I will therefore mark this question as resolved.
Proximus
BE
Are you technically fully compliant to PEGA'23?
Regards
Anthony
Rakuten Inc
JP
Thanks for replying.
Sure, I have checked that page many times. Our server meets all the requirements on that page.
Looks no problem regarding to middleware and its version.
Proximus
BE
Is it a fully fresh & first install or an upgrade?
is there anything shown in menu decisioning > infrastructure > services for stream?
You mention webuser node type. Have you well defined a Stream, Search & BackgroundProcessing nodeType.
This is the minimum you need.
Do you just try to start OOTB application, prpc/pega or have you got already your own application in it?
Have you got other PEGA instances running on same server?
You can observe the same stream error for lots of reasons depending on how it's set up.
Here, clearly global context is not detailed enough to go further
Regards
Anthony
Updated: 8 Nov 2023 22:56 EST
Rakuten Inc
JP
It's fully fresh & first install, meas clean install ? Yes. I re-created other pega server for prweb.war and db.
I understand pega node type system. I configured node type to each server correctly.
but there's no server have started ever due to this error messages.
I already have managed other pega instance as version 8.5.
I tried to install '23 version newly on new instance. and then this happened.
> Have you got other PEGA instances running on same server? No.
> Do you just try to start OOTB application, prpc/pega or have you got already your own application in it?
We have not log in this pega platform yet,(because server doesn't started.) so can't check any application for now.
Excuse me, please someone advice to me more specific by checking my log as I wrote first in this question.
Proximus
BE
The error is just the consequence of what's happening and not the cause of the issue. If you focus on it without analysing global context & setup you might never find the real issue.
You can check this one:
https://support.pega.com/question/pega-prweb-not-starting-tomcat-server
I now let it to anyone else
Regards
Anthony
Rakuten Inc
JP
OK, I understand what you say.
While asking here, I always read document again, check our context.
But for what this site is made ? What should I ask here ?
I already checked and tried that page you mentioned above.
But in my case it doesn't work. So I want to get more specific information about it.
Thanks anyway.
Pegasystems Inc.
GB
@MasashiY the PSC is a great place to get input from a wide variety of Pega users. Frequently you will have SME's who can answer your questions or point you to the correct resources.
(Many thanks @Anthony_Gourtay for having provided some valuable insight).
As documented:
"Embedded Kafka is deprecated in Pega Platform 8.8, Pega Platform '23 and Pega Platform '24.1. In the following release, Pega Platform '24.2, embedded Kafka will no longer be available. To ensure future compatibility, do not create any new installations using embedded Kafka. For further details, see External Kafka in your deployment."
The issue with starting Pega as a Stream node and a WebUser node could be due to several reasons. For the Stream service, ensure there is at least one node dedicated to Stream. For the WebUser node, ensure that the nodetype entry in the prconfig.xml file or in dynamic system settings is set to "web" .
@MasashiY the PSC is a great place to get input from a wide variety of Pega users. Frequently you will have SME's who can answer your questions or point you to the correct resources.
(Many thanks @Anthony_Gourtay for having provided some valuable insight).
As documented:
"Embedded Kafka is deprecated in Pega Platform 8.8, Pega Platform '23 and Pega Platform '24.1. In the following release, Pega Platform '24.2, embedded Kafka will no longer be available. To ensure future compatibility, do not create any new installations using embedded Kafka. For further details, see External Kafka in your deployment."
The issue with starting Pega as a Stream node and a WebUser node could be due to several reasons. For the Stream service, ensure there is at least one node dedicated to Stream. For the WebUser node, ensure that the nodetype entry in the prconfig.xml file or in dynamic system settings is set to "web" .
The error you're encountering indicates the system expecting an external Kafka service, but the URL for this service has not been provided. Starting from Pega Platform 8.4.0, it is possible to configure an external Kafka as a stream service provider. However, you mentioned that you want to use embedded Kafka, which is not recommended for Pega '23. If you cannot provision an external Kafka, you may need to consult with your system administrator or Pega Support for further assistance.
Other PSC posts
Externalisation of Kafka service
Pre-requisite for setting up external Kafka
Third-party externalized services Deployment Changes FAQs
Troubleshooting the Stream service
Please take a look at Support self-service offerings on the chronology of steps we advise users to follow - if the product is not working as documented then you can contact our Global Client Support team via the MSP portal.
Rakuten Inc
JP
Thanks for replying.
But basically as I mentioned firstly here,
I want to know and get any information about "Configuring an embedded stream service" of version 23, page line below.
Do you have any solution or do you know anything I need to check ?
And I am asking about this to Pega Support via SR, but now I don't get any solution for now.
Regards.
Updated: 15 Nov 2023 4:43 EST
Pegasystems Inc.
GB
@MasashiY many thanks for clarifying your question, I will see if I can get some further input for you.
We would like to help track your issue with the error you are encountering ("Failed to configure StreamAPI provider...: 'services/stream/broker/url' isn't provided".)
I can see that you already logged support ticket INC-A23747 on 8 November and that our engineers are working on it. Could I suggest that you continue to work with our GCS team? I have made them aware that you are actively seeking help.
Accepted Solution
Updated: 17 Nov 2023 7:06 EST
Pegasystems Inc.
GB
@MasashiY I can see that INC-A23747 has been closed following a successful conclusion:
The issue came down to the fact that the prconfig.xml. file was set incorrectly and you were not using External Stream.
This is the point which @SUMAN_GUMUDAVELLY correctly highlighted - many thanks for that!
Starting infinity, the use of embedded Kafka is not encouraged and thus the default configuration looks for external kafka connection for stream service. If the requirement is to use embedded Kafka then please add the below prconfig.xml setting,
<env name="services/stream/provider" value="Internal"/>
You confirmed yesterday that adding config below "internal kafka" to prconfig.xml allowed Stream node to correctly start.
I will therefore mark this question as resolved.
Ford Motor Company
US
Ensure you do not have DSS or prconfig.xml
Pega-Engine • prconfig/services/stream/provider/default [ Value: ExternalKafka] exist by default when you install Pega Infinity'23.
In case if you have that DSS< what it means is, Stream Services are starting as Kafka Externalized
I ran into this issue of Caused by: com.pega.platform.stream.StreamServiceException: 'services/stream/broker/url' isn't provided. when I was trying to Externalize the Kafka Services and this setting was no where documented.
Hence I suggest you to make sure none of the settings mentioned in my screenshot shouldnt excist in your freshly installed Infnity 23. 