[jira] [Closed] (EAGLE-462) Alert Dudup - same metric generate alert should be deduped

[Zeng, Bryant (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zeng, Bryant closed EAGLE-462.
--
Resolution: Fixed

> Alert Dudup - same metric generate alert should be deduped
> --
>
> Key: EAGLE-462
> URL: https://issues.apache.org/jira/browse/EAGLE-462
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-471) AlertBolt introduce un-serializble member

[Zeng, Bryant (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zeng, Bryant closed EAGLE-471.
--
Resolution: Fixed

> AlertBolt introduce un-serializble member 
> --
>
> Key: EAGLE-471
> URL: https://issues.apache.org/jira/browse/EAGLE-471
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
>Priority: Blocker
>
> AlerBolt.executors  
> 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set 
> topology.message.timeout.secs as 3600
> Exception in thread "main" java.lang.RuntimeException: 
> java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor
>at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43)
> at backtype.storm.utils.Utils.serialize(Utils.java:85)
> at 
> backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193)
> at 
> org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: java.io.NotSerializableException: 
> java.util.concurrent.ThreadPoolExecutor
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15]
>   
> idea里跑UnitTopologyMain



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-475) Fix generic email publisher and publish emails for absence alert.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425634#comment-15425634
 ] 

ASF GitHub Bot commented on EAGLE-475:
--

GitHub user pkuwm opened a pull request:

https://github.com/apache/incubator-eagle/pull/359

EAGLE-475 - Fix generic email publisher and publish emails for absenc…

…e alert.

1) Absence alerts could not be published via emails.
Root cause: in AbsencePolicyHandler, alert stream events were not emitted 
to alert bolt.
Solution: collect alert stream events and emit them to alert bolt.
2) Email publisher did not work.
Root cause: Email configurations were incorrect.
Solution: correct the email configurations and add email authentications.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pkuwm/incubator-eagle EAGLE-475

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/359.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #359


commit 6d1e99a0b03d4a9894bd3f3b53e981d5fd18dfe1
Author: pkuwm 
Date:   2016-08-18T00:06:55Z

EAGLE-475 - Fix generic email publisher and publish emails for absence 
alert.




> Fix generic email publisher and publish emails for absence alert.
> -
>
> Key: EAGLE-475
> URL: https://issues.apache.org/jira/browse/EAGLE-475
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Huizhi Lu
>Assignee: Huizhi Lu
> Fix For: v0.5.0
>
>
> 1) Absence alerts could not be published via emails.
> Root cause: in AbsencePolicyHandler, alert stream events were not emitted to 
> alert bolt.
> Solution: collect alert stream events and emit them to alert bolt.
> 2) Email publisher did not work.
> Root cause: Email configurations were incorrect.
> Solution: correct the email configurations and add email authentications.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #359: EAGLE-475 - Fix generic email publisher a...

[pkuwm]

GitHub user pkuwm opened a pull request:

https://github.com/apache/incubator-eagle/pull/359

EAGLE-475 - Fix generic email publisher and publish emails for absenc…

…e alert.

1) Absence alerts could not be published via emails.
Root cause: in AbsencePolicyHandler, alert stream events were not emitted 
to alert bolt.
Solution: collect alert stream events and emit them to alert bolt.
2) Email publisher did not work.
Root cause: Email configurations were incorrect.
Solution: correct the email configurations and add email authentications.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pkuwm/incubator-eagle EAGLE-475

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/359.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #359


commit 6d1e99a0b03d4a9894bd3f3b53e981d5fd18dfe1
Author: pkuwm 
Date:   2016-08-18T00:06:55Z

EAGLE-475 - Fix generic email publisher and publish emails for absence 
alert.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-475) Fix generic email publisher and publish emails for absence alert.

[Huizhi Lu (JIRA)]

Huizhi Lu created EAGLE-475:
---

 Summary: Fix generic email publisher and publish emails for 
absence alert.
 Key: EAGLE-475
 URL: https://issues.apache.org/jira/browse/EAGLE-475
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Huizhi Lu
Assignee: Huizhi Lu
 Fix For: v0.5.0


1) Absence alerts could not be published via emails.
Root cause: in AbsencePolicyHandler, alert stream events were not emitted to 
alert bolt.
Solution: collect alert stream events and emit them to alert bolt.

2) Email publisher did not work.
Root cause: Email configurations were incorrect.
Solution: correct the email configurations and add email authentications.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-462) Alert Dudup - same metric generate alert should be deduped

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425629#comment-15425629
 ] 

ASF GitHub Bot commented on EAGLE-462:
--

Github user mizeng closed the pull request at:

https://github.com/apache/incubator-eagle/pull/352


> Alert Dudup - same metric generate alert should be deduped
> --
>
> Key: EAGLE-462
> URL: https://issues.apache.org/jira/browse/EAGLE-462
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-471) AlertBolt introduce un-serializble member

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425627#comment-15425627
 ] 

ASF GitHub Bot commented on EAGLE-471:
--

Github user mizeng closed the pull request at:

https://github.com/apache/incubator-eagle/pull/355


> AlertBolt introduce un-serializble member 
> --
>
> Key: EAGLE-471
> URL: https://issues.apache.org/jira/browse/EAGLE-471
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
>Priority: Blocker
>
> AlerBolt.executors  
> 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set 
> topology.message.timeout.secs as 3600
> Exception in thread "main" java.lang.RuntimeException: 
> java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor
>at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43)
> at backtype.storm.utils.Utils.serialize(Utils.java:85)
> at 
> backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193)
> at 
> org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: java.io.NotSerializableException: 
> java.util.concurrent.ThreadPoolExecutor
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15]
>   
> idea里跑UnitTopologyMain



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #352: EAGLE-462: Alert Dudup

[mizeng]

Github user mizeng closed the pull request at:

https://github.com/apache/incubator-eagle/pull/352


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #355: EAGLE-471: fix AlertBolt introduce un-ser...

[mizeng]

Github user mizeng closed the pull request at:

https://github.com/apache/incubator-eagle/pull/355


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-474) some improvements of app framework: appId naming, jarFile field, InstallOperation etc.

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425625#comment-15425625
 ] 

Edward Zhang commented on EAGLE-474:


appId in ApplicationEntity should be renamed to appType. It is not necessary to 
let appId to contain site.

Application instance should be identified by app type and uuid (uuid can 
contain site)

> some improvements of app framework: appId naming, jarFile field, 
> InstallOperation etc.
> --
>
> Key: EAGLE-474
> URL: https://issues.apache.org/jira/browse/EAGLE-474
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.0
>
>
> App framework has some bugs and also needs some improvement
> 1. appId in ApplicationEntity should not contain "[,]" chars, which will make 
> storm UI not show the topology details
> 2. jarPath is not necessary to be part of ApplicationDesc or metadata xml file
> 3. InstallOperation should contain jarPath which should be in the same level 
> of appType etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-470) data enrichment refactor in eagle security monitoring

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424926#comment-15424926
 ] 

ASF GitHub Bot commented on EAGLE-470:
--

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/358


> data enrichment refactor in eagle security monitoring
> -
>
> Key: EAGLE-470
> URL: https://issues.apache.org/jira/browse/EAGLE-470
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.0
>
>
> Data enrichment happens in eagle security monitoring by retrieving 
> sensitivity data from eagle service and then join in real time.
> A lot of code is duplicated in current data enrich, this jira ticket is for 
> simplifying data enrichment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #358: data enrichment refactor in eagle securit...

[yonzhang]

Github user yonzhang closed the pull request at:

https://github.com/apache/incubator-eagle/pull/358


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-470) data enrichment refactor in eagle security monitoring

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424897#comment-15424897
 ] 

ASF GitHub Bot commented on EAGLE-470:
--

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/358

data enrichment refactor in eagle security monitoring

EAGLE-470, make enrichment easy to use

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/358.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #358


commit c95250c2f256e5a4fd30ad85068a9e7fc17c01e3
Author: yonzhang 
Date:   2016-08-17T01:09:24Z

data enrichment refactor in eagle security monitoring




> data enrichment refactor in eagle security monitoring
> -
>
> Key: EAGLE-470
> URL: https://issues.apache.org/jira/browse/EAGLE-470
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.0
>
>
> Data enrichment happens in eagle security monitoring by retrieving 
> sensitivity data from eagle service and then join in real time.
> A lot of code is duplicated in current data enrich, this jira ticket is for 
> simplifying data enrichment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #358: data enrichment refactor in eagle securit...

[yonzhang]

GitHub user yonzhang opened a pull request:

https://github.com/apache/incubator-eagle/pull/358

data enrichment refactor in eagle security monitoring

EAGLE-470, make enrichment easy to use

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/yonzhang/incubator-eagle develop

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/358.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #358


commit c95250c2f256e5a4fd30ad85068a9e7fc17c01e3
Author: yonzhang 
Date:   2016-08-17T01:09:24Z

data enrichment refactor in eagle security monitoring




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [HELP] cannot upload eagle jars to maven repository

[Michael Wu]

Henry,

I've got the access to upload artifacts to
https://repository.apache.org/service/local/staging/deploy/maven2/, and
based on the result of latest execution, all .jar, .asc, etc. of eagle
0.4.0-incubating are uploaded to the url successfully. However, I still
cannot find them via web-browser from
https://repository.apache.org/content/repositories/releases/org/apache/. I
went through all documents I had read about the uploading process, but
didn't find any instruction for how to verify the visibility of the
uploaded jars. Do you have any idea with it, please?

BTW, is there any additional operation/request I have to make, or is there
any sync process that I have to wait for? Thanks.

Michael

On Thu, Aug 11, 2016 at 11:21 AM, Michael Wu  wrote:

> Tickets created:
> https://issues.apache.org/jira/browse/INFRA-12409
> https://issues.apache.org/jira/browse/INFRA-12410
>
> On Thu, Aug 11, 2016 at 10:07 AM, Michael Wu  wrote:
>
>> Henry,
>>
>> Thank you very much for guiding me with those details! I'll do it right
>> now.
>>
>> Michael
>>
>> On Tue, Aug 9, 2016 at 2:39 AM, Henry Saputra 
>> wrote:
>>
>>> So, we need to file 2 infra tickets:
>>> 1. One is to add target in Maven repository for Eagle. You can see sample
>>> from here: https://issues.apache.org/jira/browse/INFRA-8026 or
>>> https://issues.apache.org/jira/browse/INFRA-7246
>>> 2. Create ticket for you to be granted karma to access Apache Nexus repo.
>>>
>>> -  Henry
>>>
>>> On Mon, Aug 8, 2016 at 12:56 AM, Michael Wu  wrote:
>>>
>>> > Hi Henry,
>>> >
>>> > No, eagle never pushed artifacts to ASF Nexus repository. How can we
>>> get
>>> > the access, please?
>>> >
>>> > Michael
>>> >
>>> > On Mon, Aug 8, 2016 at 2:21 PM, Henry Saputra >> >
>>> > wrote:
>>> >
>>> > > I found Eagle in ASF release dist folder but do not see it in the
>>> Nexus
>>> > > Maven repo (https://repository.apache.org)
>>> > >
>>> > > Has Eagle pushed artifacts to ASF Nexus repository for prev releases?
>>> > >
>>> > > - Henry
>>> > >
>>> > > On Wed, Aug 3, 2016 at 8:04 PM, Michael Wu 
>>> wrote:
>>> > >
>>> > > > Hi mentors,
>>> > > >
>>> > > > I was trying to use
>>> > > >
>>> > > > $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_
>>> > > PASSPHRASE}
>>> > > > deploy
>>> > > >
>>> > > > to upload eagle's jars to
>>> > > > https://repository.apache.org/service/local/staging/deploy/maven2,
>>> but
>>> > > it
>>> > > > always return 400 error, as below fragment:
>>> > > > 
>>> > > > [ERROR] Failed to execute goal
>>> > > > org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy
>>> > > (default-deploy)
>>> > > > on project eagle-parent: Failed to deploy artifacts: Could not
>>> transfer
>>> > > > artifact org.apache.eagle:eagle-parent:pom:0.4.0-incubating
>>> from/to
>>> > > > apache.releases.https (
>>> > > > https://repository.apache.org/service/local/staging/deploy/maven2
>>> ):
>>> > > Failed
>>> > > > to transfer file:
>>> > > > https://repository.apache.org/service/local/staging/deploy/
>>> > > > maven2/org/apache/eagle/eagle-parent/0.4.0-incubating/eagle-
>>> > > > parent-0.4.0-incubating.pom.
>>> > > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>> > > > 
>>> > > >
>>> > > > Could you instruct me, whether it's caused by the lack of access
>>> to the
>>> > > > repository and which mailing list I should get connected with to
>>> solve
>>> > > this
>>> > > > issue, please? Thanks.
>>> > > >
>>> > > > Michael
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>

[jira] [Created] (EAGLE-473) Query error if query string contains "[]"

[Zhao, Qingwen (JIRA)]

Zhao, Qingwen created EAGLE-473:
---

 Summary: Query error if query string contains "[]"
 Key: EAGLE-473
 URL: https://issues.apache.org/jira/browse/EAGLE-473
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.3.0
Reporter: Zhao, Qingwen
 Fix For: v0.5.0


Query 
string:[7279137F3E23471BBB397E52FC94543A/ED1F4AD763A64097B640A7CBD54F4AD9] 
Promoted Listing Job 2016/08/15/(25/29)

{code}
success: false,
exception: "java.lang.Exception: java.io.IOException: 
org.apache.eagle.storage.exception.QueryCompileException: 
java.lang.IllegalArgumentException: List query syntax is 
[]{} Aggregate query syntax is 
[]{}.{} 
org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:43)
 
org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443)
 
org.apache.eagle.service.jpm.MRJobExecutionResource.searchJobsById(MRJobExecutionResource.java:149)
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 java.lang.reflect.Method.invoke(Method.java:498) 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 
org.apache.eagle.service.jpm.MRJobExecutionResource.searchJobsById(MRJobExecutionResource.java:158)
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 java.lang.reflect.Method.invoke(Method.java:498) 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ",
obj: [ ]
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-467) Add job query apis for both running & historic jobs

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424261#comment-15424261
 ] 

ASF GitHub Bot commented on EAGLE-467:
--

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/348
  
If you declare a field as Map, then eagle will automatically adopt java 
build-in serialization/deserialization. 
Although JobConfig extends from Map, but eagle still regards it as a 
user-define type object. 


> Add job query apis for both running & historic jobs 
> 
>
> Key: EAGLE-467
> URL: https://issues.apache.org/jira/browse/EAGLE-467
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Job search rest api:
> /rest/mrJobs/search?jobId=?=?
> job list api:
> /rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
> The problem is current we store running jobs and historic jobs into different 
> places, which presents an obstacle when we want to query all jobs regardless 
> of the status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle issue #348: EAGLE-467: Job list apis for querying jobs regar...

[qingwen220]

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/348
  
If you declare a field as Map, then eagle will automatically adopt java 
build-in serialization/deserialization. 
Although JobConfig extends from Map, but eagle still regards it as a 
user-define type object. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-467) Add job query apis for both running & historic jobs

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424252#comment-15424252
 ] 

ASF GitHub Bot commented on EAGLE-467:
--

Github user wujinhu commented on the issue:

https://github.com/apache/incubator-eagle/pull/348
  
The serialization/deserialization of 
org.apache.eagle.jpm.mr.runningentity.JobConfig is a little complicated. Since 
it is a java HashMap,  should we consider to use java build-in  
serialization/deserialization?


> Add job query apis for both running & historic jobs 
> 
>
> Key: EAGLE-467
> URL: https://issues.apache.org/jira/browse/EAGLE-467
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Job search rest api:
> /rest/mrJobs/search?jobId=?=?
> job list api:
> /rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
> The problem is current we store running jobs and historic jobs into different 
> places, which presents an obstacle when we want to query all jobs regardless 
> of the status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle issue #348: EAGLE-467: Job list apis for querying jobs regar...

[wujinhu]

Github user wujinhu commented on the issue:

https://github.com/apache/incubator-eagle/pull/348
  
The serialization/deserialization of 
org.apache.eagle.jpm.mr.runningentity.JobConfig is a little complicated. Since 
it is a java HashMap,  should we consider to use java build-in  
serialization/deserialization?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-472) Fix HBase unit test

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424222#comment-15424222
 ] 

ASF GitHub Bot commented on EAGLE-472:
--

GitHub user baibaichen opened a pull request:

https://github.com/apache/incubator-eagle/pull/357

[EAGLE-472] Fix HBase unit test

HBase UT is broken due to wrong configuration and guava conflict

https://issues.apache.org/jira/browse/EAGLE-472

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/baibaichen/incubator-eagle eagle-472

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/357.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #357


commit cb9d46ef6d7b4eb72aaed780dec69d29afa930a9
Author: baibaichen 
Date:   2016-08-17T03:31:58Z

[EAGLE-472] Fix HBase unit test

HBase UT is broken due to wrong configuration and guava conflict

https://issues.apache.org/jira/browse/EAGLE-472




>  Fix HBase unit test
> 
>
> Key: EAGLE-472
> URL: https://issues.apache.org/jira/browse/EAGLE-472
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
>  Labels: test
> Fix For: v0.5.0
>
>
> HBase UT is broken due to wrong configuration and guava conflict
> # [EAGLE-331 ingestion+alert engine 
> preview|https://github.com/apache/incubator-eagle/commit/eef4930c3b9cac7d8c596af684ba098ec2b2229d],
>  see what is added in EmbeddedHbase.java. To Fix it, we needn't specify 
> *hbase.master.ipc.address*, using default value is fine, which is 0.0.0.0, 
> means all IPv4 addresses on the local machine. Please note RegionServer will 
> not use 127.0.0.1 and localhost to contact master.
> # [Rebase code 
> base|https://github.com/apache/incubator-eagle/commit/72a1501c3ff645d93067b4fd9907f8183c2763b6]
>  , guava is upgraded to *19.0*,  however the dependent HBase 
> version(0.98.4.2.2.5.1-3-hadoop2) uses 12.01. It is OK in product 
> environment, but failed in UT, see HBASE-11694. To Fix it, we can downgrade 
> to guava 15.0 which works for eagle(*Stopwatch.createStarted*) and 
> HBase(*StopWatch.elapsedMillis*)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #357: [EAGLE-472] Fix HBase unit test

[baibaichen]

GitHub user baibaichen opened a pull request:

https://github.com/apache/incubator-eagle/pull/357

[EAGLE-472] Fix HBase unit test

HBase UT is broken due to wrong configuration and guava conflict

https://issues.apache.org/jira/browse/EAGLE-472

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/baibaichen/incubator-eagle eagle-472

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/357.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #357


commit cb9d46ef6d7b4eb72aaed780dec69d29afa930a9
Author: baibaichen 
Date:   2016-08-17T03:31:58Z

[EAGLE-472] Fix HBase unit test

HBase UT is broken due to wrong configuration and guava conflict

https://issues.apache.org/jira/browse/EAGLE-472




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-472) Fix HBase unit test

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424221#comment-15424221
 ] 

ASF GitHub Bot commented on EAGLE-472:
--

Github user baibaichen closed the pull request at:

https://github.com/apache/incubator-eagle/pull/356


>  Fix HBase unit test
> 
>
> Key: EAGLE-472
> URL: https://issues.apache.org/jira/browse/EAGLE-472
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
>  Labels: test
> Fix For: v0.5.0
>
>
> HBase UT is broken due to wrong configuration and guava conflict
> # [EAGLE-331 ingestion+alert engine 
> preview|https://github.com/apache/incubator-eagle/commit/eef4930c3b9cac7d8c596af684ba098ec2b2229d],
>  see what is added in EmbeddedHbase.java. To Fix it, we needn't specify 
> *hbase.master.ipc.address*, using default value is fine, which is 0.0.0.0, 
> means all IPv4 addresses on the local machine. Please note RegionServer will 
> not use 127.0.0.1 and localhost to contact master.
> # [Rebase code 
> base|https://github.com/apache/incubator-eagle/commit/72a1501c3ff645d93067b4fd9907f8183c2763b6]
>  , guava is upgraded to *19.0*,  however the dependent HBase 
> version(0.98.4.2.2.5.1-3-hadoop2) uses 12.01. It is OK in product 
> environment, but failed in UT, see HBASE-11694. To Fix it, we can downgrade 
> to guava 15.0 which works for eagle(*Stopwatch.createStarted*) and 
> HBase(*StopWatch.elapsedMillis*)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #356: [EAGLE-472] Fix HBase unit test

[baibaichen]

Github user baibaichen closed the pull request at:

https://github.com/apache/incubator-eagle/pull/356


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-472) Fix HBase unit test

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424205#comment-15424205
 ] 

ASF GitHub Bot commented on EAGLE-472:
--

GitHub user baibaichen opened a pull request:

https://github.com/apache/incubator-eagle/pull/356

[EAGLE-472] Fix HBase unit test

HBase UT is broken due to wrong configuration and guava conflict

https://issues.apache.org/jira/browse/EAGLE-472

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/baibaichen/incubator-eagle eagle-472

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/356.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #356


commit cb9d46ef6d7b4eb72aaed780dec69d29afa930a9
Author: baibaichen 
Date:   2016-08-17T03:31:58Z

[EAGLE-472] Fix HBase unit test

HBase UT is broken due to wrong configuration and guava conflict

https://issues.apache.org/jira/browse/EAGLE-472




>  Fix HBase unit test
> 
>
> Key: EAGLE-472
> URL: https://issues.apache.org/jira/browse/EAGLE-472
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
>  Labels: test
> Fix For: v0.5.0
>
>
> HBase UT is broken due to wrong configuration and guava conflict
> # [EAGLE-331 ingestion+alert engine 
> preview|https://github.com/apache/incubator-eagle/commit/eef4930c3b9cac7d8c596af684ba098ec2b2229d],
>  see what is added in EmbeddedHbase.java. To Fix it, we needn't specify 
> *hbase.master.ipc.address*, using default value is fine, which is 0.0.0.0, 
> means all IPv4 addresses on the local machine. Please note RegionServer will 
> not use 127.0.0.1 and localhost to contact master.
> # [Rebase code 
> base|https://github.com/apache/incubator-eagle/commit/72a1501c3ff645d93067b4fd9907f8183c2763b6]
>  , guava is upgraded to *19.0*,  however the dependent HBase 
> version(0.98.4.2.2.5.1-3-hadoop2) uses 12.01. It is OK in product 
> environment, but failed in UT, see HBASE-11694. To Fix it, we can downgrade 
> to guava 15.0 which works for eagle(*Stopwatch.createStarted*) and 
> HBase(*StopWatch.elapsedMillis*)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #356: [EAGLE-472] Fix HBase unit test

[baibaichen]

GitHub user baibaichen opened a pull request:

https://github.com/apache/incubator-eagle/pull/356

[EAGLE-472] Fix HBase unit test

HBase UT is broken due to wrong configuration and guava conflict

https://issues.apache.org/jira/browse/EAGLE-472

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/baibaichen/incubator-eagle eagle-472

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/356.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #356


commit cb9d46ef6d7b4eb72aaed780dec69d29afa930a9
Author: baibaichen 
Date:   2016-08-17T03:31:58Z

[EAGLE-472] Fix HBase unit test

HBase UT is broken due to wrong configuration and guava conflict

https://issues.apache.org/jira/browse/EAGLE-472




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-472) Fix HBase unit test

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424086#comment-15424086
 ] 

ASF GitHub Bot commented on EAGLE-472:
--

Github user baibaichen closed the pull request at:

https://github.com/apache/incubator-eagle/pull/354


>  Fix HBase unit test
> 
>
> Key: EAGLE-472
> URL: https://issues.apache.org/jira/browse/EAGLE-472
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
>  Labels: test
> Fix For: v0.5.0
>
>
> HBase UT is broken due to wrong configuration and guava conflict
> # [EAGLE-331 ingestion+alert engine 
> preview|https://github.com/apache/incubator-eagle/commit/eef4930c3b9cac7d8c596af684ba098ec2b2229d],
>  see what is added in EmbeddedHbase.java. To Fix it, we needn't specify 
> *hbase.master.ipc.address*, using default value is fine, which is 0.0.0.0, 
> means all IPv4 addresses on the local machine. Please note RegionServer will 
> not use 127.0.0.1 and localhost to contact master.
> # [Rebase code 
> base|https://github.com/apache/incubator-eagle/commit/72a1501c3ff645d93067b4fd9907f8183c2763b6]
>  , guava is upgraded to *19.0*,  however the dependent HBase 
> version(0.98.4.2.2.5.1-3-hadoop2) uses 12.01. It is OK in product 
> environment, but failed in UT, see HBASE-11694. To Fix it, we can downgrade 
> to guava 15.0 which works for eagle(*Stopwatch.createStarted*) and 
> HBase(*StopWatch.elapsedMillis*)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #354: [EAGLE-472] Fix HBase unit test

[baibaichen]

Github user baibaichen closed the pull request at:

https://github.com/apache/incubator-eagle/pull/354


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-471) AlertBolt introduce un-serializble member

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424012#comment-15424012
 ] 

ASF GitHub Bot commented on EAGLE-471:
--

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/355#discussion_r75072462
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/utils/SingletonExecutor.java
 ---
@@ -0,0 +1,32 @@
+package org.apache.eagle.alert.engine.utils;
+
+import java.util.concurrent.ExecutorService;
+import java.util.concurrent.Executors;
+
+/**
+ * @author mizeng
+ * @version v1.0
+ * @description TODO
--- End diff --

Remove TODO/FIXME if unnecessary.


> AlertBolt introduce un-serializble member 
> --
>
> Key: EAGLE-471
> URL: https://issues.apache.org/jira/browse/EAGLE-471
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
>Priority: Blocker
>
> AlerBolt.executors  
> 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set 
> topology.message.timeout.secs as 3600
> Exception in thread "main" java.lang.RuntimeException: 
> java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor
>at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43)
> at backtype.storm.utils.Utils.serialize(Utils.java:85)
> at 
> backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193)
> at 
> org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: java.io.NotSerializableException: 
> java.util.concurrent.ThreadPoolExecutor
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15]
>   
> idea里跑UnitTopologyMain



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-471) AlertBolt introduce un-serializble member

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424011#comment-15424011
 ] 

ASF GitHub Bot commented on EAGLE-471:
--

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/355#discussion_r75072403
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/utils/SingletonExecutor.java
 ---
@@ -0,0 +1,32 @@
+package org.apache.eagle.alert.engine.utils;
--- End diff --

Need apache license. Other wise this should mvn failed.


> AlertBolt introduce un-serializble member 
> --
>
> Key: EAGLE-471
> URL: https://issues.apache.org/jira/browse/EAGLE-471
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
>Priority: Blocker
>
> AlerBolt.executors  
> 2016-08-16 16:13:32,994 INFO [main] runner.UnitTopologyRunner[160]: Set 
> topology.message.timeout.secs as 3600
> Exception in thread "main" java.lang.RuntimeException: 
> java.io.NotSerializableException: java.util.concurrent.ThreadPoolExecutor
>at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:43)
> at backtype.storm.utils.Utils.serialize(Utils.java:85)
> at 
> backtype.storm.topology.TopologyBuilder.createTopology(TopologyBuilder.java:106)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.buildTopology(UnitTopologyRunner.java:144)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:168)
> at 
> org.apache.eagle.alert.engine.runner.UnitTopologyRunner.run(UnitTopologyRunner.java:193)
> at 
> org.apache.eagle.alert.engine.UnitTopologyMain.main(UnitTopologyMain.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: java.io.NotSerializableException: 
> java.util.concurrent.ThreadPoolExecutor
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at 
> backtype.storm.serialization.DefaultSerializationDelegate.serialize(DefaultSerializationDelegate.java:39)[4:15]
>   
> idea里跑UnitTopologyMain



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #355: EAGLE-471: fix AlertBolt introduce un-ser...

[RalphSu]

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/355#discussion_r75072462
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/utils/SingletonExecutor.java
 ---
@@ -0,0 +1,32 @@
+package org.apache.eagle.alert.engine.utils;
+
+import java.util.concurrent.ExecutorService;
+import java.util.concurrent.Executors;
+
+/**
+ * @author mizeng
+ * @version v1.0
+ * @description TODO
--- End diff --

Remove TODO/FIXME if unnecessary.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #355: EAGLE-471: fix AlertBolt introduce un-ser...

[RalphSu]

Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/355#discussion_r75072403
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/utils/SingletonExecutor.java
 ---
@@ -0,0 +1,32 @@
+package org.apache.eagle.alert.engine.utils;
--- End diff --

Need apache license. Other wise this should mvn failed.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---