[JBoss JIRA] Moved: (JBAS-8276) Weld Extension vs. Tomcat deployer in JBoss 6
by Pete Muir (JIRA)
[ https://jira.jboss.org/browse/JBAS-8276?page=com.atlassian.jira.plugin.sy... ]
Pete Muir moved WELD-578 to JBAS-8276:
--------------------------------------
Project: JBoss Application Server (was: Weld)
Key: JBAS-8276 (was: WELD-578)
Affects Version/s: 6.0.0.M4
(was: 1.0.1.Final)
Security: Public
> Weld Extension vs. Tomcat deployer in JBoss 6
> ---------------------------------------------
>
> Key: JBAS-8276
> URL: https://jira.jboss.org/browse/JBAS-8276
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.M4
> Reporter: Heiko Braun
>
> When I deploy a web application that contains CDI beans to JBoss6-M4 I can see that bean deployment being executed two times. First the CDI deployer kicks in, then Tomcat deployer re-deploys the war archive, which causes a second execution of the extension:
> 12:20:34,082 INFO [org.jboss.weld.Version] WELD-000900 1.0.1 (SP4)
> 12:20:34,516 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Discovered Errai Service: class com.foo.server.HelloWorldService
> 12:20:34,564 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Register CDI component as MessageCallback: @Service @ApplicationScoped com.foo.server.HelloWorldService
> 12:20:34,583 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/funky-app
> 12:20:34,720 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager at java:comp/BeanManager
> 12:20:39,776 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] undeploy, ctxPath=/funky-app
> 12:20:40,246 INFO [org.jboss.weld.Version] WELD-000900 1.0.1 (SP4)
> 12:20:40,733 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Discovered Errai Service: class com.foo.server.HelloWorldService
> 12:20:40,844 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Register CDI component as MessageCallback: @Service @ApplicationScoped com.foo.server.HelloWorldService
> 12:20:40,856 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/funky-app
> 12:20:40,929 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager at java:comp/BeanManager
> Shouldn't it be the execution the extension tight to the tomcat deployer lifecycle? I.e. be dependent on it's meta data?
--
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
15 years, 1 month
[JBoss JIRA] Created: (JBCOMMON-82) FileUrlConnection can leak file descriptors
by Nikolay Tsankov (JIRA)
FileUrlConnection can leak file descriptors
-------------------------------------------
Key: JBCOMMON-82
URL: https://jira.jboss.org/jira/browse/JBCOMMON-82
Project: JBoss Common
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: common-core (2.x)
Environment: jdk 1.6
Reporter: Nikolay Tsankov
The following code demonstrates the problem, I would suggest storing the FileInputStream on first call of getInputStream() and return it on subsequent calls :
import java.io.File;
import java.io.FileOutputStream;
import java.io.InputStream;
import java.io.OutputStream;
import org.jboss.net.protocol.file.FileURLConnection;
public class FileUrlConnectionBug {
static File dir = new File("C:/test_file_url_connection");
public static void main(String[] args) throws Exception {
File tmp = makeFile("file.txt");
FileURLConnection connection = new FileURLConnection(tmp.toURI().toURL());
InputStream inputStream = connection.getInputStream();
//get the content, which is also an input stream
//calling this method causes getInputStream() to be called twice, see getContent()
//in java.net.URLConnection
InputStream contentInputStream = (InputStream) connection.getContent();
//close both streams
inputStream.close();
contentInputStream.close();
//file cannot be deleted, as there is an open file descriptor left
if (!tmp.delete()) {
System.err.println("Streams closed, but file cannot be deleted after getContent() is called");
}
//When getContent() is not called, everything is ok, file can be deleted
File tmpOk = makeFile("fileOk.txt");
FileURLConnection connectionOk = new FileURLConnection(tmpOk.toURI().toURL());
InputStream inputStreamOk = connectionOk.getInputStream();
inputStreamOk.close();
if (tmpOk.delete()) {
System.out.println("File deleted ok if getContent() is not called");
}
}
private static File makeFile(String name) throws Exception {
dir.mkdir();
File tmp = new File(dir, name);
OutputStream out = new FileOutputStream(tmp);
out.write(1);
out.close();
return tmp;
}
}
--
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
15 years, 1 month
[JBoss JIRA] Created: (JBRULES-1859) Error info not telling root cause
by Jaroslaw Kijanowski (JIRA)
Error info not telling root cause
---------------------------------
Key: JBRULES-1859
URL: https://jira.jboss.org/jira/browse/JBRULES-1859
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-guvnor
Affects Versions: 5.0.0.M3
Reporter: Jaroslaw Kijanowski
Assignee: Michael Neale
When I:
- create/copy a package and provide an already used name
- create/copy a snapshot and provide an already used name
- create/rename a status and provide an already used name
I get an error window displayed:
"The call failed on the server; see server log for details"
Users may have no access to the server log. Moreover these errors are not reflected in the Event.log
Finally, when I create a rule with a name that is already used, no information is displayed.
--
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
15 years, 1 month
[JBoss JIRA] Created: (JBRULES-2281) Testcases in Guvnor doesn't clean up correctly
by Bernd Ruecker (JIRA)
Testcases in Guvnor doesn't clean up correctly
----------------------------------------------
Key: JBRULES-2281
URL: https://jira.jboss.org/jira/browse/JBRULES-2281
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-guvnor
Reporter: Bernd Ruecker
Assignee: Mark Proctor
In the training we created a TooYoung rule (pretty easy: If a Driver is less than 18 a "Rejection" Fact is added to the working memory).
When we run a test case which expects a Rejection in the WorkingMemory afterwards and insert a driver with age 15 we get a green bar (good!).
If we now change the age to 60 and rerun it in the same window, the test keeps green. Not good! Seems like it doesn't remove the Rejection from the first run properly.
In the QA-Tab, when running all test cases, everything is fine.
--
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
15 years, 1 month