[JBoss JIRA] Commented: (EJBTHREE-420) redeploy of TreeCached entities fails
by Erica Kane (JIRA)
[ http://jira.jboss.com/jira/browse/EJBTHREE-420?page=comments#action_12353810 ]
Erica Kane commented on EJBTHREE-420:
-------------------------------------
Hi Brian, I'll be glad to help if I can. Is the EJB patch included as part of JBoss 4.0.5GA, or does it require a separate download?
(I think I was able to do a workaround originally by using remove / in the JMX console. But we then stopped using the cache as it didn't seem safe.)
> redeploy of TreeCached entities fails
> -------------------------------------
>
> Key: EJBTHREE-420
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-420
> Project: EJB 3.0
> Issue Type: Bug
> Affects Versions: EJB 3.0 RC3
> Reporter: Bill Burke
> Assigned To: Brian Stansberry
> Fix For: EJB 3.0 RC10 - FD
>
>
> 2006-01-20 15:14:19,843 INFO [STDOUT] org.hibernate.PropertyAccessException: exception getting property value with CGLIB (set hibernate.cglib.use_reflection_optimizer=false for more info) getter of com.airit.fidsdb.entity.ArrPrevPortPK.?
> at org.hibernate.tuple.PojoComponentTuplizer.getPropertyValues(PojoComponentTuplizer.java:79)
> at org.hibernate.type.ComponentType.getPropertyValues(ComponentType.java:307)
> at org.hibernate.type.ComponentType.isEqual(ComponentType.java:111)
> at org.hibernate.cache.CacheKey.equals(CacheKey.java:51)
> at org.jboss.cache.Fqn.equals(Fqn.java:134)
> at java.util.HashMap.eq(HashMap.java:277)
> at java.util.HashMap.containsKey(HashMap.java:346)
> at org.jboss.cache.eviction.LRUAlgorithm.add(LRUAlgorithm.java:126)
> at org.jboss.cache.eviction.LRUAlgorithm.processAddedNodes(LRUAlgorithm.java:99)
> at org.jboss.cache.eviction.LRUAlgorithm.processQueues(LRUAlgorithm.java:77)
> at org.jboss.cache.eviction.LRUAlgorithm.process(LRUAlgorithm.java:52)
> at org.jboss.cache.eviction.EvictionTimerTask.run(EvictionTimerTask.java:37)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> Caused by: java.lang.ClassCastException: com.airit.fidsdb.entity.ArrPrevPortPK
> at com.airit.fidsdb.entity.ArrPrevPortPK$$BulkBeanByCGLIB$$8b6b36b9.getPropertyValues(<generated>)
> at net.sf.cglib.beans.BulkBean.getPropertyValues(BulkBean.java:48)
> at org.hibernate.tuple.PojoComponentTuplizer.getPropertyValues(PojoComponentTuplizer.java:76)
> ... 13 more
--
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, 2 months
[JBoss JIRA] Created: (JBRULES-554) False "Duplicate declaration for variable" error when doing "Match( homeTeam == $team) || Match( awayTeam == $team)"
by Geoffrey De Smet (JIRA)
False "Duplicate declaration for variable" error when doing "Match( homeTeam == $team) || Match( awayTeam == $team)"
--------------------------------------------------------------------------------------------------------------------
Key: JBRULES-554
URL: http://jira.jboss.com/jira/browse/JBRULES-554
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.0.4
Reporter: Geoffrey De Smet
Assigned To: Mark Proctor
Priority: Minor
[Maybe assign to Edson, he asked me to open in mailing list thread "Yet another or question"]
On the 3.0.x branch (update from this time) when declaring this rule:
query "multipleMatchesPerTeamPerDay"
$team : Team();
Match( $id : id, homeTeam == $team, $day : day )
|| Match( $id : id, awayTeam == $team, $day : day );
exists Match( id > $id, homeTeam == $team, day == $day )
|| exists Match(id > $id, awayTeam == $team, day == $day );
end
It reports an error:
org.drools.rule.InvalidRulePackage: Duplicate declaration for variable '$day' in the rule 'multipleMatchesPerTeamPerDay'
Testcase patch coming up.
--
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, 2 months
[JBoss JIRA] Commented: (JBAS-2905) Using Microsoft SQL Server 2005 JDBC Driver, getting "The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION"
by Luc Texier (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2905?page=comments#action_12353800 ]
Luc Texier commented on JBAS-2905:
----------------------------------
This issue has been fixed by Microsoft in the latest version 1.1 of the 2005 driver
http://www.microsoft.com/downloads/details.aspx?familyid=6D483869-816A-44...
release notes
http://blogs.msdn.com/angelsb/archive/2006/08/22/713417.aspx
> Using Microsoft SQL Server 2005 JDBC Driver, getting "The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION"
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-2905
> URL: http://jira.jboss.com/jira/browse/JBAS-2905
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMS service
> Affects Versions: JBossAS-4.0.4RC1, JBossAS-4.0.3 SP1
> Environment: Microsoft SQL Server 2005 JDBC Driver
> http://www.microsoft.com/downloads/details.aspx?familyid=e22bc83b-32ff-44...
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAMSSQLDatasource
> Reporter: Luc Texier
> Priority: Minor
>
> Microsoft SQL Server 2005 JDBC Driver
> http://www.microsoft.com/downloads/details.aspx?familyid=e22bc83b-32ff-44...
> the datasource is a copy of the example available in the following wiki
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAMSSQLDatasource
> The problem occurs only after the tables are already created in the database i.e on the second and subsequent startups.
> 2006-03-08 17:58:00,969 TRACE [org.jboss.resource.connectionmanager.TxConnectionManager] commit problem:
> 2006-03-08 17:58:00,969 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
> 2006-03-08 17:58:00,969 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
> 2006-03-08 17:58:00,969 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
> org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:545)
> at org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.commit(LocalManagedConnection.java:75)
> at org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.commit(TxConnectionManager.java:872)
> at org.jboss.tm.TransactionImpl$Resource.commit(TransactionImpl.java:2250)
> at org.jboss.tm.TransactionImpl.commitResources(TransactionImpl.java:1781)
> at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:337)
> at org.jboss.tm.TxManager.commit(TxManager.java:239)
> at org.jboss.mq.sm.jdbc.JDBCStateManager$JDBCSession.close(JDBCStateManager.java:613)
> at org.jboss.mq.sm.jdbc.JDBCStateManager.initDB(JDBCStateManager.java:465)
> at org.jboss.mq.sm.jdbc.JDBCStateManager.startService(JDBCStateManager.java:378)
>
>
> 2006-03-08 17:58:01,119 TRACE [org.jboss.resource.connectionmanager.TxConnectionManager] commit problem:
> org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:545)
> at org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.commit(LocalManagedConnection.java:75)
> at org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.commit(TxConnectionManager.java:872)
> at org.jboss.tm.TransactionImpl$Resource.commit(TransactionImpl.java:2250)
> at org.jboss.tm.TransactionImpl.commitResources(TransactionImpl.java:1781)
> at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:337)
> at org.jboss.tm.TxManager.commit(TxManager.java:239)
> at org.jboss.mq.pm.jdbc2.PersistenceManager$TransactionManagerStrategy.endTX(PersistenceManager.java:215)
> at org.jboss.mq.pm.jdbc2.MSSQLPersistenceManager.createSchema(MSSQLPersistenceManager.java:99)
> at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1563)
> at org.jboss.mq.pm.jdbc2.MSSQLPersistenceManager.startService(MSSQLPersistenceManager.java:240)
>
>
>
> I've tested against MS SQL Server 2000SP4....which might explain why it breaks ;)
> NB: this problem does not exist when I use SQL Server 2000 Driver for JDBC Service Pack 3
>
--
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, 2 months
[JBoss JIRA] Commented: (JBAS-2676) ClassLoader getResources() omits directory but finds files in the directory - this affects Facelets *.taglib.xml auto-loading
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2676?page=comments#action_12353797 ]
Dimitris Andreadis commented on JBAS-2676:
------------------------------------------
No, unless you deploy the war unpacked.
> ClassLoader getResources() omits directory but finds files in the directory - this affects Facelets *.taglib.xml auto-loading
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-2676
> URL: http://jira.jboss.com/jira/browse/JBAS-2676
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: Windows XP, JDK 1.5.0_04
> Reporter: David Richmond
> Assigned To: Remy Maucherat
>
> Using JSF and Facelets.
> Have a JAR file in my WebApps WEB-INF/lib, JAR file contains META-INF/faces-config.xml and META-INF/isalib.taglib.xml
> Using the Thread.currentThread().getContextClassLoader() classloader:
> .getResources("META-INF/faces-config.xml") finds the file in the JAR
> .getResources("META-INF/") does not find the directory in the JAR
> This is quite important, since Facelets scans the classpath for "META-INF/" dircetories and searches for *.taglib.xml files therein - this allows Facelets to auto-load the files it finds.
> One work around is to copy the taglib.xml file into my web-app and point the facelets.LIBRARIES context parameter at the file. Another workaround is to put the taglib.xml file into the Web-App's META-INF directory (since WAR files are on the classpath - is this an error?). However, the taglib.xml definitions belong to the JAR and can change when the JAR source code changes - so loading from the JAR is prefered.
--
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, 2 months
[JBoss JIRA] Created: (JBMESSAGING-818) HTTP transport sends zero length lists of polled callbacks
by Tim Fox (JIRA)
HTTP transport sends zero length lists of polled callbacks
----------------------------------------------------------
Key: JBMESSAGING-818
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-818
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.Beta2
Reporter: Tim Fox
Assigned To: Ron Sigal
Fix For: 1.2.0.CR1
I have noticed that, at times, with the HTTP transport, the wireformat receives a list of polled callbacks of length zero.
This results in a pointless callback delivery being made from the server to the client.
This can be easily seen by adding the following logging to JMSWireformat:
else if (param instanceof List)
{
// List of polled Callbacks, this is how messages are delivered when using
// polled callbacks e.g. the HTTP transport
//Sanity check
if (((List)param).isEmpty())
{
log.error("Got a polled callback list - but it is empty!!!");
}
And then running the test suite. I notice most of these when running the crash tests.
--
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, 2 months
[JBoss JIRA] Created: (JBPORTAL-1276) Check for user date-registration if we can set-it up at user creation then make it read-only.
by Thomas Heute (JIRA)
Check for user date-registration if we can set-it up at user creation then make it read-only.
---------------------------------------------------------------------------------------------
Key: JBPORTAL-1276
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1276
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal Identity
Reporter: Thomas Heute
Assigned To: Boleslaw Dawidowicz
Fix For: 2.6.CR1
Property registration-date is specified writeable in:
HibernateUserImpl.java:
map.put(org.jboss.portal.identity.User.INFO_USER_REGISTRATION_DATE, new DatePropertyAccessor(org.jboss.portal.identity.User.INFO_USER_REGISTRATION_DATE, "registrationDate", true, false));
and
read-only in core/output/resources/jboss-portal.sar/conf/identity/profile-config.xml
<property>
<name>portal.user.registration-date</name>
<type>java.util.Date</type>
<access-mode>read-only</access-mode>
<usage>mandatory</usage>
<display-name xml:lang="en">Registration date</display-name>
<description xml:lang="en">Registration date of user</description>
<mapping>
<database>
<type>column</type>
<value>jbp_regdate</value>
</database>
</mapping>
</property>
This should be sorted out.
--
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, 2 months