it works fine for me
Did u check if the database really contains a MD5 enrypted and Base64
encoded stringas u specified it is only md5 encrypted ...just check it
if not remove the Base64 propertybut it is better to save then base64
encoded in the database if not
regards
JB
If u r using Jboss3.2.1 and using web clients ( like servlets,jsps to access
secure EJB's) u must do the LoginContext.login() for every call made. (
Reason i Tomcat makes use of different thread for the same caller in
successive requests)
am i right scott
regards
jani
-Ursprungliche
Hi scott,
- As u said i do call the login() method in the client before i call any
method on the server. I thought it is used for the next calls made by the
client for which there is a method permission described
-But my first call form the Client is a SessionFacade.login(usrname, pwd)
which has a
HI,
Can any one kindly send me an example how to configure the following
settings with virtual host
-Jboss-3.2.1_Tomcat4.21
I have three different war files with different contexts deployed.
I want tomcat to listen on port 80 and 443.
I want to allow the first context on port 443 only
and the
HI,
Why is it necenssary to declare local interface at all.. as u can look up
for the interface with
InitialContext() and it wil not have any rmi overhead with in the same
JVM... am i wrong ...then just pls gimme a good example or scenario were to
use them
jani
-Ursprungliche Nachricht-
try this
table.put(java.naming.factory.initial,org.jboss.naming.HttpNamingContextF
actory);
table.put(java.naming.provider.url,
http://localhost:80/invoker/JMXInvokerServlet;);
the above are the settings for http invocation
the one which u used is for normal rmi
regards
jani
Hi,
I
tried to use the system proerties for Naming and inovker services as follows
and setting the System properties when the client starts
Jboss-Tomcat/server/default/http-invoker.sar/jboss-service.xml
!-- The HTTP invoker service
configration -- mbean
It
works when i set the System properties both on client and also on the server
Jboss-Tomcat/server/default/http-invoker.sar/jboss-service.xml
!-- The
HTTP invoker service configration -- mbean
code="org.jboss.invocation.http.server.HttpInvoker"
name="jboss:service=invoker,type=http"
could be that u shuld synchronize the vector before iterating over it..just
check the java.util.Collections class for more.
jani
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von Ionel
GARDAIS
Gesendet: Mittwoch, 21. Januar 2004 18:03
An: [EMAIL
Title: AW: [JBoss-user] problem with host name resolivng via http invoker
hi,
It
works fine but...it was totally a mislead in the Jboss All docus i read some
thing like this
InvokerURL: This is
either the http URL to the InvokerServlet mapping, or the
name of a
system property that
HI all,
I have a problem , first look at the output i get
10:43:58,458 DEBUG [WorkClientEJBServiceLocator] Using the JNDI URL
:http://localhost:80/invoker/JNDIFactory 10:43:58,520 DEBUG
[HttpNamingContextFactory] Retrieving content from :
http://localhost:80/invoker/JNDIFactory 10:43:58,583
.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Janardhan
Burugupalli
Sent: Thursday, January 08, 2004 2:10 AM
To: [EMAIL PROTECTED]
Subject: AW: [JBoss-user] problem
hi,
We also did shift from JBos2.2.2 to directly 3.2.1 recently ...i think there
is a lot changed so i would suggest u to turn on the trace for the plugins
package in ur log4j.xml and the carefully watch the log file ...u will
exactly know the cause of this error ...as i guess if ur sessionbean
HI,
I think this is a silly question ,but couldnt find which tag or property
setting i am missing in the ejb-jar.xml.
This warning appears since i changed all my jaws settings of my benas to
standardjaws.xml and i dont pack any jaws.xml in the xxx.jar which is in the
ear file.
2003-07-31
HI All,
With one or two client my Clietn runs perfectly and also all the
Transactions without fail.
But incase if we are testing with some five client at the same time then
after some time some of the TX are in a
deadlock...i got the log out put which says as below
2003-07-30 12:57:39,252
hi All,
I have a similar type of problem regarding the deadlock. My client hangs
and after some time i get the following message
13:15:34,646 WARN [TransactionImpl] Transaction TransactionImpl:XidImpl
[FormatId=257, GlobalId=Entwicklung16//7, BranchQual=] timed out.
status=STATUS_ACTIVE
one short question regarding the return type Collection or Set..
I thought a finder always returns a Collection or atleast the default
finders. Or is there a way to make it return a Set. If yes, then is there a
performance gain between the two return types..and we extensivley use
iterators over
HI All,
Can any one please send me valid script fro installing
Jboss-3.2.1-Tomcat-4.1.24 as a service using JNT.exe. I am trying to
install it on an XP machine with Jdk1.4.1_03.
I am currently using this script to do it but it fails. but please excuse me
if it has been already discussed. I
Thanks Scott,
That worked !! it was a great tip ..i dont know in spite of reading the
documentation many times we miss some things
but thanks ...
and i have one more question that i see a lot of debug stmts as below
2003-07-23 07:55:54,933 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New
Hi All,
I am using Jboss-3.2.1-Tomcat-4.1.24
j2sdk1.4.1_03
SAPDB
my Problem is i have a Entity bean which has two methods
setXXX()
getXXX()
one is a setXXX() method which sets some things and in this method i am
calling a getXXX() method of the same bean.
I am using
Hi All,
I have problems regarding the Tx lock. My client hangs when performing a
specific command like loading data of a form the server. Its always in the
same place . So in dont get any error message , but to think that there is a
TX lock i dont get any information in the server.log.
I
Hi,
I get the following warning if set the metricsinterceptor to true ..am i
missing something or is this the reason that Jboss 3.2.1 doesnt inform me of
a Tx lock if it happens.
Can any one please help me out. I cant even think of debugging without
knowing were and which bean w there is a Tx
value=INFO/
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Janardhan
Burugupalli
Sent: Tuesday, July 22, 2003 10:20 AM
To: [EMAIL PROTECTED]
Subject: AW: [JBoss-user] Tx lock detection not possible even as i
enabled EntityLockMonitor
Hi All
i used this url and it worked fine
http://localhost:8080/invoker/JNDIFactory
jani
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von Kristian
Köhler
Gesendet: Mittwoch, 16. Juli 2003 09:33
An: [EMAIL PROTECTED]
Betreff: [JBoss-user] Problem accessing
HI All,
I am accessing JNDI/RMI over http on port 80. So everything works fine and
if i try to read larger data from a bean
then i get the following error.
I guess the erro might be due to the socket time out. Is there any place
for the time out of the socket or some thing like that in the
HI All,
I was testing the RMI/JNDI over http on port 80. We configured a firewall
which allows only port 80 and everything seems to be working fine. We had
done a very rigorous testing and we encountered the following exception as
al of our clients are hanged and after a while we got the
Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von Janardhan
Burugupalli
Gesendet: Freitag, 11. Juli 2003 08:37
An: [EMAIL PROTECTED]
Betreff: AW: [JBoss-user] Socket TimeOut using RMI/JNDI over HTTP
HI All,
I am accessing JNDI/RMI over http on port 80. So everything works
use ear deployment ...pack each jar file in a separate ear file and deploy
..this works
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von Oisin Kim
Gesendet: Mittwoch, 9. Juli 2003 15:23
An: [EMAIL PROTECTED]
Betreff: [JBoss-user] Linkage error
Hello
Hi All,
I have a problem with TX locking when i use the QueuedPessimisticEJBLock the
application hangs at a point due to TX dead lock but when i use the NoLock
policy it is working fine. Can any one explain me this as i think it is not
good to use the NoLock policy ..but i really dont know how
(which version?) except the RequiresNew self deadlock.
Even then, the transaction timeout should roll it back.
If you are going to use NoLock, you should use the instance
per transaction configuration.
Regards,
Adrian
On Tue, 2003-07-08 at 13:55, Janardhan Burugupalli wrote:
Hi All,
I have
Rafal Kedziorski wrote:
hi,
has anybody experiences with JBoss and SAP DB?
Regards,
Rafal
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download
Hi All,
I have a finder defined in the jwas.xml like this below
finder
namefindAllOrdered/name
query/
orderCREATINGTIME DESC/order
/finder
i dont have any query because i want all results only in the Creating
time desc format
but jboss is generating the following
[EMAIL PROTECTED] wrote:
I'm guessing here, but:
1) Can you remove the query/ element? Does this stop JBoss from
generating the where clause?
2) Can you set the query to something like 1=1?
Dan.
Hi Dan,
I made it so that i was equating a filed with thee same
like
finder
HI All,
I am having a problem when accessing the finder written for an entitiy
bean in the jwas.xml
the finder looks like this
finder
namefindAllOrdered/name
query/query
orderCREATINGTIME DESC/order
/finder
and the exception when calling this finder looks like
on Solaris 8,
HP-UX
11.0, HP-UX 11.11, RedHat 9.0, and windows NT/XP/Win2k :)
Depending upon your OS, make sure you have all of the JVM patches that
vendor requires.. You can see JVM crashes due to missing OS patches...
Lori
-Original Message-
From: Janardhan Burugupalli [mailto:[EMAIL
Hi Once Again,
Can some one help me with this issue. Or if it is already posted and
resolved i am sorry to post it once again...but please forward me the
resolution ..
thanks for ur help
StandardWrapperValve[default]: Servlet.service() for servlet default
threw exception
Janardhan
Hi,
I am using Jboss-3.2.1-Tomcat-4.1.24 .
I was using the RMI/JNDI invokations using http invoker over port 80.
and downloaded a client using webstart and after some time the Jboss had
reported this error and shut down
saying that it generated a log file and i shuld look at it.
I have gone
HI All,
I am getting the above exception which doent block anything but there
should be some reason for this
i am using jBoss3.2.1-tomcat4.1.24..
the error occurs when i click on a jnlp file which is deployed in the
WorkClient.war file ..and starts downloading the jar files .
0736
[EMAIL PROTECTED] (Janardhan Burugupalli)
Sent by: [EMAIL PROTECTED]
09.06.2003 10:32
Please respond to jboss-user
To: [EMAIL PROTECTED]
cc:
Subject:Re: [JBoss-user] problem with DuplicateClass and LocaleBUndle
hi All,
Does any one have a solution
Janardhan Burugupalli wrote:
Hi All,
I solved the problem it was my mistake that i was having the
application.xml and jboss-app.xml same ...so it was too silly...sorry
jani.
Hi Jonathan,
I have read the whole document in the link which u gave me and tried
to follow it as it said to use
regarding this i tried a lot but failed to solve this
.
Java version used is - jdk-1.3.1_04
regards
jani
Mauricio De Diana wrote:
I had the same error when I had a deployed ear with
another name but the same classes.
Regards,
Mauricio
--- Janardhan Burugupalli [EMAIL PROTECTED]
escreveu: HI
HI guys,
I get the java.lang.ClassCastException: $Proxy320 exception when i
deploy the jar file while the jboss is running that is the hot
deploy...and then if i again try to get the Home interface it gives the
above exception on JBoss-tomcat-3.2.1
can any one explain this
regards
jani
com.sap.dbtech.jdbc.translators.ConversionExceptionSapDB: Cannot read
ASCII data from this long column
had an exception while accessing data from an entity bean...can some one
explain this
thanks jani
---
This SF.net email is sponsored by:
entity
ejb-nameUser/ejb-name
!--jndi-nameUser/jndi-name--
method-attributes
method
method-nameget*/method-name
16:39:29,887 WARN [TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=entwicklung2//9, BranchQual=] timed out. status=STATUS_ACTIVE
i get the above warning and in the Jboss and the client is hanging ..can any one help me with this . i already made all the getter
[EMAIL PROTECTED] wrote:
Hi,
is there a way so that i can start tomcat/jboss on a different port
than 8080?
i assume so...but which file do i have to edit in order to do that?
thanx and regards
marco
---
This SF.net email is
not
support xa but haven't investigated much.
david jencks.
On 2003.05.28 02:55 Janardhan Burugupalli wrote:
Hi All,
My sapdb-xa-ds.xml looks like this ...i have a problem that the
AIWORKDB is not bound while starting the JBoss
can some one correct this if anything goes wrong
Hi All,
My sapdb-xa-ds.xml looks like this ...i have a problem that the
AIWORKDB is not bound while starting the JBoss
can some one correct this if anything goes wrong in this...
and also i dont know how to specofy the driver class for the database
driver .i tried the normal
Janardhan Burugupalli wrote:
Hi All,
My sapdb-xa-ds.xml looks like this ...i have a problem that the
AIWORKDB is not bound while starting the JBoss
can some one correct this if anything goes wrong in this...
and also i dont know how to specofy the driver class for the database
driver .i
49 matches
Mail list logo