[JBoss JIRA] Created: (JBBUILD-332) Anonymous implementation of abstract methods in enums causes Weaver to barf
by Manik Surtani (JIRA)
Anonymous implementation of abstract methods in enums causes Weaver to barf
---------------------------------------------------------------------------
Key: JBBUILD-332
URL: http://jira.jboss.com/jira/browse/JBBUILD-332
Project: JBoss Build System
Issue Type: Bug
Components: JBossRetro
Affects Versions: JBossRetro-1.0.4.GA
Environment: Tested with JBoss Retro snapshot (10 Jan 2007) as well as 1.0.4.GA
java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
Java HotSpot(TM) Client VM (build 1.5.0_09-b03, mixed mode, sharing)
Linux hobbes 2.6.18-1.2869.fc6xen #1 SMP Wed Dec 20 15:28:06 EST 2006 i686 i686 i386 GNU/Linux
Reporter: Manik Surtani
For example, see
http://fisheye.jboss.com/browse/~raw,r=1.7/JBoss/JBossCache/src/org/jboss...
When attempting to retroweave this enum, we see an NPE trying to get a hold of the enums in the class.
[retro] Attempting to retroweave class org.jboss.cache.lock.IsolationLevel$1
[retro] Exception in thread "main" java.lang.NullPointerException
[retro] at org.jboss.ant.tasks.retro.Weaver.rewriteEnum(Weaver.java:581)
[retro] at org.jboss.ant.tasks.retro.Weaver.doWeave(Weaver.java:463)
[retro] at org.jboss.ant.tasks.retro.Weaver.compileFile(Weaver.java:415)
[retro] at org.jboss.ant.tasks.retro.Weaver.weave(Weaver.java:328)
[retro] at org.jboss.ant.tasks.retro.Weaver.main(Weaver.java:110)
(I added the sys out in my local copy of Weaver.java to spit out the name of the offending class)
--
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: (HIBERNATE-65) Error with 'id' property with 3.2.3
by Chris Laprun (JIRA)
Error with 'id' property with 3.2.3
-----------------------------------
Key: HIBERNATE-65
URL: http://jira.jboss.com/jira/browse/HIBERNATE-65
Project: Hibernate
Issue Type: Bug
Reporter: Chris Laprun
Assigned To: Steve Ebersole
I have a property defined as:
<property name="id" not-null="true" unique="true" type="java.lang.String"/>
The query:
Iterator producerInfos = session.createQuery("from ProducerInfo pi order by pi.id").iterate();
works fine on 3.2.2 but fails in 3.2.3 with:
14:49:21,513 INFO [LongType] could not read column value from result set: col_0_0_; Wrong data type: type: VARCHAR (12) expected: BIGINT value: NetUnity
14:49:21,518 WARN [JDBCExceptionReporter] SQL Error: -16, SQLState: 37000
14:49:21,518 ERROR [JDBCExceptionReporter] Wrong data type: type: VARCHAR (12) expected: BIGINT value: NetUnity
[...]
Caused by: java.sql.SQLException: Wrong data type: type: VARCHAR (12) expected: BIGINT value: NetUnity
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcResultSet.getColumnInType(Unknown Source)
at org.hsqldb.jdbc.jdbcResultSet.getLong(Unknown Source)
at org.hsqldb.jdbc.jdbcResultSet.getLong(Unknown Source)
at org.jboss.resource.adapter.jdbc.WrappedResultSet.getLong(WrappedResultSet.java:718)
at org.hibernate.type.LongType.get(LongType.java:28)
at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:163)
at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:154)
at org.hibernate.type.ManyToOneType.hydrate(ManyToOneType.java:103)
at org.hibernate.type.EntityType.nullSafeGet(EntityType.java:204)
at org.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:93)
at org.hibernate.impl.IteratorImpl.<init>(IteratorImpl.java:58)
at org.hibernate.loader.hql.QueryLoader.iterate(QueryLoader.java:405)
--
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-792) Some "collect" rules cause hang during assertion
by Dirk Bergstrom (JIRA)
Some "collect" rules cause hang during assertion
------------------------------------------------
Key: JBRULES-792
URL: http://jira.jboss.com/jira/browse/JBRULES-792
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.1-m2
Reporter: Dirk Bergstrom
Assigned To: Mark Proctor
Some combinations of collect rules and objects result in an endless
busy loop during assertion (100% CPU usage for 18 hours and counting).
The problem doesn't happen for every object, but it is repeatable for
a given object.
For instance, with the following rule:
rule "Find all RLIs for user"
when
$user : User( )
$rli_list : RecordSet( size > 0 ) from
collect( RLIRecord( $resp : responsible -> ( $user.hasReport($resp) ) ) )
then
$user.setRecords($rli_list, DataSource.RLI);
end
With 92 Users asserted, my code asserts the first 1368 RLI objects at 6-8
miliseconds per assertion, then hangs hard on #1369 (always the same
object). It has sat there occupying a cpu full time for the last 18
hours, with no visible progress.
On the other hand, with these two rules:
when
$release : ReleaseRecord( $relname : relname )
$user : User( )
$pr_list : RecordSet( size > 0 ) from
collect( PRRecord( releases contains $relname,
$resp : responsible -> ( $user.hasReport($resp) ) ) )
then
$user.setRecords($pr_list, $release, DataSource.GNATS);
end
rule "Find all PRs for user"
when
$user : User( )
$pr_list : RecordSet( size > 0 ) from
collect( PRRecord( $resp : responsible -> ( $user.hasReport($resp) ) ) )
then
$user.setRecords($pr_list, DataSource.GNATS);
end
With 92 Users and 37 ReleaseRecords asserted, I can assert all 10600
PR objects, at between 10 and 100 msec per (it slows down a bit
towards the end). Then on the next cycle the app asserts several
hundred more User objects, and later asserts another 1500 Users,
without a hitch.
If need be, I have examples of other rule/object combinations that do
and don't work. Note that a version of the RLIRecord class is
attached to JBRULES 740.
I'm using trunk, at revision 108xx -- forgot to note the exact
revision, but it includes tirelli's hashcode caching, and a few other
changes after that.
This is a follow-on to JBRULES 740.
--
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-1443) Add a flag to allow concurrent calls on stateful session beans
by Valentijn Scholten (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1443?page=comments#action_12363368 ]
Valentijn Scholten commented on JBAS-1443:
------------------------------------------
I think an extra interceptor could work out nicely, any hints on how to implement this interceptor? Is there an interceptor we could use or use as a good base? We would need some kind of waiting/signaling to implement this. I'm not into developing interceptors, so I'm not sure how to do this best?
> Add a flag to allow concurrent calls on stateful session beans
> --------------------------------------------------------------
>
> Key: JBAS-1443
> URL: http://jira.jboss.com/jira/browse/JBAS-1443
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: EJB2
> Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
> Reporter: Scott M Stark
> Priority: Minor
>
> Weblogic has an allow-concurrent-calls proprietary tag for stateful session beans. The allow-concurrent-calls specifies whether a stateful session bean instance will allow concurrent method calls. The value of this element may be either "True" or "False". The default value is "False". When a stateful session bean instance is currently in a method call and another (concurrent) method call arrives on the server, the EJB specification requires that the server throw a RemoteException. By default, allow-concurrent-calls is false, and the EJB container will follow the EJB specification. When this value is set to true, the EJB container will block the concurrent method call and allow it to proceed when the previous call has completed.
--
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: (JBPM-929) Missing hibernate mapping file(org/jbpm/graph/action/MailAction.hbm.xml) for MailAction class.
by Yashvanth Giriyappa (JIRA)
Missing hibernate mapping file(org/jbpm/graph/action/MailAction.hbm.xml) for MailAction class.
----------------------------------------------------------------------------------------------
Key: JBPM-929
URL: http://jira.jboss.com/jira/browse/JBPM-929
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2
Environment: Windows XP,Tomcat,Mysql
Reporter: Yashvanth Giriyappa
Assigned To: Tom Baeyens
Missing hibernate mapping file(org/jbpm/graph/action/MailAction.hbm.xml) for MailAction class.
Hence ... not able to deploy a process having a mail action inside a task.
Explained in detail in the JBOSS thread "http://www.jboss.com/index.html?module=bb&op=viewtopic&t=105615"
Error stack ...
----------------------
42156 [http-8080-Processor25] ERROR org.jbpm.webapp.bean.ProcessBean - Failed to start process: org
.jbpm.graph.def.DelegationException
org.jbpm.graph.def.DelegationException
at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:367)
at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:358)
at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:261)
at org.jbpm.graph.def.GraphElement.executeActions(GraphElement.java:215)
at org.jbpm.graph.def.GraphElement.fireAndPropagateEvent(GraphElement.java:185)
at org.jbpm.graph.def.GraphElement.fireEvent(GraphElement.java:169)
at org.jbpm.graph.def.Node.enter(Node.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:147)
at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$5e7dd3fd.enter(<generated>)
at org.jbpm.graph.def.Transition.take(Transition.java:151)
at org.jbpm.graph.def.Node.leave(Node.java:393)
at org.jbpm.graph.node.TaskNode.leave(TaskNode.java:209)
at org.jbpm.graph.def.Node.leave(Node.java:357)
at org.jbpm.graph.node.TaskNode.execute(TaskNode.java:190)
at org.jbpm.graph.def.Node.enter(Node.java:318)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:147)
at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$5e7dd3fd.enter(<generated>)
at org.jbpm.graph.def.Transition.take(Transition.java:151)
at org.jbpm.graph.def.Node.leave(Node.java:393)
at org.jbpm.graph.node.StartState.leave(StartState.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:147)
at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$5e7dd3fd.leave(<generated>)
at org.jbpm.graph.exe.Token.signal(Token.java:194)
at org.jbpm.graph.exe.Token.signal(Token.java:165)
at org.jbpm.webapp.bean.ProcessBean.startInstance(ProcessBean.java:162)
at org.jbpm.webapp.bean.ProcessBean$StartInstanceListener.processAction(ProcessBean.java:123
)
at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:758)
at javax.faces.component.UICommand.broadcast(UICommand.java:368)
at javax.faces.component.UIData.broadcast(UIData.java:854)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:448)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
ava:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
ava:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Htt
p11BaseProtocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.ja
va:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at org.jbpm.mail.Mail.send(Mail.java:98)
at org.jbpm.mail.Mail.execute(Mail.java:63)
at org.jbpm.graph.def.Action.execute(Action.java:122)
at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:247)
--
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