[JBoss JIRA] (TEIID-3106) BufferManager Cleaner consuming 90% of total CPU time
by Devesh Mishra (JIRA)
[ https://issues.jboss.org/browse/TEIID-3106?page=com.atlassian.jira.plugin... ]
Devesh Mishra commented on TEIID-3106:
--------------------------------------
Still goes high CPU. logs indicate the same thing...
> BufferManager Cleaner consuming 90% of total CPU time
> -----------------------------------------------------
>
> Key: TEIID-3106
> URL: https://issues.jboss.org/browse/TEIID-3106
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.7
> Environment: zOS
> Reporter: Devesh Mishra
> Assignee: Steven Hawkins
> Labels: teiid-engine
> Attachments: BufferManagerImpl.java
>
>
> BufferManager Cleaner thread is consuming almost all of the CPU utilized by the jboss process. Thread dump shows following information.
> 3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004C41CFEB00, j9thread_t:0x0000004C52B85AE0, java/lang/Thread:0x000000481C036E20, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x76, isDaemon:true)
> 3XMTHREADINFO1 (native thread ID:0x3AEC2600, native priority:0x5, native policy:UNKNOWN)
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=2609184 (0x27D020)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.doRemove(ConcurrentSkipListMap.java:1070(Compiled Code))
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:854(Compiled Code))
> 5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x00000048393C2598, entry count: 1)
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108)
> 4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555)
> 4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505)
> When we added log statements around the BufferManagerImpl.doEvictions() it loops through the remove and firstEntry loop.
> Forum discussion link : https://community.jboss.org/message/901792
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIID-3106) BufferManager Cleaner consuming 90% of total CPU time
by Mark Addleman (JIRA)
[ https://issues.jboss.org/browse/TEIID-3106?page=com.atlassian.jira.plugin... ]
Mark Addleman commented on TEIID-3106:
--------------------------------------
Hi Steve - I took a peek at https://github.com/teiid/teiid/commit/e768057149ed049c5ab6321f63cb9dad8d4... and suspect that the id comparison should be id.compareTo(o.id). We have made that change locally and begun a test but are losing our testing window today. We'll pick this up again at our next window - which I believe is in about 8 hours.
> BufferManager Cleaner consuming 90% of total CPU time
> -----------------------------------------------------
>
> Key: TEIID-3106
> URL: https://issues.jboss.org/browse/TEIID-3106
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.7
> Environment: zOS
> Reporter: Devesh Mishra
> Assignee: Steven Hawkins
> Labels: teiid-engine
> Attachments: BufferManagerImpl.java
>
>
> BufferManager Cleaner thread is consuming almost all of the CPU utilized by the jboss process. Thread dump shows following information.
> 3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004C41CFEB00, j9thread_t:0x0000004C52B85AE0, java/lang/Thread:0x000000481C036E20, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x76, isDaemon:true)
> 3XMTHREADINFO1 (native thread ID:0x3AEC2600, native priority:0x5, native policy:UNKNOWN)
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=2609184 (0x27D020)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.doRemove(ConcurrentSkipListMap.java:1070(Compiled Code))
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:854(Compiled Code))
> 5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x00000048393C2598, entry count: 1)
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108)
> 4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555)
> 4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505)
> When we added log statements around the BufferManagerImpl.doEvictions() it loops through the remove and firstEntry loop.
> Forum discussion link : https://community.jboss.org/message/901792
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIID-3107) NPE when WS translator not used with ContentHeaders argument
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3107?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3107:
-------------------------------------
Ok, created TEIIDDES-2329 asked Designer team to notify about the version of the software when the contentType introduced, based on the response this JIRA could be rejected or used for compensation logic. The same OUT instead of return is observed on "invoke" procedure call in Designer.
> NPE when WS translator not used with ContentHeaders argument
> ------------------------------------------------------------
>
> Key: TEIID-3107
> URL: https://issues.jboss.org/browse/TEIID-3107
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.8
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIID-3108) WS translator Procedure definition defined in correctly
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-3108:
-----------------------------------
Summary: WS translator Procedure definition defined in correctly
Key: TEIID-3108
URL: https://issues.jboss.org/browse/TEIID-3108
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Misc. Connectors
Affects Versions: 8.8
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Fix For: 8.9
TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
{code}
java.lang.NullPointerException
at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIID-3106) BufferManager Cleaner consuming 90% of total CPU time
by Devesh Mishra (JIRA)
[ https://issues.jboss.org/browse/TEIID-3106?page=com.atlassian.jira.plugin... ]
Devesh Mishra edited comment on TEIID-3106 at 8/30/14 12:49 PM:
----------------------------------------------------------------
It still looked to loop around the remove, This is the thread which has consumed most of the cpu.
3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004CBCED9100, j9thread_t:0x0000004C9B9F5D60, java/lang/Thread:0x000000481C116478, state:CW, prio=5
3XMJAVALTHREAD (java/lang/Thread getId:0x7F, isDaemon:true)
3XMTHREADINFO1 (native thread ID:0x5506D400, native priority:0x5, native policy:UNKNOWN)
3XMHEAPALLOC Heap bytes allocated since last GC cycle=376012832 (0x16698020)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code))
4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code))
4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:855(Compiled Code))
5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x000000483A574070, entry count: 1)
4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108)
4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555)
4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505)
3XMTHREADINFO3 No native callstack available on this platform
NULL
was (Author: deveshmishra):
It still looked to loop around the remove, but the dump shows the following. This is the thread which has consumed most of the cpu.
3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004CB725DC00, j9thread_t:0x0000004CA3A3A720, java/lang/Thread:0x000000481C0E6330, state:CW, prio=5
3XMJAVALTHREAD (java/lang/Thread getId:0x7F, isDaemon:true)
3XMTHREADINFO1 (native thread ID:0x5508B800, native priority:0x5, native policy:UNKNOWN)
3XMHEAPALLOC Heap bytes allocated since last GC cycle=113578488 (0x6C511F8)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at java/io/FileOutputStream.writeBytes(Native Method)
4XESTACKTRACE at java/io/FileOutputStream.write(FileOutputStream.java:318(Compiled Code))
4XESTACKTRACE at java/io/BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82(Compiled Code))
4XESTACKTRACE at java/io/BufferedOutputStream.write(BufferedOutputStream.java:95(Compiled Code))
5XESTACKTRACE (entered lock: java/io/BufferedOutputStream@0x0000004845728470, entry count: 1)
> BufferManager Cleaner consuming 90% of total CPU time
> -----------------------------------------------------
>
> Key: TEIID-3106
> URL: https://issues.jboss.org/browse/TEIID-3106
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.7
> Environment: zOS
> Reporter: Devesh Mishra
> Assignee: Steven Hawkins
> Labels: teiid-engine
> Attachments: BufferManagerImpl.java
>
>
> BufferManager Cleaner thread is consuming almost all of the CPU utilized by the jboss process. Thread dump shows following information.
> 3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004C41CFEB00, j9thread_t:0x0000004C52B85AE0, java/lang/Thread:0x000000481C036E20, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x76, isDaemon:true)
> 3XMTHREADINFO1 (native thread ID:0x3AEC2600, native priority:0x5, native policy:UNKNOWN)
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=2609184 (0x27D020)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.doRemove(ConcurrentSkipListMap.java:1070(Compiled Code))
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:854(Compiled Code))
> 5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x00000048393C2598, entry count: 1)
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108)
> 4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555)
> 4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505)
> When we added log statements around the BufferManagerImpl.doEvictions() it loops through the remove and firstEntry loop.
> Forum discussion link : https://community.jboss.org/message/901792
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIID-3106) BufferManager Cleaner consuming 90% of total CPU time
by Devesh Mishra (JIRA)
[ https://issues.jboss.org/browse/TEIID-3106?page=com.atlassian.jira.plugin... ]
Devesh Mishra commented on TEIID-3106:
--------------------------------------
It still looked to loop around the remove, but the dump shows the following. This is the thread which has consumed most of the cpu.
3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004CB725DC00, j9thread_t:0x0000004CA3A3A720, java/lang/Thread:0x000000481C0E6330, state:CW, prio=5
3XMJAVALTHREAD (java/lang/Thread getId:0x7F, isDaemon:true)
3XMTHREADINFO1 (native thread ID:0x5508B800, native priority:0x5, native policy:UNKNOWN)
3XMHEAPALLOC Heap bytes allocated since last GC cycle=113578488 (0x6C511F8)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at java/io/FileOutputStream.writeBytes(Native Method)
4XESTACKTRACE at java/io/FileOutputStream.write(FileOutputStream.java:318(Compiled Code))
4XESTACKTRACE at java/io/BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82(Compiled Code))
4XESTACKTRACE at java/io/BufferedOutputStream.write(BufferedOutputStream.java:95(Compiled Code))
5XESTACKTRACE (entered lock: java/io/BufferedOutputStream@0x0000004845728470, entry count: 1)
> BufferManager Cleaner consuming 90% of total CPU time
> -----------------------------------------------------
>
> Key: TEIID-3106
> URL: https://issues.jboss.org/browse/TEIID-3106
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.7
> Environment: zOS
> Reporter: Devesh Mishra
> Assignee: Steven Hawkins
> Labels: teiid-engine
> Attachments: BufferManagerImpl.java
>
>
> BufferManager Cleaner thread is consuming almost all of the CPU utilized by the jboss process. Thread dump shows following information.
> 3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004C41CFEB00, j9thread_t:0x0000004C52B85AE0, java/lang/Thread:0x000000481C036E20, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x76, isDaemon:true)
> 3XMTHREADINFO1 (native thread ID:0x3AEC2600, native priority:0x5, native policy:UNKNOWN)
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=2609184 (0x27D020)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.doRemove(ConcurrentSkipListMap.java:1070(Compiled Code))
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:854(Compiled Code))
> 5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x00000048393C2598, entry count: 1)
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108)
> 4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555)
> 4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505)
> When we added log statements around the BufferManagerImpl.doEvictions() it loops through the remove and firstEntry loop.
> Forum discussion link : https://community.jboss.org/message/901792
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIID-3106) BufferManager Cleaner consuming 90% of total CPU time
by Devesh Mishra (JIRA)
[ https://issues.jboss.org/browse/TEIID-3106?page=com.atlassian.jira.plugin... ]
Devesh Mishra commented on TEIID-3106:
--------------------------------------
Thanks Steven, now it doesn't loop around the remove. But still had high CPU. I couldn't collect the thread dump awaiting for another high cpu instance to occur :(
> BufferManager Cleaner consuming 90% of total CPU time
> -----------------------------------------------------
>
> Key: TEIID-3106
> URL: https://issues.jboss.org/browse/TEIID-3106
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.7
> Environment: zOS
> Reporter: Devesh Mishra
> Assignee: Steven Hawkins
> Labels: teiid-engine
> Attachments: BufferManagerImpl.java
>
>
> BufferManager Cleaner thread is consuming almost all of the CPU utilized by the jboss process. Thread dump shows following information.
> 3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004C41CFEB00, j9thread_t:0x0000004C52B85AE0, java/lang/Thread:0x000000481C036E20, state:CW, prio=5
> 3XMJAVALTHREAD (java/lang/Thread getId:0x76, isDaemon:true)
> 3XMTHREADINFO1 (native thread ID:0x3AEC2600, native priority:0x5, native policy:UNKNOWN)
> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=2609184 (0x27D020)
> 3XMTHREADINFO3 Java callstack:
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.doRemove(ConcurrentSkipListMap.java:1070(Compiled Code))
> 4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code))
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:854(Compiled Code))
> 5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x00000048393C2598, entry count: 1)
> 4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108)
> 4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555)
> 4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505)
> When we added log statements around the BufferManagerImpl.doEvictions() it loops through the remove and firstEntry loop.
> Forum discussion link : https://community.jboss.org/message/901792
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIID-3107) NPE when WS translator not used with ContentHeaders argument
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3107?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-3107 at 8/29/14 8:42 PM:
----------------------------------------------------------------
Ideally it should match exactly what is in the translator / doc. result as the return value should be first and contentheaders should be added as the last parameter. But if this is already out there in a released version, then I guess that we'll have to compensate for it unfortunately.
was (Author: shawkins):
Ideally it should match exactly what is in the translator / doc. result as the return value should be first and contentheaders should be added as the last parameter.
> NPE when WS translator not used with ContentHeaders argument
> ------------------------------------------------------------
>
> Key: TEIID-3107
> URL: https://issues.jboss.org/browse/TEIID-3107
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.8
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIID-3107) NPE when WS translator not used with ContentHeaders argument
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3107?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3107:
---------------------------------------
Ideally it should match exactly what is in the translator / doc. result as the return value should be first and contentheaders should be added as the last parameter.
> NPE when WS translator not used with ContentHeaders argument
> ------------------------------------------------------------
>
> Key: TEIID-3107
> URL: https://issues.jboss.org/browse/TEIID-3107
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.8
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (TEIID-3107) NPE when WS translator not used with ContentHeaders argument
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3107?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3107:
---------------------------------------
That is not correct, the result value needs to be marked as a return value - not just an out parameter.
> NPE when WS translator not used with ContentHeaders argument
> ------------------------------------------------------------
>
> Key: TEIID-3107
> URL: https://issues.jboss.org/browse/TEIID-3107
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Affects Versions: 8.8
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months