April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9217) make undeploy cmd w/o args list the existing deployments

by Alexey Loubyansky (JIRA)

make undeploy cmd w/o args list the existing deployments -------------------------------------------------------- Key: JBAS-9217 URL: https://issues.jboss.org/browse/JBAS-9217 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 It would be useful to see the existing deployments listed before executing the command. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9218) Tab-completion for undeploy command argument

by Alexey Loubyansky (JIRA)

Tab-completion for undeploy command argument -------------------------------------------- Key: JBAS-9218 URL: https://issues.jboss.org/browse/JBAS-9218 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 It'd natural to support tab-completion for undeploy arguments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9215) delete key acts like a backspace on linux

by Alexey Loubyansky (JIRA)

delete key acts like a backspace on linux ----------------------------------------- Key: JBAS-9215 URL: https://issues.jboss.org/browse/JBAS-9215 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 The delete key on linux deletes the previous key instead of the next key. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8024) Weld deployments fail with "Error in zip file" message

by jaikiran pai (JIRA)

Weld deployments fail with "Error in zip file" message ------------------------------------------------------ Key: JBAS-8024 URL: https://jira.jboss.org/jira/browse/JBAS-8024 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.M3 Reporter: jaikiran pai More than one user has now reported that weld deployments which used to work in earlier AS versions (6.0.0.M2) have started failing in M3 with the following error: 18:51:45,567 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] : java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) [:1.6.0_17] at java.util.zip.ZipFile.<init>(ZipFile.java:114) [:1.6.0_17] at java.util.jar.JarFile.<init>(JarFile.java:133) [:1.6.0_17] at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:67) [:1.6.0_17] at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:214) [:1.6.0_17] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_17] at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:198) [:1.6.0_17] at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:50) [:1.6.0_17] at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:68) [:1.6.0_17] at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:104) [:1.6.0_17] at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:71) [:1.6.0_17] at com.sun.faces.config.AnnotationScanner.processClasspath(AnnotationScanner.java:290) [:2.0.2-FCS] at com.sun.faces.config.AnnotationScanner.getAnnotatedClasses(AnnotationScanner.java:215) [:2.0.2-FCS] at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:765) [:2.0.2-FCS] at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:736) [:2.0.2-FCS] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_17] at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_17] at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:329) [:2.0.2-FCS] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:223) [:2.0.2-FCS] at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:72) [:6.0.0.20100429-M3] Please see the referenced forum thread for the complete details -- 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, 3 months

9
15
0 / 0

[JBoss JIRA] Created: (JBRULES-2905) drools-spring: Should be able to work offline too. Include XSD in the jar and use the spring support to map the URL to the included XSD.

by Geoffrey De Smet (JIRA)

drools-spring: Should be able to work offline too. Include XSD in the jar and use the spring support to map the URL to the included XSD. ---------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2905 URL: https://issues.jboss.org/browse/JBRULES-2905 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Mark Proctor Currently using drools-spring means you need to be able to lay a connection to the Internet to download the xsd. Spring has support to avoid that. Do the following: 1) Define a good url for the XSD. The current one sux: https://github.com/droolsjbpm/droolsjbpm-integration/raw/master/drools-co... 2) Include spring properties files in the drools-spring jar to map that url to <good url> = /org/drools/container/spring/drools-spring-1.2.0.xsd If I recall correctly you need 2 properties files. 3) Actually upload the XSD to that good url too, so it's available for Eclipse/IntelliJ. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1856) JMS client hangs at FailoverValve2.close() when database hangs

by Takayoshi Kimura (JIRA)

JMS client hangs at FailoverValve2.close() when database hangs -------------------------------------------------------------- Key: JBMESSAGING-1856 URL: https://issues.jboss.org/browse/JBMESSAGING-1856 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.7.GA Reporter: Takayoshi Kimura The JMS client hangs at the following situation: * Clustered setup (JMS remote client -> clustered JMS servers -> database) * The client looks up ClusteredConnectionFactory, consume a message in transacted session and then calls session.rollback() * The database hangs for long time from here * The client calls conn.close(), no response from the server due to database hang * The client got socket timeout during database hang * The client hangs in FailoverValve2#close() JMS client socket timeout is 300sec, and PostgreSQL JDBC connection timeout is 15min or so by default. If the JMS server detects database failure and return response to the client before client timeout, the client doesn't hang. So the workaround is to set up failure detection for database at JDBC level (-ds.xml) properly to avoid long hang up. 1. Setup clustered JBoss Messaging service. JBoss EAP 5.1.0, PostgreSQL 2. Deploy testDistributedQueue-service.xml 3. Boot both nodes 4. Execute $ sh run-client.sh "server:1099" 5. Pull out the cable after the "Sleep 20 sec, pull out a network cable to the database server!" message 6. Wait 300 sec, remoting socket timeout 7. Get thread dump with kill -3 or jconsole, confirm it hangs You can use iptables command to emulate the #5: $ sudo /sbin/iptables -A INPUT -p tcp --dport 5432 -j DROP && sudo /sbin/iptables -A OUTPUT -p tcp --dport 5432 -j DROP 5432 is port number used by PostgreSQL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-9227) Convert DataSource entries to BinderService

by Jason Greene (JIRA)

Convert DataSource entries to BinderService ------------------------------------------- Key: JBAS-9227 URL: https://issues.jboss.org/browse/JBAS-9227 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jason Greene Assignee: Jason Greene Fix For: 7.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9228) Convert HQ jndi entries to BinderService

by Jason Greene (JIRA)

Convert HQ jndi entries to BinderService ---------------------------------------- Key: JBAS-9228 URL: https://issues.jboss.org/browse/JBAS-9228 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jason Greene Assignee: Jason Greene Fix For: 7.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9220) Implement JNDI and BindingService Strategy

by Shelly McGowan (JIRA)

Implement JNDI and BindingService Strategy ------------------------------------------ Key: JBAS-9220 URL: https://issues.jboss.org/browse/JBAS-9220 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming Reporter: Shelly McGowan Assignee: John Bailey Fix For: 7.0.0.Beta3 Beta3 is target to have a JNDI and binding strategy completely implemented. Everything which is bound in JNDI must have a BinderService. There are limitations currently which prevent lookups to java:comp/env such as datasources are only binding in java: -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-9118) Use a better colour scheme for code blocks in WebServices documentation pdf

by jaikiran pai (JIRA)

Use a better colour scheme for code blocks in WebServices documentation pdf --------------------------------------------------------------------------- Key: JBAS-9118 URL: https://issues.jboss.org/browse/JBAS-9118 Project: JBoss Application Server Issue Type: Enhancement Security Level: Public (Everyone can see) Components: z - Legacy - Documentation Affects Versions: 6.0.0.Final Reporter: jaikiran pai Assignee: Shelly McGowan Attachments: webservices-pdf.png The webservices pdf available here http://www.jboss.org/jbossas/docs/6-x/Component-Documentation/web-service... has a very bad colour scheme for code listing (attached image). A better colour scheme would help. The pdfs of other sections (like Security) look fine. P.S: It probably would be better to have a uniform colour scheme for all these pdfs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011