[ http://jira.jboss.com/jira/browse/JBAS-1673?page=history ]
Adrian Brock closed JBAS-1673:
--
Resolution: Done
This obviously worked with JBossMQ because the CF implements
both interfaces.
> ClassCastException in JmsActivation in setupQueueConnection
>
[ http://jira.jboss.com/jira/browse/JBAS-1673?page=history ]
Adrian Brock reassigned JBAS-1673:
--
Assign To: Adrian Brock
> ClassCastException in JmsActivation in setupQueueConnection
> ---
>
>
[
http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316818 ]
Adrian Brock commented on JBAS-1319:
What we really need is to identify the classloader
classloader.toString()
and then provide backtraces to what is holding references:
[
http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316817 ]
Adrian Brock commented on JBAS-1319:
I did redeploy it lots of times. One hours worth of redeploys in a loop.
Anyway the issue is mute, since I can see the jmx-console's
[
http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316814 ]
Adrian Brock commented on JBAS-1319:
If I redeploy the jmx-console I don't see any problem with its classloader
getting GCed.
If I redeploy the jboss-profiler.war, I don'
[
http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316810 ]
Adrian Brock commented on JBAS-1319:
I've run the following script for an hour without seeing any memory leak
or OutOfMemoryError.
while (true); do wget http://localhost:
[ http://jira.jboss.com/jira/browse/JBAS-1319?page=history ]
Adrian Brock reassigned JBAS-1319:
--
Assign To: Adrian Brock (was: Clebert Suconic)
> redeploy causes OutOfMemoryError
>
>
> Key: JBAS-1319
>
[
http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316808 ]
Adrian Brock commented on JBAS-1319:
JBoss-4.0 was udpated to 5.5 two months ago (at time of writing):
http://cvs.sourceforge.net/viewcvs.py/jboss/thirdparty/apache/tomcat
[
http://jira.jboss.com/jira/browse/JBAS-1319?page=comments#action_12316802 ]
Adrian Brock commented on JBAS-1319:
Correct, this is caused by something holding onto classloaders across
deployments.
Usually because of static collections in non rede
[ http://jira.jboss.com/jira/browse/JBAS-1319?page=history ]
Adrian Brock updated JBAS-1319:
---
Component: Web (Tomcat) service
(was: JMX)
> redeploy causes OutOfMemoryError
>
>
> Key: JBAS-1319
>
[ http://jira.jboss.com/jira/browse/JBAS-1664?page=history ]
Adrian Brock closed JBAS-1664:
--
Resolution: Won't Fix
You mean OutOfMemoryError.
In general such errors leave the JVM in an unknown/unrecoverable state.
The main difference between BMP and
[ http://jira.jboss.com/jira/browse/JBAS-1607?page=history ]
Adrian Brock closed JBAS-1607:
--
Resolution: Duplicate Issue
> Absence of optional 'transaction-timeout' element throws NumberFormatException
>
[
http://jira.jboss.com/jira/browse/JBAS-1608?page=comments#action_12316778 ]
Adrian Brock commented on JBAS-1608:
I'd guess the problem is caused by inspectMBean.jsp
using an element rather than a
so you only see the first line of the data.
> Co
[
http://jira.jboss.com/jira/browse/JBAS-1662?page=comments#action_12316777 ]
Adrian Brock commented on JBAS-1662:
SpecCompliant=true is a misnomer. It has nothing to do with
spec compliance. In fact JBoss passed the j2ee1.4 compliance suite
with th
[ http://jira.jboss.com/jira/browse/JBAS-1662?page=history ]
Adrian Brock updated JBAS-1662:
---
Version: JBossAS-4.0.2RC1
JBossAS-4.0.1 SP1
JBossAS-4.0.1 Final
JBossAS-3.2.7 Final
Component: JCA service
[ http://jira.jboss.com/jira/browse/JBBUILD-61?page=history ]
Adrian Brock updated JBBUILD-61:
Description:
Make JBossXB into a separate project
that can be consumed indepently by standalone projects.
was:
Make org.jboss.net into a separate project
th
Split out jbossxb into a separate project/binary
Key: JBBUILD-61
URL: http://jira.jboss.com/jira/browse/JBBUILD-61
Project: JBoss Build System
Type: Sub-task
Reporter: Adrian Brock
Assigned to: Ryan Campbell
[ http://jira.jboss.com/jira/browse/JBBUILD-60?page=history ]
Adrian Brock updated JBBUILD-60:
Description:
Make org.jboss.net into a separate project
that can be consumed indepently by standalone projects.
was:
Make org.jboss.logging into a separate
Split out org.jboss.logging into a separate project/binary
--
Key: JBBUILD-59
URL: http://jira.jboss.com/jira/browse/JBBUILD-59
Project: JBoss Build System
Type: Sub-task
Reporter: Adrian Brock
Assigned to:
Split out org.jboss.net into a separate project/binary
--
Key: JBBUILD-60
URL: http://jira.jboss.com/jira/browse/JBBUILD-60
Project: JBoss Build System
Type: Sub-task
Reporter: Adrian Brock
Assigned to: Ryan Ca
[ http://jira.jboss.com/jira/browse/JBAS-1645?page=history ]
Adrian Brock closed JBAS-1645:
--
Resolution: Done
I have added
true
to the invoker proxy config so that this can be turned off.
The default is true for backwards compatibility.
> The MDB shou
The MDB should not automatically create JBossMQ destinations
Key: JBAS-1645
URL: http://jira.jboss.com/jira/browse/JBAS-1645
Project: JBoss Application Server
Type: Feature Request
Components: JMS service
[ http://jira.jboss.com/jira/browse/JBAS-1613?page=history ]
Adrian Brock closed JBAS-1613:
--
Resolution: Duplicate Issue
1) Use search before reporting bugs.
2) Test the latest version before reporting bugs.
> NPE in PersistenceManager.loadFromStorag
[ http://jira.jboss.com/jira/browse/JBAS-1609?page=history ]
Adrian Brock reopened JBAS-1609:
Assign To: Ben Wang (was: Bela Ban)
This doesn't compile with jdk1.3 in branch 3.2.x
compile-classes:
[mkdir] Created dir:
/scratch/cruisecontrol/c
[ http://jira.jboss.com/jira/browse/JBAS-1635?page=history ]
Adrian Brock closed JBAS-1635:
--
Resolution: Rejected
You aren't going to get any response to a bug report against
an old release candidate.
Anyway this is an old invalid bug report:
http://i
[ http://jira.jboss.com/jira/browse/JBAS-1635?page=history ]
Adrian Brock updated JBAS-1635:
---
Component: Web (Tomcat) service
(was: Deployment Service)
> DEPLOY TO JBOSS - SERVLETINCLUDE GENERATES AN EXCEPTION
> -
[ http://jira.jboss.com/jira/browse/JBAS-1611?page=history ]
Adrian Brock closed JBAS-1611:
--
Resolution: Duplicate Issue
Is the search function broken or something?
> ClientMonitorIntecepor
> --
>
> Key: JBAS-1611
>
[ http://jira.jboss.com/jira/browse/JBAS-1636?page=history ]
Adrian Brock closed JBAS-1636:
--
Resolution: Done
Fixed. Also added a warning log of all connectionErrorOccurred events
seen by the ConnectionManager(s).
> Don't try to delist a track-connect
Don't try to delist a track-connection-by-tx connection that is already broken
and has been closed.
---
Key: JBAS-1636
URL: http://jira.jboss.com/jira/browse/JBAS-1636
Project: J
[ http://jira.jboss.com/jira/browse/JBAS-1619?page=history ]
Adrian Brock closed JBAS-1619:
--
Resolution: Done
JBoss no longer loads libraries by default.
To renable JBoss loading libraries use the system property
-Djboss.native.load=true
Also added the
[ http://jira.jboss.com/jira/browse/JBAS-1619?page=history ]
Adrian Brock updated JBAS-1619:
---
Assign To: Adrian Brock
Fix Version: JBossAS-4.0.2 Final
> LoadLibrary should be done through the deployment classloader
> -
[
http://jira.jboss.com/jira/browse/JBBUILD-48?page=comments#action_12316562 ]
Adrian Brock commented on JBBUILD-48:
-
We need to reproduce the old build with the new build so we can cutover.
Once buildmagic is no more an issue, we can more easily c
[ http://jira.jboss.com/jira/browse/JBAS-1630?page=history ]
Adrian Brock closed JBAS-1630:
--
Resolution: Duplicate Issue
And if you look at that forum thread, you'll see
I already created a bug report.
> Make it easier to deploy JCA packages with JNI
[ http://jira.jboss.com/jira/browse/JBJMX-89?page=comments#action_12316525
]
Adrian Brock commented on JBJMX-89:
---
Dimitris,
I think you'll find he is complaining about the code in
org.jboss.mx.server.MethodMapper.lookupOperation()
that resolves the m
[ http://jira.jboss.com/jira/browse/JBJMX-88?page=history ]
Adrian Brock closed JBJMX-88:
-
Resolution: Won't Fix
Use the class name not the string from the programming language:
http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Class.html#getName()
ser
[ http://jira.jboss.com/jira/browse/JBAS-1629?page=history ]
Adrian Brock closed JBAS-1629:
--
Resolution: Duplicate Issue
Please test the latest version (including release candidates)
before reporting bugs.
http://cvs.sourceforge.net/viewcvs.py/jboss/j
[ http://jira.jboss.com/jira/browse/JBAS-1604?page=history ]
Adrian Brock closed JBAS-1604:
--
Resolution: Done
The jms rar now logs connection/session and receiver usage.
It does not intercept producer usage so no logging was added here.
> Add detailed
[ http://jira.jboss.com/jira/browse/JBAS-1434?page=history ]
Adrian Brock updated JBAS-1434:
---
Fix Version: JBossAS-4.0.3 Final
Rescheduled for 4.0.3
> JMS Message Inflow
> --
>
> Key: JBAS-1434
> URL: http://jira.jboss.co
[ http://jira.jboss.com/jira/browse/JBAS-1434?page=history ]
Adrian Brock updated JBAS-1434:
---
Description:
Forums Discussion Thread:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48672
The JMS message inflow in the JMS resource adapter needs p
[ http://jira.jboss.com/jira/browse/JBAS-58?page=history ]
Adrian Brock closed JBAS-58:
Resolution: Done
I've updated the tests to include the basic deployment strategies
as outlined in the FAQ:
http://www.jboss.org/wiki/Wiki.jsp?page=WhatAreTheDifferen
[
http://jira.jboss.com/jira/browse/JBAS-1626?page=comments#action_12316472 ]
Adrian Brock commented on JBAS-1626:
I disagreed with this interceptor when it was first written
but let it pass because it is not enabled by default.
It was put there by
[ http://jira.jboss.com/jira/browse/JBAS-1446?page=history ]
Adrian Brock closed JBAS-1446:
--
Resolution: Done
Fix Version: JBossAS-4.0.2 Final
Done.
There is now trace logging for:
creating admin objects
creating activation specs
and the mdb driv
[ http://jira.jboss.com/jira/browse/JBXB-7?page=history ]
Adrian Brock updated JBXB-7:
Assign To: Alexey Loubyansky (was: Adrian Brock)
> Create a deployment instance doc illustrating the polymorphism requirements
> -
[
http://jira.jboss.com/jira/browse/JBAS-1446?page=comments#action_12316412 ]
Adrian Brock commented on JBAS-1446:
Also need logging for activation spec and admin object construction.
> org.jboss.resource.deployment.RARDeployment needs TRACE loggin
[ http://jira.jboss.com/jira/browse/JBAS-1446?page=history ]
Adrian Brock reassigned JBAS-1446:
--
Assign To: Adrian Brock
> org.jboss.resource.deployment.RARDeployment needs TRACE logging
> ---
[
http://jira.jboss.com/jira/browse/JBAS-1619?page=comments#action_12316403 ]
Adrian Brock commented on JBAS-1619:
I would question that we are even trying to load the libraries for the rar
or any deployment.
It should be left to the class(es) that
[ http://jira.jboss.com/jira/browse/JBAS-1619?page=history ]
Adrian Brock updated JBAS-1619:
---
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=61814
> LoadLibrary should be done through the deployment classloader
> -
LoadLibrary should be done through the deployment classloader
-
Key: JBAS-1619
URL: http://jira.jboss.com/jira/browse/JBAS-1619
Project: JBoss Application Server
Type: Bug
Components: Deployment Service
Backport jbossmq fixes to 3.2.8
---
Key: JBAS-1616
URL: http://jira.jboss.com/jira/browse/JBAS-1616
Project: JBoss Application Server
Type: Task
Components: JMS service
Versions: JBossAS-3.2.7 Final
Reporter: Adrian Brock
Backport jdbc rar changes from 4.0.x to 3.2.8
-
Key: JBAS-1615
URL: http://jira.jboss.com/jira/browse/JBAS-1615
Project: JBoss Application Server
Type: Task
Components: JCA service
Versions: JBossAS-3.2.7 Final
[ http://jira.jboss.com/jira/browse/JBAS-1614?page=history ]
Adrian Brock reopened JBAS-1614:
Documentation issue
> listMessageCounterHistory returns nothing on Topics but works on Queues
> --
[
http://jira.jboss.com/jira/browse/JBAS-1614?page=comments#action_12316387 ]
Adrian Brock commented on JBAS-1614:
It refers to any subscriptions (durable or non durable)
But it wouldn't be as easy to test with non durable since the subscription
is
[ http://jira.jboss.com/jira/browse/JBAS-1614?page=history ]
Adrian Brock closed JBAS-1614:
--
Resolution: Rejected
Create a durable topic subscription then see what it says.
> listMessageCounterHistory returns nothing on Topics but works on Queues
> --
[ http://jira.jboss.com/jira/browse/JBAS-1605?page=history ]
Adrian Brock closed JBAS-1605:
--
Resolution: Won't Fix
This has been a known issue with reflection since java 1.4 came out.
If you introduce an inheritance diamond, the method can appear
multi
Add detailed logging to the jms resource adapter
Key: JBAS-1604
URL: http://jira.jboss.com/jira/browse/JBAS-1604
Project: JBoss Application Server
Type: Feature Request
Components: JMS service
Versions: JBossA
[
http://jira.jboss.com/jira/browse/JBAS-1603?page=comments#action_12316314 ]
Adrian Brock commented on JBAS-1603:
> Does this mean that JBoss 3.2.x is dead, i.e. unsupported? The problem still
> exists in JBoss 3.2.7.
Without fixing the other is
[ http://jira.jboss.com/jira/browse/JBAS-1603?page=history ]
Adrian Brock closed JBAS-1603:
--
Resolution: Won't Fix
1) It is not your place to decide the priority of bug reports.
2) Don't report bugs against old versions.
3) File persistence is not supp
[ http://jira.jboss.com/jira/browse/JBAS-1391?page=history ]
Adrian Brock updated JBAS-1391:
---
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=61713
Added a discussion thread in the forums.
> Add support for datasource fail
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316308 ]
Adrian Brock commented on JBAS-1391:
I don't like the idea of it always starting from the first url.
Once it has "failed over", it should remain sticky on that url until i
[ http://jira.jboss.com/jira/browse/JBXB-5?page=comments#action_12316306 ]
Adrian Brock commented on JBXB-5:
-
The beaninfo and classinfo objects should be irrelevent,
they are implementation details mapped/injected during processing,
*after* the XML pars
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316230 ]
Adrian Brock commented on JBAS-1391:
There is an even more important problem with the DataSource of DataSources
approach.
Any failover will bypass the transaction stickne
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316225 ]
Adrian Brock commented on JBAS-1391:
Sean's comment is entirely unrelated to the problem.
He is talking about *restarting* JBossMQ with a new DataSource/ConnectionURL
ma
[
http://jira.jboss.com/jira/browse/JBAS-1391?page=comments#action_12316223 ]
Adrian Brock commented on JBAS-1391:
First, it is better to discuss the design in the dev forums.
To answer your question Alex, it can be done both ways.
The DataSource
[
http://jira.jboss.com/jira/browse/JBAS-1589?page=comments#action_12316177 ]
Adrian Brock commented on JBAS-1589:
Of course there is, I would be wasting my time if I had to refix the problem in
6 months time.
> Typo in JBossMQ's TxManager
> -
[ http://jira.jboss.com/jira/browse/JBAS-1589?page=history ]
Adrian Brock reopened JBAS-1589:
> Type in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
> URL: http://jira.jboss.com/jira/browse/JBAS-1589
> Proj
[ http://jira.jboss.com/jira/browse/JBAS-1589?page=history ]
Adrian Brock closed JBAS-1589:
--
Resolution: Done
> Typo in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
> URL: http://jira.jboss.com/jira/browse/JBAS
[ http://jira.jboss.com/jira/browse/JBAS-1589?page=history ]
Adrian Brock updated JBAS-1589:
---
Summary: Typo in JBossMQ's TxManager (was: Type in JBossMQ's TxManager)
> Typo in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
>
[ http://jira.jboss.com/jira/browse/JBAS-1589?page=history ]
Adrian Brock closed JBAS-1589:
--
Resolution: Done
Fixed
> Type in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
> URL: http://jira.jboss.com/jira/brow
Type in JBossMQ's TxManager
---
Key: JBAS-1589
URL: http://jira.jboss.com/jira/browse/JBAS-1589
Project: JBoss Application Server
Type: Bug
Components: JMS service
Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
[
http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316172 ]
Adrian Brock commented on JBAS-1552:
I've attached a simple ant build that can be used to determine
serialVersionUID for both JBoss and J2EE classes.
e.g.
ant jboss -Dclas
[ http://jira.jboss.com/jira/browse/JBAS-1552?page=history ]
Adrian Brock updated JBAS-1552:
---
Attachment: build.properties
Need to change jboss.home and j2ee.home
> JBoss use wrong version of javax.resource.ResourceException class file
> -
[ http://jira.jboss.com/jira/browse/JBAS-1552?page=history ]
Adrian Brock updated JBAS-1552:
---
Attachment: build.xml
> JBoss use wrong version of javax.resource.ResourceException class file
> -
[
http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316170 ]
Adrian Brock commented on JBAS-1552:
I just submitted a potential fix to JBoss Head
on how to change the SerialVersionUID to allow both j2eeri and legacy JBoss
compatibili
[ http://jira.jboss.com/jira/browse/JBAS-1578?page=history ]
Adrian Brock closed JBAS-1578:
--
Resolution: Done
ReceiveRequestMsg is now sent one-way
> Duplicate Messages
> --
>
> Key: JBAS-1578
> URL: http://jira.jboss
[ http://jira.jboss.com/jira/browse/JBAS-1564?page=history ]
Adrian Brock closed JBAS-1564:
--
Resolution: Done
The prepared statement is not reused when autocommit is on.
Reuse is defined as asking for the same prepared statement twice in the same
tran
[ http://jira.jboss.com/jira/browse/JBAS-1578?page=history ]
Adrian Brock updated JBAS-1578:
---
Version: JBossAS-4.0.2RC1
Fix Version: JBossAS-4.0.2 Final
> Duplicate Messages
> --
>
> Key: JBAS-1578
> URL: http://j
[
http://jira.jboss.com/jira/browse/JBAS-1578?page=comments#action_12316149 ]
Adrian Brock commented on JBAS-1578:
Fixed for now by trimming the reply.
We should decide before this goes into a release whether
we this can be a truly one-way send of
[ http://jira.jboss.com/jira/browse/JBAS-1578?page=history ]
Adrian Brock reassigned JBAS-1578:
--
Assign To: Adrian Brock
> Duplicate Messages
> --
>
> Key: JBAS-1578
> URL: http://jira.jboss.com/jira/browse/JBAS-1578
>
[ http://jira.jboss.com/jira/browse/JBAS-1587?page=history ]
Adrian Brock updated JBAS-1587:
---
Description:
Need to write some tests that tweaks the edge cases of the RAR configuration,
in particular:
no-tx vs local-tx vs xa
PreparedStatement caching
Resett
JDBC RAR tests
--
Key: JBAS-1587
URL: http://jira.jboss.com/jira/browse/JBAS-1587
Project: JBoss Application Server
Type: Task
Components: JCA service
Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
Reporter: Adrian Br
[ http://jira.jboss.com/jira/browse/JBAS-1582?page=history ]
Adrian Brock closed JBAS-1582:
--
Resolution: Done
Changed the example to use DelegatePM instead of DelegateName
> NullPersistenceManager, DelegateName is wrong
> -
[ http://jira.jboss.com/jira/browse/JBAS-1583?page=history ]
Adrian Brock closed JBAS-1583:
--
Resolution: Done
> Primary key violation on JMS_TRANSACTIONS
> -
>
> Key: JBAS-1583
> URL: http://jir
[
http://jira.jboss.com/jira/browse/JBAS-1585?page=comments#action_12316136 ]
Adrian Brock commented on JBAS-1585:
Flow control needs a lot more thought than my off the cuff trivial test.
e.g. The requests should not just be throttled they should b
[ http://jira.jboss.com/jira/browse/JBAS-1585?page=history ]
Adrian Brock updated JBAS-1585:
---
Description:
> -Original Message-
> From: Adrian Brock
> Sent: Monday, March 14, 2005 2:35 PM
> To: Ivelin Ivanov
> Cc: Stan Silvert; Neal Byrd
Primary key violation on JMS_TRANSACTIONS
-
Key: JBAS-1583
URL: http://jira.jboss.com/jira/browse/JBAS-1583
Project: JBoss Application Server
Type: Bug
Components: JMS service
Versions: JBossAS-4.0.1 Final, JBossAS-4.0
[ http://jira.jboss.com/jira/browse/JBAS-1564?page=history ]
Adrian Brock reassigned JBAS-1564:
--
Assign To: Adrian Brock
> Prepared Statement Cache does not take into account autocommit semantics
> ---
[ http://jira.jboss.com/jira/browse/JBAS-1581?page=history ]
Adrian Brock closed JBAS-1581:
--
Resolution: Done
Both configuration options are now accepted
Use CREATE_TABLES_ON_STARTUP for consistency with the persistence manager
config.
> JDBC StateMa
NullPersistenceManager, DelegateName is wrong
-
Key: JBAS-1582
URL: http://jira.jboss.com/jira/browse/JBAS-1582
Project: JBoss Application Server
Type: Bug
Components: JCA service
Versions: JBossAS-4.0.2RC1, JBoss
JDBC StateManager - CREATE_TABLES_ON_STARTUP is wrong
-
Key: JBAS-1581
URL: http://jira.jboss.com/jira/browse/JBAS-1581
Project: JBoss Application Server
Type: Bug
Components: JCA service
Versions: JBossAS-
[ http://jira.jboss.com/jira/browse/JBREM-70?page=comments#action_12316116
]
Adrian Brock commented on JBREM-70:
---
Please do not mess about with the eclipse build settings!
You can do what you like when remoting is a standalone project.
Other jars sho
[ http://jira.jboss.com/jira/browse/JBAS-1568?page=history ]
Adrian Brock closed JBAS-1568:
--
Resolution: Won't Fix
I don't see how we can satisfy both requirements that
two MDBs can be deployed with the same EJB name
and yet have unique ObjectNames.
S
[
http://jira.jboss.com/jira/browse/JBAS-1568?page=comments#action_12316079 ]
Adrian Brock commented on JBAS-1568:
I believe this is a duplicate post, but I can't find where Scott already
answered this.
The workaround is:
FIXED-NAME
etc.
>
Prepared Statement Cache does not take into account autocommit semantics
-
Key: JBAS-1564
URL: http://jira.jboss.com/jira/browse/JBAS-1564
Project: JBoss Application Server
Type: Bug
Component
Check all serverSocket accept threads
-
Key: JBAS-1559
URL: http://jira.jboss.com/jira/browse/JBAS-1559
Project: JBoss Application Server
Type: Task
Reporter: Adrian Brock
Fix For: JBossAS-4.0.2RC1
Check all serverSocke
[ http://jira.jboss.com/jira/browse/JBAS-1557?page=history ]
Adrian Brock closed JBAS-1557:
--
Resolution: Done
Fixed, also fixed the same problem in the autodiscovery thread.
> HAJNDI accept thread can die if it cannot create a new listening thread
> -
[ http://jira.jboss.com/jira/browse/JBAS-1557?page=history ]
Adrian Brock reassigned JBAS-1557:
--
Assign To: Adrian Brock
> HAJNDI accept thread can die if it cannot create a new listening thread
>
HAJNDI should use a thread pool
---
Key: JBAS-1558
URL: http://jira.jboss.com/jira/browse/JBAS-1558
Project: JBoss Application Server
Type: Feature Request
Components: Clustering
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final,
HAJNDI accept thread can die if it cannot create a new listening thread
---
Key: JBAS-1557
URL: http://jira.jboss.com/jira/browse/JBAS-1557
Project: JBoss Application Server
Type: Bug
Components: C
[ http://jira.jboss.com/jira/browse/JBAS-1541?page=history ]
Adrian Brock closed JBAS-1541:
--
Resolution: Done
The threadpools are now shutdown at connection.close() or when the
server detects the client has vanished.
> Clients hang if UIL2 server proc
[ http://jira.jboss.com/jira/browse/JBAS-1541?page=history ]
Adrian Brock updated JBAS-1541:
---
Priority: Major (was: Critical)
Fix Version: JBossAS-4.0.2RC1
(was: JBossAS-4.0.2 Final)
> Clients hang if UIL2 server process is in
1 - 100 of 565 matches
Mail list logo