When my Message Driven Bean gets activated during JBoss startup then i get
Could not instantiate bean when it want to save the parsed data to the DB.
The same happens to Session Beans which gets activated through the timerservice
in restart time (in this case it's task is to localize old data
I think i have found the problem:
The jar file was deployed into the folder
JBOSS_HOME\server\default\deploy\myfolder\ . It looks like that there is a bug
with the 4.04 release which caused my problem. I just placed the jar file
directly into the deploy folder:
No it wasn't, just bullshit.
This is the SQL-stacktrace:
| 2006-07-04 16:33:14,610 ERROR
[org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateEntityCommand.VipaEntity] Error
checking if entity exists
| org.jboss.util.NestedSQLException: Transaction is not active:
Log in is working perfect. When I log in with wrong password i am redirected to
the page defined in web.xml. But when i am using a user with missing role then
i am not redirected to the defined error page, i get the standard Tomcat HTTP
Status 403 - Access to the requested resource has been
in fact i can even write some garbage in the sql-statement tag of the
relationship definition, jboss doesn't care about. it is ignored and the
sql-statement of the first bean is taken.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3904611#3904611
Reply to
i think this is a JBoss bug - http://jira.jboss.com/jira/browse/JBAS-963
bug was mentioned first Thu Jun 20, 2002 00:00
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837631#3837631
now we have Nov 1, 2005
other occurence of this bug in the forum:
Hi,
i have exactly the same problem described here:
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837631#3837631
with the difference that i am using JBoss 4.02
the post create in the relation-table-mapping tag is ignored and replaced
with the one defined in the bean itself which
Following Failes when Client and Server are different Domains:
| public IPmonHistorySupplier( String host, int port ) throws
ServiceNotAvailableException {
| try {
| ServiceLocator serviceLocator =
ServiceLocator.getInstance(host, port);
|
|
forgot to say that when server and client are on different machines but in the
same domain it works as well.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875891#3875891
Reply to the post :
