I'm trying to set up jbpm 3.2.6.sp1. I've got everything deploying fine, but I
can't login to the jbpm-console. It took me a while to track down how I'm
supposed to populate my JBPM_ID_USER, JBPM_ID_GROUP, and JBPM_ID_MEMBERSHIP
tables with some sample data (why isn't this described in the
I have an app with an EJB that threw a NullPointerException. JBoss wrapped
this in an EJBTransactionRolledbackException, which it then threw to the
client. When this happened, JBoss didn't log the exception. My understanding
of the EJB Specification (Chapter 14, page 358) is that when an EJB
I'm trying to force an EJB call to be remote on the same machine, even though
the EJB is deployed locally (i.e. open an actual socket connection to localhost
and go through the exact same steps as a remote client would). The reason for
this is to set up a monitoring MBean that we can use to
My patch has been working fine in production for 11 days now; 4 of them at full
capacity. The pool sizes look to be correct and under control. I think that
my patch has resolved the issue.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062147#4062147
Reply
Bug filed at http://jira.jboss.com/jira/browse/JBREM-762
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4058943#4058943
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058943
___
The only relevant change that I saw to SocketServerInvoker (that I already
patched) was the call to
serverSocket.setReuseAddress(true);
Was there more that I'm missing?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057961#4057961
Reply to the post :
BTW, we are using JBoss 4.0.4 and ejb 3.0-rc9.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057962#4057962
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057962
___
jboss-user
A few months ago, I think I tried using JBoss Remoting 2.x with EJB 3.0-rc9,
and it didn't work. Should it?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057965#4057965
Reply to the post :
Thanks. Posted at
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057982
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057983#4057983
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057983
As far as I can tell, it looks like the latest version of EJB3 ships with JBoss
Remoting 1.4.3 as part of the download. I have been using 1.4.4-1.4.6 with it
for a while now. I ran into a bug in JBoss Remoting 1.4.6
(http://www.jboss.com/index.html?module=bbop=viewtopicp=4057965), and Ron
Thanks for the reply. We're using JBoss 4.0.4. Does this mean that we are
stuck on EJB3 3.0-rc9-patch-1 and JBoss Remoting 1.4.x, unless we upgrade to
JBoss 4.2.0?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057990#4057990
Reply to the post :
I tried JBoss Remoting 2.2.0 and I was unable to get it to work with JBoss
4.0.4. I'm also not too enthusiastic about that approach because looking at
the code, I don't think that this bug has been fixed in the latest version. I
am now able to reproduce this problem easily by setting
Apologies to Ron for double-posting both here and on the support ticket, but I
want to give the other kind souls who have been helping me out an update.
Just tried with store-bought 1.4.6. Exact same problem. Lots of these:
| 2007-06-27 16:19:37,799 71584 ERROR
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);
|
We're running into a problem with a brand new production system that has a
single remote EJB. We are using JBoss EJB3, which uses JBoss Remoting to do
the remote communication. We are using the standard socket invoker to handle
the communication. We are using JBoss Serialization instead of
Thanks Ron. Yeah, I came across JBREM-409 a few days ago, and had already
applied that patch from 1.4.6 (which seems to have been tagged in CVS but never
released) to our code. So this problem definitely seems to still exist in
1.4.6.
Upgrading the EJB implementation and going to Remoting
From the remoting docs:
timeout - The socket timeout value passed to the Socket.setSoTimeout() method.
Is there any way to configure the socket's connect timeout separately?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057457#4057457
Reply to the post :
Sorry, I mentioned it in the subject line, but the forums truncated it. :) I'm
using the socket transport (1.4.4).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057462#4057462
Reply to the post :
I've been doing some profiling of our remote EJB3 invocations, and I just
wanted to post and share what I found out. I was able to achieve an average
50% performance boost for our remote calls by changing 1 line in
deploy/ejb3.deployer/META-INF/jboss-service.xml:
Original line:attribute
Just a note on the check_connection bit. Glancing at the remoting code, it
looks like the check is no longer on by default in JBoss Remoting 2.0.
However, the default in 1.4.4 (the latest 1.x release) is still to check first.
I tried dropping 2.0 into JBoss, but that was a no-go.
View the
I'm sorry, I don't have any good test case to hand you. I'm using a SLSB that
sends back objects that are pretty good-sized (a few K) and variably sized.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4004124#4004124
Reply to the post :
I'm reading the section on Compression marshalling at
http://labs.jboss.com/portal/jbossremoting/docs/guide/ch05.html and thought I'd
give that configuration a try. I set up my InvokerLocator to look like the
following:
Doesn't really have anything to do with JBoss Portal, but I just patched the
chart creator to work inside JBoss Portal. In case anyone cares, here is the
patch:
diff --new-file -rc ./net/sf/jsfcomp/chartcreator/ChartListener.java
JBoss 4.0.4
JBoss Portal 2.4.0 RC2
Every time my JBoss Portal app throws an exception, I get the following error:
2006-08-02 13:45:12,625 ERROR [org.jboss.portal.server.servlet.PortalServlet]
Unexpected exception
| java.lang.IllegalStateException: Wrong tx on thread: expected
Solved my problem. The problem was that inputFileUpload relies on a servlet
filter, which doesn't work in a portlet. I found a patch for myfaces here:
http://issues.apache.org/jira/browse/MYFACES-434
and it's working with the patch applied.
View the original post :
JBoss Portal 2.4.0-CR2
Seam 1.0.0
JBoss 4.0.4
I've got a Seam app that works fine on its own. When I deploy it as a portlet,
the initial page of the portlet displays fine, but when I submit a form from
that first page, the Seam action doesn't get invoked. The page is just
redisplayed.
I've
BTW, this is my web page:
ui:composition xmlns=http://www.w3.org/1999/xhtml;
| xmlns:h=http://java.sun.com/jsf/html;
| xmlns:t=http://myfaces.apache.org/tomahawk;
| xmlns:ui=http://java.sun.com/jsf/facelets;
|
| h:form id=importForm
I'm trying to build a portlet for JBoss Portal 2.4.0-CR2 that uses Seam 1.0.0
and Facelets 1.1.5. I started with the portal example from Seam, which works
fine, and tried to plug in a facelet. I made the following changes to the
example app:
Added the following to web.xml:
filter
|
Got it working (mostly). I had to make a couple changes:
1: Use FaceletPortletViewHandler instead of FaceletViewHandler.
2: Comment out org.apache.myfaces.webapp.StartupServletContextListener in
web.xml. This causes an error when I deploy the app:
2006-07-19 14:37:04,734 ERROR
29 matches
Mail list logo
