Hello todd,
no idea... I'd set it up the same way.
Some notes, though they scarcely have an impact.
- on-line docs say min-capacity can't be less then 2, though code
verifies it to be not less then zero;
- what is strictMaximumSize? i haven't found it neither in dtd nor
code. I looked at
Made the switch from 2.4.4 to 3.0.1 and after
adding and editingstuff formy apps, I'm chasing what these errors
are asking for ?
--- 3.0.1 output
03:39:20,039 INFO [MainDeployer] Deployment
of package:
file:/u/public/jboss/jboss-3.0.1/server/default/deploy/postgres-ds.xml is
waiting for
Hi,
I am trying to setup Jboss3.0.1. The following shows up in the boot.xml.
Have added a oracle-service.xml in the default/deploy dir.
This was working fine on Jboss3.0 (with Tomcat).
Do I have anything else to the oracle-service.xml file?
Thanks in advance,
Shankar.
Here is
I sure you've seen this issue before chaps:
When I call the home.create() method I get an RMI marshelling exception.
The tomcat installation is a stand-alone installation in a seperate JVM from
located on the same box.
The code works fine in a test client outside of tomcat.
The box is a windows
Hello,
BEA WLS supports foreign key not null with CMP 2.0
(http://edocs.bea.com/wls/docs70/faq/ejb.html#257467), but
as far as i know JBoss does not. Does anybody know,
when JBoss team plans to add this kind of feature?
kind regards,
Ago Meister
Replying to myself:
I've got this working now.
Having committed a UserTransaction, if I then begin a new
UserTransaction in the same thread, using the same JMS objects
(QueueSession, etc.), MQSeries complains
It seems that a new QueueSession must be created for each transaction.
Starting a
Ago Meister wrote:
Hello,
BEA WLS supports foreign key not null with CMP 2.0
(http://edocs.bea.com/wls/docs70/faq/ejb.html#257467), but
as far as i know JBoss does not. Does anybody know,
when JBoss team plans to add this kind of feature?
I would guess by the end of the year, but I don't
Have you tried 3.0.1? It has better exception handling code, so you
should get a better error message.
-dain
Arijit Ghosh wrote:
Hi,
I'm using container managed transaction of Jboss 3.0 with Tomcat
4.0.3. We are using the Struts framework and Castor.
When i try to
Hi Shankar.
The following has been changed;
Was:
depends
optional-attribute-name=JaasSecurityManagerServicejboss.security:name=JaasSecurityManager/depends
Now:
depends
optional-attribute-name=JaasSecurityManagerServicejboss.security:service=JaasSecurityManager/depends
shankar wrote:
Hi Shankar.
The following has been changed;
Was:
depends
optional-attribute-name=JaasSecurityManagerServicejboss.security:name=JaasSecurityManager/depends
Now:
depends
optional-attribute-name=JaasSecurityManagerServicejboss.security:service=JaasSecurityManager/depends
shankar wrote:
I've improved my position a bit here for anyone's information.
M$ is a *** for putting folders in with spaces.
I had a tomcat webapp working from a documents and settings folder
this seems to be the root of the issue.
The JBoss client jars just don't seem to like spaces anywhere within the
same
Folks,
I'm trying to move over to JBoss 3.0.1 from JBoss 3.0.0 and I can't figure out my problem. When I deploy my EAR it fails due to one of my JARs being already registered.
However, the same EAR works perfectly in JBoss 3.0.0.
Stranger still, in JBoss 3.0.1, if I unzip the EAR file into a
Hello!
Are there any data on the market share of JBoss in Austria or
Germany (that is, whether JBoss is used widely in these countries) ?
I'm considering to participate on a JBoss training and want to know
whether there is a market for JBoss-related consulting in this region.
Thanks
Dimitri
Can someone post an update on the effect of the following Sun JVM bugs
on JBoss 3.0.1?
http://developer.java.sun.com/developer/bugParade/bugs/4670071.html
http://developer.java.sun.com/developer/bugParade/bugs/4699981.html
The JBoss book for 3.0.1 says that, for 3.0.0:
The default class
While using JBoss 3.0.1 (and we have never had this working with
previous versions of Jboss 3.0) we get a loader constraints violated
when deploying two application ears.
The loader constraints relate to a class inside a jar in each
application's web tier. The jars inside each each ear are
Alex:
The strictMaximumSize tag comes from a post I found on the JBoss foums referencing a
similar problem back in the 2.4 timeframe. I have tried both with and without it and
also with different numbers for maximum to no avail. I'm running out of options to
try. Is this working for you
I have figured it out. My configuration-name reference needed to be included WITHIN
the session tag, not immediately following it. Once I made this change, all worked
as documented.
Thanks for all you assistance.
Todd
--
Hello todd,
no idea... I'd set it up
Hello todd,
Friday, August 09, 2002, 6:47:47 PM, you wrote:
tac The strictMaximumSize tag comes from a post I found on the JBoss foums
referencing a similar problem back in the 2.4 timeframe. I have tried both with and
without it and also with different
tac numbers for maximum to no avail.
AFAIK, strict pool size is not available in 3.x, it had not been ported.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]De la part de
[EMAIL PROTECTED]
Envoye : vendredi, 9 aout 2002 17:48
A : [EMAIL PROTECTED]
Objet : Re[2]: [JBoss-user] How to limit # of
any idea???
Emerson Cargnin - SICREDI Serviços wrote:
I'm getting some strange errors when using JAAS through stand-alone
client. I didn't have this errors before, it appeared after migrating to
XDoclet CVS (??? nothing to do at all).
is there any way to see how a class is protected
The ejb-jar.xml descriptor is the only source of permissions. The jboss.xml
descriptor defines the security domain. Compare these two files before
and after xdoclet.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message
This is just a note for other users of PostgreSQL. With the latest version
of JBoss3.0.1 you can no longer be able to use a column definition of TIME in
Postgre. This is NOT a bug in JBoss, but rather a bug in jdbc driver for
PostgreSQL (even the latest dev driver). The JBoss3.0.1 changes
I'm trying to upgrade to 3.0.1 and get the following error even when
starting with -c default:
16:28:44,418 WARN [Manager] distributed Store
(org.jboss.jetty.session.ClusterStore) failed to initialise
java.lang.NoClassDefFoundError:
Jon Swinth wrote:
This is just a note for other users of PostgreSQL. With the latest version
of JBoss3.0.1 you can no longer be able to use a column definition of TIME in
Postgre. This is NOT a bug in JBoss, but rather a bug in jdbc driver for
PostgreSQL (even the latest dev driver).
Did login-config.xml changed in 3.0.1 version
message:
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[org.jboss.deployment.DeploymentInfo@e944a28d {
url=file:/home/emersonc/jboss-3.0.1/server/default/deploy/login-config.xml }
deployer: null
status: null
login-config.xml does not belong in the deploy directory. It ships
in the server/default/conf directory
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Emerson Cargnin - SICREDI Serviços [EMAIL PROTECTED]
Clustering is part of the all configuration, not the default. Also,
the required sar is in docs/examples/clustering/jbossha-httpsession.sar
and needs to be moved to the server/all/deploy directory.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
well, it moved to conf dir, now it works : )
Emerson Cargnin - SICREDI Serviços wrote:
Did login-config.xml changed in 3.0.1 version
message:
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[org.jboss.deployment.DeploymentInfo@e944a28d {
just a warning, that's caused by a distributable/ tag in my web.xml.
Emerson Cargnin - SICREDI Serviços wrote:
I'm trying to upgrade to 3.0.1 and get the following error even when
starting with -c default:
16:28:44,418 WARN [Manager] distributed Store
Anyone clue me in as to what's going on w/ these msgs from startup of
3.0.1 ...
Any help much appreciated.
--- output
17:18:10,151 INFO [MainDeployer] Deployment of package:
file:/u/public/jboss/jboss-3.0.1/server/default/deploy/postgres-ds.xml
is waiting for an appropriate deployer.
i just was told about that, sorry for that...
Scott M Stark wrote:
login-config.xml does not belong in the deploy directory. It ships
in the server/default/conf directory
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-
I am looking for a free software solution to load balance http requests
to multiple instances of JBoss/Jetty in a cluster inorder to test
ClusteredHttpSessions. Any ideas? What does everyone else use?
Greg Turner
---
This sf.net email is
Thanks for the reply Dain. You are right. I read the code wrong. The code
calls a method based on the destination class first before attempting the
getBytes() call. I'm guessing the reason for my issue is that the
destination class is java.util.Date which maps to getTimestamp() which is
This is the most asked question from jboss history : )
diference between 3.0.0 and 3.0.1 :
3.0.0 :
depends
optional-attribute-name=JaasSecurityManagerServicejboss.security:name=JaasSecurityManager/depends
3.0.1 :
depends
I looked in my postgres-service.xml file and it's already as you state.
Should I be changing this elsewhere?
On Friday, August 9, 2002, at 04:30 PM, Emerson Cargnin - SICREDI
Serviços wrote:
This is the most asked question from jboss history : )
diference between 3.0.0 and 3.0.1 :
not that I know, sorry...
Gary Grobe wrote:
I looked in my postgres-service.xml file and it's already as you state.
Should I be changing this elsewhere?
On Friday, August 9, 2002, at 04:30 PM, Emerson Cargnin - SICREDI
Serviços wrote:
This is the most asked question from jboss
I'm having a few problems w/ my 3.0.1 postgres
setup. I've included the error message (which I don't really understand) below
along w/ the postgres-service.xml and postgres-ds.xml files below that ... (it
just seemed to complain about the postgres-ds.xml) ...
Any help much appreciated.
There's a bug somewhere here, perhaps you could file a report.
You will stress the jca machinery less if you get the connection after the
tx has started and close the connection before the tx commits.
I think someone did get MQSeries to work, look in the messaging forum.
david jencks
On
Hi everyone -
I still need some help/guidance on this. Didn't get a response last
time around. This is a huge problem since I can't reliably get
connections when needed.
Thanks,
David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of David Brady
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
There were concurrency problems in the pool in 2.4. Many of
these have been fixed in the 2.4.5-2.4.7 release. Additional pool
issues have been fixed in the 2.4.8 release which will be available
tomorrow.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Hi All,
I am using Jboss-3.0.0_Tomcat4.0.3. I am getting following problem while
running in this environment
javax.naming.CommunicationException [Root exception is
java.lang.ClassNotFoundException: org.jboss.proxy.ClientContainer (no
security manager: RMI class loader disabled)]
I tried to put
Is the SAP adapter itself deploying properly? this makes it look like it
isn't:
ObjectName: jboss.jca:service=XaTxDS,name=SAPConnectorFactory
state: CONFIGURED
I Depend On: jboss.jca:service=RARDeployment,name=SAP R3 Connector
Depends On Me:
The incomplete deployment exception tries to tell you about all the
problems your deployments are having.
In this case, stop using *-ds.xml files or upgrade to 3.2 or 4.0 where they
are supported.
david jencks
On 2002.08.09 03:08:17 -0400 G.L. Grobe wrote:
Made the switch from 2.4.4 to 3.0.1
confirm 564564
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
Believe the deployer: null part. *-ds.xml files are only for 3.2 and
later.
david jencks
On 2002.08.09 23:47:10 -0400 G.L. Grobe wrote:
I'm having a few problems w/ my 3.0.1 postgres setup. I've included the
error message (which I don't really understand) below along w/ the
Not sure I understood this reply. What's happening is that 3.0.1 is hanging
at this point. I've placed the last lines of the output at the end of this
reply where it hangs.
- Original Message -
From: David Jencks [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, August 10, 2002
48 matches
Mail list logo
