[JBoss JIRA] Assigned: (JBAS-6717) AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
by Charles Crouch (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6717?page=com.atlassian.jira.plug... ]
Charles Crouch reassigned JBAS-6717:
------------------------------------
Assignee: Scott M Stark
> AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-6717
> URL: https://jira.jboss.org/jira/browse/JBAS-6717
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: JBoss Branch_5_x r85739, embjopr r209
> Reporter: Farah Juma
> Assignee: Scott M Stark
> Fix For: JBossAS-5.1.0.CR1
>
>
> Steps to reproduce:
> Create a new -ds.xml file. Set values for min-pool-size and max-pool-size. Request multiple connections from the connection pool. Then, close a few of these connections. Perform the "List Formatted Sub Pool Statistics" operation for this datasource. The value of "Connections In Use Count" in the result of the operation is not updated to reflect the closed connections.
> For example, when min-pool-size=5, max-pool-size=20, and there are 10 connections in use, the following is the result of the "List Formatted Sub Pool Statistics" operation after closing 2 connections:
> Sub Pool Statistics:
> Sub Pool Count: 1
> ------------------------------------------------------
> Track By Transaction: true
> Available Connections Count: 12
> Max Connections In Use Count:10
> Connections Destroyed Count:0
> **Connections In Use Count:10**
> Total Block Time:0
> Average Block Time For Sub Pool:0
> Maximum Wait Time For Sub Pool:0
> Total Timed Out:0
> The value of "Connections In Use Count" should be 8 in this case.
--
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, 1 month
[JBoss JIRA] Moved: (JBAS-6715) java.lang.RuntimeException thrown adding resource that was previously Deleted
by Charles Crouch (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-6715?page=com.atlassian.jira.plug... ]
Charles Crouch moved EMBJOPR-116 to JBAS-6715:
----------------------------------------------
Project: JBoss Application Server (was: Embedded Jopr)
Key: JBAS-6715 (was: EMBJOPR-116)
Component/s: (was: Web App/Integration)
Fix Version/s: JBossAS-5.1.0.CR1
(was: 1.2)
Security: Public
> java.lang.RuntimeException thrown adding resource that was previously Deleted
> -----------------------------------------------------------------------------
>
> Key: JBAS-6715
> URL: https://jira.jboss.org/jira/browse/JBAS-6715
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Shelly McGowan
> Assignee: Emanuel Muckenhuber
> Fix For: JBossAS-5.1.0.CR1
>
> Attachments: servlets-examples.war
>
>
> Navigation:
> Applications ==> Web Applications
> Add new Resource
> Browse to Resource
> CONTINUE
> When war archive status is 'UP', Delete .war from applications list
> Confirmation: Successfully deleted Web Application (WAR) 'hellothere.war'.
> Server side shows war was undeployed.
> Follow the same navigation steps, but this time upon Adding Resource, the following is displayed to client (and server.log):
> Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/ -> org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed DEPLOYMENTS IN ERROR: Deployment "vfszip:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/default/tmp/3j001-aeo7z0-fsjbdjc2-1-fsjbg47o-ec/hellothere.war/ deployment failed
> Reproducing this issue is blocked due to EMBJOPR-115. Assigning to myself for tracking.
--
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, 1 month
[JBoss JIRA] Created: (JBAS-6671) on Connection Factory components, jndi-name, rar-name, and connection-definition ManagedPropertys should all be mandatory, in both templates and properties on existing components
by Ian Springer (JIRA)
on Connection Factory components, jndi-name, rar-name, and connection-definition ManagedPropertys should all be mandatory, in both templates and properties on existing components
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6671
URL: https://jira.jboss.org/jira/browse/JBAS-6671
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
When creating or updating a ConnectionFactory component, when the jndi-name prop is not specified, I get:
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/notx-ds.xml" is in error due to the following reason(s): java.lang.IllegalArgumentException: Null text
when the rar-name prop is not specified, I get:
Deployment "vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/xxx-ds.xml" is in error due to the following reason(s): java.lang.IllegalArgumentException: Null name
and when the connection-definition prop is not specified, I get:
Deployment "vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/xxx-ds.xml" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: ConnectionDefinition 'null' not found in rar 'null'
which tells me all three of these props are required, so prop.isMandatory() should return true, but it currently returns false. It should return true for both CF templates and existing CF components.
Not directly related to management, but all three of the above error messages could also be significantly improved, e.g.:
The "jndi-name" property was not specified for connection factory "FooBar" - this property is required.
The "rar-name" property was not specified for connection factory "FooBar" - this property is required.
The "connection-definition" property was not specified for connection factory "FooBar" - this property is required.
--
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, 1 month
[JBoss JIRA] Created: (JGRP-911) STREAMING_STATE_TRANSFER: investigate use of UDP datagrams instead of TCP socket
by Bela Ban (JIRA)
STREAMING_STATE_TRANSFER: investigate use of UDP datagrams instead of TCP socket
--------------------------------------------------------------------------------
Key: JGRP-911
URL: https://jira.jboss.org/jira/browse/JGRP-911
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
We currently use TCP server and client sockets to transfer state with STREAMING_STATE_TRANSFER. Add an option to use the default transport (could be TCP, could be UDP).
State provider:
- Write state into an output stream
- The output stream generates unicast messages of a fixed size and sends them to the state receiver
State receiver:
- Provides an input stream
- The app reads data off of that stream
- The received message chunks are placed into the input stream
Might be more firewall friendly and causes less config overhead (e.g. punching of holes for the TCP conn in the FW).
--
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, 1 month
[JBoss JIRA] Created: (JBPORTAL-2364) Duplicate mime-mappings causes FireFox to upload *.jpg files as image/pjpeg
by Magesh Kumar B (JIRA)
Duplicate mime-mappings causes FireFox to upload *.jpg files as image/pjpeg
---------------------------------------------------------------------------
Key: JBPORTAL-2364
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2364
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.6 Final
Reporter: Magesh Kumar B
Assignee: Sohil Shah
Microsoft web browsers uploads all images with file extension *.jpg as content type image/pjpeg. This has been an issue and the world is aware of this. The same file with *.jpg extension uploads as content type image/jpeg in FireFox (using a simple upload form in JSP). However CMS file upload either through FireFox or IE always uploads *.jpg as image/pjpeg. This was attributed to the mime-mappings.xml having an additional entry towards the end of the file as:
<mime-mapping>
<extension>jpg</extension>
<mime-type>image/pjpeg</mime-type>
</mime-mapping>
However users are facing issue with this type of mime-type in mobile applications as these are not displayed in mobile browsers.
--
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, 1 month