[JBoss JIRA] Created: (JBAS-3754) ExceptionSorter which marks all exceptions as fatal
by Brian Egge (JIRA)
ExceptionSorter which marks all exceptions as fatal
---------------------------------------------------
Key: JBAS-3754
URL: http://jira.jboss.com/jira/browse/JBAS-3754
Project: JBoss Application Server
Issue Type: Patch
Security Level: Public (Everyone can see)
Reporter: Brian Egge
Priority: Trivial
With Sybase we've had a few occasions where the exception sorter does not properly detect a failed connection. We've found for our production servers the safest thing is to recycle the connection on any error. This class would also be useful if your JDBC provider doesn't have an existing exception sorter.
----
package org.jboss.resource.adapter.jdbc;
import java.sql.SQLException;
/**
* Mark all exceptions as fatal.
*
* @author <a href="mailto:brianegge@users.sourceforge.net">Brian Egge</a>
*/
public class GenericExceptionSorter implements ExceptionSorter {
public boolean isExceptionFatal(SQLException e)
{
return true;
}
}
--
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
19 years, 6 months
[JBoss JIRA] Commented: (JBCACHE-485) Refactor the current Collection classes (list and set)
by Elias Ross (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-485?page=comments#action_12346565 ]
Elias Ross commented on JBCACHE-485:
------------------------------------
Yes, changes have been committed. I haven't been able to test the performance improvement, so I can't judge what it might be.
> Refactor the current Collection classes (list and set)
> ------------------------------------------------------
>
> Key: JBCACHE-485
> URL: http://jira.jboss.com/jira/browse/JBCACHE-485
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: PojoCache
> Reporter: Ben Wang
> Assigned To: Ben Wang
> Priority: Critical
> Fix For: PojoCache
>
> Attachments: icache.diff, set.diff
>
> Original Estimate: 4 weeks
> Remaining Estimate: 4 weeks
>
> Current implementation of Collection uses direct coupling to the cache store indices. E.g., we map them into subtree according to index ordering. This is not very desirable for performance reason. We should consider to provide a indirect mapping such that it is considered a graph instead of ordered tree.
> Or we should investigate whether it is possible to use a proxy operates on java.util.* classes such that we don't need to have our own implementation. The JDK lincense aside, ArrayList, e.g., uses an internal transient array. Is it possible to "aspectize" on that array only?
--
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
19 years, 6 months
[JBoss JIRA] Created: (JBRULES-544) getQueryResults behavior: return null
by Edson Tirelli (JIRA)
getQueryResults behavior: return null
--------------------------------------
Key: JBRULES-544
URL: http://jira.jboss.com/jira/browse/JBRULES-544
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Reteoo
Affects Versions: 3.0.4
Reporter: Edson Tirelli
Assigned To: Edson Tirelli
Fix For: 3.0.5, 3.1-m1
AS REPORTED BY GEOFFREY DE SMET:
---------------------------------------------------------
Thanks Edson for fixing the getQueryResults() method in JBRULES-539.
I found something interesting I'd like to bring under discussion:
WorkingMemory.getQueryResults() returns null when:
- no such query exists in the drl's. I would have expected an IllegalArgumentException, in the spirit of fail-fast,
but it's not that big a deal.
- but it also returns null when the query has 0 results.
I would have expected a QueryResults instance with .size() == 0.
It seems inconsistent with WorkingMemory.getObjects(X.class) which does return an empty list, instead of null.
[tested on the branch for 3.0.x for Rete]
What do you think?
--
With kind regards,
Geoffrey De Smet
--
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
19 years, 6 months
[JBoss JIRA] Created: (JBPORTAL-1085) CMS Export : Exception if empty folder or no file found for one language
by Antoine Herzog (JIRA)
CMS Export : Exception if empty folder or no file found for one language
------------------------------------------------------------------------
Key: JBPORTAL-1085
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1085
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.4 Final
Environment: JBPortal 2.4 / windows / CMS all stored in filesystem.
Reporter: Antoine Herzog
Assigned To: Roy Russo
when trying to export folder or files, there is sometimes this error :
14:03:38,140 ERROR [STDERR] java.lang.NullPointerException
14:03:38,140 ERROR [STDERR] at org.jboss.portal.cms.impl.jcr.command.GetArchiveCommand.zipFiles(GetArchiveCommand.java:112)
14:03:38,140 ERROR [STDERR] at org.jboss.portal.cms.impl.jcr.command.GetArchiveCommand.execute(GetArchiveCommand.java:72)
14:03:38,140 ERROR [STDERR] at org.jboss.portal.cms.impl.jcr.JCRCommand.dispatch(JCRCommand.java:61)
14:03:38,140 ERROR [STDERR] at org.jboss.portal.cms.impl.jcr.JCRCMS.execute(JCRCMS.java:436)
sometimes is :
- when asking to export a folder and there is some sub folders with no files in it (no file for the asked language)
- when asking to export a file that exist in language A but you ask export for language B
in the code of GetArchiveCommand.java :
private ZipOutputStream zipFiles(String sPath, ZipOutputStream zos)
{
....
JCRCommand fileList = (JCRCommand) this.mContext.getCommandFactory().createFileGetCommand(node.getPath(), new Locale(this.msLanguage));
File childFile = (File) this.mContext.execute(fileList);
ZipEntry entry = new ZipEntry(this.rootFolderName + node.getPath());
zos.putNextEntry(entry);
Content content = childFile.getContent();
...
line "112" is Content content = childFile.getContent();
childFile is null when the file was not found for the language.
It should be checked before use and do nothing if the file is not found.
(optional log ?)
enhancement : may be propose the export feature to take the default language file instead (a check box in the portal CMS management screen), so some exported site could be build with always a page shown (like in CMS Portlet).
--
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
19 years, 6 months