more info on JGroups problem i'm having ...
by John Zorko
Hello, all ...
I also see the following message in the log of the node that won't
communicate:
2008-03-28 16:44:30,180 ERROR [org.jgroups.protocols.pbcast.GMS]
merge_id ([216.239.XXX.XXX:9900|1206745285182]) or this.merge_id
(null) is null (sender=10.15.XXX.XXX:9900).
... I XXXed out the last 2 octets of the IP addresses. Does this
additional message help at all?
Regards,
John
Falling You - exploring the beauty of voice and sound
http://www.fallingyou.com
16 years, 9 months
[Persistence, JBoss/CMP, Hibernate, Database] - identity fields in Entity beans
by cesar_takaide
Hello, I'm new in EJB3 technology. I'm working with an entity bean that has a identity field, so i wrote this on the field declaration:
@Id
@Column(name = "codigo", nullable = false)
@GeneratedValue(strategy=GenerationType.IDENTITY)
private Long codigo;
But, when the entity is persisted, Jboss warns me with a message :
16:42:52,947 WARN [WrappedConnection] Closing a result set you left open! Pleas
e close it yourself.
java.lang.Throwable: STACKTRACE
at org.jboss.resource.adapter.jdbc.WrappedStatement.registerResultSet(Wr
appedStatement.java:617)
at org.jboss.resource.adapter.jdbc.WrappedStatement.getGeneratedKeys(Wra
ppedStatement.java:533)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
...... etc...........
Why is this happening? Is something wrong in my code? Thank you very much for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139787#4139787
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139787
16 years, 9 months
Hello, and a question (of course) :-)
by John Zorko
Hello, all ...
I'm new to JBoss -- i'm a longtime C++ developer who has just
inherited a J2EE codebase when the developer left. I've done some
Java before, so I volunteered to maintain it (mistake #1), but the
last time I did Java was 2001 and it wasn't using beans or anything.
I'm hopeful that i'll learn a lot more about this as I work with it
more.
That being said, i've an issue i'm trying to solve. I have 2 JBoss
apps (called RMs) that talk to a central JBoss app (a broker) via
JGroups. RM #1, running on one host, successfully talks to the broker
app. RM #2, running on another host, does not. The error messages in
RM #2s log look like this:
2008-03-28 15:29:11,881 WARN [org.jgroups.protocols.pbcast.GMS] merge
responses from subgroup coordinators <= 1 ([]). Cancelling merge
2008-03-28 15:29:11,881 ERROR [org.jgroups.protocols.pbcast.GMS]
coords or merge_id == null
2008-03-28 15:29:11,881 ERROR [org.jgroups.protocols.pbcast.GMS]
coords or merge_id == null
I've done a lot of searching and haven't found much that describes how
to fix this. I've also gone through a lot (though not all, there are
dozens of them, many with dozens of params / attributes) of the beans
via the jmx-console, comparing the RM that does talk to the broker
with the RM that does not. So far, i've not found any differences.
Any help would be _greatly_ appreciated :-)
Regards,
John
Falling You - exploring the beauty of voice and sound
http://www.fallingyou.com
16 years, 9 months
[Beginners Corner] - jboss developer studio
by fedup
hi all
i'm trying to create a simple app in jboss developer studio, but having big trouble getting it to work
i created a dynamic web project
then created a helloworld servlet in the src folder
| public class HelloWorldServlet extends HttpServlet
| {
| protected void service(HttpServletRequest request, HttpServletResponse response)
| throws ServletException, IOException
| {
| ServletOutputStream out = response.getOutputStream();
| out.println("<html><body><h1>Hello World!</h1></body></html>");
| }
| }
In webContent -> WEB-INF -> web.xml i added this
| <servlet>
| <servlet-name>HelloWorldServlet</servlet-name>
| <servlet-class>test.HelloWorldServlet</servlet-class>
| </servlet>
|
| <servlet-mapping>
| <servlet-name>HelloWorldServlet</servlet-name>
| <url-pattern>/Hello</url-pattern>
| </servlet-mapping>
|
I then right-click on the folder and select Debug As - debug on server
jboss start up and i get the error - Bad version number in .class file
in the broswer address bar i put http://localhost:8080/Test/Hello but i get a 404 error
What am i doing wrong
using jboss developer studio
java 1.5
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139780#4139780
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139780
16 years, 9 months
[EJB/JBoss] - Deadlock on TIMERS table with EJB 2.1 timers
by karoberts
Jboss version: 4.05
DB: SQL Server 2005
OS: Windows Server 2003
We've been having a problem with EJB2.1 timers. Specifically single-shot (run once) timers.
First, our application creates single shot timers, and at the end of the ejbTimeout method for those timers, they create a new single shot timer with a start time in the future. We do this so that the timers execute with a fixed interval between invocations, regardless of how long they take to actually execute.
This appears to work just fine, except that eventually (depending on the interval we choose), the whole timer service will stop. Investigation using SQL server shows two transactions that are locking each other out of the TIMERS table that jboss uses to persist the timers in its DatabasePersistencePolicy. The deadlock seems to occur when one timer is deleting the now used single shot timer, and another is creating the next single shot timer. (DELETE, INSERT).
Since this is a DB deadlock, I assume that it is SQL Server specific. I examined the jboss code where this occurs, but I couldn't fix it with simple synchronization, since that would synchronize all ejbTimeout calls.
Has anyone seen this behavior before? Is there a better way to use the timer service to achieve what we need?
Also, we've seen the same locking when one timer creates another timer to run a task asynchronously.
Right now, our only options seem to be to turn off timer persistence, (NoopPersistencePolicy), or to write our own timer service using mbeans and threads (horrible).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139774#4139774
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139774
16 years, 9 months