JBoss Developer : All Content - All CommunitiesAll Content in JBoss Developerhttps://developer.jboss.org/Jive Engage2012-02-23T15:26:15Z2012-02-23T15:26:15ZenTransactions, Connections and Scrollable ResultSetsRob Shepherd/people/robshepdo-not-reply@jboss.com2012-02-23T15:35:08Z2012-02-23T15:26:15Z<!-- [DocumentBodyStart:07345e94-9405-4fef-853f-8b9dfd60a863] --><div class="jive-rendered-content"><p>Hello,</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>I'd like to find out what the problem is in our applicaton currently.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>We have a ScrollableResultSet which allows jasper to build reports containing a large quantity of records.</p><p>Each group has a subquery for which I want to perform another hibernate query however I have the following problems.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>1. in the default way, of say using a pojo seam component with an injected EntityManager, the subquery causes the ScrollableResultSet to close.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>The second call to next() on the scrollableresultset raises an exception indicating this.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>2. If I wrap the main jasper report process in a seam component with an @Transactional(REQUIRED) method then I cannot access hibernate objects after the initial run.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>the second call to next works fine, but the hibernate object within is somehow borked - </p><p>&#160;&#160; IllegalArgumentException in class: com.me.Location, getter method of property: id</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>These problems occur at the same point in the process......</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>Start main report process.....</p><p>&#160;&#160;&#160;&#160; load first group</p><p>&#160;&#160;&#160;&#160;&#160;&#160;&#160; run first subreport</p><p>&#160;&#160;&#160;&#160; load second group &lt;-- !! ERROR !!</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>How can I run a subquery on the database, whilst another long-running one is active using scroll?</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>Many thanks for any insights.</p></div><!-- [DocumentBodyEnd:07345e94-9405-4fef-853f-8b9dfd60a863] --><img src='/beacon?t=1550840230281' />2012-02-23T15:26:15Z6 years 12 months ago0Conversations, Injections, Wicket and Ajax - Strange BehaviourRob Shepherd/people/robshepdo-not-reply@jboss.com2011-05-26T17:49:21Z2011-05-25T17:27:59Z<!-- [DocumentBodyStart:718d3af3-9cc6-4cbe-84f3-da7cddfc6d69] --><div class="jive-rendered-content"><p class="wikiPara">Dear Seam Users,<br/></p><br/><p class="wikiPara">Hopefully somebody can help explain this seemingly odd behaviour that I've seen with AJAX requests using Wicket.<br/></p><br/><p class="wikiPara">Essentially, Conversations and Conversation-scoped beans are being created when they shouldn't.<br/></p><br/><br/><p class="wikiPara">The most basic example of this which I've yet to strip down completely) there is a <tt>Form</tt>, within which there is an <tt>AjaxButton</tt> with an <tt>onSubmit(target)</tt> method.&#160; <br/></p><br/><p class="wikiPara">I've added lots of trace info printing out the various details, which I will show now with some description.<br/></p><br/><br/><br/><p class="wikiPara">First the request to a bookmarkable page via entering the url into the address bar.&#160; (No conversation propagation)<br/></p><br/><!--[CodeBlockStart:9198b575-1d3e-4580-9e7e-13d7e47cc656][excluded]--><pre class="java" name="code">18:00:38,471 INFO&#160; [STDOUT] *****************************************************
18:00:38,472 INFO&#160; [STDOUT] *** @Create-ing manager object hashCode: 1783935998 cid:311
18:00:38,472 INFO&#160; [STDOUT] *****************************************************
18:00:38,476 DEBUG [ConversationListenerReport] Conversation Started
18:00:38,974 WARN&#160; [AddNewChannel] onDetach() -&gt; Rendered WebPage with Conversation ID: 311 (LRC: true)
18:00:38,975 WARN&#160; [AddNewChannel] onDetach() -&gt; Rendered WebPage with Conversation ID: 311 (LRC: true)
</pre><!--[CodeBlockEnd:9198b575-1d3e-4580-9e7e-13d7e47cc656]--><div style="display:none;"></div><br/><br/><br/><p class="wikiPara">In the above output we can see the SEAM POJO <tt>@Scope(ScopeType.Conversation)</tt> being created prior to injection into the wicket page <tt>@In(create=true)</tt><br/>The ConversationListenderReport is just an observer for LRC's beginning, which is started by the SEAM bean.&#160; <br/>The page is rendered fine and the Page onDetach() method prints the conversation details.<br/></p><br/><br/><p class="wikiPara">OK, No problems here. There is a long running conversation with ID 311.<br/></p><br/><br/><p class="wikiPara">Next, The following output is the result of a single click on the AjaxButton.<br/></p><br/><br/><br/><!--[CodeBlockStart:8a28f0fd-ddb8-4fde-aa8f-77c62c59cccd][excluded]--><pre class="java" name="code">18:00:45,139 INFO&#160; [STDOUT] *****************************************************
18:00:45,139 INFO&#160; [STDOUT] *** @Create-ing manager object hashCode: 178165655 cid:329
18:00:45,139 INFO&#160; [STDOUT] *****************************************************
18:00:45,139 INFO&#160; [STDOUT] after super.OnPageAttached() -&gt; injectedObject is not null: true
18:00:45,142 INFO&#160; [STDOUT] after super.OnPageAttached() -&gt; injectedObject: 178165655
18:00:45,142 INFO&#160; [STDOUT] after super.OnPageAttached() -&gt; Conversation - id: 329 pid: null rid: 329 lrc: false
18:00:45,146 INFO&#160; [STDOUT] AjaxButton.onSubmit() -&gt; Conversation id:311 long-running: true
18:00:45,148 INFO&#160; [STDOUT] AjaxButton.onSubmit() -&gt; injected Manager hashcode: 178165655
18:00:45,148 WARN&#160; [AddNewChannel] onDetach() -&gt; Rendered WebPage with Conversation ID: 311 (LRC: true)
18:00:45,150 INFO&#160; [STDOUT]&#160; after super.onDetach() -&gt; injected object hashcode: 178165655
18:00:45,152 WARN&#160; [AddNewChannel] onDetach() -&gt; Rendered WebPage with Conversation ID: 311 (LRC: true)
18:00:45,155 INFO&#160; [STDOUT]&#160; after super.onDetach() -&gt; injected object hashcode: 178165655
</pre><!--[CodeBlockEnd:8a28f0fd-ddb8-4fde-aa8f-77c62c59cccd]--><div style="display:none;"></div><br/><br/><br/><br/><br/><p class="wikiPara">Here we see that for some reason a new SEAM bean is being made and it thinks it is in Conversation ID no.329.<br/></p><br/><p class="wikiPara">I've overridden onPageAttached() to inspect a bit of this lifecycle, and here we see that the page has had <br/>the freshly created SEAM Bean injected in - This is not expected.<br/></p><br/><br/><p class="wikiPara">Furthermore, this is happening in a new fresh temporary conversation.<br/></p><br/><p class="wikiPara">Moreover, next when the button's onClick() is performed IT thinks it is back in Conversation 311 but has a reference<br/>to Conversation 329's SEAM Bean.<br/></p><br/><p class="wikiPara">Finally when the page's onDetach() is run, the page now think's it is back on the old Conv, but has a reference <br/>to the SEAM Bean constructed on the new Conv.<br/></p><br/><br/><br/><br/><p class="wikiPara">I'm baffeld by this - suffice to say it only happens in some cases - I'm trying to find a small example of Good and Bad.<br/></p><br/><p class="wikiPara">Is there anyway I could have programmed this to get this behaviour?<br/></p><br/><p class="wikiPara">Thanks for any input.<br/></p><br/><p class="wikiPara">Rob.<br/></p><br/><br/><p class="wikiPara">Note. All conversation ID's are&#160; result of printing <tt>Conversation.instance().getId()</tt> directly.<br/></p><br/></div><!-- [DocumentBodyEnd:718d3af3-9cc6-4cbe-84f3-da7cddfc6d69] -->2011-05-25T17:27:59Z7 years 9 months ago10Classloading between Web tier and applicationRob Shepherd/people/robshepdo-not-reply@jboss.com2010-08-20T12:19:50Z2010-08-20T12:19:50Z<!-- [DocumentBodyStart:21246599-19fc-4d37-96ba-4f3eb7cb6014] --><div class="jive-rendered-content"><p class="wikiPara">This is unlikey to be an issue with SEAM, more an issue with either my approach or JBOSS's classloader.<br/></p><br/><p class="wikiPara">Basically I ran into a problem when writing a library of Wicket components to include in the web tier of the SEAM/Wicket application.<br/></p><br/><p class="wikiPara">The library display's data, and the data is generated by SEAM beans.<br/></p><br/><p class="wikiPara">I haven't yet worked out the best solution and the one best solution which I think ought to work is broken for me. (JBoss 5)<br/></p><br/><p class="wikiPara"><a class="jive-link-external-small" href="http://datacymru.net/netstat/?p=153" rel="nofollow">Here's the Issue</a><br/></p><br/><p class="wikiPara">Any thoughts appreciated.<br/></p><br/><p class="wikiPara">Rob<br/></p><br/><br/><br/></div><!-- [DocumentBodyEnd:21246599-19fc-4d37-96ba-4f3eb7cb6014] -->2010-08-20T12:19:50Z8 years 6 months ago0abstract entity and subclasses for componentsRob Shepherd/people/robshepdo-not-reply@jboss.com2010-08-13T13:53:33Z2010-08-13T12:35:54Z<!-- [DocumentBodyStart:318e982f-676a-483b-9842-4fd63579e77a] --><div class="jive-rendered-content"><p class="wikiPara">Recently we had,<br/></p><br/><br/><br/><!--[CodeBlockStart:e2af0040-d7a4-4359-abbc-0b8da9e0c560][excluded]--><pre class="java" name="code">@Entity
@Name("user")
@Scope(SESSION)
public class User { ... }</pre><!--[CodeBlockEnd:e2af0040-d7a4-4359-abbc-0b8da9e0c560]--><div style="display:none;"></div><br/><br/><br/><p class="wikiPara">But now we must change it to the following structure:<br/></p><br/><!--[CodeBlockStart:e7f6d121-1c14-4a63-bf8e-fa8f113f5f0a][excluded]--><pre class="java" name="code">public abstract class User { ... }
public class UserTypeA extends User { ... }
public class UserTypeB extends User { ... }</pre><!--[CodeBlockEnd:e7f6d121-1c14-4a63-bf8e-fa8f113f5f0a]--><div style="display:none;"></div><br/><br/><br/><br/><p class="wikiPara">However, <br/></p><br/><p class="wikiPara">I've tried various combinations of the <tt>@Entity</tt>, <tt>@Name</tt> and <tt>@Scope</tt> annotations,<br/></p><br/><p class="wikiPara">It seems I can't have multiple sub-types with <tt>@Name</tt><br/></p><br/><!--[CodeBlockStart:cbb439e9-de6a-4e78-b280-cdcfbfd266c8][excluded]--><pre class="java" name="code">Two components with the same name and precedence - component name: user</pre><!--[CodeBlockEnd:cbb439e9-de6a-4e78-b280-cdcfbfd266c8]--><div style="display:none;"></div><br/><br/><br/><p class="wikiPara">But if they exist on <tt>User</tt> SEAM complains that <tt>User</tt> is abstract.<br/></p><br/><p class="wikiPara">Then, making <tt>User</tt> non-abstract (not ideal) I see it get's installed (But only the super-type)<br/>The other types don't get a mention.<br/></p><br/><p class="wikiPara">I see examples like this have been raised, but this is a simple case of polymorphism, where the concrete sub-types provide minor implementation differences.&#160; The whole application (apart from a single other method) just requires:<br/></p><br/><!--[CodeBlockStart:ce7102a2-0098-4926-a153-5f2b0a9fadc9][excluded]--><pre class="java" name="code">@In User user</pre><!--[CodeBlockEnd:ce7102a2-0098-4926-a153-5f2b0a9fadc9]--><div style="display:none;"></div><br/><br/><br/><p class="wikiPara">Any hints on what to do?<br/></p><br/><p class="wikiPara">Thanks and kind regards<br/></p><br/><p class="wikiPara">Rob<br/></p><br/><br/><p class="wikiPara"> <br/></p></div><!-- [DocumentBodyEnd:318e982f-676a-483b-9842-4fd63579e77a] -->2010-08-13T12:35:54Z8 years 6 months ago10Best profile for JBoss or should I use tomcatRob Shepherd/people/robshepdo-not-reply@jboss.com2010-06-30T22:35:03Z2010-06-25T15:21:46Z<!-- [DocumentBodyStart:d3327a9c-2f4a-491d-9219-91963186368f] --><div class="jive-rendered-content"><p class="wikiPara">I only have experience of JBoss AS with SEAM development but I've reached the limit of my patience.<br/></p><br/><p class="wikiPara">I'm using a stock download of JBoss on Java6 and I can't prevent it from using all of my resources when redeploying the pitifully small Seam 2.2.0.GA Ear.<br/></p><br/><p class="wikiPara">After just 2-3 re-deployments overall performance is noticablly worse<br/>After 5-6 re-deployment the CPU is at 100% and it's chomping memory.<br/></p><br/><p class="wikiPara">If I'm making tea, I find an OOM Error, If i'm not making tea - I usually just kill -9 the java process and restart the app server.<br/></p><br/><p class="wikiPara">I've tried removing the HDScanner and deploying using twiddle.sh, however JBoss just finds some other to max out on.<br/></p><br/><p class="wikiPara">(Quartz, RMI TCP Conn(that i've never used), http-8080 TCP connections, these are the usual suspects for using all my CPU)<br/></p><br/><p class="wikiPara">If I don't re-deploy the application it works fine.<br/></p><br/><br/><br/><p class="wikiPara">So,<br/></p><br/><p class="wikiPara">Firstly, Has anybody else experienced this? <br/></p><br/><p class="wikiPara">Other questions:<br/></p><br/><p class="wikiPara">Q1. Does anybody have a nice JBoss setup that works for development? That plays nicely with SEAM app re-deployments<br/>Q2. Does anybody have a good reference on what I stand to lose if I just go to tomcat.<br/>Q3. Will JBoss 6 be better (than bad)<br/></p><br/></div><!-- [DocumentBodyEnd:d3327a9c-2f4a-491d-9219-91963186368f] -->2010-06-25T15:21:46Z8 years 8 months ago10Build Time Wicket Instrumentation with Ant (and other problems)Rob Shepherd/people/robshepdo-not-reply@jboss.com2010-02-17T22:09:32Z2010-02-16T17:13:51Z<!-- [DocumentBodyStart:8e3c9cd1-055e-4718-91e2-f66ddee4f4f7] --><div class="jive-rendered-content"><p class="wikiPara">Hi,<br/></p><br/><p class="wikiPara">A simple query for those who have build time instrumentation working with Wicket.<br/></p><br/><p class="wikiPara">I have the following structure in the build.xml<br/></p><br/><br/><br/><!--[CodeBlockStart:d5884d7d-4a82-499c-840f-5b0c72e2c118][excluded]--><pre class="java" name="code">&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;mkdir dir="classes/wicket" /&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;!-- Compile the Wicket classes --&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;javac classpathref="wicket.classpath"
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; destdir="classes/wicket"
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; debug="${javac.debug}"
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; deprecation="${javac.deprecation}"
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; nowarn="off"&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;src path="src/web" /&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;/javac&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;!-- Instrument the SEAM annotations --&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;instrumentWicket outputDirectory="${war.dir}/WEB-INF/classes" useAnnotations="false"&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;classpath refid="build.classpath"/&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;fileset dir="classes/wicket" includes="**/*.class"/&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;/instrumentWicket&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;!-- Copy the html markup to the same location --&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;copy todir="${war.dir}/WEB-INF/classes"&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;fileset dir="src/web"&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;include name="**/*.html"/&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;include name="**/*.js"/&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;/fileset&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; &lt;/copy&gt;</pre><!--[CodeBlockEnd:d5884d7d-4a82-499c-840f-5b0c72e2c118]--><div style="display:none;"></div><br/><br/><br/><p class="wikiPara">But I see the following error during build at instrumentation time.<br/></p><br/><p class="wikiPara"><tt>java.lang.RuntimeException: javassist.NotFoundException: com.example.myclass</tt><br/></p><br/><p class="wikiPara">This class exists in <tt>classes/wicket</tt> <br/></p><br/><p class="wikiPara">So I'm not sure what the problem can be.&#160; Can anybody see an obvious problem with my build.xml excerpt?<br/></p><br/><p class="wikiPara">Incidentally,&#160; I'm attempting to switch to compile-time wicket instrumentation to try and workaround/resolve/indicate a strange problem.<br/></p><br/><p class="wikiPara">I have the following class in my <tt>web/</tt> folder....<br/></p><br/><!--[CodeBlockStart:470393af-88c7-4dbc-a362-ed9dd6d6f096][excluded]--><pre class="java" name="code">package com.example.effect;
import org.apache.wicket.Component;
public class TheClassName
{
&#160;&#160;&#160; //private Component component;
&#160;&#160;&#160;&#160;&#160;
&#160;&#160;&#160; public TheClassName(/*Component component*/)
&#160;&#160;&#160; {
&#160;&#160;&#160;&#160;&#160;//this.component = component;
&#160;&#160;&#160; }
}</pre><!--[CodeBlockEnd:470393af-88c7-4dbc-a362-ed9dd6d6f096]--><div style="display:none;"></div><br/><br/><br/><br/><p class="wikiPara">...And, strangely if I uncomment the above lines (in fact just the first will do) Then my application fails as follows.<br/></p><br/><!--[CodeBlockStart:e5f3ed84-677e-4d7d-b2ec-faf4b56bd79c][excluded]--><pre class="java" name="code">09:51:13,692 ERROR [[default]] Servlet.service() for servlet default threw exception
java.lang.ClassCastException: org.jboss.seam.wicket.WicketManager
&#160;&#160;&#160;&#160;&#160;at org.jboss.seam.faces.FacesManager.instance(FacesManager.java:313)
&#160;&#160;&#160;&#160;&#160;at org.jboss.seam.exception.DebugPageHandler.handle(DebugPageHandler.java:26)
&#160;&#160;&#160;&#160;&#160;at org.jboss.seam.exception.Exceptions.handle(Exceptions.java:76)
&#160;&#160;&#160;&#160;&#160;at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
&#160;&#160;&#160;&#160;&#160;at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
&#160;&#160;&#160;&#160;&#160;at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
&#160;&#160;&#160;&#160;&#160;at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
&#160;&#160;&#160;&#160;&#160;at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
&#160;&#160;&#160;&#160;&#160;at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
&#160;&#160;&#160;&#160;&#160;at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
&#160;&#160;&#160;&#160;&#160;at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
&#160;&#160;&#160;&#160;&#160;at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
&#160;&#160;&#160;&#160;&#160;at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
&#160;&#160;&#160;&#160;&#160;at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
&#160;&#160;&#160;&#160;&#160;at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
&#160;&#160;&#160;&#160;&#160;at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
&#160;&#160;&#160;&#160;&#160;at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
&#160;&#160;&#160;&#160;&#160;at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
&#160;&#160;&#160;&#160;&#160;at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
&#160;&#160;&#160;&#160;&#160;at java.lang.Thread.run(Thread.java:613)</pre><!--[CodeBlockEnd:e5f3ed84-677e-4d7d-b2ec-faf4b56bd79c]--><div style="display:none;"></div><br/><br/><br/><p class="wikiPara">....I'm thus making the assumption that Run-Time instrumentation is failing somehow (sliently) and WicketManager doesn't get constructed (Warning - guess hazarding in progress!!)<br/></p><br/><p class="wikiPara">Strange but true.<br/></p><br/><p class="wikiPara">With thanks for any help with these problems<br/></p><br/><p class="wikiPara">Rob<br/></p><br/><br/></div><!-- [DocumentBodyEnd:8e3c9cd1-055e-4718-91e2-f66ddee4f4f7] -->2010-02-16T17:13:51Z9 years 4 days ago20JVM Crash on XenRob Shepherd/people/robshepdo-not-reply@jboss.com2009-11-10T15:19:42Z2009-11-09T19:34:57Z<!-- [DocumentBodyStart:d0a3f714-9e9e-4bd4-8c48-abc315fa34ef] --><div class="jive-rendered-content"><p>Vanilla download of 5.1.0-GA on Ubuntu Hardy 8.04 Xen PV Guest.<br/><br/>The JVM Crashes (libjvm) with a seemingly arbitrary SIGSEGV shortly (1-10s) after starting AS.<br/><br/>Tried and tested with all available JVMs<br/>1.5 through 1.7 (sun and openjdk)<br/><br/>Nevertheless,<br/>The system is stable when reducing the amount of memory allocated to the system from 4GB to 1GB<br/><br/>Who can I report this to? JBoss? Ubuntu? Xen?<br/><br/>I will shortly find the exact failure value for allocated memory.<br/><br/>What can I get/produce/generate to assist in getting this fixed?<br/><br/>Many thanks<br/><br/>Rob<br/><br/></p></div><!-- [DocumentBodyEnd:d0a3f714-9e9e-4bd4-8c48-abc315fa34ef] -->2009-11-09T19:34:57Z9 years 3 months ago40Mail-Excel-PDF without JSF (With Wicket)Rob Shepherd/people/robshepdo-not-reply@jboss.com2009-10-30T18:51:16Z2009-10-29T18:51:59Z<!-- [DocumentBodyStart:6e489e25-253d-46ae-831e-35b38f14633b] --><div class="jive-rendered-content"><p class="wikiPara">Dear Group,<br/></p><br/><p class="wikiPara">This question has been asked before (but it has never received any repiles)<br/></p><br/><p class="wikiPara"><a class="jive-link-external-small" href="http://www.seamframework.org/Community/MailAndPDFRendererOutsideJSFLifecycle" rel="nofollow">http://www.seamframework.org/Community/MailAndPDFRendererOutsideJSFLifecycle</a><br/><a class="jive-link-external-small" href="http://www.seamframework.org/Community/MailRenderer" rel="nofollow">http://www.seamframework.org/Community/MailRenderer</a><br/></p><br/><p class="wikiPara">Could I ask again, to see if anybody has any ideas.<br/></p><br/><p class="wikiPara">I'd really like to render email, pdf and excel but I'm using wicket.<br/></p><br/><p class="wikiPara">What would be required to get a working renderer?<br/></p><br/><p class="wikiPara">With a great many thanks<br/></p><br/><p class="wikiPara">Rob</p></div><!-- [DocumentBodyEnd:6e489e25-253d-46ae-831e-35b38f14633b] -->2009-10-29T18:51:59Z9 years 4 months ago10RequestParameter in WicketRob Shepherd/people/robshepdo-not-reply@jboss.com2009-09-29T06:49:11Z2009-09-24T07:16:04Z<!-- [DocumentBodyStart:c35a0b19-69df-40f1-b0b5-433087625a8f] --><div class="jive-rendered-content"><p class="wikiPara">Is there a way to harness RequestParameters in a Seam/Wicket application.<br/></p><br/><br/><br/><!--[CodeBlockStart:7c9019e2-c8fc-4d4d-8e36-2196e61d157f][excluded]--><pre class="java" name="code">@RequestParameter
Long entityID</pre><!--[CodeBlockEnd:7c9019e2-c8fc-4d4d-8e36-2196e61d157f]--><div style="display:none;"></div><br/><br/><br/><br/><br/><p class="wikiPara">results in a <br/></p><br/><blockquote class="wikiBlockquote"><br/>java.lang.IllegalStateException: No FacesContext associated with current thread, cannot convert request parameter type<br/></blockquote><br/></div><!-- [DocumentBodyEnd:c35a0b19-69df-40f1-b0b5-433087625a8f] -->2009-09-24T07:16:04Z9 years 5 months ago50injected EntityManager in EJBs and POJOsRob Shepherd/people/robshepdo-not-reply@jboss.com2009-09-24T03:01:49Z2009-09-23T19:29:24Z<!-- [DocumentBodyStart:396b8b3e-8cf2-40f1-b0fa-93b5f925da8a] --><div class="jive-rendered-content"><p class="wikiPara">If I have a @Stateful session bean,<br/></p><br/><p class="wikiPara">then a merge(entity); flush(); permits me to either persist or update a new or detached entity.<br/></p><br/><p class="wikiPara">If I turn the bean in to a regular POJO seam component, then it doesn't persist the entity.<br/></p><br/><p class="wikiPara">Can anybody explain why?<br/></p><br/><br/><br/><p class="wikiPara">In a @Stateful EJB, is a @In EntityManager SEAM or Container managed?<br/></p><br/><p class="wikiPara">Thanks<br/></p><br/><p class="wikiPara">Rob</p></div><!-- [DocumentBodyEnd:396b8b3e-8cf2-40f1-b0fa-93b5f925da8a] -->2009-09-23T19:29:24Z9 years 5 months ago20