[JBoss JIRA] Created: (JBAS-3824) Fix environment context for EJB2.1 and Servlets
by Thomas Diesler (JIRA)
Fix environment context for EJB2.1 and Servlets
-----------------------------------------------
Key: JBAS-3824
URL: http://jira.jboss.com/jira/browse/JBAS-3824
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: JBossAS-5.0.0.CR1
/home/tdiesler/svn/jbossws/trunk/src/test
[tdiesler@tdvaio test]$ ant -Dtest=jaxrpc/enventry test
tests-main:
[junit] Running org.jboss.test.ws.jaxrpc.enventry.EnvEntryEJBTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.982 sec
[junit] Test org.jboss.test.ws.jaxrpc.enventry.EnvEntryEJBTestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 3 sec
[junit] Test org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase FAILED
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBCACHE-784) "Random" TimeoutException occurs after CacheLoader get() returns
by James Hickey (JIRA)
"Random" TimeoutException occurs after CacheLoader get() returns
----------------------------------------------------------------
Key: JBCACHE-784
URL: http://jira.jboss.com/jira/browse/JBCACHE-784
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Cache loaders
Affects Versions: 1.4.0
Environment: JBCache 1.4.0GA working in REPL_ASYNC mode on multiple Weblogic 8.1 instances (pessimistic locking), no eviction policy
Reporter: James Hickey
Assigned To: Manik Surtani
We experience a strange issue which happens every so often whereby shortly after one of our replicated cache instances calls it's CacheLoader.get() to populate a particular FQN, a TimeoutException occurs - It is extremely difficult to reproduce but the scenario/stack trace follows:
The below exception is thrown 15 secs (configured timeout) AFTER the cache loader's get() method successfully returns (can see this as we have debugging in the cache loader). Subsequent calls are instantaneously successful and do not result in a further call to the cacheloader.
It looks to me like it could possibly be some kind of tx/locking/thread contention issue, as it happens more often than not where we have approx 10-20 threads which have all resulted in a call to the cache loader in a short space of time.
Any advice/opinion would be appreciated
Thanks
James
org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/demandload/db/gps/ipb/security/sdm/840/SECNO/DB0028807589, calle
r=GlobalTransaction:<10.152.103.22:28680>:363, lock=write owner=GlobalTransaction:<10.152.103.22:28680>:362 (org.jboss.cache.lock.Lo
ckStrategyReadCommitted@10e4fd3)
at org.jboss.cache.Node.acquire(Node.java:407)
at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:231)
at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:166)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.CacheLoaderInterceptor.invoke(CacheLoaderInterceptor.java:197)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:32)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.CacheStoreInterceptor.invoke(CacheStoreInterceptor.java:135)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:345)
at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:156)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:138)
at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5535)
at org.jboss.cache.TreeCache.get(TreeCache.java:3485)
at org.jboss.cache.TreeCache.get(TreeCache.java:3466)
at org.jboss.cache.TreeCache.get(TreeCache.java:3453)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBCACHE-1026) Concurrent creation of nodes fails with optimistic locking, even if nodes are empty and contain no data.
by Manik Surtani (JIRA)
Concurrent creation of nodes fails with optimistic locking, even if nodes are empty and contain no data.
--------------------------------------------------------------------------------------------------------
Key: JBCACHE-1026
URL: http://jira.jboss.com/jira/browse/JBCACHE-1026
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.4.1.SP3
Reporter: Manik Surtani
Assigned To: Manik Surtani
Priority: Minor
Fix For: 2.0.0.CR1, 2.0.0.GA, 1.4.1.SP4
Create /parent/child1 and /parent/child2 concurrently. This is a race condition where when trying to validate the 2 txs, both txs have /parent marked as "created" in their workspace. When tx1 commits, this succeeds. When tx2 tries to commit, ths fails validation since /parent exists in the tree even though it is marked as created in tx2's workspace.
This manifests itself in exceptions such as
org.jboss.cache.optimistic.DataVersioningException: Tx attempted to create /parent anew. It has already been created since this tx started by another (possibly remote) tx.
Now this is VALID behaviour since we shouldn't attempt to create /parent twice, but as an optimisation, it should be allowed to succeed IF when tx2 attempts to validate, the node exists in the tree AND doesn't contain any data or the node does not exist in the workspace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBPORTAL-1361) error in buildmagic.ent
by Luca Stancapiano (JIRA)
error in buildmagic.ent
-----------------------
Key: JBPORTAL-1361
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1361
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 3.2 Final
Environment: eclipse 3.2.2 , ant
Reporter: Luca Stancapiano
Assigned To: Julien Viet
Fix For: 3.2 Final
I'm using jbossportal taken from http://anonsvn.jboss.org/repos/portal/trunk
when I compile through build.xml into build project of jbossportal, I have this error:
Buildfile: /root/workspace_portal_trunk/build/build.xml
check.inhibit.downloads:
createthirdparty:
_buildmagic:init:
Trying to override old definition of task property
_buildmagic:init:module-local-properties:
_buildmagic:init:project-local-properties:
_buildmagic:init:buildlog:
BUILD FAILED
/root/workspace_portal_trunk/tools/etc/buildfragments/buildmagic.ent:152: taskdef A class needed by class org.jboss.portal.common.junit.ant.ConfigurableJUnitTask cannot be found: junit/framework/Test
Total time: 1 second
in buildmagic.ent : 152 I have this code:
<path id="junit_.task.classpath">
<pathelement location="${project.tools}/lib/explode.jar"/>
</path>
<taskdef
name="junit_"
classname="org.jboss.portal.common.junit.ant.ConfigurableJUnitTask"
classpathref="junit_.task.classpath"/>
I don't know what is its usefulness but if I comment the entire block, build succeed. I send you buildmagic.ent with commented block
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Resolved: (JBAS-3047) WebApps ignore java2ClassLoadingCompliance in jboss-web.xml
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3047?page=all ]
Scott M Stark resolved JBAS-3047.
---------------------------------
Resolution: Done
> WebApps ignore java2ClassLoadingCompliance in jboss-web.xml
> -----------------------------------------------------------
>
> Key: JBAS-3047
> URL: http://jira.jboss.com/jira/browse/JBAS-3047
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service, ClassLoading
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: SuSE Linux 9.1, Sun JDK 1.4.2_11
> Reporter: Kevin Yeung
> Assigned To: Scott M Stark
> Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3
>
>
> I deploy the same jar file (kevin.jar) in a war and its containing ear. In the war, I have a test JSP that loads a class from kevin.jar and displays its class loader.
> The class is loaded using the war class loader. So, I added the following to jboss-web.xml under the war's WEB-INF
> <class-loading java2ClassLoadingCompliance='true'>
> Didn't work. So I added this:
> <class-loading java2ClassLoadingCompliance='true'>
> <loader-repository>
> dot.com:loader=unique-archive-name
> <loader-repository-config>
> java2ParentDelegaton=true
> </loader-repository-config>
> </loader-repository>
> </class-loading>
> Didn't work either. Class continues to be loaded from war's class loader.
> Deleted JAR from WEB-INF/lib and class is now loaded from ear.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Reopened: (JBAS-3047) WebApps ignore java2ClassLoadingCompliance in jboss-web.xml
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3047?page=all ]
Scott M Stark reopened JBAS-3047:
---------------------------------
Assignee: Scott M Stark
> WebApps ignore java2ClassLoadingCompliance in jboss-web.xml
> -----------------------------------------------------------
>
> Key: JBAS-3047
> URL: http://jira.jboss.com/jira/browse/JBAS-3047
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service, ClassLoading
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: SuSE Linux 9.1, Sun JDK 1.4.2_11
> Reporter: Kevin Yeung
> Assigned To: Scott M Stark
> Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.0.GA
>
>
> I deploy the same jar file (kevin.jar) in a war and its containing ear. In the war, I have a test JSP that loads a class from kevin.jar and displays its class loader.
> The class is loaded using the war class loader. So, I added the following to jboss-web.xml under the war's WEB-INF
> <class-loading java2ClassLoadingCompliance='true'>
> Didn't work. So I added this:
> <class-loading java2ClassLoadingCompliance='true'>
> <loader-repository>
> dot.com:loader=unique-archive-name
> <loader-repository-config>
> java2ParentDelegaton=true
> </loader-repository-config>
> </loader-repository>
> </class-loading>
> Didn't work either. Class continues to be loaded from war's class loader.
> Deleted JAR from WEB-INF/lib and class is now loaded from ear.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Updated: (JBAS-3047) WebApps ignore java2ClassLoadingCompliance in jboss-web.xml
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3047?page=all ]
Scott M Stark updated JBAS-3047:
--------------------------------
Comment: was deleted
> WebApps ignore java2ClassLoadingCompliance in jboss-web.xml
> -----------------------------------------------------------
>
> Key: JBAS-3047
> URL: http://jira.jboss.com/jira/browse/JBAS-3047
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service, ClassLoading
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: SuSE Linux 9.1, Sun JDK 1.4.2_11
> Reporter: Kevin Yeung
> Assigned To: Scott M Stark
> Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.0.GA
>
>
> I deploy the same jar file (kevin.jar) in a war and its containing ear. In the war, I have a test JSP that loads a class from kevin.jar and displays its class loader.
> The class is loaded using the war class loader. So, I added the following to jboss-web.xml under the war's WEB-INF
> <class-loading java2ClassLoadingCompliance='true'>
> Didn't work. So I added this:
> <class-loading java2ClassLoadingCompliance='true'>
> <loader-repository>
> dot.com:loader=unique-archive-name
> <loader-repository-config>
> java2ParentDelegaton=true
> </loader-repository-config>
> </loader-repository>
> </class-loading>
> Didn't work either. Class continues to be loaded from war's class loader.
> Deleted JAR from WEB-INF/lib and class is now loaded from ear.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Updated: (JBAS-3047) WebApps ignore java2ClassLoadingCompliance in jboss-web.xml
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3047?page=all ]
Scott M Stark updated JBAS-3047:
--------------------------------
Component/s: ClassLoading
Web (Tomcat) service
Fix Version/s: JBossAS-4.2.0.GA
JBossAS-5.0.0.Beta3
The java2ClassLoadingCompliance was not being honored from the war.
> WebApps ignore java2ClassLoadingCompliance in jboss-web.xml
> -----------------------------------------------------------
>
> Key: JBAS-3047
> URL: http://jira.jboss.com/jira/browse/JBAS-3047
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service, ClassLoading
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: SuSE Linux 9.1, Sun JDK 1.4.2_11
> Reporter: Kevin Yeung
> Assigned To: Scott M Stark
> Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.0.GA
>
>
> I deploy the same jar file (kevin.jar) in a war and its containing ear. In the war, I have a test JSP that loads a class from kevin.jar and displays its class loader.
> The class is loaded using the war class loader. So, I added the following to jboss-web.xml under the war's WEB-INF
> <class-loading java2ClassLoadingCompliance='true'>
> Didn't work. So I added this:
> <class-loading java2ClassLoadingCompliance='true'>
> <loader-repository>
> dot.com:loader=unique-archive-name
> <loader-repository-config>
> java2ParentDelegaton=true
> </loader-repository-config>
> </loader-repository>
> </class-loading>
> Didn't work either. Class continues to be loaded from war's class loader.
> Deleted JAR from WEB-INF/lib and class is now loaded from ear.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months