Thanks for your reply. Upgrade from jboss 4.0.1SP1 to 4.2.2.GA with jdk 1.5.
The exception occurs regularly without affecting any functionality that I can
see. It does not happen during startup but during deployment and running the
app. But it seems to have been resolved now that I removed
Dear guys,
How do I interpret the following stacktrace after upgrading to 4.2.2.GA:
2008-02-02 19:12:28,151 DEBUG
[org.jboss.web.tomcat.security.SecurityFlushSessionListener] Obtaining
SecurityManagerService failed::
| java.lang.ClassCastException: org.jnp.interfaces.NamingContext
|
There are at leaast 3 workarounds which work for me so upload directory is
independent of jboss installation directory:
a) Set the upload directory in a properties file,
b) use a symbolic link in your file system, or
c) store the files in a database.
You can always inspect the apache file
Dear experts,
The file server/default/deploy/jbossweb.sar/ROOT.war/readme.html
is browsable at http://localhost/readme.html
Are there jbossweb settings enabling browsing a file like
server/default/deploy/jbossweb.sar/ROOT.war/réadme.html
at http://host/réadme.html ?
Thanks
Niklas
View the
genman wrote :
| Does it work?
|
| What is your OS? If Linux, did you set your default Locale to UTF-8?
On MS-Windows it works and on Linux (Ubuntu) it works with Apache2 Web Server
but not with JBoss Web Server, JBoss AS nor Tomcat. A file named café.html is
inaccessible (404) from the
I also have this problem reproduced with jboss4.2CR2 with an app which works
with suns app server. The attribute id is mandatory for the tag.
index.jsp:
| [EMAIL PROTECTED] contentType=text/html%
| [EMAIL PROTECTED] pageEncoding=UTF-8%
| [EMAIL PROTECTED]
Apache and mod_jk in front of jboss can achieve it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4043283#4043283
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4043283
___
PeterJ wrote : Sorry, I was typing from memory and not from example code. I
meant to also show getting the connection from the datasource and then closing
the connection in the fiinally block.
Thank you Peter. I am happy now that the connection is closing. I am now
deploying to the jboss web
PeterJ wrote : You code should look like:
|
| DataSource ds = null;
| | try {
| | ds = ctx.lookup(...);
| | --do database stuff --
| | } finally {
| | if (ds != null) ds.close();
| | }
|
| If you don't close the datasource before exiting the method, you get
I get the message
[org.jboss.resource.connectionmanager.CachedConnectionManager] Closing a
connection for you. Please close them yourself:
org.jboss.resource.adapter.jdbc.WrappedConnection
What am I missing?
View the original post :
10 matches
Mail list logo
