February 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2567) Knowledge Agent needs drools-compiler dependency even if it is only working with compiled resources.

by Esteban Aliverti (JIRA)

Knowledge Agent needs drools-compiler dependency even if it is only working with compiled resources. ---------------------------------------------------------------------------------------------------- Key: JBRULES-2567 URL: https://jira.jboss.org/browse/JBRULES-2567 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-core (expert) Affects Versions: 5.1.0.M2, 5.1.0.M1 Reporter: Esteban Aliverti Assignee: Esteban Aliverti Fix For: 5.1.0.CR1 The Knowledge Agent is creating a kbuilder even if all the monitored resources are of type PKG. This forces to have a dependency on drools-compiler. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2678) The current Drools-Spring does not provide User Name, Password, basicAuthentication attributes in kagent

by Kiran Phadatare (JIRA)

The current Drools-Spring does not provide User Name, Password, basicAuthentication attributes in kagent --------------------------------------------------------------------------------------------------------- Key: JBRULES-2678 URL: https://jira.jboss.org/browse/JBRULES-2678 Project: Drools Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 5.1.0.FINAL Environment: Drools Guvnor, KnowledgeAgent, Drools - Spring Configuration Reporter: Kiran Phadatare Assignee: Mark Proctor Priority: Optional When using a change-set and drools-spring config. for kagent beans to get pakage content from guvnor repository as follows : <drools:kagent kbase="knowledgeBase" id="kagent" new-instance="false"> <drools:resources> <drools:resource type="PKG" source="http://localhost:8080/drools- guvnor/org.drools.guvnor.Guvnor/package/org.mkcl.insync/LATEST" /> </drools:resources> </drools:kagent> this fails because the new drools guvnor requires authentication from v5.1.0Final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBLOGGING-13) Only copy log level config over when receiving a JMX notification of type "jboss.logging.log4j.reconfigure"

by David Lloyd (JIRA)

Only copy log level config over when receiving a JMX notification of type "jboss.logging.log4j.reconfigure" ----------------------------------------------------------------------------------------------------------- Key: JBLOGGING-13 URL: https://jira.jboss.org/jira/browse/JBLOGGING-13 Project: JBoss Logging Issue Type: Task Security Level: Public (Everyone can see) Components: jboss-logbridge Affects Versions: 1.0.0.CR2-jboss-logbridge Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.0.0.CR3-jboss-logbridge -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-1293) Mixture of logical names (host+number) and UUIDs appears in a view addresses

by Allen Zhao (JIRA)

Mixture of logical names (host+number) and UUIDs appears in a view addresses ---------------------------------------------------------------------------- Key: JGRP-1293 URL: https://issues.jboss.org/browse/JGRP-1293 Project: JGroups Issue Type: Bug Affects Versions: 2.11 Environment: Windows Reporter: Allen Zhao Assignee: Bela Ban We are using jGroups a lot in our applications. Mixture of logical names (host+number) and UUIDs appears in a view addresses some time when we restart some group members. At some point, the view for one member is [dev-zhaoa-48631|22] [dev-zhaoa-48631, dev-zhaoa-14374, dev-zhaoa-45685] but for another member, it is [dev-zhaoa-48631|23] [dev-zhaoa-48631, fb564aa3-5328-569b-ff3f-84de4a6323c3, d38da714-6217-b59f-e80c-7904b047b875, dev-zhaoa-50510] I tried to catch the exact scenario to reproduce this, but it is difficult when I try it on purpose. But this happens quite often. I'll try to add more information here. Thank you very much for look into the problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1434) 5.0.0CR1: EJB refs across EARs don't work

by Juergen Zimmermann (JIRA)

5.0.0CR1: EJB refs across EARs don't work ----------------------------------------- Key: EJBTHREE-1434 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1434 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 5.0.0.CR1 Environment: JBoss 5.0.0.CR1, JDK 6u10beta Reporter: Juergen Zimmermann I'm having 2 different EARs and stateless session beans of the 2nd EAR are referencing stateless session beans of the 1st ear. It worked fine with 4.2.2 I'll attach a stripped down testcase: * src.zip: source of projects for Eclipse w/ JBoss Tools * hska.ear.zip: exploded EAR 1 (and zipped for transferring) * testHska.ear.zip: exploded EAR 1 (and zipped for transferring) src.zip: * hska is the 1st EAR project * hskaEJB contains the ejb module for hska * testHska is the EAR project for the 2nd EAR * testHskaEJB is the ejb module for testHska and references a SLSB of hskaEJB * testHskaClient is an application client module for testHska using JUnit -- 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

13 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-7883) @Resource mail session injection, injects incrrect mail session

by Mark Lowe (JIRA)

@Resource mail session injection, injects incrrect mail session --------------------------------------------------------------- Key: JBAS-7883 URL: https://jira.jboss.org/jira/browse/JBAS-7883 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA, JBossAS-5.0.1.GA Environment: Linux 64 bit , sun JDK 1.6.0.14 Reporter: Mark Lowe Please forgive me if I've posted this to the incorrect component or failed to find an existing bug, I did look. I'm porting our applications from Jboss 4.2.3 and found the following problem injecting mail sessions in EJBs and Servlet components. I have several mails sessions configured. For example <mbean code="org.jboss.mail.MailService" name="jboss:service=MyMailServer1"> <attribute name="JNDIName">foo/MyMailServer1</attribute> <attribute name="User">myuser</attribute> <attribute name="Password">myuserpw</attribute> <attribute name="Configuration"> <configuration> </configuration> </attribute> <depends>jboss:service=Naming</depends> </mbean> The jndi tree is created and all is present and correct. @Resource(name="MyMailServer1",mappedName="foo/MyMailServer1") private Session session; Returns the default mail session (java:/Mail). When I removed the java:/Mail session jboss find the last session from the configuration and arbitrarily injects it. I also tested this placing another configuration after the java:/Mail config, and the result was that the session configured below (i.e. last) was referenced. In short to recreate the bug. Create 2 additional mail sessions in a *-service.xml file. Deploy a servlet, ejb or other component that supports @Resource. Attempt to inject one of the custom sessions (not java:/Mail using @Resource(mappedName="[jndi name]". I also attempted to force the issue using a resource-ref in jboss.xml matching the resource-ref-name with the @Resource(name=".") and using the jndi-name (in case the usage of mappedname as been changed since 4.2.3. ) With no result. Assuming this is a real bug, workarounds? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
19
0 / 0

[JBoss JIRA] Created: (JBREM-1273) Assure version compatibility with earlier versions of Remoting

by Ron Sigal (JIRA)

Assure version compatibility with earlier versions of Remoting -------------------------------------------------------------- Key: JBREM-1273 URL: https://issues.jboss.org/browse/JBREM-1273 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.4.SP1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1261) Prevent DOS attack on BisocketServerInvoker$SecondaryServerSocketThread

by Ron Sigal (JIRA)

Prevent DOS attack on BisocketServerInvoker$SecondaryServerSocketThread ----------------------------------------------------------------------- Key: JBREM-1261 URL: https://issues.jboss.org/browse/JBREM-1261 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3.SP3, 2.5.3.SP1 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.3.SP2, 2.2.3.SP4 >From the original bug report: Exploiting and thus confirming this vulnerability is extremely simple: Simply connect to the bisocket control connection (ie. "telnet <jboss-host> <control-connection-port>") without sending any data on the connection. As long as this connection is open, no clients can connect to the bisocket control port because the connections are not accepted at server side. The cause of this vulnerability is found in method org.jboss.remoting.transport.bisocket.BisocketServerInvoker$SecondaryServerSocketThread.run(), which contains the accept-loop for the bisocket control connection. After having accepted a connection, the accept loop thread reads from the newly created connection expecting the client to send an action code and a listener id. If the client sends nothing, the accept loop thread will block in the read call, causing no other connections to be accepted. To fix, the accept loop thread should not do the read on the new connection. Instead it should start a new thread that does the read -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2577) License headers are missing for most of the files

by Toni Rikkola (JIRA)

License headers are missing for most of the files ------------------------------------------------- Key: JBRULES-2577 URL: https://jira.jboss.org/browse/JBRULES-2577 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: All Reporter: Toni Rikkola Assignee: Toni Rikkola Priority: Minor Fix For: 5.1.0.CR1 Add the headers. Add the maven task to trunk. Add documentation to the release wiki. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (JBRULES-2855) Dos2unix all source files (except .bat)

by Geoffrey De Smet (JIRA)

Dos2unix all source files (except .bat) --------------------------------------- Key: JBRULES-2855 URL: https://issues.jboss.org/browse/JBRULES-2855 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor A couple months back we decided to use line ending \n and encoding UTF-8 for all files, except for property files which don't use UTF-8. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2011