[JBoss JIRA] Created: (JBAS-7013) Seam Booking IOException with JSF2 Beta1 on AS5
by Stan Silvert (JIRA)
Seam Booking IOException with JSF2 Beta1 on AS5
-----------------------------------------------
Key: JBAS-7013
URL: https://jira.jboss.org/jira/browse/JBAS-7013
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JSF
Affects Versions: JBossAS-5.1.0.GA
Reporter: Stan Silvert
Assignee: Stan Silvert
I drop-in replaced JSF in AS5.1 with JSF 2 Beta 1.
With the Seam Booking demo, I bundle the old facelets and have:
<context-param>
<param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>
<param-value>true</param-value>
</context-param>
I get the stack trace below. Though it doesn't seem to affect the application, I need to figure out why this is happening.
13:38:34,463 ERROR [compiler] Error Loading Library: vfszip:/C:/jboss-5.1.0.GA/s
erver/default/deploy/jbossweb.sar/jsf-libs/jsf-impl.jar/META-INF/mojarra_ext.tag
lib.xml
java.io.IOException: Error parsing [vfszip:/C:/jboss-5.1.0.GA/server/default/dep
loy/jbossweb.sar/jsf-libs/jsf-impl.jar/META-INF/mojarra_ext.taglib.xml]:
at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.ja
va:410)
at com.sun.facelets.compiler.TagLibraryConfig.loadImplicit(TagLibraryCon
fig.java:431)
at com.sun.facelets.compiler.Compiler.initialize(Compiler.java:87)
at com.sun.facelets.compiler.Compiler.compile(Compiler.java:104)
at com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFace
letFactory.java:218)
at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFacelet
Factory.java:149)
at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFacelet
Factory.java:100)
at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java
:517)
at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.jav
a:567)
at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWra
pper.java:108)
at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.j
ava:216)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePha
se.java:124)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:103)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter
.java:83)
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter
.java:69)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter
.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter
.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter
.java:69)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter
.java:69)
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter
.java:69)
at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter
.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.proce
ss(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invok
e(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
onnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ss(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
7)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.xml.sax.SAXException: Error Handling [vfszip:/C:/jboss-5.1.0.GA/s
erver/default/deploy/jbossweb.sar/jsf-libs/jsf-impl.jar/META-INF/mojarra_ext.tag
lib.xml@42,29]
at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.error(TagLi
braryConfig.java:376)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified(Unkno
wn Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Sourc
e)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElemen
t(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanR
ootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Sour
ce)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:198)
at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.ja
va:407)
... 54 more
Caused by: org.xml.sax.SAXParseException: Document root element "facelet-taglib"
, must match DOCTYPE root "null".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Un
known Source)
... 73 more
--
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
[JBoss JIRA] Created: (JGRP-1280) Bind error messages should report incorrect IP addresses
by Manik Surtani (JIRA)
Bind error messages should report incorrect IP addresses
--------------------------------------------------------
Key: JGRP-1280
URL: https://issues.jboss.org/browse/JGRP-1280
Project: JGroups
Issue Type: Enhancement
Affects Versions: 2.11
Reporter: Manik Surtani
Assignee: Bela Ban
Not tried on 2.12, etc as yet. This is when you specify an incorrect bind address - one that is not available on the target host - and instead of reporting this, JGroups attempts to increase the port number and retry, eventually failing with a port being out of range. This can be very misleading as it leads you to debug conflicting ports, etc., when in fact the problem is a badly configured IP address.
This was reported a few years back on the forums, but I've still seen the issue on JGroups 2.11.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (EJBTHREE-2235) Ejb3AuthenticationInterceptorv2.invoke() throws IllegalStateException
by Juergen Zimmermann (JIRA)
Ejb3AuthenticationInterceptorv2.invoke() throws IllegalStateException
---------------------------------------------------------------------
Key: EJBTHREE-2235
URL: https://issues.jboss.org/browse/EJBTHREE-2235
Project: EJB 3.0
Issue Type: Bug
Components: ejb3_1, Security
Reporter: Juergen Zimmermann
My web app is based on JBossAS 6, EJB 3.1, Weld, and RichFaces 4. When I'm doing just a few mouse clicks and then do nothing (i.e. waiting for a timeout), then I get the following stacktrace. I upgraded to JBossAS 6.0.1-SNAPSHOT Hudson build 2296 to have Weld 1.1.0.
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/swe2]] Session event listener threw exception: java.lang.IllegalStateException: Local Call: Security Context is null
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:109) [:1.7.20]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) [:1.7.20]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) [:1.7.20]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.7.20]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) [:1.7.20]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:333) [:1.7.20]
at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:158) [:1.7.20]
at org.jboss.ejb3.nointerface.impl.invocationhandler.NoInterfaceViewInvocationHandler.invokeEndpoint(NoInterfaceViewInvocationHandler.java:143) [:]
at org.jboss.ejb3.nointerface.impl.invocationhandler.NoInterfaceViewInvocationHandler.access$000(NoInterfaceViewInvocationHandler.java:54) [:]
at org.jboss.ejb3.nointerface.impl.invocationhandler.NoInterfaceViewInvocationHandler$1.invoke(NoInterfaceViewInvocationHandler.java:103) [:]
at org.jboss.ejb3.sis.reflect.InterceptorInvocationHandler$1.proceed(InterceptorInvocationHandler.java:84) [:1.0.0-alpha-1]
at org.jboss.ejb3.sis.InterceptorAssembly$1.proceed(InterceptorAssembly.java:82) [:1.0.0-alpha-1]
at org.jboss.ejb3.nointerface.impl.async.AsyncClientInterceptor.invoke(AsyncClientInterceptor.java:119) [:]
at org.jboss.ejb3.sis.InterceptorAssembly$1.proceed(InterceptorAssembly.java:74) [:1.0.0-alpha-1]
at org.jboss.ejb3.nointerface.impl.invocationhandler.ObjectMethodsInterceptor.invoke(ObjectMethodsInterceptor.java:78) [:]
at org.jboss.ejb3.sis.InterceptorAssembly$1.proceed(InterceptorAssembly.java:74) [:1.0.0-alpha-1]
at org.jboss.ejb3.sis.InterceptorAssembly.invoke(InterceptorAssembly.java:90) [:1.0.0-alpha-1]
at org.jboss.ejb3.sis.reflect.InterceptorInvocationHandler.invoke(InterceptorInvocationHandler.java:110) [:1.0.0-alpha-1]
at org.jboss.ejb3.nointerface.impl.invocationhandler.NoInterfaceViewInvocationHandler.invoke(NoInterfaceViewInvocationHandler.java:115) [:]
at org.jboss.ejb3.proxy.javassist.JavassistInvocationHandlerAdapter.invoke(JavassistInvocationHandlerAdapter.java:71) [:1.0.0-alpha-1]
at de.swe2.bestellverwaltung.ui.Warenkorb_$$_javassist_18.toString(Warenkorb_$$_javassist_18.java) [:]
at sun.reflect.GeneratedMethodAccessor318.invoke(Unknown Source) [:1.6.0_23]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_23]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_23]
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) [:6.0.1-SNAPSHOT]
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) [:6.0.1-SNAPSHOT]
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) [:6.0.1-SNAPSHOT]
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) [:6.0.1-SNAPSHOT]
at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:126) [:6.0.1-SNAPSHOT]
at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:62) [:6.0.1-SNAPSHOT]
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) [:6.0.1-SNAPSHOT]
at de.swe2.bestellverwaltung.ui.org$jboss$weld$bean-jboss$classloader:id="vfs:$$-JBossAS-deploy$swe2$ear$swe2Web$war$"-SessionBean-Warenkorb_$$_WeldProxy.toString(org$jboss$weld$bean-jboss$classloader:id="vfs:$$-JBossAS-deploy$swe2$ear$swe2Web$war$"-SessionBean-Warenkorb_$$_WeldProxy.java) [:]
at java.lang.String.valueOf(String.java:2826) [:1.6.0_23]
at java.lang.StringBuilder.append(StringBuilder.java:115) [:1.6.0_23]
at org.jboss.weld.context.SerializableContextualInstanceImpl.toString(SerializableContextualInstanceImpl.java:67) [:6.0.1-SNAPSHOT]
at java.lang.String.valueOf(String.java:2826) [:1.6.0_23]
at java.lang.StringBuilder.append(StringBuilder.java:115) [:1.6.0_23]
at org.jboss.weld.context.beanstore.AttributeBeanStore.attach(AttributeBeanStore.java:120) [:6.0.1-SNAPSHOT]
at org.jboss.weld.context.AbstractBoundContext.activate(AbstractBoundContext.java:75) [:6.0.1-SNAPSHOT]
at org.jboss.weld.context.http.HttpSessionContextImpl.destroy(HttpSessionContextImpl.java:76) [:6.0.1-SNAPSHOT]
at org.jboss.weld.servlet.WeldListener.sessionDestroyed(WeldListener.java:97) [:6.0.1-SNAPSHOT]
at org.apache.catalina.session.StandardSession.expire(StandardSession.java:686) [:]
at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:581) [:]
at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:691) [:]
at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:676) [:]
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1314) [:]
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1599) [:]
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1608) [:]
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1608) [:]
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1588) [:]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (SECURITY-558) BaseCertLoginModule should also work with a truststore
by Marcus Moyses (JIRA)
BaseCertLoginModule should also work with a truststore
------------------------------------------------------
Key: SECURITY-558
URL: https://issues.jboss.org/browse/SECURITY-558
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: PicketBox_v4_0_alpha2, JBossSecurity_2.0.4.SP6
Reporter: Marcus Moyses
Assignee: Marcus Moyses
Fix For: JBossSecurity_2.0.4.SP7, PicketBox_v4_0_alpha3
BaseCertLoginModule uses a JaasSecurityDomain to validate the certificates. Currently it only uses the configured keystore for this. We need to allow the truststore to be checked by default and fallback to the keystore if the truststore is not configured.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (SECURITY-559) AdvancedLdapLoginModule: Service Principal is not constructed from java.naming.provider.url
by John Ruiz (JIRA)
AdvancedLdapLoginModule: Service Principal is not constructed from java.naming.provider.url
-------------------------------------------------------------------------------------------
Key: SECURITY-559
URL: https://issues.jboss.org/browse/SECURITY-559
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Negotiation
Affects Versions: Negotiation_2.0.3.GA
Environment: Windows Server 2008 R2 domain controller, Red Hat 5.5 Application Server (JBoss), Windows 7 Clients
Reporter: John Ruiz
Assignee: Darran Lofthouse
Priority: Critical
When using org.jboss.security.negotiation.AdvancedLdapLoginModule chained with SPNEGO/Kerberos against Active Directory, the service principal specified in the TGS-REQ is ldap/foo.com, even though java.naming.provider.url is set to LDAP://dc1.foo.com.
Because of this, the /Secured test in the jboss-negotiation-toolkit will fail to bind to AD/LDAP because the KDC returns an error KRB5KDC_ERR_S_PRINCIPAL_UNKNOWN.
The correct service principal name that the TGS-REQ should request is LDAP/dc1.foo.com because dc1.foo.com is what was provided in java.naming.provider.url.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBMESSAGING-1845) Remoting configuration parameter adjustment
by Yong Hao Gao (JIRA)
Remoting configuration parameter adjustment
-------------------------------------------
Key: JBMESSAGING-1845
URL: https://issues.jboss.org/browse/JBMESSAGING-1845
Project: JBoss Messaging
Issue Type: Task
Components: JMS Remoting
Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP11
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP12, 1.4.8.GA
Current remoting config has the following commented:
<!-- the following parameters are useful when there is a firewall between client and server. Uncomment them if so.-->
<!--
<attribute name="numberOfCallRetries" isParam="true">5</attribute>
<attribute name="pingFrequency" isParam="true">30000</attribute>
<attribute name="pingWindowFactor" isParam="true">71582</attribute>
<attribute name="generalizeSocketException" isParam="true">true</attribute>
-->
So defaults for those params will be used, and will turn off pinging on control connection, which would be useful to keep the control connection alive in case of a firewall. So we should uncomment it as the following
<!-- the following parameters are useful when there is a firewall between client and server. Adjust the values to suit your environment.-->
<attribute name="numberOfCallRetries" isParam="true">5</attribute>
<attribute name="pingFrequency" isParam="true">30000</attribute>
<attribute name="pingWindowFactor" isParam="true">71582</attribute>
<attribute name="generalizeSocketException" isParam="true">true</attribute>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBAS-8794) AS 6.0 dist zip: File names differing only in letter case
by Ondrej Zizka (JIRA)
AS 6.0 dist zip: File names differing only in letter case
---------------------------------------------------------
Key: JBAS-8794
URL: https://issues.jboss.org/browse/JBAS-8794
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: OSGi integration
Affects Versions: 6.0.0.Final
Reporter: Ondrej Zizka
Priority: Minor
All these files are the same:
jboss-6.0.0.Final\docs\licenses\GNU Lesser General Public Licence - lgpl.txt
jboss-6.0.0.Final\docs\licenses\GNU LESSER GENERAL PUBLIC LICENSE - lgpl.txt
jboss-6.0.0.Final\docs\licenses\GNU Lesser General Public License - lgpl.txt
jboss-6.0.0.Final\docs\licenses\GNU Lesser General Public License (LGPL), Version 2.1 - lgpl.txt
More, the first two cause error when extracting on Windows since Windows filesystems consider paths differing in letter cases the same paths.
I suggest to remove three of the files above.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (EJBTHREE-2234) Clustered @Singleton
by Carlo de Wolf (JIRA)
Clustered @Singleton
--------------------
Key: EJBTHREE-2234
URL: https://issues.jboss.org/browse/EJBTHREE-2234
Project: EJB 3.0
Issue Type: Feature Request
Reporter: Carlo de Wolf
Fix For: TBD EAP 6
It should be possible to create a clustered singleton by just adding the @Clustered annotation.
@Singleton
@Clustered
public class MyScheduler {
}
Care should be taken that the life-cycle callbacks are only invoked once on one node, the other nodes will only receive the state of the singleton after post-construct.
Concurrency management of the singleton should happen cross-cluster, so that a singleton with read lock can be concurrently invoked on any node. After existing a method with a write lock the state must be synchronized across the cluster before new invocations are processed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months