June 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: ResourceNotFoundException after Seam 2.0 upgrade

by mgrouch

Cleaning cache solved it. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058499#4058499 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058499

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: ResourceNotFoundException after Seam 2.0 upgrade

by fernando_jmt

Remove your browser cache: Ctrl+F5 or F5 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058498#4058498 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058498

18 years, 9 months

1
0
0 / 0

[Management, JMX/JBoss] - How to call a secured EJB method from the Service mbean star

by batter

I added a @RolesAllowed annotation to my EJB. I have an MBean (created using the @Service/@management annotations) that wants to call that EJB in its start method and of course gets an authentication exception. From the jmx-console is works fine since I edited the jmx-console security realm. Is there some other security realm I need to edit? And as an "ps": the method I call is basically to schedule the EJB to be run at certain intervals; now if there are better ways of doing *that*; it would be appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058497#4058497 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058497

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: <ui:insert /> stopped working in Seam 2.0 within source

by gavin.king＠jboss.com

By the way, suffice to say I find this pretty difficult to believe, since ui:insert is used in many of the Seam examples, which are working great. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058495#4058495 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058495

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: <ui:insert /> stopped working in Seam 2.0 within source

by gavin.king＠jboss.com

It is facelets 1.1.13a. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058494#4058494 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058494

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: <ui:insert /> stopped working in Seam 2.0 within source

by mgrouch

No exception, but the content which is supposed to be rendered by <ui:insert /> is not rendered. Seam 2.0 ships with own facelets version, could it be bug there? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058493#4058493 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058493

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: <ui:insert /> stopped working in Seam 2.0 within source

by gavin.king＠jboss.com

(1) "stopped working"?? Error? Or it just behaves differently now? (2) ui:insert is a built-in facelets tag, so this can't be a Seam issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058492#4058492 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058492

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - <ui:insert /> stopped working in Seam 2.0 within source tags

by mgrouch

<ui:insert /> stopped working in Seam 2.0 within facelets source tags View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058491#4058491 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058491

18 years, 9 months

1
0
0 / 0

[Remoting] - Re: EJB3/Socket invoker - connection timeouts

by gurgstar

Two suggestions (1) Stop writing code that relies on interrupting threads. (2) To avoid lost wake up problems, replace foo.notify() with something that stays signalled if there are no threads calling foo.wait(). Consider using a Semaphore or a BlockingQueue from util.concurrent / java.util.concurrent. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058489#4058489 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058489

18 years, 9 months

1
0
0 / 0

[Remoting] - Re: EJB3/Socket invoker - connection timeouts

by javajedi

Ok, I wrapped the code in wakeup() inside of a try/catch, with a catch block that looks like this: | } catch (Exception e) { | synchronized (clientpool) { | synchronized (threadpool) { | clientpool.remove(this); | threadpool.add(this); | Thread.interrupted(); | } | } | throw e; | } | and so far no deadlocks, but there were still plenty "mismatch version of JBossSerialization signature" errors spewing. I tried switching from JBoss Serialization back to Java Serialization. Instead of the "mismatch version" errors, I got a bunch of these: | 2007-06-27 16:37:22,519 156879 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] (SocketServerInvoker#0-3873:) Failed to accept socket connection | java.lang.reflect.InvocationTargetException | at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source) | at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) | at java.lang.reflect.Constructor.newInstance(Constructor.java:513) | at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:188) | at org.jboss.remoting.transport.socket.ServerThread.wakeup(ServerThread.java:233) | at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:461) | at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:392) | at java.lang.Thread.run(Thread.java:619) | Caused by: java.io.EOFException | at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2279) | at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2748) | at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780) | at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280) | at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73) | at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52) | at org.jboss.remoting.transport.socket.ServerSocketWrapper.createInputStream(ServerSocketWrapper.java:56) | at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76) | at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:54) | at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:50) | ... 8 more | So I don't think JBoss Serialization is at fault here. It looks like my socket timeout of 6 seconds was just not long enough to read what it needed before the socket timed out. I switched the socket timeout back to the default (60 seconds?) This seems to have halted all of the errors coming from the wakeup() method. So the key to preventing the deadlock seems to be catching the exception that is coming from wakeup() and resetting the state (i.e. adding the thread back to the threadpool) before continuing. Does this seem reasonable? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058488#4058488 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058488

18 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user June 2007