Fwd: Re: Tags don't show up in Tags dropdown menu
by Bela Ban
FYI
-------- Forwarded Message --------
Subject: Re: Tags don't show up in Tags dropdown menu
Date: Wed, 11 Jan 2017 16:54:07 -0800
From: Francis (GitHub Staff) <support(a)github.com>
To: Bela Ban <belaban(a)mailbox.org>
Hi Bela -
Thanks for getting in touch! The tag dropdown is capped at 100 tags for
performance reasons, but you can still get the full list of tags on the
repository tags page:
https://github.com/belaban/JGroups/tags
You can access the |JGroups-3.6.12.Final| tag by navigating to this URL:
https://github.com/belaban/JGroups/tree/JGroups-3.6.12.Final
I hope that helps, but let me know if you have any other questions!
All the best,
Francis
------------------------------------------------------------------------
Howdy folks,
kudos for the great work on GH!
in my repo github.com/belaban/JGroups, under "branch:master" ->
"tags", only a fraction of the tags show up. When I clone the repo,
or on git ls-remote, they do show up (for example
JGroups-3.6.12.Final), see below.
Can you look at this? Not high prio as everything works, but is this
a bug in GH?
Cheers,
Bela
[belasmac] /Users/bela/JGroups$ git ls-remote origin |grep 3.6.12
X11 forwarding request failed on channel 0
7c4e70131237dd6b54d8c8bc2f2c336f40b93518 refs/tags/JGroups-3.6.12.Final
9 years, 2 months
Property substitution for attributes that are part of paths - ISPN-7326
by Galder Zamarreño
Hey Paul,
Re: https://issues.jboss.org/browse/ISPN-7326
I have some doubts how to achieve what I'm trying to do in ^
More specifically, backup's 'site' attribute and remote-site's name attributes are special in the sense that they're not represented as SimpleAttributeDefinition instances. Instead, it seems like they're expected to be fully resolved when the XML read since they are part of path addresses.
Resolution when XML is read does not work since reading is done by the host controller and I'd want the resolution to happen when the particular server node starts up.
So, what would be the best way to achieve what I'm after?
One way I was thinking is maybe leaving the XML reading part as is, and only when the cache is added, do the resolution manually there. However, this does not seem to work as is, because the XML attribute is already resolved when I add the cache and it's resolved to the default value (cos process controller was not started with -D...), so I can't seem to get the original XML value. Moreover, even if this was resolved, would it be fine for the path address to have the default value for the property in it, and the actual cache configured with the name passed via system property? Doesn't sound right...
Any other way? Maybe add separate SimpleAttributeDefinition instances for these XML attributes on top of their path address values?
Cheers,
--
Galder Zamarreño
Infinispan, Red Hat
9 years, 2 months
Infinispan Memory Issue - Storing Index Memory(ram) - OutOfMemoryError: Java heap space
by Sridhar Jena
Hi Dev Team,
I am using infinispan 8.2.4 standalone hotrod server and i am facing
"*java.lang.OutOfMemoryError: Java heap space*" issue when putting or
retrieving the data into cache.
In below two ways i have loaded the data into local cache.
_/*Case 1*/_ : *(Data Loading is taking more time, But there is no issue
with **"**OutOfMemoryError: Java heap space**"**)*
In this case I am storing the index into a different dedicated
infinispan cache by using the below tag ,
/*<property name="default.directory_provider">Infinispan</property>*/
I have observed that it is taking much time to load the data into cache
, but in this case i am not facing /Java Out of memory heap space/ issue
during data putting or retrieving.
/Below is local cache configuration,/
<local-cache name="MERCHANT_STORE_DETAILS" start="EAGER">
<locking acquire-timeout="30000" concurrency-level="1000"
striping="false"/>
<transaction mode="NONE"/>
<eviction strategy="NONE"/>
<file-store path="/MRSD/data" purge="false"
passivation="false" preload="true"/>
<indexing index="LOCAL">
<property
name="default.indexmanager">*org.infinispan.query.indexmanager.InfinispanIndexManager*</property>
<property
name="default.directory_provider">*Infinispan*</property>
<property
name="default.metadata_cachename">MRSD-INDEX_META_DATA</property>
<property
name="default.data_cachename">MRSD-INDEX_DATA</property>
<property
name="default.locking_cachename">MRSD-INDEX_LOCKING</property>
</indexing>
</local-cache>
<local-cache name="MRSD-INDEX_META_DATA" start="EAGER">
<indexing index="NONE"/>
<file-store path="/MRSD/index/indexMetadata" shared="false"
purge="false" passivation="false" preload="true" fetch-state="true"
read-only="false"/>
</local-cache>
<local-cache name="MRSD-INDEX_DATA" start="EAGER">
<indexing index="NONE"/>
<file-store path="MRSD/index/indexData" shared="false"
purge="false" passivation="false" preload="true" fetch-state="true"
read-only="false"/>
</local-cache>
<local-cache name="MRSD-INDEX_LOCKING" start="EAGER">
<indexing index="NONE"/>
<file-store path="MRSD/index/indexLocking" shared="false"
purge="false" passivation="false" preload="true" fetch-state="true"
read-only="false"/>
</local-cache>
*Time Taken To Load Data: *3 Min 13 Sec*
*
*Number of Records :* 45024
/*_Case 2_ */: *(Data Loading is very quick, But issue with
**"**OutOfMemoryError: Java heap space**"**)*
In this case I am storing the index into memory by using the below tag ,
/*<property name="default.directory_provider">ram</property>*/
I have observed that, data has loaded into cache with in some seconds
for same number of records that mentioned in _Case 1_,
But in this case when i am trying the store the same number of
records(*45024*) multiple times and retrieving the data in same duration
, It is throwing *OutOfMemoryError: Java heap space *in
/infinispan-server-8.2.4.Final/standalone/configuration/server.log./
/Below is local cache configuration,
/<local-cache name="MERCHANT_STORE_DETAILS" start="EAGER">
<locking acquire-timeout="30000" concurrency-level="1000"
striping="false"/>
<transaction mode="NONE"/>
<eviction strategy="NONE"/>
<indexing index="LOCAL">
<property
name="default.indexmanager">near-real-time</property>
<property
name="default.directory_provider">ram</property>
</indexing>
</local-cache>
*Time Taken To Load Data: *32 Sec
*Number of Records :* 45024
_*Exception In Details
*_2017-01-09 06:38:31,777 ERROR [stderr]
(HotRod-externalServerHandler-1-88) Exception in thread
"HotRod-externalServerHandler-1-88" java.lang.OutOfMemoryError: Java
heap space
2017-01-09 06:39:18,706 ERROR
[org.hibernate.search.exception.impl.LogErrorHandler] (Lucene Merge
Thread #7869 for index
org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper)
HSEARCH000058: HSEARCH000118: Exception during index Merge operation:
org.apache.lucene.index.MergePolicy$MergeException:
java.lang.OutOfMemoryError: Java heap space
at
org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:668)
at
org.hibernate.search.backend.impl.lucene.overrides.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:42)
at
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:648)
Caused by: java.lang.OutOfMemoryError: Java heap space
2017-01-09 06:41:23,919 ERROR [stderr]
(HotRod-externalServerHandler-1-88) at
org.antlr.runtime.Lexer.emit(Lexer.java:160)
2017-01-09 06:36:54,872 ERROR
[org.jboss.as.controller.management-operation]
(DeploymentScanner-threads - 2) WFLYCTL0013: Operation
("read-children-resources") failed - address: ([]):
java.lang.OutOfMemoryError: Java heap space
at java.util.HashMap.resize(HashMap.java:703)
at java.util.HashMap.putVal(HashMap.java:628)
at java.util.HashMap.put(HashMap.java:611)
at
org.jboss.as.controller.OperationContextImpl$AuthorizationResponseImpl.addResourceResult(OperationContextImpl.java:2356)
at
org.jboss.as.controller.OperationContextImpl$AuthorizationResponseImpl.access$700(OperationContextImpl.java:2328)
at
org.jboss.as.controller.OperationContextImpl.getBasicAuthorizationResponse(OperationContextImpl.java:1764)
at
org.jboss.as.controller.OperationContextImpl.authorize(OperationContextImpl.java:1659)
at
org.jboss.as.controller.OperationContextImpl.authorize(OperationContextImpl.java:1618)
at
org.jboss.as.controller.OperationContextImpl.getResourceRegistration(OperationContextImpl.java:567)
at
org.jboss.as.controller.operations.global.ReadChildrenResourcesHandler.execute(ReadChildrenResourcesHandler.java:94)
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
at
org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
at
org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
at
org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)
at
org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
at
org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204)
at
org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:659)
at
org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:649)
at
org.jboss.as.server.deployment.scanner.DefaultDeploymentOperations.getDeploymentsStatus(DefaultDeploymentOperations.java:76)
at
org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$ScanContext.<init>(FileSystemDeploymentService.java:1614)
at
org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$ScanContext.<init>(FileSystemDeploymentService.java:1563)
at
org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:568)
at
org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:489)
at
org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentScanRunnable.run(FileSystemDeploymentService.java:250)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
2017-01-09 06:38:39,564 ERROR
[org.infinispan.interceptors.InvocationContextInterceptor]
(HotRod-externalServerHandler-1-107) ISPN000136: Error executing command
PutKeyValueCommand, writing keys [[B0x4a1b313031323331..[29]]:
java.lang.OutOfMemoryError: Java heap space
at
java.util.ResourceBundle.putBundleInCache(ResourceBundle.java:1694)
at java.util.ResourceBundle.findBundle(ResourceBundle.java:1471)
at java.util.ResourceBundle.findBundle(ResourceBundle.java:1419)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1361)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:890)
at sun.util.resources.LocaleData$1.run(LocaleData.java:164)
at sun.util.resources.LocaleData$1.run(LocaleData.java:160)
at java.security.AccessController.doPrivileged(Native Method)
at sun.util.resources.LocaleData.getBundle(LocaleData.java:160)
at
sun.util.resources.LocaleData.getNumberFormatData(LocaleData.java:156)
at
sun.util.locale.provider.LocaleResources.getNumberPatterns(LocaleResources.java:439)
at
sun.util.locale.provider.NumberFormatProviderImpl.getInstance(NumberFormatProviderImpl.java:177)
at
sun.util.locale.provider.NumberFormatProviderImpl.getNumberInstance(NumberFormatProviderImpl.java:149)
at java.text.NumberFormat.getInstance(NumberFormat.java:875)
at java.text.NumberFormat.getInstance(NumberFormat.java:861)
at java.text.NumberFormat.getNumberInstance(NumberFormat.java:458)
at org.infinispan.commons.util.Util.prettyPrintTime(Util.java:353)
at
org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.lock(DefaultLockManager.java:238)
at
org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockAndRecord(AbstractLockingInterceptor.java:193)
at
org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitNonTxDataWriteCommand(AbstractLockingInterceptor.java:98)
at
org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor.visitDataWriteCommand(NonTransactionalLockingInterceptor.java:41)
at
org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitPutKeyValueCommand(AbstractLockingInterceptor.java:65)
at
org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:78)
at
org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at
org.infinispan.interceptors.CacheMgmtInterceptor.updateStoreStatistics(CacheMgmtInterceptor.java:191)
at
org.infinispan.interceptors.CacheMgmtInterceptor.visitPutKeyValueCommand(CacheMgmtInterceptor.java:177)
at
org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:78)
at
org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at
org.infinispan.interceptors.compat.BaseTypeConverterInterceptor.visitPutKeyValueCommand(BaseTypeConverterInterceptor.java:84)
at
org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:78)
at
org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99)
at
org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:114)
Could any one please help me here to fix the "*OutOfMemoryError: Java
heap space*" issue for _*Case 2.
*_Please let me know if you need more information on this.
Thanks in advance.
_*
*_
--
Aurus Signature
*________________________________________________________________________________________________________________________________________________________________*
*Thanks and Regards,*
*Sridhar Jena,* Sr. Techincal Lead, Products
*+91 - 20 - 27655062* | *+91 - 9226345267* | *sjena345* |
*www.aurusinc.com* <http://www.aurusinc.com/>
*Plot G-2, Sector 26, Pradhikaran, Pune, Maharashtra-411044*
<http://www.aurusinc.com/>
<https://www.facebook.com/pages/Aurus-Inc-Solution-and-Services-Provider/1...>
<https://twitter.com/aurustech> <http://linkedin.com/company/aurustech>
<https://plus.google.com/100924847781939597025>
/*Please consider the environment before printing this e-mail */
Disclaimers: This message contains confidential information and is
intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system. E-mail
transmission cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail transmission. If verification
is required please request a hard-copy version.
9 years, 2 months
JDK 9 EA Build 151 is available on java.net
by Rory O'Donnell
Hi Galder,
Best wishes for the New Year.
Dalibor and I will be at FOSDEM '17, Brussels 4 & 5 February. Let us
know if you will be there, hopefully we can meet up !
*JDK 9 Early Access* b151 <https://jdk9.java.net/download/> is
available on java.net
There have been a number of fixes to bugs reported by Open Source
projects since the last availability email :
* JDK-8171377 : Add sun.misc.Unsafe::invokeCleaner
* JDK-8075793 : Source incompatibility for inference using -source 7
* JDK-8087303 : LSSerializer pretty print does not work anymore
* JDK-8167143 :CLDR timezone parsing does not work for all locales
Other changes that maybe of interest:
* JDK-8066474 : Remove the lib/$ARCH directory from Linux and Solaris
images
* JDK-8170428 : Move src.zip to JDK/lib/src.zip
*JEPs intergrated:*
* JEP 295 <http://openjdk.java.net/jeps/295>: Ahead-of-Time
Compilation has been integrated in b150.
*Schedule - Milestones since last availability email *
* *Feature Extension Complete 22nd of December 2016*
* *Rampdown Started 5th of January 2017
*
o Phases in which increasing levels of scrutiny are applied to
incoming changes.
o In phase 1, only P1-P3 bugs can be fixed. In phase 2 only
showstopper bugs can be fixed.
Rgds,Rory
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
9 years, 2 months
