January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8026) HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager

by jaikiran pai (JIRA)

HornetQ group-address and port configurations for discovery and broadcast groups should use ServiceBindingManager ------------------------------------------------------------------------------------------------------------------ Key: JBAS-8026 URL: https://jira.jboss.org/jira/browse/JBAS-8026 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS (HornetQ) Reporter: jaikiran pai Assignee: Clebert Suconic Fix For: 6.0.0.M4 Currently the discovery group and the broadcast group in hornetq-configuration.xml in AS are used for configuring the group-address and the port: <broadcast-groups> <broadcast-group name="bg-group1"> <group-address>231.7.7.7</group-address> <group-port>9876</group-port> <broadcast-period>5000</broadcast-period> <connector-ref connector-name="netty"/> </broadcast-group> </broadcast-groups> <discovery-groups> <discovery-group name="dg-group1"> <group-address>231.7.7.7</group-address> <group-port>9876</group-port> <refresh-timeout>10000</refresh-timeout> </discovery-group> </discovery-group> The ServiceBindingManager http://community.jboss.org/wiki/AS5ServiceBindingManager should instead be used for these properties. -- 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

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-8156) When cookie is set and retrieved, the value get surronded by double quotes

by Adeeb Abdulkarim (JIRA)

When cookie is set and retrieved, the value get surronded by double quotes -------------------------------------------------------------------------- Key: JBAS-8156 URL: https://jira.jboss.org/browse/JBAS-8156 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: Linux 2.6.18-92.el5xen #1 SMP Tue Apr 29 13:31:30 EDT 2008 x86_64 JBOSS Version: jboss-eap-4.3.0.GA CP06 Reporter: Adeeb Abdulkarim When cookie is set and then get the value get surronded by double quotes. E.g. Cookie appCookie = new Cookie("applpath", "/MyAppRoot"); resp.addCookie(appCookie); Accessing at client side (JS) function getColorCookie(sName) { var aCookie = document.cookie.split("; "); for (var i=0; i < aCookie.length; i++) { var aCrumb = aCookie[i].split("="); if (sName == aCrumb[0]) return unescape(aCrumb[1]); } return null; } Expected Result: applpath = /MyAppRoot Actual Result: applpath = "/MyAppRoot" -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8017) Complete Site and Documentation for AS6 Web Container

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 Web Container ----------------------------------------------------- Key: JBAS-8017 URL: https://jira.jboss.org/jira/browse/JBAS-8017 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert -- 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

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8269) Cannot bundle newest derby with app

by Matthew Schmidt (JIRA)

Cannot bundle newest derby with app ----------------------------------- Key: JBAS-8269 URL: https://jira.jboss.org/browse/JBAS-8269 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: 6.0.0.M4 Reporter: Matthew Schmidt Assignee: Scott M Stark When bundling derby.jar into our application, we get the following error under 6.0.0.M4. It appears to be looking for a method signature that doesn't exist in the main classloader: 06:59:18,314 WARN [org.jboss.deployment.MainDeployer] Failed to deploy: file:/Users/matt/Projects/qato/deploy/qato.war/: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfs:///Users/matt/Projects/qato/deploy/qato.war/ -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///Users/matt/Projects/qato/deploy/qato.war/ DEPLOYMENTS IN ERROR: Deployment "vfs:///Users/matt/Projects/qato/deploy/qato.war/" is in error due to the following reason(s): java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.derby.jdbc.EmbedXAConnection.getXAResource()Ljavax/transaction/xa/XAResource;" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, org/apache/derby/jdbc/EmbedXAConnection, and the class loader (instance of <bootloader>) for interface javax/sql/XAConnection have different Class objects for the type javax/transaction/xa/XAResource used in the signature at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370) [:2.2.0.Alpha6] at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316) [:2.2.0.Alpha6] at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.Alpha6] at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:957) [:2.2.0.Alpha6] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:373) [:6.0.0.20100721-M4] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_20] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_20] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_20] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.Beta5] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.Beta5] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.Beta5] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.Beta5] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.Beta5] at org.jboss.system.server.jmx.MBeanServerWrapper.invoke(MBeanServerWrapper.java:138) [:6.0.0.20100721-M4 (Build SVNTag:JBoss_6.0.0.20100721-M4 date: 20100723)] at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) [:1.6.0_20] at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) [:1.6.0_20] at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) [:1.6.0_20] at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1360) [:1.6.0_20] at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) [:1.6.0_20] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_20] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_20] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_20] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) [:1.6.0_20] at sun.rmi.transport.Transport$1.run(Transport.java:159) [:1.6.0_20] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_20] at sun.rmi.transport.Transport.serviceCall(Transport.java:155) [:1.6.0_20] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) [:1.6.0_20] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) [:1.6.0_20] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20] at java.lang.Thread.run(Thread.java:637) [:1.6.0_20] or -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8020) Complete Site and Documentation for AS6 Weld

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 Weld -------------------------------------------- Key: JBAS-8020 URL: https://jira.jboss.org/jira/browse/JBAS-8020 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert -- 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

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-8656) TimerService broken in AS600CR1

by Vitaliy Abramov (JIRA)

TimerService broken in AS600CR1 ------------------------------- Key: JBAS-8656 URL: https://jira.jboss.org/browse/JBAS-8656 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Scheduling/Timers Affects Versions: 6.0.0.CR1 Environment: Java 1.6_20 Windows, Linux Reporter: Vitaliy Abramov Assignee: Dimitris Andreadis TimerService started by Schedule annotation not working correctly. In 6.0.0.M5 everything works as expected, in 6.0.0.CR1 timer callback called five times in a row every minute. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
12
0 / 0

[JBoss JIRA] Created: (JBAS-8114) Automatically set EJB timeout greater than session timeout if CDI is enabled

by Shane Bryzak (JIRA)

Automatically set EJB timeout greater than session timeout if CDI is enabled ---------------------------------------------------------------------------- Key: JBAS-8114 URL: https://jira.jboss.org/browse/JBAS-8114 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.M3 Reporter: Shane Bryzak Assignee: Pete Muir The EJB timeout (for SFSBs) should automatically be set to be longer than the session timeout, if CDI/Weld is enabled . Otherwise we can get exceptions such as the following, if a SFSB times out before the session ends: javax.ejb.NoSuchEJBException: Could not find stateful bean: 3j001-kry0ga-gaj04tmw-1-gal0kea7-ek org.jboss.ejb3.cache.simple.SimpleStatefulCache.get(SimpleStatefulCache.java:479) org.jboss.ejb3.cache.simple.SimpleStatefulCache.get(SimpleStatefulCache.java:430) org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:59) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:193) org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:109) org.jboss.ejb3.nointerface.impl.invocationhandler.NoInterfaceViewInvocationHandler.invoke(NoInterfaceViewInvocationHandler.java:148) org.jboss.ejb3.proxy.javassist.JavassistInvocationHandlerAdapter.invoke(JavassistInvocationHandlerAdapter.java:71) org.jboss.weld.examples.pastecode.session.History_$$_javassist_737.search(History_$$_javassist_737.java) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:304) org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:298) org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127) org.jboss.weld.util.CleanableMethodHandler.invoke(CleanableMethodHandler.java:43) org.jboss.weld.examples.pastecode.session.History_$$_javassist_724.search(History_$$_javassist_724.java) sun.reflect.GeneratedMethodAccessor2070.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:304) org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:298) org.jboss.weld.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:113) org.jboss.weld.util.CleanableMethodHandler.invoke(CleanableMethodHandler.java:43) org.jboss.weld.examples.pastecode.session.History_$$_javassist_735.search(History_$$_javassist_735.java) sun.reflect.GeneratedMethodAccessor2069.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.el.parser.AstValue.invoke(AstValue.java:196) org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:72) org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:72) com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:98) com.sun.faces.facelets.tag.jsf.core.DeclarativeSystemEventListener.processEvent(EventHandler.java:118) javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2345) javax.faces.event.SystemEvent.processListener(SystemEvent.java:102) com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:1993) com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:1941) com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:285) com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:243) org.jboss.weld.integration.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:336) com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:114) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68) org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:164) org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141) org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:417) -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-8476) Embed tattletale to help diagnose classpath/classloading issues

by Baptiste MATHUS (JIRA)

Embed tattletale to help diagnose classpath/classloading issues --------------------------------------------------------------- Key: JBAS-8476 URL: https://jira.jboss.org/browse/JBAS-8476 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.1.0.GA Reporter: Baptiste MATHUS Assignee: Scott Stark Trying to migrate a working tomcat application to JBoss AS, I'm having a hard-time finding where the classes come/get loaded from. I just discovered JBAS-3180 and thought it would be great to have a standard servlet or something that would help have insights about some deployed webapp. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8715) classloader leak test failure in IsolatedEjb3EarClassloaderLeakTestCase

by Scott Marlow (JIRA)

classloader leak test failure in IsolatedEjb3EarClassloaderLeakTestCase ----------------------------------------------------------------------- Key: JBAS-8715 URL: https://jira.jboss.org/browse/JBAS-8715 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott Marlow Assignee: Andrew Rubinger Fix For: 6.0.0.Final Example of failure is on https://hudson.jboss.org/hudson/job/JBoss-AS-6.0.x-classloader-leak-x86_6... To reproduce with AS6 build: 1. Setup virtual ip addresses (for the clustering part of the test) su /sbin/ip addr add 172.19.1.2/32 dev eth0 /sbin/ip addr add 172.19.1.3/32 dev eth0 2. build as and cd into testsuite folder ./build.sh ./build.sh tests-all-classloader-leak -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8099) Lazy-load JSF configurations in JSF Deployer

by Stan Silvert (JIRA)

Lazy-load JSF configurations in JSF Deployer -------------------------------------------- Key: JBAS-8099 URL: https://jira.jboss.org/browse/JBAS-8099 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JSF Affects Versions: 6.0.0.M4 Reporter: Stan Silvert Assignee: Stan Silvert Priority: Minor The JSF configurations/implementations are loaded at startup by the JSF Deployer. This could improve startup a tiny bit if each were loaded on demand. -- 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

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 January 2011