Hi!
vtieu wrote
> My question is how can I increase the Java heap memory when I run the
> ignite.sh? Thanks.
To do this you should run the ignite.sh script like this:
./ignite.sh -J-Xmx12g
This command will set the maximum available heap memory to 12G (you can
provide the value that fits
Hi,
The only workaround I see right now is to create special class that fill
flatten all fields with proper names/aliases and use it as a cache value.
As for your patch, can you please create a Jira ticket and attach it there?
Someone in the community will review. You can ask any
Hi Kevin,
The difference is that data streamer uses remove() method to update the
cache, while your second test uses clearAll(). remove() and removeAll() are
transactional operations and it also updates persistence store if you have
it. clearAll(), on the other side, only removes the data from
Hi,
I reproduced the issue and created a ticket [1]. Someone in the community
will take a look shortly and provide feedback.
[1] https://issues.apache.org/jira/browse/IGNITE-1886
-Val
--
View this message in context:
Hi,
Can you please subscribe to the mailing list so that we receive email
notifications? Follow the instructions here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
It looks like your cache is never started. Can you show how you do this?
Where do you
Hi,
diopek wrote
> Is it possible to keep all the configuration defined in cache xml file as
> default, just set the startSize using CacheConfiguration API.
You can put your cache configuration template outside IgniteConfiguration
bean and then use Ignition.loadSpringBean() method.
For
Vladimir Ozerov wrote
> Some time ago there was a discussion to implement native IGFS -> OS
> adapter
> [2], but no final decisions were made. As were are seing growing interest
> to this feature probably we should resume this thread.
Vladimir,
I think Kobe and Paolo are looking for the opposite
Hi,
Can you please subscribe to the mailing list so that community will receive
email notifications? Follow the instructions here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
OhTaeHyeon wrote*
> How do I fix this?
>
> Caused by:
Create ticket: https://issues.apache.org/jira/browse/IGNITE-1926
Kobe, Paolo, this task doesn't seem to be very complicated. How about
picking it up?
-Val
--
View this message in context:
Hi,
Here is the ticket for this issue:
https://issues.apache.org/jira/browse/IGNITE-1897
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Write-behind-question-tp1936p1947.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
I'm a bit confused :) Can you please clarify what you meant by "I can only
connect to local server if i have an active remote server node running."?
Does it work for you if you remove 127.0.0.1 from IP finder list and use a
local non-loopback address instead (like 192.168.x.x, for example)?
Hi Lin Lyu,
Cahe interceptor is configured per cache (see
CacheConfiguration.setInterceptor() configuration property). So you don't
need to do any additional filtering, just set this configuration only for
one cache.
-Val
--
View this message in context:
Hi,
Can you please subscribe to the mailing list so that we receive email
notification for your posts? You can refer to this instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
As for your issue, I reproduced it and it looks weird for me, so I
Hi,
Can you please subscribe to the mailing list so that we receive email
notification for your posts? You can refer to this instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
Stolidedog wrote
> I get a OutOfMemoryError when I have multiple
Hi Lokesh,
Can you please subscribe to the mailing list so that we can receive email
notifications? For instructions please refer to this page:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
LokeshBhate wrote
> I am getting stream terminated message
Hi Alexey,
Alexey V. Ryazanov wrote
> I stop grid by
/
> G.stop("myGridName", false);
/
>
> It seems to me it takes some time to stop. Can I be notified somehow when
> grid has actually been stopped? Cause now I have to use
/
> Thread.sleep()
/
> in order to take a time before I can start
Hi Kevin,
Can you show your cache configuration?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-read-through-when-invoking-EntryProcessor-tp1557p1558.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Kevin,
You also need to set this property:
cacheConfiguration.setLoadPreviousValue(true);
It enables read-through for all update operations that also read previous
value (getAndPut, replace, invoke, etc.).
-Val
--
View this message in context:
Alexey V. Ryazanov wrote
No, it's not helpful for me.
But thank you for information.
Alexey,
Can you describe your use case so that we can suggest a proper solution?
-Val
--
View this message in context:
Alexey V. Ryazanov wrote
I suggest continue discuss my case
in this thread
http://apache-ignite-users.70518.x6.nabble.com/Where-can-I-keep-some-meta-information-about-my-nodes-td1109.html
. Thanks for information about attributes.
OK, responded there.
-Val
--
View this message in
deepakmca05 wrote
I have couple of questions around ignite architecture for production set
up.
As the documentations says the cluster can be partitioned into cluster
groups of Data Grid/Compute grid etc.
So my question here is do we need to define the data grid and compute grid
on the same
Alexey V. Ryazanov wrote
I created a simple plugin. It looks alive - i see calls to methods like
onIgniteStart(), createComponent(), provideDiscoveryData(). But I don't
see any calls to method validateNewNode() even when I starting a lot of
new nodes. Where I made a mistake? My plugin
guherbozdogan wrote
I would like to query the following architectural query. The context of
project employs the Apache Data Grid system as in memory grid for a web
system and the cache data will also be persisted to a nosql db server
cluster (data grid will be connected to a persistent nosql
diopek wrote
> We are developing batch application that will eventually be generating
> unordered, large number or records data file around 1GB using
> multi-threads/process. What would be the best practices to accomplish this
> using Ignite. Using ignite data cache with write-behind (file system)
Isaeed Mohanna wrote
> Hi
> I got confused because maven official repository lists these builds as
> alpha in the type column as seen here
> http://mvnrepository.com/artifact/org.apache.ignite/ignite-core
> It will help resolve the confusion if the build type is changed to stable
> instead of
yaoqin wrote
> Is there any extra settings, if I use SSDs instead of normal disks?
> Or just insert a SSD to an ignite node without any configurations?
Current implementation of swap space SPI uses standard Java file API, do it
can transparently work with both spin disks and SSD. There are no
The build works for me. And actually it looks weird that it tries to go to
codehaus repo, because this plugin is available in Maven Central. Is it
possible that you have this repo specified somewhere? E.g., in
.m2/settings.xml file?
-Val
--
View this message in context:
mfronczyk wrote
> How will it work with Persistent Store configured with write-through or
> write-behind? Won't the whole value (16384 element array) be persisted
> each
> time a single entry of the array is modified?
The whole entry will be passed to CacheStore.write(..) method and it's up to
Enrico Olivelli wrote
> Is there any way to use org.apache.ignite.plugin.security package classes
> ?
Enrico,
This package contains only basic API classes, like interfaces and enums. You
will probably use them in your plugin implementation, but you still need to
implement GridSecurityProcessor
big-jobiees wrote
> In the ignite repo i see lots of branches.
>
> my question is what dose head of master represent, in terms of Ignite
> development. ?
>
> the latest greatest edge of development ? or only stable complete
> features added ?
>
> Thanks
Hi,
Master contains only completed
javadevmtl wrote
> Val are you talking about me? I thought I was. Unless my mobile phone did
> something funny. I have been posting for a while...
No, this was for Mike. Sorry for the confusion :)
-Val
--
View this message in context:
roar109 wrote
> If I understand your suggestion correctly is to make single Ignite
> instance per jboss in this case to avoid this sync mechanism?
This should help too. But it sounds like that in your case you can simply
disable shared memory communication. To do this add the following in your
Hi,
Please start Visor in the verbose mode:
./ignitevisorcmd.sh -v
It will show you the full log and full exception trace.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Can-t-seem-to-connect-grid-visor-tp1442p1450.html
Sent from the Apache Ignite
Hi Kevin,
I'm not sure I fully understand what you're trying to achieve. Can you
describe your use case in more details? What is the purpose of this
'locking' field?
As for 'update_timestamp', I think you should not update it automatically on
MySQL side, because cache will not know about this
Hi Kevin,
First of all, the transaction behaves correctly and is rolled back. So you
get '6' when you're still inside the transaction and '5' after the commit
failed.
But you're right about the exception not being rethrown. We will take a look
at this.
-Val
--
View this message in context:
First of all, I would upgrade to 1.4 and see if it works there as you expect.
There were fixes for SQL failover since 1.1.
Can you describe you deployment in more details? Do you have a
web-application with an embedded Ignite client node and several server nodes
that this client node connects to?
Hi Mirko,
>From what I see, the thread that was doing get() was interrupted. Is it your
thread or you're calling cache from an Ignite job?
-Val
--
View this message in context:
Hi Matt,
Attributes can't be changed in runtime because they are exchanged in
discovery when a node join topology. I think you should have a replicated
cache with node ID to collection of tags mapping. You can create cluster
groups that will dynamically assign computations to nodes based on the
Hey Dan,
I'm to reproduce the issue myself and I have couple of questions:
- What Hibernate version do you have?
- What access type are you using (READ_WRITE, TRANSACTIONAL, ...)?
- You mentioned you use HibernateTransactionManager. Do you have any
transactional methods that spawn several update
Hi,
Can you please properly subscribe to the user list so we can get email
notifications? You can refer to these instructions for more info:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
KWANGSIK LEE wrote
> In my company, we're heavy user of
Hi Dan,
Did you have a chance to run with more debug? I really want to fix this
issue and your log could be really helpful.
Thanks!
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-L2-cache-transactions-tp1460p1506.html
Sent from the Apache
vpasynkova wrote
> The client (even though it does join the ignite cluster) doesn't query the
> cache directly. It sends http requests to the nodes, which in turn query
> the cache using query API. We are using Ignite verison 1.1.0.
If the client joins the cluster, I don't see any reason to use
Hi,
Can you please properly subscribe to the user list so we can get email
notifications? You can refer to these instructions for more info:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
vpasynkova wrote
> I have a client node in my multi-node
mfronczyk wrote
> Can I make transaction writes to the persistence store atomic with
> write-behind? As you wrote, writes always happen on the primary node when
> write-behind is enabled. This means that if there were multiple keys
> modified in a single transaction and these keys belong to
Hi Kevin,
My answers are inline...
kevin wrote
> 1. Is the difference between "evict" and "clear" that "evict" will remove
> entries from cache, but will move them to off-heap or swap if configured,
> and "clear" will remove entries from the cache as well as off-heap memory
> and swap storage?
Hi Kevin,
This approach is not going to work in distributed system because the object
can be serialized and sent from one node to another.
It sounds like you should use IgniteCache.putIfAbsent() method to update the
entry. It guarantees that only one of two concurrent updates succeeds. Let
me
kevin wrote
> Wouldn't IgniteCache.putIfAbsent() only work when you're inserting a new
> value (two concurrent creates, as opposed to two concurrent updates)?
putIfAbsent() operation means that the entry will not be updated if the
value is already set, i.e. will not be overwritten. In case of
Kevin,
Is this the only query you're going to execute? If so, this is a simple
caching use case, i.e. you want to cache DB query results in memory. In this
case you can save this query result (e.g., collection of persons for a
particular organization) as one entry and use simple cache lookups and
Hi Alexey,
Can you please properly subscribe to the user list so we can get email
notifications? You can refer to these instructions for more info:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
Alexey V. Ryazanov wrote
> I want (for testing purposes)
Hi Dan,
Can you just zip log files and attach them (or upload somewhere)?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-L2-cache-transactions-tp1460p1485.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Kevin,
I reproduced the issue and created a ticket [1]. I think it will be fixed in
the next release.
[1] https://issues.apache.org/jira/browse/IGNITE-1552
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/SQL-IN-operator-example-tp1493p1494.html
Sent
Hi Dan,
Looks like this is not enough as well. Can you rerun with the following
debug settings?
I understand that this will likely produce large files, but we don't see any
other way to investigate this.
Thanks for you help!
-Val
--
View this message in context:
Hi,
Can you please properly subscribe to the user list so we can get email
notifications? You can refer to these instructions for more info:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
Vamsi wrote
> I am tryign a clinet server setup. I have setup a
Hi!
Most likely you declared the factory or the listener as an anonymous class.
Anonymous classes always contain reference to the parent class (LongCache in
your case). So if the factory is serialized in the context of LongCache
instance, this instance is also serialized. In case of static method
Hi Satya,
The main problem here is that Ignite is completely abstracted from the
persistence store by CacheStore interface. It can be any storage -
relational database, disk based key-value storage, MongoDB, HDFS, etc... The
implementation of such trigger will be different for different stores,
Juan,
Here is the ticket for this:
https://issues.apache.org/jira/browse/IGNITE-2087
What other properties except the class loader should be honored in your
point of view? Please share your thoughts in the ticket. You are also free
to pick it up and make the fix ;)
-Val
--
View this message
Hi,
I'm not familiar with JBoss classloading model, but I would start with
making sure that your data model classes (the ones that are stored in cache)
are available on classpath of all nodes (both servers and clients). Probably
you need to put them to the same module where Ignite is deployed, so
Fsapei,
Automatic discovery process has nothing to do with caches, it's a protocol
allowing several nodes to form a cluster. A cluster can have multiple
caches, which are independent and isolated from each other. So, if I
correctly understood your proposal, it will not work. I think you should go
Juan,
Do I understand correctly, that if Ignite's cache manager sets its class
loader (the one that was passed to getCacheManager() method) to the
IgniteConfiguration when starting a node, everything will work properly? If
so, it's a good point and looks like an easy fix.
Please confirm that I
Paulo,
You can also take a look at IgniteReflectionFactory class, which is similar
to ClassFactory, but allows to provide additional properties. Sound like it
can be useful in your case.
-Val
--
View this message in context:
Juan,
I don't see why we should provide cache configuration properties there,
because cache is created by CacheManager, not CachingProvider, and based on
configuration object, not Spring XML file.
At the same time I agree that now there is now way to use Ignite's
CacheManager without Spring and
Juan,
I don't see how this will help you.
IgnitionEx.loadConfigurations(springCfgUrl) still uses Spring to load
configuration from the file.
I think the best way is to create IgniteConfiguration object, set class
loader, start Ignite and create cache using Ignite API. If you then use only
JCache
Hi Kamesh,
Here are my answers.
1. You should try loading the data in multithreaded fashion. The easiest way
to do this is to extend CacheLoadOnlyStoreAdapter instead of
CacheStoreAdapter and implement inputIterator and parse methods instead of
loadCache method. This adapter will parallelize
Hi Jennifer,
Test classes are not included in binary distributions. If you want to run a
test, you will have to download the source release [1] and build it
yourself.
Let us know if you have any issues with this.
[1] https://ignite.apache.org/download.cgi#sources
-Val
--
View this message
Kobe,
Yes, your understanding is correct. Let us know if anything doesn't work for
you.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Connecting-two-nodes-in-IGFS-tp2196p2203.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Completely agree with Juan. Setting class loader only for default
configuration is definitely not enough for the most use cases.
I reopened the ticket. Anton, will you have a chance to finish the fix?
-Val
--
View this message in context:
Hi Ravi,
Can you please properly subscribe to the mailing list so that community
receives email notifications? Just follow the simple instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
Ravi wrote
>
Hi victor.x.qu,
Can you please properly subscribe to the mailing list so that the community
receives email notifications? Just follow the simple instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
victor.x.qu wrote
> Hi
>
> Firstly, my
wychoi,
XObject$2 is a name of some anonymous class that was declared inside XObject
class. You don't have it in the snippet you provided, but the message
clearly shows that the instance of such a class is created. This makes me
think that you have some issues with the classpath. Can you
ignite_mk,
I don't think you have to package it, it's just a requirement for
environment, similar to .NET runtime. Ignite can work on any version of JDK7
or JDK8, there is no reason to upgrade each time new Java is released.
-Val
--
View this message in context:
Hi Antonio,
Can you please properly subscribe to the mailing list, so that the community
receives email notifications? Just follow the simple instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
asi wrote
> HI,
>
> I am new to Apache
Hi Benoit,
Can you please properly subscribe to the mailing list, so that the community
receives email notifications? Just follow this simple instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
Benoit Laurent wrote
> Hi,
>
> I've got a silly
Hi Kevin,
The event listener is called from the synchronized block on entry, so there
is no reason to use explicit lock there - the key is already locked. And
actually since you're locking the same key, this code should not deadlock
(and it works for me). Probably the issue is caused by some
Hi,
I'm not sure I understand your concern. You should assign a separate
multicast group for each Ignite cluster and make sure that none of these
groups are used by other applications. This will isolate different services
from each other.
Makes sense?
-Val
--
View this message in context:
Vinay,
Ignite.createCache() method will throw an exception if the cache already
exists. But if you use Ignite.getOrCreateCache() method instead, it will be
either created with the provided configuration, or you will get an already
existing cache. In the latter case the configuration you provide
Hi Vinay,
I'm not sure I understand the issue. Spring fully supports JCache
annotations and Ignite can be plugged in via SpringCacheManager we provide.
What's wrong with this implementation and why do you want another one?
If you use Ignite-specific features like SQL queries, you will have to use
Vinay,
As a first step I would recommend to refer to cache store examples provided
in Ignite: JDBC-based [1], Spring-based [2] and Hibernate-based [3]. They
all are pretty similar and demonstrate similar functionality, but
implemented using different tools. Note that corresponding session
rexer wrote
> Yes, I understand it.
> My question is about - what multicast addresses i can use?
> Which pool of addresses i can use?
> For example, for 4 different clusters.
Multicast IP range is 224.0.0.0 through 239.255.255.255 (some of them
already assigned) [1] and Ignite doesn't introduce
Hi wychoi,
Most likely you have different classpath on different nodes. Can you make
sure that the latest versions of XObject and all other classes you have are
deployed on all nodes?
Please let us know if it helps.
-Val
--
View this message in context:
Hi Raghavendra,
As a first step I would check the server node logs for any errors that could
happen there. My guess is that they simply ran out of memory and stopped
processing the requests. How much heap memory did you allocate per node?
Note that having 60GB of physical memory doesn't mean that
Jeniffer,
You can find example configurations here:
https://github.com/apache/ignite/tree/master/examples/config
The actual content depends on what discovery mechanism you want to use,
whether you need events, caches, etc...
If you want to start with all defaults, you can use Ignite's default
Hi Sumesh,
Can you please properly subscribe to the mailing list so that community
receives email notifications? Just follow the instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
sumesh wrote
> How can i change the server IP and Port so
Hi,
Can you please properly subscribe to the mailing list so that the community
receives email notifications? Jus follow the instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
sahilnarwal wrote
> Getting below logs :
> 2015-12-22
Hi,
You're right, text queries are based on Lucene full text search engine and
therefore fully support Lucene syntax [1].
E.g., query that searches only one field looks like this:
TextQuery(Person.class, "resume:Master");
[1] https://lucene.apache.org/core/2_9_4/queryparsersyntax.html
-Val
Hi Seshu,
The issue is not reproduced for me. How do you check current memory size of
the cache? Do you have a failing test that you can share with us?
-Val
--
View this message in context:
Hi Yury,
Please properly subscribe to the mailing list so that community receives
email notifications. Follow the instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
yury_alpatov wrote
> Hi all! I am newby in Apache Ignite. I want to
Hi Greg,
Good point about several nodes in topology! Seshu, please keep in mind that
this is a per-node setting, so the limit is actually multiplied by the
number of nodes.
XML looks correct to me. Ignite uses Spring-based configuration, which
supports expressions and "p:" syntax via custom
Hi Yury,
Port 11211 is used for REST by default, not for discovery. Can you try
starting both node and the Visor with the 'example-ignite.xml' configuration
file provided in examples?
To start a node:
./ignite.sh examples/config/example-ignite.xml
To open Visor:
open
Hi,
Please properly subscribe to the mailing list so that community can receive
email notifications. Follow the instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
liutong wrote
> my company uses windows server,but i read ignite doc just
Hi Seshu,
Thanks for the test, looks like it reproduces the issue. We will investigate
and fix it in 1.6. Here is the ticket:
https://issues.apache.org/jira/browse/IGNITE-2289
-Val
--
View this message in context:
Hi,
Can you please properly subscribe to the mailing list, so that community
receives email notifications? Just follow the instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
vinaysharmahbd wrote
> 1)Can I have a near cache in client
Hi Erik,
Generally, cache store is designed to be shared across all nodes. Dumping
data to local FS can lead to different data consistency issues and
definitely not an easy task.
If you want to persist your data, but avoid large latencies of DB, you can
use write-behind caching [1].
BTW,
Hi Kevin,
Can you please properly subscribe to the mailing list so that community
receives email notifications. Follow the instructions here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
Kevin Daly wrote
> Is there a syntax that can be used for
Hi,
Can you please properly subscribe to the mailing list so that community
receives email notifications? Follow the instructions here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
wychoi wrote
> hi
> In multiple cluster nodes environment
>
> I
Hi Kobe,
All Ignite artifacts are in Maven Central, there is no designated repo.
ignite-spring:1.4.0 [1] is there. ignite-hadoop2-integration module doesn't
exist, but there is ignite-hadoop [2] (and this is the correct name).
It looks like you have some local configuration issue. I would try to
Hi Satya,
Ignite is designed to be the primary data storage and treats DB as a backing
persistent store that is never accessed directly. It's most effective with
this approach.
Syncing data in other direction is also possible, but it has to be done by
the store, so the implementation will be
Vinay,
Near cache on client is created separately using Ignite.createNearCache() or
Ignite.getOrCreateNearCache() method.
The configuration you're referring to creates near caches on server nodes
(next to the instances of distributed cache). This supports rare use case
when all data is accessed
Hi,
Window functions are not supported, but it looks like you're simply querying
maximum balance for each group. Am I missing something?
In this case you can execute something like this:
SELECT yyyappid, max(balance) FROM ... GROUP BY yyyappid
Will this work for you?
-Val
--
View this
Hi Dharam,
Can you please properly subscribe to the mailing list so that the community
can receive email notifications? Here is the instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
dharamthacker wrote
> I am new to ignite and POCing
You should not use try-with-resources block, because it implicitly closes the
streamer at the end, but you want to keep it opened. Simply remove the 'try
(...) {}' from the code and it should work.
-Val
--
View this message in context:
1 - 100 of 1797 matches
Mail list logo