November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBVFS-160) FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows

by James Livingston (JIRA)

FileSystemContext.getFileURI returns wrong URI for UNC paths on Windows ----------------------------------------------------------------------- Key: JBVFS-160 URL: https://jira.jboss.org/browse/JBVFS-160 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.3.SP1 Environment: Windows Reporter: James Livingston Assignee: John Bailey Attachments: UncPathTest.java When passed a File for something with a UNC path (e.g. \\127.0.0.1\shared), FileSystemContext.getFileURI() return a URI like "file://127.0.0.1/shared" (which is what Windows itself uses) rather than "file:////127.0.0.1/shared" (which Java uses, and converts for OS calls). This will cause JBoss to fail to deploy things if they are located on an unmapped UNC location. I'm attaching a test case for this. To use it, you need to run it on a Windows system and have access to a something with a UNC path. The code as written expects there to be a SMB share called "shared" on the machine it is run on, but it can easily be change to point elsewhere. -- 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, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBVFS-165) VFSInputSource should not implement getCharacterStream

by Ales Justin (JIRA)

VFSInputSource should not implement getCharacterStream ------------------------------------------------------ Key: JBVFS-165 URL: https://jira.jboss.org/browse/JBVFS-165 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.0.CR5, 2.2.0.GA, 2.1.3.SP1, 2.1.3.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.1.3.SP2, 3.0.0.CR6 It's related to the encoding with which the XML is parsed. The encoding specified in <?xml version="1.0" encoding="UTF-8"?> is guaranteed to be used unless the user provides a java.io.Reader to the parser. Which is what happens in our case, the encoding specified in the XML is ignored and the system default one is used instead. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2487) NPE on line 69 of ConcurrentNodeMemories.java when calling JPAKnowledgeService.loadStatefulKnowledgeSession

by hoogenbj (JIRA)

NPE on line 69 of ConcurrentNodeMemories.java when calling JPAKnowledgeService.loadStatefulKnowledgeSession ----------------------------------------------------------------------------------------------------------- Key: JBRULES-2487 URL: https://jira.jboss.org/jira/browse/JBRULES-2487 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 4.2.3, Java 6 64-bit, Windows Vista 64-bit Reporter: hoogenbj Assignee: Mark Proctor Hi, I get a NullPointerException on line 69 of ConcurrentNodeMemories when calling JPAKnowledgeService.loadStatefulKnowledgeSession(...) in order to complete a work item using session.getWorkItemManager().completeWorkItem(...). Further investigation reveals that the objectType on line 332 of InputMarshaller refers to one of my objects that I passed as part of the second argument object when calling startProcess on the knowledge session that I got with JPAKnowledgeService.newStatefulKnowledgeSession. The objectTypeNode on line 333 of InputMarshaller is null which eventually causes the NPE in ConcurrentNodeMemories. This error does not occurr when starting and completing the whole process without retrieving the session from the database. Which seems to indicate that something is not persisted or correctly retrieved from the database. This is a serious problem for us. It means we have to find an alternative for Drools flow... -- 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, 5 months

6
9
0 / 0

[JBoss JIRA] Created: (JBRULES-2279) Cached ObjectTypeNodes are not restored when deserializing session

by Kris Verlaenen (JIRA)

Cached ObjectTypeNodes are not restored when deserializing session ------------------------------------------------------------------ Key: JBRULES-2279 URL: https://jira.jboss.org/jira/browse/JBRULES-2279 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Reporter: Kris Verlaenen Assignee: Edson Tirelli When the InputMarshaller is restoring facts in the working memory, it is using the ObjectTypeNodes of the rete tree to link the facts to their object type nodes. This currently fails if no ObjectTypeNode is present for that type (because the type is not used in a rule somewhere). This ObjectTypeNode should be recreated on request if necessary. -- 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, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBLOGGING-48) @Message should be declared @Documented

by Pete Muir (JIRA)

@Message should be declared @Documented --------------------------------------- Key: JBLOGGING-48 URL: https://jira.jboss.org/browse/JBLOGGING-48 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Pete Muir Assignee: David Lloyd This means the annotation and it's value will appear in the javadoc - obiviously useful for someone exploring the javadoc -- 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, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-8245) Fix org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase

by Brian Stansberry (JIRA)

Fix org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase -------------------------------------------------------------- Key: JBAS-8245 URL: https://jira.jboss.org/browse/JBAS-8245 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3, Test Suite Reporter: Brian Stansberry Fix For: 6.0.0.Final http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test... -- 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, 5 months

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files

by Emmanuel Bernard (JIRA)

Should we add a relax flag for people using out of order content inside elements of their XML files --------------------------------------------------------------------------------------------------- Key: JBAS-8268 URL: https://jira.jboss.org/browse/JBAS-8268 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.M4 Reporter: Emmanuel Bernard Assignee: Ales Justin Fix For: 6.0.0.Final It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the content in elements https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_... Would it make sense to have a flag to relax this rule? I am thinking of people with existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of use and less pain in support down the road). -- 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, 5 months

6
15
0 / 0

[JBoss JIRA] Created: (JBAS-8623) Update JBoss Threads to resolve unneeded CPU consumption

by Rico Neubauer (JIRA)

Update JBoss Threads to resolve unneeded CPU consumption -------------------------------------------------------- Key: JBAS-8623 URL: https://jira.jboss.org/browse/JBAS-8623 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Affects Versions: 6.0.0.M5 Reporter: Rico Neubauer JBTHR-17 fixes a major issue regarding CPU-usage. JBoss6 should update jboss-threads.jar to include that fix. -- 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, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-7218) ENC EM injection erroneously happens only once for web modules

by henk de boer (JIRA)

ENC EM injection erroneously happens only once for web modules -------------------------------------------------------------- Key: JBAS-7218 URL: https://jira.jboss.org/jira/browse/JBAS-7218 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA Environment: Observed problem on Mac OS X 10.5.7 and Debian Lenny 64 bits using JDK 6 Reporter: henk de boer Using a persistence-context-ref element in the web.xml of a web module, it appears that this causes an EntityManager instance to be injected only once into the ENC of this component. However, the EJB 3.0 spec states in section 16.2.1: "In general, lookups of objects in the JNDI java: namespace are required to return a new instance of the requested object every time." So the observed behavior seems to violate the spec. In addition, this is particularly troublesome since an EntityManager is explicitly not thread-safe. Using the same EM instance for simultaneous requests therefor doesn't work. Of course there are several other methods to obtain an EM reference, for instance binding an EM factory directly to JNDI and using that to obtain the reference. -- 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, 5 months

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-8348) ServerInfo needs a privileged block in getRootThread

by Anil Saldhana (JIRA)

ServerInfo needs a privileged block in getRootThread ---------------------------------------------------- Key: JBAS-8348 URL: https://jira.jboss.org/browse/JBAS-8348 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: System service Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 6.0.0.CR1, 7.0.0.M1 Port JBPAPP-4901 -- 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, 5 months

4
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2010