I would like to add several additional matches to the DeploymentFilter in
jboss-service.xml.For example in the root of our war we have several symbolic
links that link to several hundred gigabytes of content, I'd like skip that directory.
Option 1 (Prefered):
I would like to be able to sp
I went back to the Oracle8 datasource mapping and that fixed the problem also.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842621#3842621
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842621
--
I've attributed this problem to a change in the standardjbosscmp-jdbc.xml file. The
oracle9i mappings have changed the datatypes that java.sql.Timestamp map to. Under
Oracle8 they mapped to DATE datatypes and under Oracle9i they map to TIMESTAMP(9)
datatypes. I've modified the database to be
Take a look at the log again. This is all one transaction, I'm the only user on the
system, and the primary key of the record being updated exactly matches the one that
was just inserted.
This is not new code, and worked fine under other application servers, hmm...can't
possibly be jboss, co
I have a strange problem where in one transaction I have a cmp entity bean that
inserts a row and in the same transaction updates that row. The update is failing
with 'Expected one affected row: rowsAffected=0'
Here is some trace level logging that shows the problem
| 2004.07.16 13:51:10.9
I am having the same problem
| 2004.07.16 08:58:30.609 EDT INFO [STDOUT] org.jboss.tm.JBossRollbackException:
Unable to commit, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=DBOON1//197,
BranchQual=] status=STATUS_NO_TRANSACTION; - nested throwable:
(javax.ejb.EJBException: Update fail
We only get these warnings when we extend a container, if we leave the container
configuration blank the jboss.xml, which means we're using 'Standard CMP EntityBean'
container, we don't get these warnings.
However when I extend the 'Standard CMP EntityBean' container, I also get these
wranings.
LmnkStatementImpl is a InvocationHandler, and in the ivoke method we do this:
| else if (method.getName().equals("close")) {
| this.close();
| realStatement.close();
| }
|
So we intercept the the close of the statement and first close the resultsets,
just to follow up, the problem turned out to be that we were missing the trailing
slash on our extra deployment url '/'.
Thanks
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842296#3842296
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=po
This might be more what you were after though:
|/**
| * Get the emails that have not been sent yet. This email contains
| * a recipient list of 1 IndividualRecipient.
| *
| * @param since the time to look for new emails since, this
| * is a perfor
the resultset is close when the statement is closed, which is close when the
connection is closed. Here is the code that we use to close the resultsets:
| /**
| * free up resources opened from this statement.
| */
|public void close() {
| if ( resources.size() == 0
Ok, smarty pants, here's the full stack:
| 2004.07.10 00:34:15.153 GMT WARN
[org.jboss.resource.adapter.jdbc.WrappedConnection] Closing a result set you left
open! Please close i
| t yourself.
| java.lang.Exception: STACKTRACE
| at
org.jboss.resource.adapter.jdbc.WrappedStateme
Appologies if this is a faq, can't find much information on it though. We're getting
these warnings about 'Unable to passivate due to ctx lock, id=101663'
Happens on jboss 3.2.3 with cmp 1.X beans , we're using a customized container for
these entity beans:
|
| LMNK Standard C
Okay, so I'm not the only one to run into this:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=49695
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841914#3841914
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&
This post is regarding
http://sourceforge.net/tracker/index.php?func=detail&aid=990142&group_id=22866&atid=376685
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841912#3841912
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=rep
Here is the scenario
we have true for our datasource. We also have
code that wraps Connections and statements and closes resultsets when you close
statements, and the same for statements when you close connections. This is code that
has been working for quite some time, under jboss 3.2.3 as w
Two things make me think that this error is caused by the ear:
1) I only get the error when I have the loader-repository specified in the ear
2) The error messages show up while deploying the ear
| 2004.05.18 07:25:07.890 EDT INFO [org.jboss.deployment.MainDeployer] Deployed
package: file:/C:
Just to be clear, this is what I'm attempting to do, from page 71 of JBossBook_322.pdf:
To enable an EAR specific loader repository, you need to create a
META-INF/jboss-app.xml descriptor as shown in Listing 2-10LISTING 2-10. An example
jboss-app.xml descriptor for enabled scoped class loading a
Right, thoughat's what the message says, but what is a top level deployment?I
thought that an ear qualified as a top level deployment...
Thanks
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835480#3835480
Reply to the post :
http://www.jboss.org/index.
I'm attempting to get class isolation by using the hierachical loader repository. My
goal is to get unique instances of classes so that each ear can maintain state in
static instance variables independent of the other ears. I have two ears, deployed in
one JVM. I have tried this with 3.2.3 an
20 matches
Mail list logo
