October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3834) i18n of jmx-console

by Ryusuke Kajiyama (JIRA)

i18n of jmx-console ------------------- Key: JBAS-3834 URL: http://jira.jboss.com/jira/browse/JBAS-3834 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.4.GA Environment: Any operating system with multiple language such as MS932 (Japanese) Reporter: Ryusuke Kajiyama We found that there are difference in screen-displayed multibyte characters on using Internet Explorer and Firefox. When using MS932, with IE, characters are returned same as posted, however with Firefox, characters are url-escaped like %xx. Our guess is that html of jmx-console does not have charset and there are no functions to handle encoding request parameter. It could be fixed if there were some filter action something like distinguish character set of posted data, and add <meta> tag into html or set Content-Type. -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1278) DSL Parser "eval"

by M H (JIRA)

DSL Parser "eval" ----------------- Key: JBRULES-1278 URL: http://jira.jboss.com/jira/browse/JBRULES-1278 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1 Reporter: M H Assigned To: Mark Proctor Priority: Blocker rule "PatternTest" when $pli:Item( title matches "^Test\s*") then # end this one compiles but on Runtime it ends in an Exception when title looks for example like this "BlaBla (Test)". as workaround i thought about using the next part, but rule "PatternTest" when $pli:Item( eval(title.matches("^Test\s*")) ) then # end it resolves into, also it shouldn't (because title.matches() is Java Code a shouldn't be parsed by the DSL Parser itself): SyntaxfehlerRule Compilation error : [Rule name=OnlineStreaming Start, agendaGroup=MAIN, salience=100, no-loop=true] com/p7s1/swi/phoenix/n24/Rule_OnlineStreaming_Start_0.java (19:923) : Invalid escape sequence (valid ones are \b \t \n \f \r \" \' \\ ) -- 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

15 years, 8 months

3
14
0 / 0

[JBoss JIRA] Created: (JBAS-4154) Get the server to run under a security manager

by Scott M Stark (JIRA)

Get the server to run under a security manager ---------------------------------------------- Key: JBAS-4154 URL: http://jira.jboss.com/jira/browse/JBAS-4154 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Scott M Stark Assigned To: Scott M Stark The testsuite tests-security-manager target was failing due to the aop layer not creating classes with correct ProtectionDomains. This is fixed in (JBAOP-368). The next problem is that the server.policy needs to use vfsfile urls for the permission assignments. However, because these are URLs and not URIs, there has to be a URL handler available when the policy is read at bootstrap. Currently a policy entry like: grant codeBase "vfsfile:${jboss.home.dir}/lib/-" { permission java.security.AllPermission; }; fails because the jboss vfsfile URL handler is unknown: policy: Adding policy entry: policy: signedBy null policy: codeBase vfsfile:/tmp/trunk/build/output/jboss-5.0.0.Beta2/lib/- java.security.policy: error adding Entry: java.net.MalformedURLException: unknown protocol: vfsfile policy: -- 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

15 years, 8 months

4
17
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-148) Implement ScopedKernel

by Ales Justin (JIRA)

Implement ScopedKernel ---------------------- Key: JBMICROCONT-148 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-148 Project: JBoss MicroContainer Issue Type: Feature Request Components: Kernel Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC-2.0.0.GA Implement support for scoped deployments on top of scoped metadata. -- 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

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3765) AOP-based version of RetryInterceptor

by Brian Stansberry (JIRA)

AOP-based version of RetryInterceptor ------------------------------------- Key: JBAS-3765 URL: http://jira.jboss.com/jira/browse/JBAS-3765 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB2, EJB3, Remoting Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta The (Single)RetryInterceptor only works for EJB 2. Need to: 1) Create a version that uses the AOP interceptor model rather than org.jboss.invocation. 2) Ensure all proxy factories bind an InvokerLocator in JNDI and include in the proxy metadata the location of the binding. 3) Add the interceptor to the various interceptor stack configs. -- 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

15 years, 8 months

8
13
0 / 0

[JBoss JIRA] Created: (JBWEB-91) AJP implementation broken : ajp_connection_tcp_get_message::jk_ajp_common.c (981): wrong message

by Michal Borowiecki (JIRA)

AJP implementation broken : ajp_connection_tcp_get_message::jk_ajp_common.c (981): wrong message ------------------------------------------------------------------------------------------------ Key: JBWEB-91 URL: http://jira.jboss.com/jira/browse/JBWEB-91 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Environment: Linux 2.6.20-gentoo-r8 #1 SMP jbossweb-1.0.1.GA-linux2-i686.tar.gz sun-jdk-1.5.0.11 and sun-jdk-1.6.0.01 Apache: Apache/1.3.37 JK: mod_jk/1.2.18 Reporter: Michal Borowiecki Assigned To: Mladen Turk Fix For: JBoss Web Server 1.0.1 GA When response is greater than abount 225 kB and error is detected on Apache side in mod_jK: last normal log entry: [Wed Aug 29 11:24:57 2007] [97923:0000] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1037): 03f0 75 6C 74 3D 64 6F 63 75 6D 65 6E 74 2E 66 6F 72 - ult=document.for then error: [Wed Aug 29 11:24:57 2007] [97923:0000] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (981): wrong message format 0x743d from 192.168.0.34:8139 [Wed Aug 29 11:24:57 2007] [97923:0000] [error] ajp_get_reply::jk_ajp_common.c (1556): Tomcat is down or network problems. Part of the response has already been sent to the client [Wed Aug 29 11:24:57 2007] [97923:0000] [info] ajp_service::jk_ajp_common.c (1751): Receiving from tomcat failed, recoverable operation attempt=1 [Wed Aug 29 11:24:57 2007] [97923:0000] [info] ajp_service::jk_ajp_common.c (1783): Sending request to tomcat failed, recoverable operation attempt=2 [Wed Aug 29 11:24:57 2007] [97923:0000] [error] ajp_service::jk_ajp_common.c (1794): Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=server3 failed At another time the error message said: [Wed Aug 29 11:02:26 2007] [84055:0000] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (981): wrong message format 0x2263 or [Wed Aug 29 11:02:32 2007] [34375:0000] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (981): wrong message format 0x656c JBoss logs show a normal response sent: [29/Aug/2007:11:02:24 +0200] "GET /is/transactions.jsf HTTP/1.1" 200 373004 [29/Aug/2007:11:02:30 +0200] "POST /is/transactions.jsf HTTP/1.1" 200 372579 Apache logs show an error: [29/Aug/2007:11:02:26 +0200] "GET /is/transactions.jsf HTTP/1.1" 503 265 [29/Aug/2007:11:02:32 +0200] "POST /is/transactions.jsf HTTP/1.1" 503 265 The same Apache/mod_jk configuration works fine talking to JBoss-4.0.5.GA so the bug must be jboss web server specific. -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-757) getMessageContext Not Implemented

by ppc (JIRA)

getMessageContext Not Implemented --------------------------------- Key: EJBTHREE-757 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: ppc jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. Form this version with the new JbossWS stack as far i know i not anymore possible to retreive a SOAP attachement . With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :( -- 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

15 years, 8 months

4
17
0 / 0

[JBoss JIRA] Created: (EJBTHREE-989) Can't inject resources of type URL

by Carlo de Wolf (JIRA)

Can't inject resources of type URL ---------------------------------- Key: EJBTHREE-989 URL: http://jira.jboss.com/jira/browse/EJBTHREE-989 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1219) Using DSL and accumulate in Drools BRMS leads to unexpected results

by Cristiano Giuffrida (JIRA)

Using DSL and accumulate in Drools BRMS leads to unexpected results ------------------------------------------------------------------- Key: JBRULES-1219 URL: http://jira.jboss.com/jira/browse/JBRULES-1219 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1 Environment: HP-UX java version "1.5.0.05" Reporter: Cristiano Giuffrida Assigned To: Mark Proctor Details of this problem are described in the following thread: http://www.nabble.com/Using-DSL-and-accumulate-in-Drools-BRMS-leads-to-un... -- 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

15 years, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1056) Redo NestedBeanUnitTestCase.testConsistentPassivatedState()

by Brian Stansberry (JIRA)

Redo NestedBeanUnitTestCase.testConsistentPassivatedState() ----------------------------------------------------------- Key: EJBTHREE-1056 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1056 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor NestedBeanUnitTestCase.testConsistentPassivatedState() is a pretty weak test for the EJBTHREE-1053 condition; when the parent issue is fixed, replace this test with something better. -- 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

15 years, 9 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007