[JBoss JIRA] Commented: (JBAS-4178) RunAsListener uses unsupported implementation
by Remy Maucherat (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-4178?page=comments#action_12356993 ]
Remy Maucherat commented on JBAS-4178:
--------------------------------------
I posted an email on this earlier this month, so I think this issue should be closed:
I looked at what it was used for (supporting run-as when running the servlet's init and destroy methods), and there's no easy way to do it without this thing. I said it was unsupported since the impl of this capability hasn't changed since 4.0, I had forgotten it existed, and I am not aware of anyone else using it either. Since it works, I suppose it can be supported again :)
It is easy to disable usage of the listener in JBoss, BTW, and IMO it should be removed before performance testing (although the sync/clone is removed - which is good since the listener is there by default -, it will still generate tons of garbage objects which can't really be optimized away).
> RunAsListener uses unsupported implementation
> ---------------------------------------------
>
> Key: JBAS-4178
> URL: http://jira.jboss.com/jira/browse/JBAS-4178
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: JBossAS-4.0.5.GA
> Reporter: Ryan Campbell
> Assigned To: Anil Saldhana
> Priority: Critical
> Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3
>
>
> Class org.jboss.web.tomcat.security.RunAsListener is an implementation of InstanceListener interface used for establishment of run-as role for servlet init/destroy events. According to tomcat developers, InstanceListener interface is meant for debugging purposes only and is causing some performace degradations.
--
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, 3 months
[JBoss JIRA] Commented: (JBPORTAL-832) CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged
by Kirill Vodonosov (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-832?page=comments#action_12356981 ]
Kirill Vodonosov commented on JBPORTAL-832:
-------------------------------------------
Error in file \core-cms\src\main\org\jboss\portal\core\cms\ui\admin\CMSAdminPortlet.java
for JBoss Portal 2.6 beta 1 change:
-----------------------------------------------------------------------------------------------------------------------
from:
content.setBasePath(sFilePath + "/" + new Locale(sLanguage).getLanguage());
content.setBytes(sContent.getBytes());
file.setContent(new Locale(sLanguage), content);
-----------------------------------------------------------------------------------------------------------------------
to:
content.setBasePath(sFilePath + "/" + new Locale(sLanguage).getLanguage());
try {
content.setBytes(sContent.getBytes("UTF-8"));
}
catch (Exception e)
{
throw new PortletException(e);
}
file.setContent(new Locale(sLanguage), content);
> CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBPORTAL-832
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-832
> Project: JBoss Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Portal CMS
> Environment: jboss4.0.3sp1
> Reporter: Mike Khlu
> Assigned To: Sohil Shah
> Attachments: ??????? ? ???-??? ???????.PNG, issue-screenshot.GIF, jbossportali18nbug.GIF, russian-in-1251.txt, russian-in-utf8.html
>
>
> When I input ru-characters in the text area it has been puted into table in native encoding (cp1251) - !!! not UTF-8. But pages are sends in UTF-8, and it damaged.
> I think that I have to encode the request in UTF-8 ???
> ---------------------------------------------
> create file.html in Ru (in cms admin) with this text
> abc???
> then look at the last record of JBP_CMS_VERSION_BINVAL
> (six bytes in BINVAL_DATA field):
> 61 62 63 e0 e1 e2
> it is cp1251 encoding !!!!
> why this text non unicoded ???
> then when i retrive it i have - 'abc???'
> I think that problem isn't in ContentTypeInterceptor because it succefully
> sets UTF8, because localized resources seems right (in russian).
> may be it is need to store text in CLobs insdead blobs ??? (a use Derby) or customize Jackrabbit ???
> -----------------------------------------------------------
> but when I upload file on UTF-8 with russian characters - all correct.
> I think that cms saves the content in one byte encoding (cp1250 or same).
--
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, 3 months
[JBoss JIRA] Updated: (JBAS-3071) MemoryLeak (redeployment) on EJB3
by Ortwin Glück (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3071?page=all ]
Ortwin Glück updated JBAS-3071:
-------------------------------
Attachment: leaks.txt
I used jmap to get a histogram after undeployment of a large application. Here are my results. Maybe they are helpful.
JBossAS-4.0.4, EJB-3RC8, jdk-1.6, WinXP.
> MemoryLeak (redeployment) on EJB3
> ---------------------------------
>
> Key: JBAS-3071
> URL: http://jira.jboss.com/jira/browse/JBAS-3071
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB3
> Affects Versions: JBossAS-4.0.4.CR2
> Reporter: Clebert Suconic
> Assigned To: Carlo de Wolf
> Priority: Critical
> Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.0.GA
>
> Attachments: leaks.txt
>
>
> This might be caused by JBAS-3016:
> But I'm seeing this strong reference:
> org.jboss.mx.loading.UnifiedClassLoader3@33411906
> !--- org.jboss.ejb3.stateless.StatelessContainer@29610827
> We should make sure EJB3 packages are not leaking.
--
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, 3 months
[JBoss JIRA] Created: (JBRULES-746) NPE when dumping XML
by Edson Tirelli (JIRA)
NPE when dumping XML
--------------------
Key: JBRULES-746
URL: http://jira.jboss.com/jira/browse/JBRULES-746
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.1-m1
Reporter: Edson Tirelli
Assigned To: Edson Tirelli
Fix For: 3.1-m2
REPORTED BY SANJAY SINGH
---------------------------------------------
What is wrong with this drl file ? When i try to create a xml out of it .. it keeps on failing on me .. while testing things out the rule works just fine .. its just the XmlDumper class which throws exception (InvocationTarget) .. Anybody else tried to generate xmls from drl files .. there are not many examples for the latest syntax of XML so i thought to create the DRL's first and then generate XML's off them .. but a very basic Drl failing is just killing my enthusiasm to go on with drools ..
DRL
package com.walmart.itemfile.item.rules
import com.walmart.itemfile.item.vo.ItemVo;
import com.walmart.itemfile.item.dao.ItemDao;
import com.walmart.itemfile.item.dao.ItemValidationDao;
import java.lang.String;
global com.walmart.itemfile.item.dao.ItemValidationDao itemValidationDao;
global com.walmart.itemfile.rules.ValidationErrorMap errors;
rule "Item status sode cannot be null"
when
item : ItemVo(itemStatusCode == null)
then
errors.addValidationError("nullItemStatusCode","Item Status Code is null");
System.out.println("Item Status Code is " + item.getItemStatusCode());
end
JAVA
DrlParser parser = new DrlParser();
final PackageDescr pkgOriginal = parser.parse( new InputStreamReader( getClass().getResourceAsStream( "testRules.drl" ) ) );
final XmlDumper dumper = new XmlDumper();
final String result = dumper.dump( pkgOriginal );
EXCEPTION
...
Caused by: java.lang.NullPointerException
at org.drools.xml.XmlDumper.replaceIllegalChars(XmlDumper.java:309)
at org.drools.xml.XmlDumper.visitLiteralRestrictionDescr(XmlDumper.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at org.drools.util.ReflectiveVisitor.visit(ReflectiveVisitor.java:41)
at org.drools.xml.XmlDumper.processFieldConstraint(XmlDumper.java:216)
at org.drools.xml.XmlDumper.visitFieldConstraintDescr(XmlDumper.java:102)
...
--
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, 3 months
[JBoss JIRA] Commented: (JBPORTAL-467) Login page needs to use the theme of the requested portal
by Antoine Herzog (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-467?page=comments#action_12356936 ]
Antoine Herzog commented on JBPORTAL-467:
-----------------------------------------
The same for Internationalization
can't get i18n labels in the login page
the only way to do this know : put the locale in the server session, and retrieve it in the login page
i have not tried it yet... hope it will works...
> Login page needs to use the theme of the requested portal
> ---------------------------------------------------------
>
> Key: JBPORTAL-467
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-467
> Project: JBoss Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Portal Core
> Affects Versions: 2.2 Final
> Reporter: Martin Holzner
>
> The Login.jsp that the web.xml's form login points to is in the portal-server.war.
> A call to this jsp does not go through any of the stacks in the portal core, and hence there is no portal or page object available to determine the currently set property for the selected theme. As a result, the Login jsp cannot be styled in synch with the rest of the portal.
> In the context of having a synchronized look and feel throughout a portal, the login needs to be able to select the same theme as the portal that was requested, so that the login fits seemlessly into the UI flow.
--
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, 3 months