[JBoss JIRA] Created: (JBAS-4951) Retry debug message within UnifiedInvokerHAProxy.invoke() is misleading
by Galder Zamarreno (JIRA)
Retry debug message within UnifiedInvokerHAProxy.invoke() is misleading
-----------------------------------------------------------------------
Key: JBAS-4951
URL: http://jira.jboss.com/jira/browse/JBAS-4951
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: Brian Stansberry
Priority: Minor
UnifiedInvokerHAProxy.invoke():
...
failoverAuthorized = txContextAllowsFailover(invocation);
failoverCounter++;
invocation.setValue("FAILOVER_COUNTER", new Integer(failoverCounter), PayloadKey.AS_IS);
log.debug("Received GenericClusteringException where request was not completed. Will retry.");
continue;
...
The debug message before continue is misleading. The call will only be retried if the failover is authorised and
there're any targets available, otherwise it won't. The log message should be reworded.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (JBRULES-1250) Allow option to completely remove an asset from the repository
by Shahad Ahmed (JIRA)
Allow option to completely remove an asset from the repository
--------------------------------------------------------------
Key: JBRULES-1250
URL: http://jira.jboss.com/jira/browse/JBRULES-1250
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-brms
Affects Versions: 4.0.1
Reporter: Shahad Ahmed
Assigned To: Mark Proctor
If you use the archive feature to remove a rule or package from the BRMS it is not really seen as gone, as if you attempt to create a new rule or package with the same name as the archived rules or package then you get an error saying that the rule or package already exists (looking at the source code, the repository does not care if an item is archived or not, so it will always throw an error if an asset with an existing name is created).
I'm assuming this is the designed behaviour and not a bug (I've asked about this a couple of times on the user list and got no replies to the contrary).
However, it would be very useful to be able to remove a rule or package so that you can then recreate it (e.g by importing new versions from a drl file). At present, you have to laboriously rename the rules and packages you want to remove, so that when they are archived their names do not clash with the new versions of the rules and packages you want to import or recreate. Perhaps all that is involved in implementing this new remove feature is to just automatically rename the package and its rules before archiving it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (JBCACHE-1126) distribution example cannot complete (2.0 CR3)
by Aleksandar Kostadinov (JIRA)
distribution example cannot complete (2.0 CR3)
----------------------------------------------
Key: JBCACHE-1126
URL: http://jira.jboss.com/jira/browse/JBCACHE-1126
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.CR3
Environment: linux, jdk1.5.0_11
Reporter: Aleksandar Kostadinov
Assigned To: Manik Surtani
Fix For: 2.0.0.CR4
All examples fail - some can't compile, some at runtime. These that compile are running and seem to do something (at least eat some CPU cycles) but don't complete within few minutes and through exceptions so I consider them failing. Anything I'm doing wrong? btw I run with ant.
One problem with a known reason: on loadtime example path is specified with ";" between file names and not ":". To be portable to windows and unix ant path or location element has to be used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months