[JBoss-dev]

2003-08-17 Thread
Title: 






 
  
 
   
   

 
  

   

 
5000








  
   
! 
  
   
   
  140019650050052050050050050020060035 
   
  24190050005 
   
   

  
  
   

  
   

010-84898025,84898027
   ! 

If this email faze you ,please Click 
Here! ,we won't send you again.
 
  
  


  
  





---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-764553 ] housekeeping in ServerImpl and ServerConfigLocator

2003-08-17 Thread SourceForge.net
Bugs item #764553, was opened at 2003-07-02 15:28
Message generated for change (Comment added) made by juhalindfors
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=764553group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Rod Burgett (rodburgett)
Assigned to: Juha Lindfors (juhalindfors)
Summary: housekeeping in ServerImpl and ServerConfigLocator

Initial Comment:
This patch addresses housekeeping deficiencies in the 
org.jboss.system.server.ServerImpl and 
ServerConfigLocator classes.

The ServerConfigLocator class has no shutdown method 
but it does hold a static reference to an 
MBeanProxyExt.  This reference becomes invalid when 
the MBeanServer is shutdown.  This patch adds a static 
shutdown method to null out the reference.  Code to 
invoke this new method is added to the shutdown 
processing in ServerImpl.

Several updates are made to the ServerImpl class, some 
making use of updates to other classes from this and 
another patch.  The dependency on another patch is 
noted in the change descriptions below.

There are two changes to the ServerImpl.shutdown() 
method: the shutdown hook that was registered with 
the system runtime during startup is removed, and a null 
check is added before invoking accessors on the 
ServerConfig.

It makes sense to unregister the shutdown hook when 
JBoss is shutdown manually.  In the situation where 
JBoss startup/shutdown is controlled by an outside 
class, this shutdown hook will attempt to repeat the 
process when the VM exits.

Since the init() method will throw an 
IllegalStateException if it finds a non-null config field, 
the shutdown process needs to null out this field.  That 
makes it prudent to check for a null value prior to 
attempting to access methods.  Default values for 
local 'exitOnShutdown' and 'blockingShutdown' flags are 
taken from ServerConfig when config == null.

A few lines of cleanup are added to the 
ShutdownHook.run() method to null out some ServerImpl 
fields and to encourage the GC to run.  This shutdown() 
method needs a (config == null) before attempting to 
find and delete the tmp/deploy directory.

A few comments and error literals from the 
ShutdownHook.shutdownDeployments() and 
shutdownServices() methods suffered from cut-n-paste 
lapse, they are corrected in this patch.

The ShutdownHook.removeMBeans() method is updated 
to include a check for non-null mbean server reference.  
Also, the previous request that the MBeanServerFactory 
release the current mbean server is replaced with a 
request to shutdown the mbean registry.  The registry 
shutdown() method is added by JBoss patch #763378, 
which includes addition of a shutdown method to the 
MBeanServerImpl.  The mbean server shutdown process 
includes a call to the 
MBeanSercverFactory.releaseMBeanServer() method.  
Note that the current patch will cause a run time error - 
probably UnsupportedMethod - if patch #763378 is not 
applied before the current patch.

Prior to shutting down the registry, a new 
ShutdownHook method is called to remove any leftover 
service mbeans.  This new method, 
removeLeftoverMBeans(), queries the mbean server for 
all registered mbeans and attempts to remove most.  
This server impl lacks permission to remove mbeans from 
the 'implementation' domain, so these are skipped, they 
must be removed by the mbean server.


--

Comment By: Juha Lindfors (juhalindfors)
Date: 2003-08-17 15:43

Message:
Logged In: YES 
user_id=175239

I read through the patch and it looks to me the removal of
shutdown hook is in incorrect place. 

If the hook is removed and we have ExitOnShutdown == true
then the call to Runtime.exit() will not have a chance to
execute the shutdown hook (or it should explicitly do so
inside the ServerImpl.exit() method).

For ExitOnShutdown == false the patch looks valid as both
execution paths will execute the shutdown hook's shutdown()
method explicitly.

If I missed something in your patch let me know. Otherwise I
will apply it with the above modification.


--

Comment By: Rod Burgett (rodburgett)
Date: 2003-07-02 15:28

Message:
Logged In: YES 
user_id=681969

add the other diff file...

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=764553group_id=22866


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]

[JBoss-dev] [ jboss-Bugs-782678 ] DistributedReplicantManager.isMasterReplica(String) false +

2003-08-17 Thread SourceForge.net
Bugs item #782678, was opened at 2003-08-04 10:18
Message generated for change (Comment added) made by slaboure
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=782678group_id=22866

Category: Clustering
Group: v3.2
Status: Closed
Resolution: Fixed
Priority: 6
Submitted By: Sacha Labourey (slaboure)
Assigned to: Sacha Labourey (slaboure)
Summary: DistributedReplicantManager.isMasterReplica(String) false +

Initial Comment:
There is a race condition i the 
DistributedReplicantManager.isMasterReplica(String) that 
shows up when this 
method is called from within a notifyKeyListeners as 
shown by this stack trace:

Thread main@65 status: RUNNING
- isMasterReplica():437, 
org.jboss.ha.framework.server.DistributedReplicantManag
erImpl
- isDRMMasterReplica():234, 
org.jboss.ha.jmx.HAServiceMBeanSupport
- partitionTopologyChanged():103, 
org.jboss.ha.singleton.HASingletonSupport
- replicantsChanged():197, 
org.jboss.ha.jmx.HAServiceMBeanSupport$1
- notifyKeyListeners():675, 
org.jboss.ha.framework.server.DistributedReplicantManag
erImpl
- add():326, 
org.jboss.ha.framework.server.DistributedReplicantManag
erImpl
- registerDRMListener():204, 
org.jboss.ha.jmx.HAServiceMBeanSupport
- startService():144, 
org.jboss.ha.jmx.HAServiceMBeanSupport

This is due the the choice to return true when the key in 
question is in the
localReplicants table, but not the replicants table:

public boolean isMasterReplica (String key)
{
   if (!localReplicants.containsKey (key))
  return false;

   Vector allNodes = this.partition.getCurrentView ();
   HashMap repForKey = (HashMap)replicants.get
(key);
   if (repForKey==null)
  return true; 

This seems to be an ambiguous condition as this 
condition exists for a node that 
calls add and when the state has not synched or has 
failed to synch. Another 
problem I'm seeing at least in the context of the 
singleton service is that the 
notion of the master node is unstable. Here is the output 
from one of 3 nodes 
running the singleton service starting with the addition 
of the final node shown 
as view 2.

15:35:44,637 INFO  [Server] JBoss (MX MicroKernel) 
[3.2.2RC3 (build: 
CVSTag=Branch_3_2 date=200307312219)] Started in 
5s:948ms
15:36:27,719 INFO  [DefaultPartition] New cluster view: 
2 ([lamia:32947, 
172.17.66.54:2821, ironmaiden:51770] delta: 1)
15:36:27,749 INFO  [DefaultPartition:ReplicantManager] 
Dead members: 0
15:37:13,555 INFO  [DefaultPartition] New cluster view 
(id: 3, delta: -1) : 
[172.17.66.54:2821, ironmaiden:51770]
15:37:13,575 INFO  [DefaultPartition:ReplicantManager] 
Dead members: 1
15:38:13,321 INFO  [HASingletonMBeanExample] Notified 
to start as singleton
15:38:13,321 INFO  [DefaultPartition] New cluster view 
(id: 4, delta: 1) : 
[172.17.66.54:2821, ironmaiden:51770, lamia:32949]
15:38:13,331 INFO  [DefaultPartition:ReplicantManager] 
Dead members: 0
15:38:13,361 INFO  [HASingletonMBeanExample] Notified 
to stop as singleton
15:39:13,447 INFO  [HASingletonMBeanExample] Notified 
to start as singleton
15:39:13,457 INFO  [HASingletonMBeanExample] Notified 
to stop as singleton

With view 3 the orginal node and singleton is killed and 
the node for which the 
console output corresponds(172.17.66.54) is selected as 
the singleton. When the 
third node is started again there is some thrashing due 
to the existing 2 nodes 
both selecting themselves as the singleton and telling 
the other to stop and it 
appears that there is no singleton choosen. The problem 
seems to be inconsistent 
  matching of member names. Once only knows it IP 
while the other node knows the 
hostnames. Here is the console view of the second node 
showing the hostnames and 
its thrashing:

15:25:21,023 INFO  [Server] JBoss (MX MicroKernel) 
[3.2.2RC3 (build: 
CVSTag=Branch_3_2 date=200307312219)] Started in 
13s:597ms
15:26:05,562 INFO  [DefaultPartition] New cluster view: 
3 ([succubus:2821, 
ironmaiden:51770] delta: -1)
15:26:05,573 INFO  [DefaultPartition:ReplicantManager] 
Dead members: 1
15:27:05,506 INFO  [HASingletonMBeanExample] Notified 
to start as singleton
15:27:05,509 INFO  [DefaultPartition] New cluster view: 
4 ([succubus:2821, 
ironmaiden:51770, lamia:32949] delta: 1)
15:27:05,513 INFO  [DefaultPartition:ReplicantManager] 
Dead members: 0
15:27:05,531 INFO  [HASingletonMBeanExample] Notified 
to stop as singleton
15:28:05,520 INFO  [HASingletonMBeanExample] Notified 
to start as singleton
15:28:05,526 INFO  [HASingletonMBeanExample] Notified 
to stop as singleton

Its not clear that the 
DistributedReplicantManager.isMasterReplica was 
designed 
to be used for the selection of a singleton node, but if it 
is, the logic needs 
to be firmed up. If not, the singleton service needs to be 
built on something else.

-- 

Scott Stark
Chief Technology Officer
JBoss Group, LLC


--


[JBoss-dev] [ jboss-Bugs-767905 ] Farm re-deployment doesn't work

2003-08-17 Thread SourceForge.net
Bugs item #767905, was opened at 2003-07-08 19:00
Message generated for change (Comment added) made by slaboure
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=767905group_id=22866

Category: Clustering
Group: v3.2
Status: Open
Resolution: Fixed
Priority: 5
Submitted By: Kevin Duffey (kevin-duffey)
Assigned to: Sacha Labourey (slaboure)
Summary: Farm re-deployment doesn't work

Initial Comment:
We are seeing sporadic workings of the 
clustering/farming redeployment. If we drop a jar in 
the /farm of one node, it properly gets copied and 
deployed to other nodes in the same partition. If we 
drop a new version of the same .jar, it appears that 
other nodes get some sort of message, but the .jar is 
not actually copied and redeployed on the other nodes.

If we delete a .jar out of the /farm dir of one node, it 
seems to properly undeploy and delete it out of other 
nodes as well.

Not sure if this last item is a separate bug, but if you 
bring on a new node, nothing in the /farm dir of any 
other node seems to get farmed to the newly online 
node. That is to say, an empty node, one without 
the .jar in its /farm dir, seems to not get the .jar at all 
until you delete then drop the .jar in a farm dir again.

I do not know if the above occurs if you reboot a node 
with the jar in the farm or not.


--

Comment By: Sacha Labourey (slaboure)
Date: 2003-08-17 22:41

Message:
Logged In: YES 
user_id=95900

A bug has been fixed, can you please try again with a fresh 
CVS checkout (wait 24h to see the changes in anonymous 
CVS)

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=767905group_id=22866


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-585014 ] JBossCMP giving error in dynamic-ql when passing an array wi

2003-08-17 Thread SourceForge.net
Bugs item #585014, was opened at 2002-07-22 11:58
Message generated for change (Comment added) made by dsundstrom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=585014group_id=22866

Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Emerson Cargnin (echofloripa)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBossCMP giving error in dynamic-ql when passing an array wi

Initial Comment:
When creating dynamic queries, normally someone have 
a max size array created at first, and populate it 
depending on the business rules (for example, having 
null parameters). If you create an array with size of three 
and jboss-ql = 
SELECT object(p) FROM TestParent p WHERE 
p.idade=?1  ORDER BY p.nome 
array = [20, null] 
although i use just the first one jboss it gives me the 
following error : 
 
13:59:22,954 INFO  [STDOUT] Parameter[1] is null 
13:59:22,954 ERROR [STDERR] 
javax.ejb.FinderException: Parameter[1] is null 
13:59:22,956 ERROR [STDERR] at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCDynamicQLQuery.execute(JDBCDynamicQLQuery.java:61) 
13:59:22,956 ERROR [STDERR] at 
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCSelectorBridge.execute(JDBCSelectorBridge.java:64)
 
13:59:22,957 ERROR [STDERR] at 
org.jboss.ejb.plugins.cmp.bridge.EntityBridgeInvocationHandler.invoke(EntityBridgeInvocationHandler.java:95)
 
13:59:22,957 ERROR [STDERR] at 
org.jboss.proxy.compiler.Runtime.invoke(Runtime.java:59) 
13:59:22,958 ERROR [STDERR] at 
server.ejb.TestParentEJB$Proxy.ejbSelectGeneric(generated) 
13:59:22,958 ERROR [STDERR] at 
server.ejb.TestParentEJB.ejbHomeSelectTest(TestParentEJB.java:150) 
13:59:22,958 ERROR [STDERR] at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method) 
13:59:22,959 ERROR [STDERR] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
13:59:22,959 ERROR [STDERR] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
13:59:22,960 ERROR [STDERR] at 
java.lang.reflect.Method.invoke(Method.java:324) 
13:59:22,960 ERROR [STDERR] at 
org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1137)
 
13:59:22,960 ERROR [STDERR] at 
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:73) 
13:59:22,961 ERROR [STDERR] at 
org.jboss.ejb.plugins.EntitySynchronizationInter 

--

Comment By: Dain Sundstrom (dsundstrom)
Date: 2003-08-17 17:41

Message:
Logged In: YES 
user_id=251431

I am no no longer a JBoss committer, so I am unable to fix
any bugs.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=585014group_id=22866


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-550606 ] Too many AND's and OR's with Sybase

2003-08-17 Thread SourceForge.net
Bugs item #550606, was opened at 2002-04-30 08:00
Message generated for change (Comment added) made by dsundstrom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=550606group_id=22866

Category: JBossCMP
Group: v4.0
Status: Open
Resolution: Postponed
Priority: 5
Submitted By: Daniel Moos (moosi_1978)
Assigned to: Nobody/Anonymous (nobody)
Summary: Too many AND's and OR's with Sybase

Initial Comment:
I have following problems with Sybase 11.9.2 and
JBoss3.0.0RC1:

If Jboss call findAll()-Methode, then throws a
following Exception :

14:25:40,730 INFO  [STDOUT] SQLException:
SQLState(Z) vendor code(404)
14:25:40,731 INFO  [STDOUT]
com.sybase.jdbc2.jdbc.SybSQLException: Too many ANDs or
ORs in expression (limit 250 per expression level). Try
splitting query or limiting ANDs and ORs.

Before Jboss call findAll-Methode, put i 300 rows in a
Table over Jboss. What i doing false? Who can help me?





--

Comment By: Dain Sundstrom (dsundstrom)
Date: 2003-08-17 17:36

Message:
Logged In: YES 
user_id=251431

I am no no longer a JBoss committer, so I am unable to fix
any bugs.

--

Comment By: Sacha Labourey (slaboure)
Date: 2003-04-19 11:22

Message:
Logged In: YES 
user_id=95900

Is this now fixed Dain?

--

Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-06-24 18:51

Message:
Logged In: YES 
user_id=251431

This will be fixed during the rewrite of the metadata
package in 3.1.

--

Comment By: Daniel Moos (moosi_1978)
Date: 2002-05-02 04:50

Message:
Logged In: YES 
user_id=332885

Sorry, i set you're proposition and the Exception did not
change. I even set in jaws.xml or standardjaws.xml a
read-ahead tag to true, no change too.

--

Comment By: Georg Schmid (giorgio42)
Date: 2002-04-30 12:26

Message:
Logged In: YES 
user_id=437570


Maybe reducing the page size for the read-ahead
to something below 250 (in standardjbosscmp-jdbc.xml or
jbosscmp-jdbc.xml) helps.

Georg

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=550606group_id=22866


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-595672 ] Deserialization broken in JBoss 3.01

2003-08-17 Thread SourceForge.net
Bugs item #595672, was opened at 2002-08-15 13:28
Message generated for change (Comment added) made by dsundstrom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=595672group_id=22866

Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: Wont Fix
Priority: 8
Submitted By: Boris Tamarkin (upss)
Assigned to: Nobody/Anonymous (nobody)
Summary: Deserialization broken in JBoss 3.01

Initial Comment:
Win2000 operating system
MySQL or MS SQLServer 2000 databases

mapping in standardjbosscmp-jdbc.xml (same as in 3.0)
for mySQL
java-typejava.lang.Object/java-type
jdbc-typeJAVA_OBJECT/jdbc-type
sql-typeLONGBLOB/sql-type

java-typejava.lang.Object/java-type 
jdbc-typeJAVA_OBJECT/jdbc-type 
sql-typeIMAGE/sql-type 

Repeat scenario
Having CMP2 entity bean with one Object atribute.
Call setObject works fine and store as a Blob in 
database.
When trying to retreive after, failure happens.
Stacktrace attached below

*Notes:
1. Serialization and deserialization doing only with 3.01 
version of JBoss
2. Not trying to deserealize old blobs (I am aware of it 
can be not supported and compatible with earlier version 
of JBoss)
3. This functionality and same code works fine with 
previous JBoss 3.0 version, but it is broken in 3.01.
Thanks

Stacktrace
*
10:51:02,738 ERROR [LogInterceptor] 
TransactionRolledbackLocalException, causedB
y:
java.sql.SQLException: Unable to load to deserialize 
result: java.io.StreamCorru
ptedException: invalid stream header
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCUtil.convertByteArra
yToObject(JDBC
Util.java:612)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCUtil.getResult
(JDBCUtil.java:311)
at 
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMP
FieldBridge.load
ArgumentResults
(JDBCAbstractCMPFieldBridge.java:350)
at 
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMP
FieldBridge.load
InstanceResults(JDBCAbstractCMPFieldBridge.java:304)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityComman
d.execute(JDBCLoad
EntityCommand.java:142)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityComman
d.execute(JDBCLoad
EntityCommand.java:62)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.load
Entity(JDBCStoreM
anager.java:572)
at 
org.jboss.ejb.plugins.CMPPersistenceManager.loadEntit
y(CMPPersistence
Manager.java:410)
at 
org.jboss.resource.connectionmanager.CachedConnectio
nInterceptor.load
Entity(CachedConnectionInterceptor.java:353)
at 
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.inv
oke(EntityS
ynchronizationInterceptor.java:262)
at 
org.jboss.resource.connectionmanager.CachedConnectio
nInterceptor.invo
ke(CachedConnectionInterceptor.java:186)
at 
org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke
(EntityInstance
Interceptor.java:152)
at 
org.jboss.ejb.plugins.EntityLockInterceptor.invoke
(EntityLockIntercep
tor.java:107)
at 
org.jboss.ejb.plugins.EntityCreationInterceptor.invoke
(EntityCreation
Interceptor.java:69)
at 
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext
(AbstractTxInte
rceptor.java:107)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti
ons(TxIntercep
torCMT.java:178)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke
(TxInterceptorCMT.java:6
0)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke
(SecurityInterceptor.
java:130)
at org.jboss.ejb.plugins.LogInterceptor.invoke
(LogInterceptor.java:203)
at org.jboss.ejb.EntityContainer.invoke
(EntityContainer.java:493)
at 
org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.inv
oke(BaseLoca
lContainerInvoker.java:301)
at org.jboss.ejb.plugins.local.EntityProxy.invoke
(EntityProxy.java:38)
at $Proxy161.getKeyValue(Unknown Source)
at com.rendition.MyEJB.retrieveKey
(MyEJB.java:155)
**

--

Comment By: Dain Sundstrom (dsundstrom)
Date: 2003-08-17 17:41

Message:
Logged In: YES 
user_id=251431

I am no no longer a JBoss committer, so I am unable to fix
any bugs.

--

Comment By: Axel Mueller (camueller)
Date: 2002-11-12 15:46

Message:
Logged In: YES 
user_id=389955

It seems to be fixed in 3.0.4 (in 3.2.0beta it is NOT fixed).

--

Comment By: Stephen Coy (scoy)
Date: 2002-11-01 17:25

Message:
Logged In: YES 
user_id=463096

I believe that its fixed in Branch_3_0, Branch_3_2 and HEAD


--

Comment By: Boris Tamarkin (upss)
Date: 2002-11-01 11:45

Message:
Logged In: YES 
user_id=595649

Is it fixed in release, or in CVS?
In JBoss 3.0.3 is not seem to be fixed.
Thanks

--

Comment By: Stephen Coy (scoy)
Date: 2002-10-31 01:29

[JBoss-dev] [ jboss-Bugs-571995 ] Wrong error reporting for ejb finders

2003-08-17 Thread SourceForge.net
Bugs item #571995, was opened at 2002-06-21 02:07
Message generated for change (Comment added) made by dsundstrom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=571995group_id=22866

Category: JBossCMP
Group: v4.0
Status: Open
Resolution: Postponed
Priority: 5
Submitted By: Stephen Coy (scoy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong error reporting for ejb finders

Initial Comment:
I had erroneously declared a finder method as:

java.util.Set findUserLists(com.whitesmiths.sacha.ejb.auth.interfaces.UserLocal user)

Note the use of Set. Sets are only legal for select methods.

When I tried to deploy this, JBoss (Branch_3_0) said:

org.jboss.deployment.DeploymentException: Error compiling ejbql; - nested throwable: 
(org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered EOF at line 1, column 
96.
Was expecting one of:
IN ...
ABSTRACT_SCHEMA ...
)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.init(JDBCEJBQLQuery.java:46)
at 
org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createEJBQLQuery(JDBCCommandFactory.java:44)

which had me looking for syntax errors in the EJB QL, instead of the method signature.



--

Comment By: Dain Sundstrom (dsundstrom)
Date: 2003-08-17 17:39

Message:
Logged In: YES 
user_id=251431

I am no no longer a JBoss committer, so I am unable to fix
any bugs.

--

Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-06-24 18:54

Message:
Logged In: YES 
user_id=251431

This will be fixed during the rewrite of the metadata
package in 3.1.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=571995group_id=22866


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-562004 ] 'Error setting column value' using dependent value classes w

2003-08-17 Thread SourceForge.net
Bugs item #562004, was opened at 2002-05-29 13:11
Message generated for change (Comment added) made by dsundstrom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=562004group_id=22866

Category: JBossCMP
Group: v4.0
Status: Open
Resolution: Postponed
Priority: 5
Submitted By: Justin Casp (jcasp)
Assigned to: Nobody/Anonymous (nobody)
Summary: 'Error setting column value' using dependent value classes w

Initial Comment:
I posted this problem a few weeks ago on jboss.org forums, but it's down 
right  
now so I can't reference that post.  I figured out how to create a simple test  
case that reliably reproduces the problem.  
  
The error message 'Error setting column value' occurs when I have an  
existing CMP bean that reads existing records from a datasource.  The bean  
uses a dependent value class, although I'm not sure if this problem is  
specific to dependent value classes or just any cmp bean with fields 
mapped  
to columns.  
If I create the record externally (e.g., using psql, the postgres command line  
tool) and only set a few of the columns to non-null values, when I attempt to  
load that bean instance with a finder, jboss throws the following exception 
on  
the server:  
 
12:03:56,650 ERROR [STDERR] java.lang.NullPointerException  
12:03:56,652 ERROR [STDERR] at  
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  
12:03:56,652 ERROR [STDERR] at  
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)  
12:03:56,653 ERROR [STDERR] at  
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)  
12:03:56,653 ERROR [STDERR] at  
java.lang.reflect.Method.invoke(Method.java:324)  
12:03:56,653 ERROR [STDERR] at  
org.jboss.ejb.plugins.cmp.jdbc.JDBCTypeComplexProperty.setColumnValue(JDBCTypeComplexProperty.java:142)
  
12:03:56,654 ERROR [STDERR] at  
org.jboss.ejb.plugins.cmp.jdbc.JDBCTypeComplex.setColumnValue(JDBCTypeComplex.java:158)
  
12:03:56,654 ERROR [STDERR] at  
org.jboss.ejb.plugins.cmp.jdbc.JDBCTypeComplex.setColumnValue(JDBCTypeComplex.java:133)
  
12:03:56,654 ERROR [STDERR] at  
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFieldBridge.loadArgumentResults(JDBCAbstractCMPFieldBridge.java:352)
  
12:03:56,655 ERROR [STDERR] at  
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFieldBridge.loadInstanceResults(JDBCAbstractCMPFieldBridge.java:304)
  
12:03:56,655 ERROR [STDERR] at  
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:140)
  
12:03:56,655 ERROR [STDERR] at  
org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:62)
  
12:03:56,655 ERROR [STDERR] at  
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDBCStoreManager.java:496)  
12:03:56,656 ERROR [STDERR] at  
org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity(CMPPersistenceManager.java:410) 
 
12:03:56,656 ERROR [STDERR] at  
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.loadEntity(CachedConnectionInterceptor.java:314)
  
12:03:56,656 ERROR [STDERR] at  
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:310)
  
12:03:56,657 ERROR [STDERR] at  
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:147)
  
12:03:56,657 ERROR [STDERR] at  
org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:193)
  
12:03:56,657 ERROR [STDERR] at  
org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:107)  
12:03:56,658 ERROR [STDERR] at  
org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:69)
  
12:03:56,658 ERROR [STDERR] at  
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96)  
12:03:56,658 ERROR [STDERR] at  
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167)  
12:03:56,659 ERROR [STDERR] at  
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61)  
12:03:56,659 ERROR [STDERR] at  
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:129)  
12:03:56,659 ERROR [STDERR] at  
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166)  
12:03:56,659 ERROR [STDERR] at  
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:145)
  
12:03:56,660 ERROR [STDERR] at  
org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:482)  
12:03:56,660 ERROR [STDERR] at  
org.jboss.ejb.Container.invoke(Container.java:694)  
12:03:56,660 ERROR [STDERR] at  
org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1024)  
12:03:56,661 ERROR [STDERR] at  
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)  
12:03:56,661 ERROR [STDERR] at  

[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 92 % ( 13 / 14 ) - come on - pull your finger out

2003-08-17 Thread Chris Kimpton
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS==
===
===


JBoss daily test results

SUMMARY

Number of tests run:   14



Successful tests:  13

Errors:1

Failures:  0





[time of test: 2003-08-18.00-27 GMT]
[java.version: 1.4.1_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-18.7]

See http://jboss1.kimptoc.net/linux1/logtests/testresults/reports/html//. for
the junit report of this test.

NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   InvocationLogUnitTestCase
Test:testClientInvocationLog(org.jboss.test.aop.test.InvocationLogUnitTestCase)
Type:error
Exception:   java.lang.InternalError
Message: Test timeout
-


===Mon Aug 18 
01:27:39 BST 2003
===Linux nog 
2.4.20-18.7 #1 Thu May 29 08:32:50 EDT 2003 i686 unknown
===java 
version 1.4.1_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02)
Java HotSpot(TM) Client VM (build 1.4.1_03-b02, mixed mode)


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Job Failed to Complete Successfully

2003-08-17 Thread Chris Kimpton
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS==
===
===
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/aoptest.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/jbossdo-tx.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/dl11.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/cmp2-commerce.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/security-srp.sar
 [copy] Copying 2 files to 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/rsrc2.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/circularity.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/rsrc31.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/rsrc32.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/rsrc3.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/https-service.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/jbossdo-query.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/rsrc4.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/security-proxy.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/entityref.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/interrupt.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/loadingresource.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/securitymgr-ejb.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/testcopylocaldir.sar
 [copy] Copying 7 files to 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/jbossdo-callbacks.jar
  [ear] Building ear: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/loadingresource.ear
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/cmp2-lob.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/securitymgr-tests.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/testcrashinstart.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/hloadingresource.ear
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/testnullinfo.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/jbossdo-mktransient.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/brokendeployer.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/classpath.sar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/testmbeanclassloader.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/cmp2-optimisticlock.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/sessiona.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/sessionb.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/eardeployment.ear
[mkdir] Created dir: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/unpacked/eardeployment.ear/META-INF
 [copy] Copying 1 file to 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/unpacked/eardeployment.ear/META-INF
[unjar] Expanding: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/sessiona.jar into 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/unpacked/eardeployment.ear/sessiona.jar
[unjar] Expanding: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/sessionb.jar into 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/unpacked/eardeployment.ear/sessionb.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/abstract.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/ctstest.jar
  [jar] Building jar: 
/home/jbossci/jbossci/jboss-head-test/testsuite/output/lib/concrete.jar
  [ear] Building ear: 

[JBoss-dev] [ jboss-Bugs-789318 ] ObjectMessage.getObject() doesn't work in JBoss 3.2.1

2003-08-17 Thread SourceForge.net
Bugs item #789318, was opened at 2003-08-15 10:56
Message generated for change (Comment added) made by greenfuzz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=789318group_id=22866

Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 7
Submitted By: Mike Osganian (osganian)
Assigned to: Nobody/Anonymous (nobody)
Summary: ObjectMessage.getObject() doesn't work in JBoss 3.2.1

Initial Comment:
Attached is a zip file containing a simple example of the 
problem.  The problem is simple.  I have an object that i 
wrap in an ObjectMessage and send that message to a 
JMS queue.  My message driven bean receives this 
message and tests to see what type of object the 
wrapped object is.  In a simple case (the wrapped 
object just implements java.io.Serializable) it works.  But 
when the wrapped object extends an Object that 
extends java.util.EventObject (which implements 
java.io.Serializable) the Message Driven bean doesn't 
determine the type of the wrapped object correctly.  
Even if I explicitly define Object2 and/or Object3 as 
implementing java.io.Serializable it still doesn't work.

The attached zip file shows the problem.  I am wrapping 
up a message of type Object1 and Object3.  When the 
message driven bean recieves theses messages it sees 
Object1 as Object1 but it sees Object3 as Object2 EVEN 
through the classname is Object3.

OS: Windows XP
JDK version: 1.4.2
JBoss version: 3.2.1 (with Tomcat 4.1.24)

Console Output (server.log is also bundled in the 
attached zip file):

...
11:28:22,019 INFO  [Server] JBoss (MX MicroKernel) 
[3.2.1 (build: CVSTag=JBoss_3
_2_1 date=200305041533)] Started in 21s:389ms
10:16:28,995 WARN  [ClassLoadingTask] Duplicate class 
found: bug.Object3
Current CS: (file:/C:/jboss-
3.2.1/server/default/tmp/deploy/server/default/deploy/bu
g.jar/44.bug.jar no certificates)
Duplicate CS: (file:/C:/jboss-
3.2.1/server/default/deploy/bug.jar no certificates)
11:29:23,542 INFO  [STDOUT] .
11:29:23,552 INFO  [STDOUT] Instance of OBJECT 2: 
Object #3
11:29:23,552 INFO  [STDOUT] Classes Equal: false
11:29:23,552 INFO  [STDOUT] OBJECT CLASS: 'class 
bug.Object3'
11:29:23,552 INFO  [STDOUT] OBJECT CLASS 
NAME: 'bug.Object3'
11:29:23,552 INFO  [STDOUT] OBJECT's SUPER: 'class 
bug.Object2'
11:29:23,502 INFO  [STDOUT] .
11:29:23,512 INFO  [STDOUT] Instance of OBJECT 1: 
Object #1
11:29:23,512 INFO  [STDOUT] Classes Equal: true
11:29:23,522 INFO  [STDOUT] OBJECT CLASS: 'class 
bug.Object1'
11:29:23,522 INFO  [STDOUT] OBJECT CLASS 
NAME: 'bug.Object1'
11:29:23,522 INFO  [STDOUT] OBJECT's SUPER: 'class 
java.util.EventObject'

To run the test is simple.  I provided a build script and a 
run script.  You might need to update some paths to 
your jboss deploy directory so the scripts will work.


--

Comment By: Chris Klumb (greenfuzz)
Date: 2003-08-17 22:08

Message:
Logged In: YES 
user_id=846089

Object3, being a subclass of Object2, is an instanceof 
Object2.  If you want the exact class use getClass().

Am I missing something here?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=789318group_id=22866


---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development