[JBoss JIRA] Moved: (EJBTHREE-2264) Cannot specify default loadBalancePolicy for Clustered EJB3s
by Brad Maxwell (JIRA)
[ https://issues.jboss.org/browse/EJBTHREE-2264?page=com.atlassian.jira.plu... ]
Brad Maxwell moved JBPAPP-6912 to EJBTHREE-2264:
------------------------------------------------
Project: EJB 3.0 (was: JBoss Enterprise Application Platform)
Key: EJBTHREE-2264 (was: JBPAPP-6912)
Affects Version/s: bom-eap5-1.0.2
(was: EAP_EWP 5.1.0)
Component Fix Version(s): proxy-clustered 1.0.4
Component/s: proxy-clustered
(was: Clustering)
Security: (was: Public)
Fix Version/s: bom-eap5-1.0.3
(was: EAP_EWP 5.1.2)
Docs QE Status: (was: NEW)
> Cannot specify default loadBalancePolicy for Clustered EJB3s
> ------------------------------------------------------------
>
> Key: EJBTHREE-2264
> URL: https://issues.jboss.org/browse/EJBTHREE-2264
> Project: EJB 3.0
> Issue Type: Bug
> Components: proxy-clustered
> Affects Versions: bom-eap5-1.0.2
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: bom-eap5-1.0.3
>
>
> Tried using ejb3-interceptors-aop.xml, however it seems you cannot modify @Clustered annotations, since the EJBs already have @Clustered on them.
> This file is where the defaults are currently, This file can be modified to allow you to specify the default loadBalancePolicy to be specified and the default sticky load balance policy in the $JBOSS_HOME/server/$PROFILE/deployers/ejb3.deployer/META-INF/ejb3-deployers-jboss-beans.xml
> jboss-ejb3-proxy-clustered-1.0.3/src/main/java/org/jboss/ejb3/proxy/clustered/registry/ProxyClusteringRegistry.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBRULES-3152) Control of KnowledgeAgent instances
by Burkhard Vogel (JIRA)
Control of KnowledgeAgent instances
-----------------------------------
Key: JBRULES-3152
URL: https://issues.jboss.org/browse/JBRULES-3152
Project: Drools
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 5.2.0.Final
Reporter: Burkhard Vogel
Assignee: Mark Proctor
There should be a way limit the number of KA on a server - as I restart test-clients and redeploy my client apps they tend to accumulate. Shouldn't the KA name be unique and any reference to a KA with the same name recover the already created KA? Or shouldn't all KA created by a client app (web or standalone) die when the creating app terminates?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1132) OSGi warnings at startup
by David Bosschaert (JIRA)
OSGi warnings at startup
------------------------
Key: AS7-1132
URL: https://issues.jboss.org/browse/AS7-1132
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.0.CR1
Reporter: David Bosschaert
Priority: Minor
While starting up AS7 the following warning appear on the console. Not sure yet whether this is serious or not. Broadly speaking the OSGi subsystem does work.
16:27:51,972 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-12) Unable to set the URLStreamHandlerFactory
16:27:51,973 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-12) Unable to set the ContentHandlerFactory
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1158) EJB-Timer Implementation is missing / not integrated
by Sebastian Jancke (JIRA)
EJB-Timer Implementation is missing / not integrated
----------------------------------------------------
Key: AS7-1158
URL: https://issues.jboss.org/browse/AS7-1158
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.0.0.CR1
Reporter: Sebastian Jancke
EJB-Component is missing an integrated EJB-Timer-Implementation.
Creating a time from within an EJB gives the following stacktrace:
...
{code}
Caused by: java.lang.UnsupportedOperationException: This is a temporary non-functional timerservice. No operations are allowed on it.
at org.jboss.as.ejb3.component.EJBComponent$NonFunctionalTimerService.<init>(EJBComponent.java:337)
at org.jboss.as.ejb3.component.EJBComponent$NonFunctionalTimerService.<init>(EJBComponent.java:335)
at org.jboss.as.ejb3.component.EJBComponent.getTimerService(EJBComponent.java:200)
at org.jboss.as.ejb3.component.TimerServiceBindingSource$TimerServiceManagedReference.getInstance(TimerServiceBindingSource.java:81)
at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptor.java:64)
{code}
The problem is a missing piece in the EJBComponent.java(line 198):
{code}
public TimerService getTimerService() throws IllegalStateException {
// TODO: Temporary, till we have a working timerservice integrated
return new NonFunctionalTimerService();
}
{code}
https://github.com/jbossas/jboss-as/blob/master/ejb3/src/main/java/org/jb...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBXB-209) Enum parsing requires value equal to type name
by Thomas Diesler (JIRA)
Enum parsing requires value equal to type name
----------------------------------------------
Key: JBXB-209
URL: https://jira.jboss.org/jira/browse/JBXB-209
Project: JBoss XML Binding (JBossXB)
Issue Type: Bug
Affects Versions: JBossXB-2.0.1.GA
Reporter: Thomas Diesler
Caused by: java.lang.RuntimeException: Invalid value mandatory valid are [MANDATORY, OPTIONAL]
at org.jboss.xb.builder.runtime.EnumValueAdapter.cast(EnumValueAdapter.java:136)
at org.jboss.xb.builder.runtime.AbstractPropertyHandler.attribute(AbstractPropertyHandler.java:115)
at org.jboss.xb.binding.sunday.unmarshalling.AttributesHandler.attributes(AttributesHandler.java:51)
at org.jboss.xb.binding.sunday.unmarshalling.DefaultElementHandler.attributes(DefaultElementHandler.java:65)
at org.jboss.xb.builder.runtime.BeanHandler.startParticle(BeanHandler.java:124)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:630)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
public enum TAvailability
{
MANDATORY("mandatory"),
OPTIONAL("optional");
private final String value;
TAvailability(String v)
{
value = v;
}
public String value()
{
return value;
}
public static TAvailability fromValue(String v)
{
for (TAvailability c : TAvailability.values())
{
if (c.value.equals(v))
{
return c;
}
}
throw new IllegalArgumentException(v);
}
}
--
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
14 years, 9 months