Lost source codes...
IgniteInternalFuture commitTxAsync(final
GridNearTxLocal tx) {
FutureHolder holder = lastFut.get();
holder.lock();
try {
IgniteInternalFuture fut = holder.future();
if (fut != null && !fut.isDone()) {
Ignit
Hi!
Ignite 2.3, Maximum permit count exceeded on Semaphore...
GridCacheAdapter.commitTxAsync():
But saveFuture() don't call acquire, only release:
May be need *retry = true*?
Alexander
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi!
In Ignite 2.0 missing FairAffinityFunction. Why?
Alexander
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/FairAffinityFunction-in-Ignite-2-0-tp14381.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi, Val!
The problem is solved in that such modifications in filterReachable()
method:
for (Future fut : futs) {
try {
fut.get();
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
throw new Ignit
Hi, Val!
The root cause is clear:
[IgniteUtils.class]
for (InetSocketAddress addr : addrs)
allInetAddrs.add(*addr.getAddress()*);
List reachableInetAddrs =
U.filterReachable(allInetAddrs);
[InetSocketAddress.class]
/**
*
* Gets the {@code InetAddress}
Ok. Serializable is not so good example. Conversion to bytes sequence and its
comparation is not effective and unambiguous. But what about Number as super
type?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Mix-in-cache-keys-objects-with-different-types-tp1435
Hello!
IgniteCache cache = ...;
You can't have both objects with keys of type Long and String. Why?
Alexander.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Mix-in-cache-keys-objects-with-different-types-tp14354.html
Sent from the Apache Ignite Users mailing
Hello!I have on the server have exception:And client does not receive
response...I solved the problem by modifying the code as follows:Source of
the value null I yet don't understand, but this patch fix problem.Alexander
--
View this message in context:
http://apache-ignite-users.70518.x6.nabbl
Hi, All!
I found that during the execution Ignite 2.0 accumulate threads with the
name 'pool--thread-' and as result occurs OutOfMemoryException -
unable to create native thread.
Research led me to a method IgniteUtiuls.filterReachable():
/ public static List filterReachable(Collection
addrs) {
