[jira] [Updated] (KYLIN-3178) Delete table acl failed will cause the wabpage awalys shows "Please wait..."

2018-01-17 Thread peng.jianhua (JIRA)

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

peng.jianhua updated KYLIN-3178:

Summary: Delete table acl failed will cause the wabpage awalys shows 
"Please wait..."  (was: Delete table acl failed will cause the wabpage awalys 
shows loading)

> Delete table acl failed will cause the wabpage awalys shows "Please wait..."
> 
>
> Key: KYLIN-3178
> URL: https://issues.apache.org/jira/browse/KYLIN-3178
> Project: Kylin
>  Issue Type: Bug
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
> Attachments: 
> 0001-KYLIN-3178-Delete-table-acl-failed-will-cause-the-wa.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KYLIN-3178) Delete table acl failed will cause the wabpage awalys shows loading

2018-01-17 Thread peng.jianhua (JIRA)

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

peng.jianhua updated KYLIN-3178:

Attachment: 0001-KYLIN-3178-Delete-table-acl-failed-will-cause-the-wa.patch

> Delete table acl failed will cause the wabpage awalys shows loading
> ---
>
> Key: KYLIN-3178
> URL: https://issues.apache.org/jira/browse/KYLIN-3178
> Project: Kylin
>  Issue Type: Bug
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
> Attachments: 
> 0001-KYLIN-3178-Delete-table-acl-failed-will-cause-the-wa.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (KYLIN-3178) Delete table acl failed will cause the wabpage awalys shows loading

2018-01-17 Thread peng.jianhua (JIRA)
peng.jianhua created KYLIN-3178:
---

 Summary: Delete table acl failed will cause the wabpage awalys 
shows loading
 Key: KYLIN-3178
 URL: https://issues.apache.org/jira/browse/KYLIN-3178
 Project: Kylin
  Issue Type: Bug
  Components: Web 
Affects Versions: v2.3.0
Reporter: peng.jianhua
Assignee: peng.jianhua






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3176) kylin startup failed on hive 2.2.0

2018-01-17 Thread peng.jianhua (JIRA)

[ 
https://issues.apache.org/jira/browse/KYLIN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329868#comment-16329868
 ] 

peng.jianhua commented on KYLIN-3176:
-

ok.

> kylin startup failed on hive 2.2.0
> --
>
> Key: KYLIN-3176
> URL: https://issues.apache.org/jira/browse/KYLIN-3176
> Project: Kylin
>  Issue Type: Bug
>  Components: Environment 
>Affects Versions: v2.3.0
> Environment: hive 2.2.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments: 0001-KYLIN-3176.patch
>
>
> org.apache.catalina.LifecycleException: Failed to initialize component 
> [StandardServer[9005]]
>  at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
>  at org.apache.catalina.startup.Catalina.load(Catalina.java:643)
>  at org.apache.catalina.startup.Catalina.start(Catalina.java:682)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:606)
>  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
>  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:606)
>  at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
>  at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
>  Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.derby.jdbc.AutoloadedDriver40
>  at java.lang.Class.forName0(Native Method)
>  at java.lang.Class.forName(Class.java:278)
>  at java.sql.DriverManager.isDriverAllowed(DriverManager.java:463)
>  at java.sql.DriverManager.isDriverAllowed(DriverManager.java:455)
>  at java.sql.DriverManager.getDrivers(DriverManager.java:356)
>  at 
> org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:288)
>  at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
>  at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>  at 
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:388)
>  at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
>  ... 14 more
>  
>  
>  
> Exclude hive's derbyclient-10.11.1.1.jar from Kylin's classpath will solve 
> the problem



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3165) Cannot auto mege segments

2018-01-17 Thread Shaofeng SHI (JIRA)

[ 
https://issues.apache.org/jira/browse/KYLIN-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328681#comment-16328681
 ] 

Shaofeng SHI commented on KYLIN-3165:
-

Patch merged to master branch, thanks yang hao!

> Cannot auto mege segments
> -
>
> Key: KYLIN-3165
> URL: https://issues.apache.org/jira/browse/KYLIN-3165
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v2.2.0
>Reporter: Yang Hao
>Assignee: Yang Hao
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-3165.apache-master.001.patch
>
>
> The function of auto merge loses efficacy after we upgrade to 2.2.0, related 
> stack is:
> 2018-01-14 11:21:10,965 ERROR [Thread-694] service.CacheService:88 : Error in 
> updateOnNewSegmentReady()
> java.lang.IllegalArgumentException
>  at com.google.common.base.Preconditions.checkArgument(Preconditions.java:76)
>  at org.apache.kylin.cube.CubeManager.mergeSegments(CubeManager.java:547)
>  at 
> org.apache.kylin.rest.service.CubeService.mergeCubeSegment(CubeService.java:646)
>  at 
> org.apache.kylin.rest.service.CubeService.updateOnNewSegmentReady(CubeService.java:594)
>  at 
> org.apache.kylin.rest.service.CubeService$$FastClassBySpringCGLIB$$17a07c0e.invoke()
>  at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669)
>  at 
> org.apache.kylin.rest.service.CubeService$$EnhancerBySpringCGLIB$$eaadc7fa.updateOnNewSegmentReady()
>  at org.apache.kylin.rest.service.CacheService$1$1.run(CacheService.java:86)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (KYLIN-3165) Cannot auto mege segments

2018-01-17 Thread Shaofeng SHI (JIRA)

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

Shaofeng SHI resolved KYLIN-3165.
-
   Resolution: Fixed
Fix Version/s: v2.3.0

> Cannot auto mege segments
> -
>
> Key: KYLIN-3165
> URL: https://issues.apache.org/jira/browse/KYLIN-3165
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v2.2.0
>Reporter: Yang Hao
>Assignee: Yang Hao
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-3165.apache-master.001.patch
>
>
> The function of auto merge loses efficacy after we upgrade to 2.2.0, related 
> stack is:
> 2018-01-14 11:21:10,965 ERROR [Thread-694] service.CacheService:88 : Error in 
> updateOnNewSegmentReady()
> java.lang.IllegalArgumentException
>  at com.google.common.base.Preconditions.checkArgument(Preconditions.java:76)
>  at org.apache.kylin.cube.CubeManager.mergeSegments(CubeManager.java:547)
>  at 
> org.apache.kylin.rest.service.CubeService.mergeCubeSegment(CubeService.java:646)
>  at 
> org.apache.kylin.rest.service.CubeService.updateOnNewSegmentReady(CubeService.java:594)
>  at 
> org.apache.kylin.rest.service.CubeService$$FastClassBySpringCGLIB$$17a07c0e.invoke()
>  at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669)
>  at 
> org.apache.kylin.rest.service.CubeService$$EnhancerBySpringCGLIB$$eaadc7fa.updateOnNewSegmentReady()
>  at org.apache.kylin.rest.service.CacheService$1$1.run(CacheService.java:86)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (KYLIN-3004) Delete cube segment validation

2018-01-17 Thread Yang Hao (JIRA)

[ 
https://issues.apache.org/jira/browse/KYLIN-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328621#comment-16328621
 ] 

Yang Hao edited comment on KYLIN-3004 at 1/17/18 11:06 AM:
---

Thanks [~julianpan] Now it satisfy some needs. 


was (Author: yanghaogn):
Thanks [~julianpan] Now it satisfy som needs. 

> Delete cube segment validation
> --
>
> Key: KYLIN-3004
> URL: https://issues.apache.org/jira/browse/KYLIN-3004
> Project: Kylin
>  Issue Type: Bug
>  Components: REST Service
>Affects Versions: v2.1.0
>Reporter: Pan, Julian
>Assignee: Pan, Julian
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN_3004.patch, KYLIN_3004.patch
>
>
> In version 2.1, kylin allow hole between segment.
> But currently, there is validation for delete segment.
> Here is the code in CubeService:
>  if (!segmentName.equals(cube.getSegments().get(0).getName())
> && 
> !segmentName.equals(cube.getSegments().get(cube.getSegments().size() - 
> 1).getName())) {
> throw new 
> BadRequestException(String.format(msg.getDELETE_NOT_FIRST_LAST_SEG(), 
> segmentName));
> }
> Does it make sense? Should we remove the limit?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3004) Delete cube segment validation

2018-01-17 Thread Yang Hao (JIRA)

[ 
https://issues.apache.org/jira/browse/KYLIN-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328621#comment-16328621
 ] 

Yang Hao commented on KYLIN-3004:
-

Thanks [~julianpan] Now it satisfy som needs. 

> Delete cube segment validation
> --
>
> Key: KYLIN-3004
> URL: https://issues.apache.org/jira/browse/KYLIN-3004
> Project: Kylin
>  Issue Type: Bug
>  Components: REST Service
>Affects Versions: v2.1.0
>Reporter: Pan, Julian
>Assignee: Pan, Julian
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN_3004.patch, KYLIN_3004.patch
>
>
> In version 2.1, kylin allow hole between segment.
> But currently, there is validation for delete segment.
> Here is the code in CubeService:
>  if (!segmentName.equals(cube.getSegments().get(0).getName())
> && 
> !segmentName.equals(cube.getSegments().get(cube.getSegments().size() - 
> 1).getName())) {
> throw new 
> BadRequestException(String.format(msg.getDELETE_NOT_FIRST_LAST_SEG(), 
> segmentName));
> }
> Does it make sense? Should we remove the limit?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3176) kylin startup failed on hive 2.2.0

2018-01-17 Thread Shaofeng SHI (JIRA)

[ 
https://issues.apache.org/jira/browse/KYLIN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328605#comment-16328605
 ] 

Shaofeng SHI commented on KYLIN-3176:
-

Jianhua,

You're correct; I meet this on an EMR cluster, and just fixed it within 
KYLIN-3129. Almost the same change as your patch. Since it has been checked in, 
so I won't merge this patch. Thanks!

> kylin startup failed on hive 2.2.0
> --
>
> Key: KYLIN-3176
> URL: https://issues.apache.org/jira/browse/KYLIN-3176
> Project: Kylin
>  Issue Type: Bug
>  Components: Environment 
>Affects Versions: v2.3.0
> Environment: hive 2.2.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments: 0001-KYLIN-3176.patch
>
>
> org.apache.catalina.LifecycleException: Failed to initialize component 
> [StandardServer[9005]]
>  at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
>  at org.apache.catalina.startup.Catalina.load(Catalina.java:643)
>  at org.apache.catalina.startup.Catalina.start(Catalina.java:682)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:606)
>  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
>  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:606)
>  at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
>  at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
>  Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.derby.jdbc.AutoloadedDriver40
>  at java.lang.Class.forName0(Native Method)
>  at java.lang.Class.forName(Class.java:278)
>  at java.sql.DriverManager.isDriverAllowed(DriverManager.java:463)
>  at java.sql.DriverManager.isDriverAllowed(DriverManager.java:455)
>  at java.sql.DriverManager.getDrivers(DriverManager.java:356)
>  at 
> org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:288)
>  at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
>  at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>  at 
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:388)
>  at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
>  ... 14 more
>  
>  
>  
> Exclude hive's derbyclient-10.11.1.1.jar from Kylin's classpath will solve 
> the problem



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (KYLIN-3176) kylin startup failed on hive 2.2.0

2018-01-17 Thread Shaofeng SHI (JIRA)

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

Shaofeng SHI resolved KYLIN-3176.
-
Resolution: Duplicate

> kylin startup failed on hive 2.2.0
> --
>
> Key: KYLIN-3176
> URL: https://issues.apache.org/jira/browse/KYLIN-3176
> Project: Kylin
>  Issue Type: Bug
>  Components: Environment 
>Affects Versions: v2.3.0
> Environment: hive 2.2.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments: 0001-KYLIN-3176.patch
>
>
> org.apache.catalina.LifecycleException: Failed to initialize component 
> [StandardServer[9005]]
>  at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
>  at org.apache.catalina.startup.Catalina.load(Catalina.java:643)
>  at org.apache.catalina.startup.Catalina.start(Catalina.java:682)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:606)
>  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
>  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:606)
>  at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
>  at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
>  Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.derby.jdbc.AutoloadedDriver40
>  at java.lang.Class.forName0(Native Method)
>  at java.lang.Class.forName(Class.java:278)
>  at java.sql.DriverManager.isDriverAllowed(DriverManager.java:463)
>  at java.sql.DriverManager.isDriverAllowed(DriverManager.java:455)
>  at java.sql.DriverManager.getDrivers(DriverManager.java:356)
>  at 
> org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:288)
>  at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
>  at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>  at 
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:388)
>  at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
>  ... 14 more
>  
>  
>  
> Exclude hive's derbyclient-10.11.1.1.jar from Kylin's classpath will solve 
> the problem



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KYLIN-3177) Merged Streaming cube segment has no start/end time

2018-01-17 Thread Shaofeng SHI (JIRA)

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

Shaofeng SHI updated KYLIN-3177:

Description: 
Create a streaming cube, define auto merge thresholds; and then build it 
repeatedly.

When some segments be merged into a bigger segment, the new segment's start 
time and end time be 0 (show 1970-01-01).

 

This is a bug similar with KYLIN-3165, introduced to Kylin 2.2 with KYLIN-2818

  was:
Create a streaming cube, define auto merge thresholds; and then build it 
repeatedly.

When some segments be merged into a bigger segment, the new segment's start 
time and end time be 0 (show 1970-01-01).

 

This is a bug similar with KYLIN-3165, introduced to Kylin 2.2 


> Merged Streaming cube segment has no start/end time
> ---
>
> Key: KYLIN-3177
> URL: https://issues.apache.org/jira/browse/KYLIN-3177
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine, Metadata
>Affects Versions: v2.2.0
>Reporter: Shaofeng SHI
>Assignee: Wang Cheng
>Priority: Major
>
> Create a streaming cube, define auto merge thresholds; and then build it 
> repeatedly.
> When some segments be merged into a bigger segment, the new segment's start 
> time and end time be 0 (show 1970-01-01).
>  
> This is a bug similar with KYLIN-3165, introduced to Kylin 2.2 with KYLIN-2818



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KYLIN-3168) CubeHFileJob should use currentHBaseConfiguration but not new create hbase configuration

2018-01-17 Thread wuyingjun (JIRA)

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

wuyingjun updated KYLIN-3168:
-
Request participants: Billy Liu  (was: )

> CubeHFileJob should use currentHBaseConfiguration but not new create hbase 
> configuration
> 
>
> Key: KYLIN-3168
> URL: https://issues.apache.org/jira/browse/KYLIN-3168
> Project: Kylin
>  Issue Type: Bug
>Affects Versions: v2.2.0
>Reporter: wuyingjun
>Assignee: wuyingjun
>Priority: Major
> Attachments: AfterModified.png, CubeHFileJob_Exception.png, 
> KYLIN-3168.patch
>
>
> CubeHFileJob  use new hbase configuration is not correct because when the 
> zookeeper quorum is not localhost (job worker), kylin may account zookeeper 
> ConnectionLossException.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KYLIN-3129) Startup error on EMR 5.8+

2018-01-17 Thread Shaofeng SHI (JIRA)

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

Shaofeng SHI updated KYLIN-3129:

Priority: Major  (was: Minor)

Exclude derby from Kylin's classpath will fix the later error:

 

https://github.com/apache/kylin/commit/a6189a6069589a05db5a99bd2bc48242e67cc34d

> Startup error on EMR 5.8+
> -
>
> Key: KYLIN-3129
> URL: https://issues.apache.org/jira/browse/KYLIN-3129
> Project: Kylin
>  Issue Type: Improvement
>  Components: Environment 
>Reporter: Shaofeng SHI
>Assignee: Shaofeng SHI
>Priority: Major
> Fix For: v2.3.0
>
>
> When run "bin/kylin.sh start", it reports an NoSuchMethodError:
> {code:java}
> Caused by: org.springframework.beans.BeanInstantiationException: Failed to 
> instantiate [com.fasterxml.jackson.datatype.joda.JodaModule]: Constructor 
> threw exception; nested exception is java.lang.NoSuchMethodError: 
> org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter;
>   at 
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
>   at 
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:102)
>   at 
> org.springframework.http.converter.json.Jackson2ObjectMapperBuilder.registerWellKnownModulesIfAvailable(Jackson2ObjectMapperBuilder.java:764)
>   at 
> org.springframework.http.converter.json.Jackson2ObjectMapperBuilder.configure(Jackson2ObjectMapperBuilder.java:607)
>   at 
> org.springframework.http.converter.json.Jackson2ObjectMapperBuilder.build(Jackson2ObjectMapperBuilder.java:590)
>   at 
> org.springframework.http.converter.json.MappingJackson2HttpMessageConverter.(MappingJackson2HttpMessageConverter.java:57)
>   at 
> org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter.(AllEncompassingFormHttpMessageConverter.java:61)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.(RequestMappingHandlerAdapter.java:182)
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>   at 
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142)
>   ... 28 more
> Caused by: java.lang.NoSuchMethodError: 
> org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter;
>   at 
> com.fasterxml.jackson.datatype.joda.ser.JodaDateSerializerBase.(JodaDateSerializerBase.java:15)
>   at 
> com.fasterxml.jackson.datatype.joda.JodaModule.(JodaModule.java:39)
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>   at 
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142)
>   ... 40 more
> {code}
> After doing some investigation, found the DateTimeFormatter wasn't loaded 
> from Kylin's lib, but from:
>  [Loaded org.joda.time.format.DateTimeFormatter from 
> file:/usr/lib/hbase/lib/jruby-complete-1.6.8.jar]
> Then I remove that jar (this is a client node), restart Kylin again, this 
> time the error disappeared, by changed to another:
> {code:java}
> mv /usr/lib/hbase/lib/jruby-complete-1.6.8.jar 
> /usr/lib/hbase/lib/jruby-complete-1.6.8.jar_
> {code}
> {code:java}
> Caused by: java.lang.ClassCastException: 
> com.fasterxml.jackson.datatype.joda.JodaModule cannot be cast to 
> com.fasterxml.jackson.databind.Module
> at 
> org.springframework.http.converter.json.Jackson2ObjectMapperBuilder.registerWellKnownModulesIfAvailable(Jackson2ObjectMapperBuilder.java:764)
> at 
> org.springframework.http.converter.json.Jackson2ObjectMapperBuilder.configure(Jackson2ObjectMapperBuilder.java:607)
> at 
> org.springframework.http.converter.json.Jackson2ObjectMapperBuilder.build(Jackson2ObjectMapperBuilder.java:590)
> at 
> org.springframework.http.converter.json.MappingJackson2HttpMessageConverter.(MappingJackson2HttpMessageConverter.java:57)
> at 
> org.springframework.http.converter.support.AllEncompassingFormHttpMessageConverter.(AllEncompassingFormHttpMessageConverter.java:61)
> at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.(RequestMappingHandlerAdapter.java:182)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 

[jira] [Closed] (KYLIN-3170) Kylin generate wrong cuboids

2018-01-17 Thread Xingxing Di (JIRA)

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

Xingxing Di closed KYLIN-3170.
--
Resolution: Not A Bug

> Kylin generate wrong cuboids
> 
>
> Key: KYLIN-3170
> URL: https://issues.apache.org/jira/browse/KYLIN-3170
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v1.6.0, v2.2.0
> Environment: kylin2.2.0, hbase1.2.4
>Reporter: Xingxing Di
>Assignee: Shaofeng SHI
>Priority: Major
>
> We have a cube which has 5 dimensions and 2 agg groups:
> 5 dimensions : A, B, C, D, E
> agg group1 : Mandatory Dimensions (A, B),  Hierarchy Dimensions (D, E)
> agg group2 : Mandatory Dimensions (A, B),  Hierarchy Dimensions (C, E)
>  
> The cube generate 5 cuboids :
>  
> Cuboid 1
>      Cuboid 11011
>          Cuboid 11010
>      Cuboid 11101
>          Cuboid 11100
>  
> there this no cuboid 11000 , I'm confused about this,  I think this should be 
> a bug.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (KYLIN-3170) Kylin generate wrong cuboids

2018-01-17 Thread Xingxing Di (JIRA)

[ 
https://issues.apache.org/jira/browse/KYLIN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328503#comment-16328503
 ] 

Xingxing Di edited comment on KYLIN-3170 at 1/17/18 8:52 AM:
-

I debugged "Cuboid.isValid" method, i found there is a config property  : 
"kylin.cube.aggrgroup.isMandatoryOnlyValid"  , after i set it to true the 
generated cuboids just like i expected.

I will close this issue.


was (Author: dixingx...@yeah.net):
I debugged "Cuboid.isValid" method, i found there is a config property  : 
"kylin.cube.aggrgroup.isMandatoryOnlyValid"  , after i set it to true the 
generated cuboids just like i expected.

I will close this issue.

> Kylin generate wrong cuboids
> 
>
> Key: KYLIN-3170
> URL: https://issues.apache.org/jira/browse/KYLIN-3170
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v1.6.0, v2.2.0
> Environment: kylin2.2.0, hbase1.2.4
>Reporter: Xingxing Di
>Assignee: Shaofeng SHI
>Priority: Major
>
> We have a cube which has 5 dimensions and 2 agg groups:
> 5 dimensions : A, B, C, D, E
> agg group1 : Mandatory Dimensions (A, B),  Hierarchy Dimensions (D, E)
> agg group2 : Mandatory Dimensions (A, B),  Hierarchy Dimensions (C, E)
>  
> The cube generate 5 cuboids :
>  
> Cuboid 1
>      Cuboid 11011
>          Cuboid 11010
>      Cuboid 11101
>          Cuboid 11100
>  
> there this no cuboid 11000 , I'm confused about this,  I think this should be 
> a bug.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (KYLIN-3170) Kylin generate wrong cuboids

2018-01-17 Thread Xingxing Di (JIRA)

[ 
https://issues.apache.org/jira/browse/KYLIN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328503#comment-16328503
 ] 

Xingxing Di commented on KYLIN-3170:


I debugged "Cuboid.isValid" method, i found there is a config property  : 
"kylin.cube.aggrgroup.isMandatoryOnlyValid"  , after i set it to true the 
generated cuboids just like i expected.

I will close this issue.

> Kylin generate wrong cuboids
> 
>
> Key: KYLIN-3170
> URL: https://issues.apache.org/jira/browse/KYLIN-3170
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v1.6.0, v2.2.0
> Environment: kylin2.2.0, hbase1.2.4
>Reporter: Xingxing Di
>Assignee: Shaofeng SHI
>Priority: Major
>
> We have a cube which has 5 dimensions and 2 agg groups:
> 5 dimensions : A, B, C, D, E
> agg group1 : Mandatory Dimensions (A, B),  Hierarchy Dimensions (D, E)
> agg group2 : Mandatory Dimensions (A, B),  Hierarchy Dimensions (C, E)
>  
> The cube generate 5 cuboids :
>  
> Cuboid 1
>      Cuboid 11011
>          Cuboid 11010
>      Cuboid 11101
>          Cuboid 11100
>  
> there this no cuboid 11000 , I'm confused about this,  I think this should be 
> a bug.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KYLIN-3176) kylin startup failed on hive 2.2.0

2018-01-17 Thread peng.jianhua (JIRA)

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

peng.jianhua updated KYLIN-3176:

Attachment: 0001-KYLIN-3176.patch

> kylin startup failed on hive 2.2.0
> --
>
> Key: KYLIN-3176
> URL: https://issues.apache.org/jira/browse/KYLIN-3176
> Project: Kylin
>  Issue Type: Bug
>  Components: Environment 
>Affects Versions: v2.3.0
> Environment: hive 2.2.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments: 0001-KYLIN-3176.patch
>
>
> org.apache.catalina.LifecycleException: Failed to initialize component 
> [StandardServer[9005]]
>  at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
>  at org.apache.catalina.startup.Catalina.load(Catalina.java:643)
>  at org.apache.catalina.startup.Catalina.start(Catalina.java:682)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:606)
>  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
>  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:606)
>  at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
>  at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
>  Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.derby.jdbc.AutoloadedDriver40
>  at java.lang.Class.forName0(Native Method)
>  at java.lang.Class.forName(Class.java:278)
>  at java.sql.DriverManager.isDriverAllowed(DriverManager.java:463)
>  at java.sql.DriverManager.isDriverAllowed(DriverManager.java:455)
>  at java.sql.DriverManager.getDrivers(DriverManager.java:356)
>  at 
> org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:288)
>  at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
>  at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>  at 
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:388)
>  at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
>  ... 14 more
>  
>  
>  
> Exclude hive's derbyclient-10.11.1.1.jar from Kylin's classpath will solve 
> the problem



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (KYLIN-3177) Merged Streaming cube segments has no start/end time

2018-01-17 Thread Shaofeng SHI (JIRA)

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

Shaofeng SHI reassigned KYLIN-3177:
---

Assignee: Wang Cheng  (was: Shaofeng SHI)

> Merged Streaming cube segments has no start/end time
> 
>
> Key: KYLIN-3177
> URL: https://issues.apache.org/jira/browse/KYLIN-3177
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine, Metadata
>Affects Versions: v2.2.0
>Reporter: Shaofeng SHI
>Assignee: Wang Cheng
>Priority: Major
>
> Create a streaming cube, define auto merge thresholds; and then build it 
> repeatedly.
> When some segments be merged into a bigger segment, the new segment's start 
> time and end time be 0 (show 1970-01-01).
>  
> This is a bug similar with KYLIN-3165, introduced to Kylin 2.2 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (KYLIN-3177) Merged Streaming cube segments has no start/end time

2018-01-17 Thread Shaofeng SHI (JIRA)
Shaofeng SHI created KYLIN-3177:
---

 Summary: Merged Streaming cube segments has no start/end time
 Key: KYLIN-3177
 URL: https://issues.apache.org/jira/browse/KYLIN-3177
 Project: Kylin
  Issue Type: Bug
  Components: Job Engine, Metadata
Affects Versions: v2.2.0
Reporter: Shaofeng SHI
Assignee: Shaofeng SHI


Create a streaming cube, define auto merge thresholds; and then build it 
repeatedly.

When some segments be merged into a bigger segment, the new segment's start 
time and end time be 0 (show 1970-01-01).

 

This is a bug similar with KYLIN-3165, introduced to Kylin 2.2 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (KYLIN-3176) kylin startup failed on hive 2.2.0

2018-01-17 Thread peng.jianhua (JIRA)

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

peng.jianhua updated KYLIN-3176:

Description: 
org.apache.catalina.LifecycleException: Failed to initialize component 
[StandardServer[9005]]
 at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:643)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:682)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
 at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
 Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.derby.jdbc.AutoloadedDriver40
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:278)
 at java.sql.DriverManager.isDriverAllowed(DriverManager.java:463)
 at java.sql.DriverManager.isDriverAllowed(DriverManager.java:455)
 at java.sql.DriverManager.getDrivers(DriverManager.java:356)
 at 
org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:288)
 at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
 at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
 at 
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:388)
 at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
 ... 14 more

 

 

 

Exclude hive's derbyclient-10.11.1.1.jar from Kylin's classpath will solve the 
problem

  was:
org.apache.catalina.LifecycleException: Failed to initialize component 
[StandardServer[9005]]
 at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:643)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:682)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
 at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.derby.jdbc.AutoloadedDriver40
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:278)
 at java.sql.DriverManager.isDriverAllowed(DriverManager.java:463)
 at java.sql.DriverManager.isDriverAllowed(DriverManager.java:455)
 at java.sql.DriverManager.getDrivers(DriverManager.java:356)
 at 
org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:288)
 at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
 at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
 at 
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:388)
 at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
 ... 14 more


> kylin startup failed on hive 2.2.0
> --
>
> Key: KYLIN-3176
> URL: https://issues.apache.org/jira/browse/KYLIN-3176
> Project: Kylin
>  Issue Type: Bug
>  Components: Environment 
>Affects Versions: v2.3.0
> Environment: hive 2.2.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
>
> org.apache.catalina.LifecycleException: Failed to initialize component 
> [StandardServer[9005]]
>  at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
>  at org.apache.catalina.startup.Catalina.load(Catalina.java:643)
>  at 

[jira] [Created] (KYLIN-3176) kylin startup failed on hive 2.2.0

2018-01-17 Thread peng.jianhua (JIRA)
peng.jianhua created KYLIN-3176:
---

 Summary: kylin startup failed on hive 2.2.0
 Key: KYLIN-3176
 URL: https://issues.apache.org/jira/browse/KYLIN-3176
 Project: Kylin
  Issue Type: Bug
  Components: Environment 
Affects Versions: v2.3.0
 Environment: hive 2.2.0
Reporter: peng.jianhua
Assignee: peng.jianhua


org.apache.catalina.LifecycleException: Failed to initialize component 
[StandardServer[9005]]
 at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:643)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:682)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
 at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.derby.jdbc.AutoloadedDriver40
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:278)
 at java.sql.DriverManager.isDriverAllowed(DriverManager.java:463)
 at java.sql.DriverManager.isDriverAllowed(DriverManager.java:455)
 at java.sql.DriverManager.getDrivers(DriverManager.java:356)
 at 
org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:288)
 at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
 at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
 at 
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:388)
 at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
 ... 14 more



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)