[
https://issues.apache.org/jira/browse/STORM-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365469#comment-15365469
]
ASF GitHub Bot commented on STORM-1945:
---------------------------------------
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/1541#discussion_r69841403
--- Diff: storm-core/src/jvm/org/apache/storm/utils/TopologySpoutLag.java
---
@@ -43,26 +43,44 @@
public static List<Map<String, Object>> lag (StormTopology
stormTopology, Map topologyConf) {
List<Map<String, Object>> result = new ArrayList<>();
Map<String, SpoutSpec> spouts = stormTopology.get_spouts();
- Object object = null;
+ String className = null;
for (Map.Entry<String, SpoutSpec> spout: spouts.entrySet()) {
try {
SpoutSpec spoutSpec = spout.getValue();
ComponentObject componentObject =
spoutSpec.get_spout_object();
- object = Utils.getSetComponentObject(componentObject);
--- End diff --
The problem starts here. For many situation we can't deserialize Spout
object since UI doesn't have dependency for that Spout, for example,
storm-kafka or storm-kafka-client.
> Internal Server Error shown on topology page for topology using KafkaSpout
> --------------------------------------------------------------------------
>
> Key: STORM-1945
> URL: https://issues.apache.org/jira/browse/STORM-1945
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-ui
> Affects Versions: 2.0.0, 1.1.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Critical
> Attachments: Screen Shot 2016-07-06 at 4.25.41 PM.png
>
>
> When opening topology page which uses old storm-kafka Spout, page shows
> Internal Server Error on bottom side.
> And REST API /api/v1/topology/:topology/lag also shows Internal Server Error.
> Its errorMessage is describing NPE, but stack track gives less help since
> it's already within catch statement so we can't trace why origin exception is
> thrown by only looking at errorMessage. And there's no error message on ui
> log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
