March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1160) IronJacamar 1.0.25.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1160: -------------------------------------- Summary: IronJacamar 1.0.25.Final Key: JBJCA-1160 URL: https://issues.jboss.org/browse/JBJCA-1160 Project: IronJacamar Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.25.Final Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1818) Discovery protocol for Google Cloud Storage

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1818?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1818: --------------------------- Description: Write a discovery protocol based on Google Cloud Storage. This can then be used with Google Compute Engine. Using S3_PING as starting point should be simple, see [1]. An overview of the API is at [2]. [1] https://developers.google.com/storage/docs/migrating [2] https://developers.google.com/storage/docs/xml-api-overview was: Write a discovery protocol based on Google Cloud Storage. This can then be used with Google Compute Engine. Using S3_PING as starting point should be simple, see [1]. [1] https://developers.google.com/storage/docs/migrating > Discovery protocol for Google Cloud Storage > ------------------------------------------- > > Key: JGRP-1818 > URL: https://issues.jboss.org/browse/JGRP-1818 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > Write a discovery protocol based on Google Cloud Storage. This can then be used with Google Compute Engine. Using S3_PING as starting point should be simple, see [1]. > An overview of the API is at [2]. > [1] https://developers.google.com/storage/docs/migrating > [2] https://developers.google.com/storage/docs/xml-api-overview -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1818) Discovery protocol for Google Cloud Storage

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/JGRP-1818?page=com.atlassian.jira.plugin.... ] Ales Justin updated JGRP-1818: ------------------------------ Summary: Discovery protocol for Google Cloud Storage (was: Discovery protocol for Gogle Cloud Storage) > Discovery protocol for Google Cloud Storage > ------------------------------------------- > > Key: JGRP-1818 > URL: https://issues.jboss.org/browse/JGRP-1818 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > Write a discovery protocol based on Google Cloud Storage. This can then be used with Google Compute Engine. Using S3_PING as starting point should be simple, see [1]. > [1] https://developers.google.com/storage/docs/migrating -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1818) Discovery protocol for Gogle Cloud Storage

by Bela Ban (JIRA)

Bela Ban created JGRP-1818: ------------------------------ Summary: Discovery protocol for Gogle Cloud Storage Key: JGRP-1818 URL: https://issues.jboss.org/browse/JGRP-1818 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.5 Write a discovery protocol based on Google Cloud Storage. This can then be used with Google Compute Engine. Using S3_PING as starting point should be simple, see [1]. [1] https://developers.google.com/storage/docs/migrating -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3195) VFS root creation is wrong on Windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3195?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3195: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1082491 > VFS root creation is wrong on Windows > ------------------------------------- > > Key: WFLY-3195 > URL: https://issues.jboss.org/browse/WFLY-3195 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VFS > Reporter: David Lloyd > Assignee: Tomaz Cerar > > This may ultimately be a problem with VFS, or with WildFly. > We create our deployment root with an absolute VFS path of {{/content}} (see https://github.com/wildfly/wildfly/blob/dca817f584a24525c5a2f2f655aefed6d... for details). However on Windows, we have special path handling (see https://github.com/jbossas/jboss-vfs/blob/eff9d8ae6d49e30038126304b5858c6... for details) which causes these paths to become absolute with a drive letter (e.g. {{W:/tmp/blah/foo/content/...}}) but only on windows. This makes writing policy files (for EAP) quite difficult, as well as just being generally wrong. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3195) VFS root creation is wrong on Windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3195?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3195: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1082491, https://bugzilla.redhat.com/show_bug.cgi?id=1082518 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1082491) > VFS root creation is wrong on Windows > ------------------------------------- > > Key: WFLY-3195 > URL: https://issues.jboss.org/browse/WFLY-3195 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VFS > Reporter: David Lloyd > Assignee: Tomaz Cerar > > This may ultimately be a problem with VFS, or with WildFly. > We create our deployment root with an absolute VFS path of {{/content}} (see https://github.com/wildfly/wildfly/blob/dca817f584a24525c5a2f2f655aefed6d... for details). However on Windows, we have special path handling (see https://github.com/jbossas/jboss-vfs/blob/eff9d8ae6d49e30038126304b5858c6... for details) which causes these paths to become absolute with a drive letter (e.g. {{W:/tmp/blah/foo/content/...}}) but only on windows. This makes writing policy files (for EAP) quite difficult, as well as just being generally wrong. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3195) VFS root creation is wrong on Windows

by David Lloyd (JIRA)

David Lloyd created WFLY-3195: --------------------------------- Summary: VFS root creation is wrong on Windows Key: WFLY-3195 URL: https://issues.jboss.org/browse/WFLY-3195 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: VFS Reporter: David Lloyd Assignee: David Lloyd This may ultimately be a problem with VFS, or with WildFly. We create our deployment root with an absolute VFS path of {{/content}} (see https://github.com/wildfly/wildfly/blob/dca817f584a24525c5a2f2f655aefed6d... for details). However on Windows, we have special path handling (see https://github.com/jbossas/jboss-vfs/blob/eff9d8ae6d49e30038126304b5858c6... for details) which causes these paths to become absolute with a drive letter (e.g. {{W:/tmp/blah/foo/content/...}}) but only on windows. This makes writing policy files (for EAP) quite difficult, as well as just being generally wrong. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3195) VFS root creation is wrong on Windows

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3195?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-3195: --------------------------------- Assignee: Tomaz Cerar (was: David Lloyd) > VFS root creation is wrong on Windows > ------------------------------------- > > Key: WFLY-3195 > URL: https://issues.jboss.org/browse/WFLY-3195 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VFS > Reporter: David Lloyd > Assignee: Tomaz Cerar > > This may ultimately be a problem with VFS, or with WildFly. > We create our deployment root with an absolute VFS path of {{/content}} (see https://github.com/wildfly/wildfly/blob/dca817f584a24525c5a2f2f655aefed6d... for details). However on Windows, we have special path handling (see https://github.com/jbossas/jboss-vfs/blob/eff9d8ae6d49e30038126304b5858c6... for details) which causes these paths to become absolute with a drive letter (e.g. {{W:/tmp/blah/foo/content/...}}) but only on windows. This makes writing policy files (for EAP) quite difficult, as well as just being generally wrong. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1159) ConnectionListener leaked if TSR throws IllegalStateException

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1159?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1159. ------------------------------------ Resolution: Done > ConnectionListener leaked if TSR throws IllegalStateException > ------------------------------------------------------------- > > Key: JBJCA-1159 > URL: https://issues.jboss.org/browse/JBJCA-1159 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.24.Final, 1.1.4.Final > Environment: AS7 EAP6.1 > Reporter: gui borland > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.25.Final, 1.1.5.Final, 1.2.0.Beta1 > > > When a connection is retrieved from the MCP, ironjacamar will register it to ongoing JTA transaction. However, if the ongoing TX is not 'active' anymore the connection is lost. > The code of AbstractPool demonstrates the problem. The call to getLock will throw an exception if the current TX is not active anymore and the cl is not returned to the pool. > This issue can be reproduced on AS7 by using any EJB that requires a tx and does something with a DB connection. Put a breakpoint in the code below after retrieving the connectionlistener, and then wait for the transaction to timeout. Once that's done, continue the thread. The connection is not release (can be seen in JMX) > We have noticed this problem regularly during our performance tests. > {code} > ConnectionListener cl = mcp.getConnection(subject, cri); > if (trace) > log.tracef("Got connection from pool tracked by transaction=%s tx=%s", cl, trackByTransaction); > TransactionSynchronizationRegistry tsr = getTransactionSynchronizationRegistry(); > Lock lock = getLock(); > try > { > lock.lockInterruptibly(); > } > catch (InterruptedException ie) > { > Thread.interrupted(); > throw new ResourceException(bundle.unableObtainLock(), ie); > } > {code} > It seems this issue was introduced by changes done for https://issues.jboss.org/browse/JBJCA-572 -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3194) ApplicationClient container can not use a declarative method to activate EJBClientInterceptors

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-3194?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink reassigned WFLY-3194: -------------------------------------- Assignee: Stuart Douglas > ApplicationClient container can not use a declarative method to activate EJBClientInterceptors > ---------------------------------------------------------------------------------------------- > > Key: WFLY-3194 > URL: https://issues.jboss.org/browse/WFLY-3194 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Client > Affects Versions: 8.0.0.Final > Environment: appclient > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Labels: ejb > > With the java services approach it is possible to add a client side interceptor by adding the services file META-INF/services/org.jboss.ejb.client.EJBClientInterceptor to activate the interceptor if the class is accessable. > The file must be added to the client.jar in case of a simple standalone client. > And to the ejb.jar if the interceptor is used inside a server application. > For the appclient I expect that add this file to > EAR/client.jar/META-INF/services > will do the same. > Nevertheless adding the file to ear/META_INF ear/ejb.jar/META-INF do not woth either. > Also adding the class to the client.jar, as ear module or as server module with dependency did not work. > All theses Interceptors can be used if the client Main method add this with the JBoss API. > A working example can be found here > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client/ap... > For the example with the services approach try > https://github.com/wfink/jboss-eap-quickstarts/tree/application-client-wi... -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014