Ok, now I can see it...
Yes, it´s the query in the assignment process.
I have solved it...
I must write the To query without /
Thanks...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4202316#4202316
Reply to the post :
In the meantime, move the persistence.xml to the META-INF folder of your EJB
jar instead of keeping it in the META-INF of the EAR.
http://docs.jboss.org/ejb3/app-server/reference/build/reference/en/html/entityconfig.html
View the original post :
I believe this was fixed as part of
https://jira.jboss.org/jira/browse/JBAS-6061.
Also see this http://www.jboss.com/index.html?module=bbop=viewtopict=143892.
Did you change any configuration files of JBoss while creating the new test1
configuration?
View the original post :
anonymous wrote : while doing so, i have copied some jars into jboss.
Which jars have you copied and where?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4202322#4202322
Reply to the post :
Hello,
I'm running an .ear-Application on JBoss 4.2.2 containing jBPM. The
Swing-Client running on the client machine works fine when connecting to the
application server with the .ear-Application which uses a datasource in the
java:-namespace.
However, if I start a certain part of the
Hi All,
I am using jboss4.0.5+mysql5.0+hibernate3,i want to keep the database
connection alive,How can i do this,what configuraion should i do?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4202325#4202325
Reply to the post :
More details please, like the exception stacktrace. You mention that you are
using the datasource in hibernate.cfg.xml, which i believe is on the server
side (the same server where datasource is present). So i don't think there
should have been a problem.
While posting logs or xml content or
Hi JBoss Team!
I'm running JBoss Messaging with JBM statistics via JMX. Major monitoring
points are total message count since startup and getting current message count.
http://www.javapattern.info/attach/1/1128702652.jpg
Our transaction volume is over 5 millions message per day, however
Any chance that this problem of very long timeouts in spite of being configured
as much shorter is related to (and hopefully solved with) JIRA JBMESSAGING-1482
(Client remoting configuration not properly passed to jboss remoting)?
View the original post :
101 - 109 of 109 matches
Mail list logo