May 2013 - jboss-dev-forums - Jboss List Archives

[JBoss Web Development] - jsessionid, plus sign causes double escape error, jboss7 - iis

by Krwyth Nowe

Krwyth Nowe [https://community.jboss.org/people/md1037] created the discussion "jsessionid, plus sign causes double escape error, jboss7 - iis" To view the discussion, visit: https://community.jboss.org/message/819156#819156 -------------------------------------------------------------- We are running Jboss AS7 inside IIS using the ajp connector. Everything works fine except the jsessionid variable causes a 404 error (IIS double escape error) when it has a plus sign in it. Like this: http://site/something.do;jsessionid=x2iV3knb6EjbYrnLjE+0FpVJ.node1?method... http://site/something.do;jsessionid=x2iV3knb6EjbYrnLjE+0FpVJ.node1?method... I could allow IIS to accept double escape requests (security hole), or rewrite the URLs (PITA). Does anyone have another suggestion for either removing the jsessionid or ensuring it doesn't have a plus sign? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/819156#819156] Start a new discussion in JBoss Web Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 7 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Transactions Development] - TransactionMonitoringAndVisualization

by Tom Jenkinson

Tom Jenkinson [https://community.jboss.org/people/tomjenkinson] commented on the document "TransactionMonitoringAndVisualization" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-48255#comment-12145 -------------------------------------------------- You are right Mark, with JTS and JTA we can handle DUPID (we have a retry loop). My recollection was that with JCA inflow we could not modify the branches in any scenario, however looking at the code I see that if we detect that the root Xid is one of ours (FORMATID) we can indeed modify the branches. --------------------------------------------------

12 years, 7 months

1
0
0 / 0

Community Updates, May 16 - May 23

by JBoss Community

=============================================================== Community Updates for May 16 - May 23 =============================================================== Your Content * testing the new list server [https://community.jboss.org/thread/127309] was viewed 13,213 times and replied to by 3 people * No Link to Jboss Nukes [https://community.jboss.org/thread/90785] was viewed 111,562 times and replied to by 3 people Your Connections - Activity by people you are following You don't have any connections yet. Find people and connect! [https://community.jboss.org/people/] Popular Content - The content that is most viewed and participated in * Deploying HTML5 Applications To Openshift [https://community.jboss.org/docs/DOC-17450] * Open Session in View [https://community.jboss.org/docs/DOC-13954] * Data Source Configuration in AS 7 [https://community.jboss.org/docs/DOC-16657] * how I set up a PostgreSQL JDBC Driver on JBoss 7 [https://community.jboss.org/blogs/amartin-blog/2012/02/08/how-to-set-up-a...] * Statement Regarding Security Threat to JBoss Application Server [https://community.jboss.org/blogs/mjc/2011/10/20/statement-regarding-secu...] * EAP binaries available for all developers [https://community.jboss.org/blogs/mark.little/2013/03/07/eap-binaries-ava...] * Re: Jboss admin console password [https://community.jboss.org/message/751359#751359] * Re: java.net.BindException: Address already in use: JVM_Bind [https://community.jboss.org/message/795418#795418] * Re: HTTPS on JBoss AS 7 - truststore configuration [https://community.jboss.org/message/809854#809854] Tips and tricks - Compare Document Versions This feature is so handy you'll wonder where it's been all your life. You can see the full history of a document in Community, and compare any two versions to see what changed between them. When viewing a document just click on the magnifying glass icon next to the version number to see the two most recent versions compared side-by-side. Or, click on Manage versions in the Actions area to see the entire history of the document. Find out more. Not interested in these emails anymore, or want to change how often they come? Update your email preferences by visiting: https://community.jboss.org/user-notification-preferences!input.jspa

12 years, 7 months

1
0
0 / 0

[EJB3 Development] - EJB 3.0 Project with 2.x entity beans

by Marc Anthony Puca

Marc Anthony Puca [https://community.jboss.org/people/marcanthony] created the discussion "EJB 3.0 Project with 2.x entity beans" To view the discussion, visit: https://community.jboss.org/message/818823#818823 -------------------------------------------------------------- Hi to everyone, I have a quick question I hope someone can help me with, I have an EJB 3.0 project with 3.0 session beans and would like to deploy a few 2.x entity beans in the same project, is that possible? I am running jboss 4.2.1 thanks Marc -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/818823#818823] Start a new discussion in EJB3 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 7 months

2
1
0 / 0

[JBoss Transactions Development] - Re: JTA 1.2 Implementation Work

by Paul Robinson

Paul Robinson [https://community.jboss.org/people/paul.robinson] created the discussion "Re: JTA 1.2 Implementation Work" To view the discussion, visit: https://community.jboss.org/message/818842#818842 -------------------------------------------------------------- Mark, > Mark Little wrote: > > No code changes for this is even better then :) It has been a while since that code was written :p Yes, that pleased me too! Thanks for checking. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/818842#818842] Start a new discussion in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 7 months

1
0
0 / 0

[JBoss Transactions Development] - Re: JTA 1.2 Implementation Work

by Paul Robinson

Paul Robinson [https://community.jboss.org/people/paul.robinson] created the discussion "Re: JTA 1.2 Implementation Work" To view the discussion, visit: https://community.jboss.org/message/818698#818698 -------------------------------------------------------------- Thanks Tom, > Tom Jenkinson wrote: > > Also, your description in "Other Spec Changes" omits the fact that com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple::rollback(), endSuspendedRMs() is also invoked. > Updated. > Tom Jenkinson wrote: > > Near as I can work out though, endSuspendedRMs is almost superflous as topLevel* will end ASSOCIATION_SUSPENDED branches anyway? It seems that way to me, but I may well be missing some corner-case. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/818698#818698] Start a new discussion in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 7 months

2
1
0 / 0

Re: [jboss-dev-forums] [JBoss Transactions Development] - TransactionMonitoringAndVisualization

by Mark Little

Mark Little [https://community.jboss.org/people/marklittle] commented on the document "TransactionMonitoringAndVisualization" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-48255#comment-12137 -------------------------------------------------- The "diamond" is something we support in JTS and JTA, including catching and dealing with DUPID exceptions. A lot of the distributed JTS tests were written specifically to test these scenarios. --------------------------------------------------

12 years, 7 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS 7 Development] - Design of AS7 multi-JSF feature

by Bruno Lam

Bruno Lam [https://community.jboss.org/people/qjafcunuas38] commented on the document "Design of AS7 multi-JSF feature" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-47689#comment-12136 -------------------------------------------------- Hi Torben, i didn't resolved it for the moment. I'm continuing to used mojarra ... I'll prefer to use MyFaces instead of Mojarra, because : http://blog.oio.de/2013/04/08/jsf-comparison-myfaces-vs-mojarra/ (https://amxprd0610.outlook.com/owa/redir.aspx?C=sFtHuq608EWv1XkqLxJzhaaoS...) I'll will try asap with new JBoss EAP Beta version. I think it's not a trouble with RichFaces, because there is the same error without RichFaces component, and only with an outputScript (something like <h:outputScript library="javax.faces" name="jsf.js" />). --------------------------------------------------

12 years, 7 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss Transactions Development] - TransactionMonitoringAndVisualization

by Tom Jenkinson

Tom Jenkinson [https://community.jboss.org/people/tomjenkinson] commented on the document "TransactionMonitoringAndVisualization" To view all comments on this document, visit: https://community.jboss.org/docs/DOC-48255#comment-12135 -------------------------------------------------- Hi Paul, Just to follow up on here re our conversation yesterday. The limitations insofar as diamonds are concerned are as follows: * With JTS and WSAT/JTA each server creates its own unique branch for the same RM, which unfortunately means that you can get a distributed dead lock * Distributed JTA has been implemented to leverage the JCA inflow code. This means that it suffers from the same limitations as JCA in that as with JCA we are unable to modify the xid during propagation and so two different servers can end up enlisting the same resource manager with the same XID resulting in a duplicate XID exception. I hope that helps to clarify, Tom --------------------------------------------------

12 years, 7 months

1
0
0 / 0

[JBoss Transactions Development] - Narayana Release Process

by Tom Jenkinson

Tom Jenkinson [https://community.jboss.org/people/tomjenkinson] modified the document: "Narayana Release Process" To view the document, visit: https://community.jboss.org/docs/DOC-17433 -------------------------------------------------------------- This page provides a list of instructions that must be done *in order* when doing a release of Narayana. h2. Check JIRA 1. Check all issues resolved. 2. Create next point release version if not exists - this is so you can push issues in step 3 below. 3. Unresolved issues should be resolved or pushed. h2. Check Hudson Ensure no test failures in the group of hudson tests, for the branch you intend to release. h2. Raise AS7 component upgrade request in Jira Prepare for a PR to update AS7. 1. https://issues.jboss.org/browse/AS7 https://issues.jboss.org/browse/AS7 2. create a new 'component update' issue.1. Ensure the module is set to 'transactions' 2. select an appropriate 'fix for'. 3. Assign it to yourself. h2. Do Release h3. Git Branches (4.17 and 5 only) Must be done first as the build-release-packages.xml relies on the tag being available cd $NARAYANA_SRC/scripts pre-release.sh <next version, e.g: 5.0.0.M3> h3. Create the AS7 pull request branch and roll the jbosstm/jboss-as branch to next SNAPSHOT (UN-TESTED COMMANDS!!) BRANCH=4_BRANCH AS_BRANCH=master JIRA=AS7-5815 CURRENT=4.17.2.Final NEXT=4.17.3.Final git clone git@github.com:jbosstm/jboss-as.git cd jboss-as git checkout $BRANCH git remote add upstream git://github.com/jbossas/jboss-as.git git pull --rebase --ff-only upstream $AS_BRANCH sed -i "s/$CURRENT-SNAPSHOT/$CURRENT/g" pom.xml git commit -am "Upgrade Narayana to $CURRENT" # should use git merge-base $BRANCH upstream/master # You will need to resolve som merge conflicts. Most likely around version numbers. git rebase -i HEAD~10 git checkout -b "${JIRA}_Upgrading_Narayana_to_${CURRENT}" git checkout $BRANCH sed -i "s/$CURRENT/$NEXT-SNAPSHOT/g" pom.xml git commit -am "Upgrade Narayana to $NEXT-SNAPSHOT" git push origin "${JIRA}_Upgrading_Narayana_to_${CURRENT}" git push origin $BRANCH h2. Build and release h3. blacktie windows binaries CURRENT=<Version to release. e.g 5.0.0.M2> On Windows: rem You need to build the windows version separately as we don't support cross compile git clone git(a)github.com (mailto:git@github.com):jbosstm/blacktie.git build.bat install -DskipTests scp blacktie/target/blacktie-$CURRENT-vc9x32-bin.zip <user>@<ipaddress>: h3. Narayana upload CURRENT=<Version to release. e.g 5.0.0.M2> mkdir -p ~/narayana/filemgmt.jboss.org/ On Linux: sshfs jbosstm(a)filemgmt.jboss.org (mailto:jbosstm@filemgmt.jboss.org): ~/narayana/filemgmt.jboss.org/ On MacOS: sshfs -o defer_permissions jbosstm(a)filemgmt.jboss.org (mailto:jbosstm@filemgmt.jboss.org): ~/narayana/filemgmt.jboss.org/ git clone git(a)github.com (mailto:git@github.com):jbosstm/narayana.git cd narayana git checkout $CURRENT On Linux: ant -f build-release-pkgs.xml dist downloads docs magnolia -Drsync=false On MacOS: ant -f build-release-pkgs.xml dist downloads docs magnolia h3. svn branches #Make sure your checkout has no local changes svn update svn status POINT_VERSION=5 NEXT_POINT_VERSION=6 #Update the version in text files find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final-SNAPSHOT/4\116\2$POINT_VERSION\3Final/" svn commit -m "Updated to version 4.16.$POINT_VERSION.Final" #Tag the release: svn cp https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16 https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_4_Final/ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${POINT_V... -m "4.16.$POINT_VERSION" #Bump to next version using similar find to above find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v target | xargs grep -l "4[._]16" | xargs sed -i "s/4$[._]$16$[._]$${POINT_VERSION}$[._]$Final/4\116\2${NEXT_POINT_VERSION}\3Final-SNAPSHOT/" svn commit -m "Updated to version 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" #Update the maven version of jbossts in our fork of JBossAS: https://github.com/jbosstm/jboss-as https://github.com/jbosstm/jboss-as git checkout 4_16_BRANCH git pull --rebase --ff-only #Check no local changes git status sed -i "s/4.16.${POINT_VERSION}.Final-SNAPSHOT/4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT/g" pom.xml git commit -am "Updated to 4.16.${NEXT_POINT_VERSION}.Final-SNAPSHOT" git push #Build and deploy the release to nexus staging: mkdir ~/filemgmt.jboss.org/ sshfs -o defer_permissions mailto:jbosstm@filemgmt.jboss.org jbosstm(a)filemgmt.jboss.org: ~/filemgmt.jboss.org/ svn switch https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_$ https://svn.jboss.org/repos/labs/labs/jbosstm/tags/JBOSSTS_4_16_${NEXT_PO... ant -f build-release-pkgs.xml dist mvn-repository downloads magnolia h3. h2. Release the artifact through Nexus 1. https://repository.jboss.org/nexus/index.html#welcome https://repository.jboss.org/nexus/index.html#welcome 2. login 3. "Staging Repositories" 4. Click tickbox for your repo 5. Click "Close" 6. Don't worry about a description, just click "Close" 7. Click tickbox after it is closed 8. Click "Release" 9. Again a description doesn't matter h2. Push Upstream Check that the pull request will work. *If it doesn't and it requires Narayana changes you *have* to rev the version number - DON'T attempt to re-release with the same version number:* JIRA=AS7-5815 CURRENT=4.17.2.Final git clone mailto:git@github.com git@github.com:jbosstm/jboss-as.git cd jboss-as git checkout "${JIRA}_Upgrading_Narayana_to_${CURRENT}" rm -rf ~/.m2/repository/org/jboss/jbossts rm -rf ~/.m2/repository/org/jboss/narayana ./build.sh clean install 1. Raise the pull request using our branch 2. Update http://172.17.131.2/view/Narayana+BlackTie-release/job/release-narayana-A... this job to run our CI over the PR. You need to re-run this every time you change the PR, top make sure it still works. 3. Once merged, resolve the AS7 Jira issue. 4. Once merged, rebase the jbosstm/jboss-as 5_BRANCH|4_BRANCH branch with the updated wildfly master branch h2. JIRA Release 1. Close all issues for the release 2. Mark as released (Need admin permissions) h2. Update Website Update the Narayana community site: * Login to Magnolia* https://www.jboss.org/author/.magnolia/pages/adminCentral.html https://www.jboss.org/author/.magnolia/pages/adminCentral.html * Login with credentials: Tom and Paul know these, ask them. * Documentation* Browse to 'jbosstm/documentation' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.documentation.4.16.5.Final.xml' file * Long left click on the file name and replace the '.' with '_'. * Right click on the new file and click 'move' * Drag the file to the top of the documentation list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Downloads* Browse to 'jbosstm/downloads' * right click on 'downloads' and select 'import' * browse to the location of the 'website.jbosstm.downloads.4.16.5.Final.xml' file * Long left click on the file name and replace the '.' with '_'. * Right click on the new file and click 'move' * Drag the file to the top of the downloads list. * Right click on the new page and select 'open page...' * Check that the page looks right and that the download links work * Right click on the new page and select 'activate' * You now need to wait for the page to be moderated before it will appear. * Announcement* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'announcement' pane * Update the announcement for this release. * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. * Release notes* Right click on 'jbosstm' and select 'open page...' * Click edit on the 'getting started' pane on the right-hand-side * Edit the release notes url to point to the release notes for this version * Click save * Right click on 'jbosstm' and select 'activate changes' * You now need to wait for the page to be moderated before it will appear. h2. Update CI Update jobs, to use the new Version (quickstarts, etc). Need a ful list of steps here. h2. Checked the released Quickstarts Make sure the released quickstarts run against the released Narayana. Do this by updating this job: http://172.17.131.2/view/Narayana+BlackTie-release/job/release-btny-naray... http://172.17.131.2/view/Narayana+BlackTie-release/job/release-btny-naray... Need a ful list of steps here. h2. Promote NOTE: It is worth waiting for the merge of the pull request before advertising, or at least wait for the merge build notification first ;) Promote the release through the following channels: 1. Email jbossts-announce(a)lists.jboss.org (mailto:jbossts-announce@lists.jboss.org) 2. Forum 3. Blog: project in (jbtm, blacktie) AND fixversion = "5.0.0.M2" AND priority >= major AND issuetype not in (Bug, task) AND resolution not in ("Duplicate Issue", Rejected, "Won't Fix", "Out of Date", "Cannot Reproduce Bug") -------------------------------------------------------------- Comment by going to Community [https://community.jboss.org/docs/DOC-17433] Create a new document in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]

12 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2013