Switch to use TransactionSynchronizationRegistry.registerInterposedSynchronization?
by Scott Marlow
We are supposed to be able to use
TransactionSynchronizationRegistry.registerInterposedSynchronization
(TSR) in our containers but I wanted to bring up an ordering issue that
can happen.
If you look at http://pastie.org/1836698, you can see what happened when
Hibernate registered a synchronization object with the TSR and we tried
after to get a database connection from the connection pool.
Basically, once a synchronization object is registered with the TSR, the
other way of registering a synchronization object through the
Transaction registerSynchronization() cannot be used (or you get the
above linked IllegalStateException error).
The short term fix was to avoid registering Hibernate with the TSR and
instead use the Transaction registerSynchronization(). This helped
avoid the ISE exception as the TSR sync ordering check is avoided.
The Transaction registerSynchronization(), has no ordering requirements
but as we have seen, the TSR registerInterposedSynchronization does.
I think we need to be consistent across our projects and either use TSR
or avoid it (to avoid the "Synchronizations are not allowed!" JTA
error). If/when we use it, we need to coordinate the switch over to it,
so that all projects have time to switch to it.
I'm hoping someone will tell me that there is an easier path to use TSR
registerInterposedSynchronization in some of our projects. What do you
think?
The other question, is how/when we should we coordinate a switch over to
use TSR (assuming there is agreement that we should coordinate the switch)?
Scott
13 years, 11 months
SPNEGO authentication fails loading configuration
by Christoph Gostner
Hi,
I'm running into problems using the SPNEGO authenticator in AS7.
I created a module with the costumized picketbox jar, modified the
Authenticators.properties in jbossweb-7.0.0.CR1.jar and deployed the test
toolkit.
At first sight the deployment process works. But testing the application,
it can't find the required login modules configured in standalone.xml.
So I debugged the complete process and compared my application with a
working
BASIC authentication jar.
Deploying the BasicAuthentication.jar, the required configuration is set in
JaasConfigurationService.start(...). The configuration includes all the
login
modules, configured in standalone.xml.
When I deploy the negotiation toolkit, the configuration is not set. The
authentication process tries to load the configuration in
Configuration.getConfiguration()
but a new configuration instance is created with no login modules in it.
The authenticator is a subclass of AuthenticatorBase.
It seems that JBoss doesn't recognize that the application is JAAS enabled.
I don't see the difference between the BASIC authentication application and
SPNEGO toolkit. Has somebody an explanation for this phenomenon?
Christoph
13 years, 11 months
Secure HTTP API Endpoint
by Heiko Braun
I would suggest we do provide an out-the-box config that secures the HTTP endpoint:
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<users>
<user username="admin">
<password>password</password>
</user>
</users>
</authentication>
</security-realm>
</security-realms>
</management>
Any objections or good reasons not to do it?
Ike
13 years, 11 months
Re: [jboss-as7-dev] jboss-as7-dev Digest, Vol 7, Issue 34
by Michael Musgrove
Can you give me an example of what other projects are providing you with
or indicate what you prefer. Then I can look into adding it.
BTW AS7 will be consuming JBOSSTS_4_14_0_Final so what is the process
for making changes.
> Can these TxStats be accessed via something other than JMX? If at all
> possible I want the AS management layer (in the AS transactions module)
> to not rely on JMX to pull data from subsystems.
>
> On 5/11/11 9:42 AM, Michael Musgrove wrote:
>> Can you clarify what it is that you need to know. I don't understand where these attributes are coming from nor what their values mean.
>>
>> We do have various beans that we have, in the past, exposed via JMX or via RHQ. For example, consider the first attribute "core-environment" => .... I guess this is referring to our CoreEnvironment bean which does have a property called socketProcessIdPort which we use to facilitate creation of unique ids and it also has a property called nodeIdentifier which we use to ensure that different recovery managers don't end up recovering each others transactions. But there are also other properties in that bean which your snippet does not mention.
>>
>> The enable-statistics property simply enables metrics gathering for transaction counts (heuristics, commits etc). Once enabled the statistics can be retrieved from our TxStats MBean.
>>
>> Mike
>>
>>
>> ----- Original Message -----
>>
>>>> From: "Heiko Braun"<hbraun(a)redhat.com>
>>>> To:"jboss-as7-dev(a)lists.jboss.org Development"<jboss-as7-dev(a)lists.jboss.org>
>>>> Sent: Tuesday, May 10, 2011 9:07:24 AM
>>>> Subject: [jboss-as7-dev] TX subsystem management use cases
>>>>
>>>>
>>>>
>>>> Can anyone shed some light on the management op's for the transaction
>>>> subsystem?
>>>> The attribute names indicate more sophisticated features, like
>>>> statistics.
>>>>
>>>> I would need to know how to work with this data in order expose
>>>> reasonable functionality through the web UI.
>>>>
>>>> [domain@localhost:9999 /]
>>>> /profile=default/subsystem=transactions:read-resource(recursive=true)
>>>> {
>>>> "outcome" => "success",
>>>> "result" => {
>>>> "core-environment" => {
>>>> "socket-binding" => "txn-socket-process-id",
>>>> "node-identifier" => undefined
>>>> },
>>>> "recovery-environment" => {
>>>> "socket-binding" => "txn-recovery-environment",
>>>> "status-socket-binding" => "txn-status-manager"
>>>> },
>>>> "coordinator-environment" => {
>>>> "enable-statistics" => undefined,
>>>> "default-timeout" => undefined
>>>> },
>>>> "object-store" => {
>>>> "relative-to" => undefined,
>>>> "path" => undefined
>>>> }
>>>> },
>>>> "compensating-operation" => undefined
>>>> }
>>>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
13 years, 11 months
Changes to .jsp in an exploded deployment no longer picked up?
by Jaikiran Pai
One of the very useful features in previous JBoss AS versions was the
ability of the server to identify and pick up changes to a .jsp page in
an exploded deployment and serve the updated content on next request.
Trying this out in JBoss AS 7.0.0.Beta3, I see that this no longer works:
1) Create and deploy a test.war (along with a test.war.dodeploy) in the
standalone/deployments.
2) test.war contains a test.jsp with an intentional syntax error in it
3) Access the jsp via browser and see the (expected) compilation error.
Now open the test.jsp file in a text editor, from the exploded test.war
deployment, and edit it to fix the error
4) Access the jsp via browser again. Tried it more than once. I still
see the compilation failure i.e. the jsp changes aren't being picked up
anymore. I had to undeploy and redeploy the exploded deployment for the
changes to be picked up.
I remember that in previous versions of AS there were some parameters
for the jsp compiler/executor which by default enabled this check for
jsp changes. Has this changed in AS7? Where and what values are set
currently? Or has this got something to do with the way we handle
exploded deployment in AS7?
-Jaikiran
13 years, 12 months
Consolidate Arquillian test infrastructure
by Thomas Diesler
I picked this up today and continued here
https://github.com/tdiesler/jboss-as/tree/as734
Status
------
* all references to ARQ Alpha4.SP are gone
* embedded/remote containers excluded from the build
* arquillian common + service migrated to Beta1
* all testsuites that are part of the normal build use arquillian
modules (i.e. not arquillian2)
* arquilllian2, demos2, testsuite2 are there for reference only
* mvn -DskipTests clean install should be ok
* lots of test failures expected
Next
----
* work through the testsuites (i.e. smoke, etc) and make the tests pass
against the Beta1 arquillian service
* when tests pass move the them from testsuite2 to testsuite
* get rid of testsuite2 and arquillian2
* send the pull request
I suggest we send the pull request when there is a significant chunk of
tests that pass against the ARQ Beta1 service. Folks can then help to
get the remaining @Ignores sorted out.
I'll pick this up tomorrow again.
cheers
-thomas
On 05/27/2011 08:09 AM, Andrew Lee Rubinger wrote:
> https://github.com/ALRubinger/jboss-as/commit/eaf0412be816d6ed23239424cdd...
>
>
> This has been rebased off upstream/master.
>
> S,
> ALR
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
13 years, 12 months
mappedname behavior ?
by Max Rydahl Andersen
Hi,
I've started trying to use various examples about JEE5/JEE6 which all seem to use mappedname as Glassfish, Weblogic and recently Websphere is using it (as a name that can be used at both declaration and resource lookup time within the same module)
I know that mappendname is left unspecified in the spec, but it seems most other JEE vendors have aligned (or at least seem to have aligned).
>From what I can understand and see JBoss EJB3 have had different implementations of this over time and in AS 7 have moved to simply completely ignore the mappedname attribute.
Does there exist any forum threads and documentation (beyond the that outlines
the reasons why JBoss EJB3 isn't aligning with what seems to be the consensus across the various servers ?
I'm asking since it would make not only users but also tool developers life much easier if one could actually write and generate almost portable code ;)
/max
http://about.me/maxandersen
13 years, 12 months
newbie doubts: features/release schedule
by Geraldo Augusto de Oliveira Netto
Hi Guys,
How are you doing out there?
I'd like to know
if there is any list of features that will be included on as7?
and also if there is any release schedule defined?
I read a lot of things at the web, but did not find any `official information`
Kind Regards and Best Wishes,
Geraldo Netto
13 years, 12 months
