[JBoss JIRA] (AS7-5714) JPA "Session Open Count" statistic appears to be bogus
by Jess Sightler (JIRA)
Jess Sightler created AS7-5714:
----------------------------------
Summary: JPA "Session Open Count" statistic appears to be bogus
Key: AS7-5714
URL: https://issues.jboss.org/browse/AS7-5714
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jess Sightler
Assignee: Scott Marlow
Priority: Minor
After running a small sample app, Session Open Count in the admin console displays 900006. Session close count is 1 (as expected). Memory usage does not significantly increase.
The sample app exposes an EntityManager like this:
@Produces
public EntityManager getEntityManager() {
System.out.println("Getting entity manager!");
return entityManager;
}
A JAX-RS service then injects the entity manager, and performs a few simple queries:
@Inject
private EntityManager entityManager;
@GET()
@Produces("text/plain")
public String sayHello() {
try {
userTransaction.begin();
Car car = new Car();
car.setCarName("Name: " + System.currentTimeMillis());
entityManager.persist(car);
Car car2 = new Car();
car2.setCarName("Name: " + System.currentTimeMillis());
entityManager.persist(car2);
for (int i = 0; i < 900000; i++) {
Query q = entityManager.createQuery("select c from Car c");
List<Car> resultList = q.getResultList();
for (Car c : resultList) {
System.out.println("Car: " + c);
}
}
return "stub";
}
I don't see any way that this could actually be opening this many sessions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-5818) Fix cache control headers on FF
by Heiko Braun (JIRA)
Heiko Braun created AS7-5818:
--------------------------------
Summary: Fix cache control headers on FF
Key: AS7-5818
URL: https://issues.jboss.org/browse/AS7-5818
Project: Application Server 7
Issue Type: Feature Request
Components: Console, Domain Management
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: 7.2.0.Alpha1
The last modified header seems to force FF to send a revalidation upon every request. This is not necessary and causes additional traffic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-5903) OSGi tests may incorrectly assume that a given service is available
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5903:
-----------------------------------
Summary: OSGi tests may incorrectly assume that a given service is available
Key: AS7-5903
URL: https://issues.jboss.org/browse/AS7-5903
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Similar to AS7-5828 there may be other tests that could potentially fail because of an invalid assumption that a given service is available. This may especially happen if the test before changes the framework startlevel.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-5902) HornetQ does not delete message from queue when the message is rolled back and the DLQ is not present
by Ravi Bhardwaj (JIRA)
Ravi Bhardwaj created AS7-5902:
----------------------------------
Summary: HornetQ does not delete message from queue when the message is rolled back and the DLQ is not present
Key: AS7-5902
URL: https://issues.jboss.org/browse/AS7-5902
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Ravi Bhardwaj
Assignee: Jeff Mesnil
When a message is rolled back and the DLQ binding configured for queue is missing, the server throws the following warning message saying that it is dropping the message, however we can still see the message count and In Delivery count as :
WARN [org.hornetq.core.server.impl.QueueImpl] (Thread-3 (HornetQ-server-HornetQServerImpl::serverUUID=c7787105-2983-11e2-94d2-611405d536ca-619601171)) Message Reference[143]:RELIABLE:ServerMessage[messageID=143,priority=4, bodySize=178,expiration=0, durable=true, address=jms.queue.TestQ2,properties=TypedProperties[null]]@1575145817 has exceeded max delivery attempts. No bindings for Dead Letter Address jms.queue.DLQ123 so dropping it
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBRULES-3682) Guvnor drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3682?page=com.atlassian.jira.plug... ]
Michael Anstis moved GUVNOR-1967 to JBRULES-3682:
-------------------------------------------------
Project: Drools (was: Guvnor)
Key: JBRULES-3682 (was: GUVNOR-1967)
Issue Type: Task (was: Enhancement)
Affects Version/s: 5.3.0.Final
(was: drools-5.3.0.Final)
> Guvnor drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.
> ---------------------------------------------------------------------------------------------
>
> Key: JBRULES-3682
> URL: https://issues.jboss.org/browse/JBRULES-3682
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 5.3.0.Final
> Environment: local
> Reporter: Amit Telang
> Labels: maven
>
> Hi, after inclusion guvnor 5.x in application, we are unable to deploy our application through Hudson on our managed server. Issue is related to drools-compiler-5.3.0.Final.jar dependancy with antlr3.3 jar file. If I use exclusion tag to exclude this it excludes all the jar which starts with antlr.
> If I use package exclude to include this antlr3.3 it do not compile. Unable to resolve this small looking issue for a long time.
> Please provide any valuable feedback if someone also faces this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBRULES-3682) drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3682?page=com.atlassian.jira.plug... ]
Michael Anstis updated JBRULES-3682:
------------------------------------
Summary: drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR. (was: Guvnor drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.)
> drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.
> ---------------------------------------------------------------------------------------
>
> Key: JBRULES-3682
> URL: https://issues.jboss.org/browse/JBRULES-3682
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 5.3.0.Final
> Environment: local
> Reporter: Amit Telang
> Labels: maven
>
> Hi, after inclusion guvnor 5.x in application, we are unable to deploy our application through Hudson on our managed server. Issue is related to drools-compiler-5.3.0.Final.jar dependancy with antlr3.3 jar file. If I use exclusion tag to exclude this it excludes all the jar which starts with antlr.
> If I use package exclude to include this antlr3.3 it do not compile. Unable to resolve this small looking issue for a long time.
> Please provide any valuable feedback if someone also faces this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (AS7-4692) Review SecurityContext associations
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-4692:
-------------------------------------
Summary: Review SecurityContext associations
Key: AS7-4692
URL: https://issues.jboss.org/browse/AS7-4692
Project: Application Server 7
Issue Type: Task
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.2.0.Alpha1
We should re-review the approach we take for security context association within AS7 containers.
Back at the time of AS 3 it fairly reliable to assume a 1:1 mapping of thread and client with the incoming connection being allocated it's own thread, this is no longer automatically the case and different containers can use different threading models e.g. using Executors to handle asynchronous requests.
The problem with using a ThreadLocal approach is that every time a container diverges from the 1:1 mapping of thread and client that container needs to work around the issue of an invalid SecurityContext association.
One possibility is to pass responsibility for managing the context to the container although this then introduces the question of how it is passed from container to container. This issue needs to consider this further.
Also need to review further how the security context can be created at all entry points to the server and how it can be manually switched now that we use SASL on entry for remote calls we do now have the opportunity for equivalent behaviour at the entry point for both web and ejb type calls - in the past we only had this opportunity for web based calls and would only create a security context on entering the interceptors for the EJB calls.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months