[JBoss JIRA] Created: (JBREM-851) In LeasePinger and TimerUtil replace Timer if it has shut down
by Ron Sigal (JIRA)
In LeasePinger and TimerUtil replace Timer if it has shut down
--------------------------------------------------------------
Key: JBREM-851
URL: http://jira.jboss.com/jira/browse/JBREM-851
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
When all of the …
[View More]TimerTasks running in a java.util.TimerTask have shut down, the TImer will also shut down, at which point it will accept no more TimerTasks. There are places in Remoting where there should be a test which will create a new Timer the attempt to schedule a TimerTask results in an exception.
Two places the problem exists:
1. org.jboss.remoting.LeasePinger, and
2. org.jboss.remoting.util.TimerUtil.
A similar problem is described in JBREM-748 "BisocketClientInvoker should guard agains scheduling on an expired Timer"
Reported by James on Remoting forum.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
16 years, 11 months
[JBoss JIRA] Created: (JBREM-804) Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator
by Ron Sigal (JIRA)
Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator
-------------------------------------------------------------------------------------------
Key: JBREM-804
URL: http://jira.jboss.com/jira/browse/JBREM-804
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.2.2.GA
Reporter: Ron Sigal
Assigned To: Ron …
[View More]Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Currently, the value for the parameter org.jboss.remoting.transport.http.HTTPMetadataConstants.NO_THROW_ON_ERROR in org.jboss.remoting.transport.http.HTTPClientInvoker is configurable only by way of the invocation metadata map passed to org.jboss.remoting.Client.invoke().
However, for EJB3 invocations, the Client is created by the EJB3 proxy (org.jboss.aspects.remoting.InvokeRemoteInterceptor, in particular) and is not accessible by application code. If HTTPClientInvoker checked the InvokerLocator for this parameter, then it could be configured declaratively in the EJB3 jboss-service.xml file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
16 years, 11 months
[JBoss JIRA] Created: (JBAS-4943) jboss-ds_1_5.dtd is wrong
by Michael Lipp (JIRA)
jboss-ds_1_5.dtd is wrong
-------------------------
Key: JBAS-4943
URL: http://jira.jboss.com/jira/browse/JBAS-4943
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation, JCA service
Affects Versions: JBossAS-4.0.5.GA
Environment: Any
Reporter: Michael Lipp
Assigned To: Norman Richards
The jboss-ds_1_5.dtd (as distributed …
[View More]in docs/dtd/) is wrong or not up-to-date (and there is no newer version and no out-of-date mark). As has been pointed out by Adrian Brock in JBAS-4942, it is possible to specify a loader-repository like this:
<connection-factories>
<!-- The loader repository name used by the ear -->
<loader-repository>jboss.test:loader=JavaClassIsolation</loader-repository>
<tx-connection-factory>
<!-- The "path" to the rar -->
<rar-name>some.ear#some.rar</rar-name>
<etc/>
</tx-connection-factory>
</connection-factories>
... although this is not compliant with the DTD!
Keeping the DTD up-to-date would avoid unnecessary bug reports and/or forum questions because looking at the DTD is the first step in finding out how to configure required behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
16 years, 11 months
[JBoss JIRA] Created: (EJBTHREE-1151) When using a MappedSuperclass then application is not deployable
by Roland Burgermann (JIRA)
When using a MappedSuperclass then application is not deployable
----------------------------------------------------------------
Key: EJBTHREE-1151
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1151
Project: EJB 3.0
Issue Type: Bug
Components: EJB3 Extensions
Affects Versions: AS 4.2.2.GA
Reporter: Roland Burgermann
I have tagged a class with the stereotype <<MappedSuperClass>> which holds some …
[View More]general attributes.
As described in the EJB3 specification i didn't have a DAO class or a DAO implementation class, because they are not necessary.
But when i try to deploy my application with JBoss 4.2.2.GA i got the following error:
2007-12-04 15:03:51,328 DEBUG [org.jboss.ejb3.Ejb3Module] Initialization failed jboss.j2ee:service=EJB3,module=ejb3xfire-core-1.0-SNAPSHOT.jar
java.lang.ClassNotFoundException: No ClassLoaders found for: com.company.samples.ejb3xfire.GeneralEntityDaoImpl
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.ejb3.Ejb3DescriptorHandler.getContainers(Ejb3DescriptorHandler.java:303)
at org.jboss.ejb3.Ejb3Deployment.deployBeansFromLib(Ejb3Deployment.java:465)
.......
The whole stack trace can be found in the JBoss forum.
When i'm using JBoss 4.0.5.GA with the EJB3 RC9 Patch 1 then my application is startable.
>> For me, this is a Blocker-Bug!! <<
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
16 years, 11 months
[JBoss JIRA] Created: (JBBUILD-449) Add metamatrix users to maven repository committers.
by Paul Gier (JIRA)
Add metamatrix users to maven repository committers.
----------------------------------------------------
Key: JBBUILD-449
URL: http://jira.jboss.com/jira/browse/JBBUILD-449
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assigned To: Paul Gier
Fix For: Maven Build - Maint 2008
These developers need access to commit to the maven repository.
rhauch, sjacobs,vhalbert,shawkins,blafond,…
[View More]rareddy,jverhaeg,dflorian,pnittel,wgibson,jdoyle,tejones
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
16 years, 11 months