[jboss-user] [JBossCache] - Re: Replication doesn't work even with the sample code provi
Yes, it is aspectized - but not really :) The missing piece of the puzzle's looks to be located. Running the files via run.aop.example is functional. We are running this within Eclipse. There it is only semi-functional. We aspectized that source externally and are only referencing it's classes but I hypothesize the configuration is such that eclipse detects the .class change done outside of its control and is overwriting the aspectized class. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3977911#3977911 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977911 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Urgent- Socket error when adding object to DB using JDBC
We are not using transactions. Keeping the connections open and reusable was the intent; our information obtained earlier was that this scenario could not run at all and we needed to use a connection pool - however that does not suit our purpose as it would require significant alteration of the existing code OR use of a JNDI interface plus app server which is 100% against the scope of what we are trying to achieve. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3977548#3977548 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977548 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Urgent- Socket error when adding object to DB using JDBC
Agreed - however we are doing limited, time-bound feasibility studies of many competing combinatorials in order to see if we should make a recommendation for a specific direction. If this is the direction we take, a connection pool is mandatory - but likely would be the job of the container / app server we select. Thanks much for your assistance. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3977674#3977674 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977674 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Replication doesn't work even with the sample code provi
I can check - but can you explain why that would allow for communication after a remove/put and when the cache is created but not when it is altered? Does the aspectizing insert hooks within the get/sets for triggers? I apologize for asking what's probably an obvious question - I am learning as we proceed. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3977676#3977676 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977676 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Replication doesn't work even with the sample code provi
Thanks for the explanation - I do see the content within the jboss-aop.xml file, so this should be functional. 'myObject' is a contrived example for illustration - in fact, we are using code based upon the sample PojoCache which uses the Student, Person, Course, etc. Without the remove(), the replication does not occur. It must have a remove then a putObject. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3977697#3977697 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977697 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Urgent- Socket error when adding object to DB using JDBC
Adding the following additional change allowed for 10,000 consecutive updates
without error.
public NonManagedConnectionFactory(String url, String usr, String pwd)
{
this.url = url;
this.usr = usr;
this.pwd = pwd;
// what if I do a connection right off?
// BEGIN MODIFICATION: GJF - October 10, 2006
Connection con = getConnection();
try {
con.setAutoCommit(false);
} catch( SQLException e ){
// don't care
}
// END MODIFICATION
}
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3977285#3977285
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977285
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Urgent- Socket error when adding object to DB using JDBC
[EMAIL PROTECTED] wrote : What does this change actually do? It just seems to create a new connection and store it in threadlocal when the cacheloader is constructed, and that's it. | | So all it does is store a conn for a particular thread (the one that starts the cache). Other threads will still have to call getConnection() each time with a prepare(). | | Am I missing something, how does this result in being able to deal with capacity better? Correct, note that it also enforces setting autocommit off. I am only fleetingly familiar with this code base - however I cannot deny the evidence of the tests. I can (now) successfully run up to 50,000 stores without issue. This does in fact seem to address the issue. Perhaps you can identify the full reason as to why. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3977343#3977343 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977343 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossCache] - Re: Urgent- Socket error when adding object to DB using JDBC
After running a large number of tests, all of which repeatably and consistently
fail in and around approximately 1970-1990 cache updates, I have made the
following change.
After this change, the code then fails between 3900-4000 updates. It appears
that this is a minor defect or at least a suboptimization with the original
connection code.
The connection is stored into TLS during the
NonManagedConnectionFactory.prepare() method but it seems it is not put in
place after the null detect/create code within
NonManagedConnectionFactory.getConnection.
I urge you to examine this.
e.g.
...
public Connection getConnection()
{
Connection con = (Connection) connection.get();
if(con == null)
{
try
{
con = DriverManager.getConnection(url, usr, pwd);
// CODE ADDED HERE
connection.set(con);
// END CODE MODIFICATION
}
catch(SQLException e)
...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3976403#3976403
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3976403
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
