[JBoss JIRA] (AS7-6624) Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
by Alexey S. (JIRA)
Alexey S. created AS7-6624:
------------------------------
Summary: Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
Key: AS7-6624
URL: https://issues.jboss.org/browse/AS7-6624
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.1.Final
Reporter: Alexey S.
Assignee: Scott Marlow
I am using JPA Hibernate in Timer EJB.
After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened.
my datasource is
<xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true">
<xa-datasource-property name="ServerName">
localhost
</xa-datasource-property>
<xa-datasource-property name="DatabaseName">
db
</xa-datasource-property>
<xa-datasource-property name="User">
root
</xa-datasource-property>
<xa-datasource-property name="Password">
xxxxx
</xa-datasource-property>
<xa-datasource-property name="AutoReconnectForPools">
true
</xa-datasource-property>
<xa-datasource-property name="FailOverReadOnly">
false
</xa-datasource-property>
<xa-datasource-property name="MaxReconnects">
100
</xa-datasource-property>
<xa-datasource-property name="ReconnectAtTxEnd">
true
</xa-datasource-property>
<driver>com.mysql</driver>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
<check-valid-connection-sql>select 1</check-valid-connection-sql>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
</validation>
</xa-datasource>
--
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, 2 months
[JBoss JIRA] (SECURITY-728) WebJASPIOptionalAuthenticator does not actually authenticate
by Anil Saldhana (JIRA)
[ https://issues.jboss.org/browse/SECURITY-728?page=com.atlassian.jira.plug... ]
Anil Saldhana reassigned SECURITY-728:
--------------------------------------
Assignee: Stefan Guilhen (was: Anil Saldhana)
Check this...
> WebJASPIOptionalAuthenticator does not actually authenticate
> ------------------------------------------------------------
>
> Key: SECURITY-728
> URL: https://issues.jboss.org/browse/SECURITY-728
> Project: PicketBox
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: PIcketBox_4_0_15.Final
> Reporter: arjan tijms
> Assignee: Stefan Guilhen
> Labels: jaspi, jaspic, jsr196, spec_violation
>
> According to the JASPIC specification, a SAM should be invoked for unprotected resources as well as protected resources. Invoking the SAM for unprotected resources is required for pre-emptive authentication.
> This is detailed in section 3.8 of the JSR 196 (JASPIC) specification and is explicitly acknowledged by the spec lead at http://java.net/jira/browse/SERVLET_SPEC-21
> However, the documented {{WebJASPIAuthenticator}} valve is not invoked for unprotected resources. There is an undocumented valve, {{WebJASPIOptionalAuthenticator}}, which can be used, but this one does not actually authenticate.
> See the following fragment:
> {code}
> boolean isValid = sam.isValid(messageInfo, new Subject(), messageLayer, appContext, cbh);
> if (isValid) {
> WebLogger.WEB_SECURITY_LOGGER.debugf("JASPI validation for unprotected request context %s succeeded", request.getServletPath());
> sam.secureResponse(messageInfo, new Subject(), messageLayer, appContext, cbh);
> }
> {code}
> As can be seen, the callbackhandler ({{cbh}}) is *not* processed.
> Additionally, the javadoc comments for {{WebJASPIOptionalAuthenticator}} says calling unprotected resources is optional, but I don't think this is the case:
> {code}
> /**
> * <p>
> * This class implements a JASPI authenticator for unprotected resources. In the JASPI Servlet profile, authentication
> * for unprotected resources is optional but it is still allowed. When performed, the JASPI authentication modules must
> * grant access to the unprotected resources irrespective of the caller, which may be anonymous (i.e, no security info
> * supplied).
> * </p>
> *
> * @author <a href="mailto:sguilhen@redhat.com">Stefan Guilhen</a>
> */
> @SuppressWarnings("unused")
> public class WebJASPIOptionalAuthenticator extends ValveBase {
> {code}
> {{WebJASPIOptionalAuthenticator}} should probably contain the following code in the {{isValid}} if statement:
> {code}
> PasswordValidationCallback pvc = cbh.getPasswordValidationCallback();
> CallerPrincipalCallback cpc = cbh.getCallerPrincipalCallback();
>
> // get the client principal from the callback.
> Principal clientPrincipal = cpc.getPrincipal();
> if (clientPrincipal == null) {
> clientPrincipal = new SimplePrincipal(cpc.getName());
> }
>
> // if the client principal is not a jboss generic principal, we need to build one before registering.
> if (!(clientPrincipal instanceof JBossGenericPrincipal))
> clientPrincipal = this.buildJBossPrincipal(clientSubject, clientPrincipal);
>
> this.register(request, response, clientPrincipal, authMethod, pvc.getUsername(),
> new String(pvc.getPassword()));
> {code}
> (code taken from {{WebJASPIAuthenticator}}).
> Perhaps it's better if the two valves are merged?
--
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, 2 months
[JBoss JIRA] (DROOLS-49) Improve Drools project to support deployment on JBoss Fuse (Apache Karaf) platform
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-49?page=com.atlassian.jira.plugin.... ]
Geoffrey De Smet commented on DROOLS-49:
----------------------------------------
Turns out the pull requests are versus 5.5.x, not master, which explains the <manifestFile>META-INF/MANIFEST.MF</manifestFile> stuff. It's unclear to which extent the changes on master already fix or don't fix this problem.
> Improve Drools project to support deployment on JBoss Fuse (Apache Karaf) platform
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-49
> URL: https://issues.jboss.org/browse/DROOLS-49
> Project: Drools
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5
> Reporter: Charles Moulliard
> Assignee: Mark Proctor
>
> Existing Drools project has already been modified to support OSGI but the work done is incomplete, buggy and cannot be deployed like that on Apache Karaf (JBoss Fuse).
> In order to allow Drools deployment on Karaf container, I suggest that first we prepare a uberjar bundle of Drools project (1) before to decide strategy to adopt to deploy Drools on OSGI platform and expose OSGI service (2)
> Description of work already done
> 1) Add maven-felix bundle, packaging = bundle & define package to be imported/exported for drools-spring, drools-camel, drools-persistence-jpa, drools-decision-tables
> 2) Create a provisioning feature file to deploy Drools project on Apache Karaf 2.3.0
> 3) Create a itest project validating approach on Karaf with pax-exam & drools example
--
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, 2 months
[JBoss JIRA] (AS7-6070) Domain mode: kill an unresponsive JVM
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6070?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6070:
----------------------------------
Assignee: Emanuel Muckenhuber (was: Brian Stansberry)
Fix Version/s: 8.0.0.Alpha1
This seems fairly straightforward, since we already have logic in the testsuite for hard-killing processes.
> Domain mode: kill an unresponsive JVM
> -------------------------------------
>
> Key: AS7-6070
> URL: https://issues.jboss.org/browse/AS7-6070
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Dennis Reed
> Assignee: Emanuel Muckenhuber
> Fix For: 8.0.0.Alpha1
>
>
> If an AS instance gets into a state where it cannot be controlled normally by the host controller, local OS commands must be used to kill it.
> It would be helpful to be able to kill an unresponsive JVM through the management interface.
--
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, 2 months
[JBoss JIRA] (DROOLS-49) Improve Drools project to support deployment on JBoss Fuse (Apache Karaf) platform
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-49?page=com.atlassian.jira.plugin.... ]
Geoffrey De Smet commented on DROOLS-49:
----------------------------------------
I just saw that (at least) some of the pull requests, still use the hack <manifestFile>META-INF/MANIFEST.MF</manifestFile>. Thanks to cvgaviao's pull request in December 2012, we don't use that any more.
I presume you were working on an old clone and some of the issues might have already been fixed by cvgaviao's work.
Please reopen the pulls requests:
- with proper styling (so the changes are clear)
- based on top of the <packaging>bundle</packaging> work of cvgaviao, instead of undoing that work.
- preferably isolated per issue ("bug: improving osgi handling" versus "new feature: osgi-fying more modules"), so non-controversial changes are merged early instead of being delayed with the controversial changes (making them even more complex to understand).
I 'll handle the "bug: improving osgi handling" pull requests.
> Improve Drools project to support deployment on JBoss Fuse (Apache Karaf) platform
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-49
> URL: https://issues.jboss.org/browse/DROOLS-49
> Project: Drools
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5
> Reporter: Charles Moulliard
> Assignee: Mark Proctor
>
> Existing Drools project has already been modified to support OSGI but the work done is incomplete, buggy and cannot be deployed like that on Apache Karaf (JBoss Fuse).
> In order to allow Drools deployment on Karaf container, I suggest that first we prepare a uberjar bundle of Drools project (1) before to decide strategy to adopt to deploy Drools on OSGI platform and expose OSGI service (2)
> Description of work already done
> 1) Add maven-felix bundle, packaging = bundle & define package to be imported/exported for drools-spring, drools-camel, drools-persistence-jpa, drools-decision-tables
> 2) Create a provisioning feature file to deploy Drools project on Apache Karaf 2.3.0
> 3) Create a itest project validating approach on Karaf with pax-exam & drools example
--
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, 2 months
[JBoss JIRA] (AS7-6623) Form field clipping can be improved
by Heiko Braun (JIRA)
Heiko Braun created AS7-6623:
--------------------------------
Summary: Form field clipping can be improved
Key: AS7-6623
URL: https://issues.jboss.org/browse/AS7-6623
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: 7.3.0.Alpha1
The fileds clip at a certain size. Ideally they should allow to see the full value upon hover. Maybe conjunction with a clipping symbol "[...]" ?
--
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, 2 months
[JBoss JIRA] (AS7-6623) Form field clipping can be improved
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6623?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-6623:
-----------------------------
Description: The fields clip at a certain size. Ideally they should allow to see the full value upon hover. Maybe conjunction with a clipping symbol "[...]" ? (was: The fileds clip at a certain size. Ideally they should allow to see the full value upon hover. Maybe conjunction with a clipping symbol "[...]" ?)
> Form field clipping can be improved
> -----------------------------------
>
> Key: AS7-6623
> URL: https://issues.jboss.org/browse/AS7-6623
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Console
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 7.3.0.Alpha1
>
>
> The fields clip at a certain size. Ideally they should allow to see the full value upon hover. Maybe conjunction with a clipping symbol "[...]" ?
--
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, 2 months
[JBoss JIRA] (DROOLS-49) Improve Drools project to support deployment on JBoss Fuse (Apache Karaf) platform
by Charles Moulliard (JIRA)
[ https://issues.jboss.org/browse/DROOLS-49?page=com.atlassian.jira.plugin.... ]
Charles Moulliard commented on DROOLS-49:
-----------------------------------------
So what do you suggest to do ?
> Improve Drools project to support deployment on JBoss Fuse (Apache Karaf) platform
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-49
> URL: https://issues.jboss.org/browse/DROOLS-49
> Project: Drools
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5
> Reporter: Charles Moulliard
> Assignee: Mark Proctor
>
> Existing Drools project has already been modified to support OSGI but the work done is incomplete, buggy and cannot be deployed like that on Apache Karaf (JBoss Fuse).
> In order to allow Drools deployment on Karaf container, I suggest that first we prepare a uberjar bundle of Drools project (1) before to decide strategy to adopt to deploy Drools on OSGI platform and expose OSGI service (2)
> Description of work already done
> 1) Add maven-felix bundle, packaging = bundle & define package to be imported/exported for drools-spring, drools-camel, drools-persistence-jpa, drools-decision-tables
> 2) Create a provisioning feature file to deploy Drools project on Apache Karaf 2.3.0
> 3) Create a itest project validating approach on Karaf with pax-exam & drools example
--
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, 2 months
[JBoss JIRA] (JGRP-1602) AsyncRequestHandler changes
by Bela Ban (JIRA)
Bela Ban created JGRP-1602:
------------------------------
Summary: AsyncRequestHandler changes
Key: JGRP-1602
URL: https://issues.jboss.org/browse/JGRP-1602
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.3
* Add a method to response which allows access to the Message sent back, e.g. sendReply(Message): in this case, the implementor would create its own message object
* Investigate whether to provide separate RequestHandler and AsyncRequestHandler interfaces: does this break MuxRpcDispatcher code ?
--
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, 2 months