[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/server/AxisService.java:413:
unreported exception javax.xml.parsers.ParserConfigurationException; must be caught
or declared to be thrown
Document deployDoc= XMLUtils.newDocument();
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/server/AxisService.java:415:
unreported exception javax.xml.parsers.ParserConfigurationException; must be caught
or declared to be thrown
Document deployClientDoc= XMLUtils.newDocument();
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/server/AxisService.java:543:
unreported exception javax.xml.parsers.ParserConfigurationException; must be caught
or declared to be thrown
Document undeployDoc= XMLUtils.newDocument();
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:33:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public class Adaptor extends ServiceMBeanSupport implements AdaptorMBean, Constants {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:33:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
public class Adaptor extends ServiceMBeanSupport implements AdaptorMBean, Constants {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:33:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public class Adaptor extends ServiceMBeanSupport implements AdaptorMBean, Constants {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:119:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(str,objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:123:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
return getServer().deserialize(str,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:143:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:36:
org.jboss.net.jmx.adaptor.AttributeSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.AttributeSerializer
public class AttributeSerializer implements Serializer {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:112:
createAttributeElement(java.lang.String,java.lang.Class,javax.xml.namespace.QName,boolean,org.w3c.dom.Document)
in org.apache.axis.wsdl.fromJava.Types cannot be applied to
(java.lang.String,java.lang.String,boolean,org.w3c.dom.Document)
types.createAttributeElement(
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/ObjectNameSerializer.java:35:
org.jboss.net.jmx.adaptor.ObjectNameSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.ObjectNameSerializer
public class ObjectNameSerializer implements Serializer {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/server/MBeanProvider.java:326:
warning: setMode(int) in org.apache.axis.wsdl.fromJava.Emitter has been deprecated
emitter.setMode(Emitter.MODE_RPC);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/server/MBeanProvider.java:328:
warning: setMode(int) in org.apache.axis.wsdl.fromJava.Emitter has been deprecated
emitter.setMode(Emitter.MODE_DOCUMENT);
^
6 errors
10 warnings
BUILD FAILED
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.4.1_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/server/AxisService.java:413:
unreported exception javax.xml.parsers.ParserConfigurationException; must be caught
or declared to be thrown
Document deployDoc= XMLUtils.newDocument();
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/server/AxisService.java:415:
unreported exception javax.xml.parsers.ParserConfigurationException; must be caught
or declared to be thrown
Document deployClientDoc= XMLUtils.newDocument();
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/server/AxisService.java:543:
unreported exception javax.xml.parsers.ParserConfigurationException; must be caught
or declared to be thrown
Document undeployDoc= XMLUtils.newDocument();
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:118:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public java.io.ObjectInputStream deserialize(java.lang.String str,
javax.management.ObjectName objectName, byte[] values) throws
javax.management.InstanceNotFoundException, javax.management.OperationsException,
javax.management.ReflectionException {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:122:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
public java.io.ObjectInputStream deserialize(java.lang.String str, byte[] values)
throws javax.management.OperationsException, javax.management.ReflectionException {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:142:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public java.io.ObjectInputStream deserialize(javax.management.ObjectName
objectName, byte[] values) throws javax.management.InstanceNotFoundException,
javax.management.OperationsException {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:119:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(str,objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:123:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
return getServer().deserialize(str,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:143:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:36:
org.jboss.net.jmx.adaptor.AttributeSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.AttributeSerializer
public class AttributeSerializer implements Serializer {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:112:
createAttributeElement(java.lang.String,java.lang.Class,javax.xml.namespace.QName,boolean,org.w3c.dom.Document)
in org.apache.axis.wsdl.fromJava.Types cannot be applied to
(java.lang.String,java.lang.String,boolean,org.w3c.dom.Document)
types.createAttributeElement(
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/ObjectNameSerializer.java:35:
org.jboss.net.jmx.adaptor.ObjectNameSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.ObjectNameSerializer
public class ObjectNameSerializer implements Serializer {
^
Re: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Do you want this feature on 3.2? Very much! Cheers --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Hello,
Yesterday I commited a BeanShell (BSH, www.beanshell.org) sub-deployer in
HEAD. It is in module varia and you can find its lib in
varia/output/lib/bsh-deployer.sar.
It allows you to hot-deploy *.bsh files in /deploy.
SIMPLE USAGE: client-only
=
In its simple usage, the script will act as a simple client-script making
invocations on other objects. Each script can follow the
org.jboss.system.Service interface i.e. the create, start, stop and destroy
calls. You can implement only a subset of those. Thus, a very simply
one-line script can be: Simple.bsh:
void start() { System.out.println (I'm called!); }
that's it.
ADVANCED USAGE: server script!
==
But it is almost as easy to make your script a JBoss service fully
invocable/administrable through JMX! For this, your script can implement any
of the methods of the following interface:
public interface ScriptService
extends org.jboss.system.Service
{
public String objectName ();
public String[] dependsOn ();
public Class[] getInterfaces ();
public void setCtx (ServiceMBeanSupport wrapper);
}
You can implement the objectName method to choose your own MBean ObjectName.
You can implement the dependsOn method to return a set of JMX MBean
ObjectName (as string) on which you depends (for service lifecyle).
You can implement the getInterfaces method to return the set of interfaces
that you *say* your script do implement. Your wrapper will analyse these
interfaces and fully generate the associated JMX MBeanInfo (the script
wrapper is a Dynamic MBean).
Example, let's say you have this interface:
public interface MyIntf
{
public void doThat();
public String getRWString ();
public void setRWString (String val);
public String getROString ();
}
You could then provide this script:
String name = bla;
String objectName () { return jboss.scripts:service=myService; }
Class[] getInterfaces () { return new Class[] {MyIntf.class}; }
void create () { System.out.println (Create called on me); }
void doThat () { System.out.println (doThat called); }
String getRWString() { return super.name; }
void setRWString(String bla) { super.name = bla; }
String getROString() { return I am read-only!; }
Then, not only can you invoke methods and get/set attributes on your script
using JMX, you can also browse your scripts using the
http://localhost:8080/jmx-console/ and see all available methods/attributes
(MBeanInfo is generated by the DynamicMBean script wrapper)
Infos on BeanShell are available here: www.beanshell.org
Do you want this feature on 3.2?
Cheers,
Sacha
P.S.: This e-mail is cross-posted to the beanshell-users ML.
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: [JBoss-dev] Updating to use Axis 1.1 beta
You should have tried to build/build most before submitting then you would have noticed that the axis-beta patch has not yet been applied to jboss.net and broke the build. Grrmpf. This leaves it to me to repair it. How I love that. CGJ -Ursprüngliche Nachricht- Von: Tom Elrod [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 7. Januar 2003 08:58 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-dev] Updating to use Axis 1.1 beta I have updated the following in thirdparty to support Axis 1.1 beta (which I needed for JMX SOAP Connector). The update was done to HEAD in CVS. thirdparty/apache-axis/README thirdparty/apache-axis/release-notes.html thirdparty/apache-axis/lib/axis.jar thirdparty/apache-axis/lib/jaxrpc.jar thirdparty/apache-axis/lib/saaj.jar thirdparty/apache-commons/lib/commons-discovery.jar I was unable to verify any affect this might have had on the other jboss projects (other than the e-mail sent out previously), so if you are using any of these, please verify it does not break any of your code. Thanks. -Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jung , Dr. Christoph Sent: Thursday, January 02, 2003 3:42 AM To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-dev] Updating to use Axis 1.1 beta Tom, There is already a patch for jboss.net submitted which addresses some additional exceptions raised in the Axis1.1 beta. I think that I will be able to apply it such that jboss.net will cope with both 1.0 and 1.1 ... I would also give my ok for putting the 1.1 binaries into head, but I would hesitate going for beta in the 3.2 branch. CGJ -Ursprüngliche Nachricht- Von: Tom Elrod [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 31. Dezember 2002 06:28 An: [EMAIL PROTECTED] Betreff: [JBoss-dev] Updating to use Axis 1.1 beta I have written a SOAP connector to be used within the JBoss-MX project which uses Axis 1.1 beta. I know that Axis 1.0 is being used in the root thirdparty for jboss.net and was wondering if someone could tell me if there would be a problem upgrading it to 1.1 beta so both sub-projects (jboss-mx and jboss.net) could use the same libraries? Thanks. -Tom --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-663859 ] Deadlock in shutdown hooks when interrupting startup
Bugs item #663859, was opened at 2003-01-07 11:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=663859group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Dave Marquard (lurp) Assigned to: Nobody/Anonymous (nobody) Summary: Deadlock in shutdown hooks when interrupting startup Initial Comment: Steps to reproduce: While JBoss is starting up (i.e., deploying services, ejbs, etc.), hit Ctrl+C to halt the VM. About two thirds of the time a deadlock will happen in the shutdown hooks. JBoss version: 3.0.5rc1 JDK version: 1.4.1_01 OS: Windows XP The thread dump of the deadlock is attached. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=663859group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
org.jboss.net.axis.mail.MailTransportService -- MailTransportServiceMBean qualified
to MailTransportServiceMBean
org.jboss.net.axis.server.AxisServiceMBean -- EngineConfigurationMBean qualified to
EngineConfigurationMBean
[mkdir] Created dir: /home/jboss/jbossci/jboss-head/jboss.net/output/classes/main
[javac] Compiling 69 source files to
/home/jboss/jbossci/jboss-head/jboss.net/output/classes/main
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/ServiceFactory.java:15:
warning: org.apache.axis.configuration.DefaultEngineConfigurationFactory in
org.apache.axis.configuration has been deprecated
import org.apache.axis.configuration.DefaultEngineConfigurationFactory;
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/ServiceFactory.java:88:
warning: org.apache.axis.configuration.DefaultEngineConfigurationFactory in
org.apache.axis.configuration has been deprecated
return new DefaultEngineConfigurationFactory().getClientEngineConfig();
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:33:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public class Adaptor extends ServiceMBeanSupport implements AdaptorMBean, Constants {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:33:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
public class Adaptor extends ServiceMBeanSupport implements AdaptorMBean, Constants {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:33:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public class Adaptor extends ServiceMBeanSupport implements AdaptorMBean, Constants {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:119:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(str,objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:123:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
return getServer().deserialize(str,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:143:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:36:
org.jboss.net.jmx.adaptor.AttributeSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.AttributeSerializer
public class AttributeSerializer implements Serializer {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:112:
createAttributeElement(java.lang.String,java.lang.Class,javax.xml.namespace.QName,boolean,org.w3c.dom.Document)
in org.apache.axis.wsdl.fromJava.Types cannot be applied to
(java.lang.String,java.lang.String,boolean,org.w3c.dom.Document)
types.createAttributeElement(
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/ObjectNameSerializer.java:35:
org.jboss.net.jmx.adaptor.ObjectNameSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.ObjectNameSerializer
public class ObjectNameSerializer implements Serializer {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/server/MBeanProvider.java:326:
warning: setMode(int) in org.apache.axis.wsdl.fromJava.Emitter has been deprecated
emitter.setMode(Emitter.MODE_RPC);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/server/MBeanProvider.java:328:
warning: setMode(int) in
[JBoss-dev] ejb-name as default jms client id
Hi, Currently JBoss does not provide any default jms client id for message driven beans. This is especially inconvenient because jms client id is required for mdbs doing durable topic subscriptions and XDocLet does not currently support mdb-client-id attribute. I wonder if mdb's ejb-name looks like a reasonable default value in this case. The change is trivial and I can commit it if there are no objections. -- Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 7-January-2003
JBoss daily test results SUMMARY Number of tests run: 1009 Successful tests: 1003 Errors:5 Failures: 1 [time of test: 2003-01-07.12-29 GMT] [java.version: 1.3.1] [java.vendor: Apple Computer, Inc.] [java.vm.version: 1.3.1_03-69] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Mac OS X] [os.arch: ppc] [os.version: 10.2.3] See http://users.jboss.org/~starksm/Branch_3_0/2003-01-07.12-29 for details 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: LocalWrapperCleanupUnitTestCase Test: testAutoCommitOffInRemoteUserTx(org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: EJBException:; nested exception is: javax.ejb.EJBException: Row committed, autocommit still on! - Suite: MissingClassUnitTestCase Test: testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: SimpleUnitTestCase Test:testSecureHttpInvoker(org.jboss.test.naming.test.SimpleUnitTestCase) Type:error Exception: javax.security.auth.login.LoginException Message: Missing users.properties file. - Suite: SimpleUnitTestCase Test:testLoginInitialContext(org.jboss.test.naming.test.SimpleUnitTestCase) Type:error Exception: javax.naming.AuthenticationException Message: Failed to login using protocol=testLoginInitialContext - Suite: HttpsUnitTestCase Test:testHttpsURL(org.jboss.test.security.test.HttpsUnitTestCase) Type:error Exception: java.io.IOException Message: Failed to get SSLContext for TLS algorithm - Suite: BeanStressTestCase Test:testDeadLockFromClient(org.jboss.test.deadlock.test.BeanStressTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: expected a client deadlock for AB BA - --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossXidFactory and MS SQL Server
If l understand the transaction logger, it is persisting the last globalIdNumber between JBoss sessions. If thats the case l would agree it will do the job. You have a NoLogTxLogger in the package. If someone were to use this TxLogger we could see the MS SQL Server problem. Your code in JBossXidFactory.startService() sets the globalIdNumber to zero if there is no TxLogger. If there is no TxLogger we could also see the MS SQL Server problem. Are the NoLogTxLogger or null TxLogger senarios likely to happen? - Original Message - From: David Jencks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 06, 2003 4:55 AM Subject: Re: [JBoss-dev] JBossXidFactory and MS SQL Server I probably wont be able to look at this in detail for at least several days. Could you please 1. look at the transaction logging in jboss 4 to see if that looks like a better long-term solution: if I understand the problem you are having the logging should also solve it. I __might__ backport this to 3.2 but almost certainly not to 3.0.x 2. indicate which version(s) of jboss your patch is for. 3. file either a bug report or a patch on sourceforge and assign it to me if possible. Otherwise I am very apt to lose track of this. Thanks david jencks On 2003.01.05 14:28:58 -0500 Jamie Burns wrote: David J, back in October we were dialoging about XidFactory and a transaction id problem that could occur if MS SQL Server is not restarted when JBoss is stopped and started. The problem was traced to the XidFactory using the same baseGlobalId and resetting its globalIdNumber to zero each time it is started. Ive made some changes to JBossXidFactory based on our discussion. At the time you asked about looking into a guid that is used in other parts of JBoss as a solution to creating a unique baseGlobalId each time JBoss is started. The org.jboss.util.id package has a GUID class that creates unique ids based on the host address, time stamps and counters. The guid it creates is around 40 characters long and will be unique even for multiple instances of JBoss on the same physical machine. I wasnt sure if you still wanted to keep the hostname in baseGlobalId. Ive kept it in but, its likely it will be truncated alot of the time because of the size of the GUID. The JBossXidFactory sticks to reserving 14 characters for the globalIdNumber. The setter method for baseGlobalId doesnt enforce this. Ive added code to truncate the value passed to the setter if it is too long. Im not sure if this is the best approach though. Truncating the value may remove enough significant characters from the string that it is no longer unique. Maybe it would be better to throw some exception if the baseGlobalId was set to a string that doesnt leave 14 characters for the globalIdNumber. What is your view on this? In the old XidFactory you had a setter method for the globalIdNumber. You dont have this in JBossXidFactory so the next comment isnt very relevant, but l'll make it to be thorough. The globalIdNumber is a long which can be up to 22 digits. My thought with the old XidFactory was that someone could supply a globalIdNumber that was greater than 14 digits. If you put a setter method for globalIdNumber back into JBossXidFactory or if you get more than 10^14 transactions taking place in the lifetime of a JBoss instance (pretty unlikely l guess) you will have the potential for non-unique transaction ids. One last thing - again to be thorough. The GUID uses the system time a few times to create its unique string. The system time on MS Windows is only accurate to the nearest 10-15 milliseconds. Someone would be pretty unlucky to get two GUIDs that are the same, but it is possible on a Windows machine if they are created within 10-15 ms of each other. If it does happen to someone maybe they will find this posting. I cant see a way to get a 100% guarantee of uniqueness. Ive attached JBossXidFactory with the changes lve made. Let me know if you need anything done. Jamie !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN HTMLHEAD META http-equiv=Content-Type content=text/html; charset=iso-8859-1 META content=MSHTML 6.00.2600.0 name=GENERATOR STYLE/STYLE /HEAD BODY bgColor=#ff DIVFONT face=Arial size=2David J,/FONT/DIV DIVFONT face=Arial size=2/FONTnbsp;/DIV DIVFONT face=Arial size=2back in October we were dialoging about XidFactory and a transaction id problem that could occur if MS SQL Server is not restarted when JBoss is stopped and started. The problem was traced to the XidFactory using the same baseGlobalId and resetting its globalIdNumber to zero each time it is started./FONT/DIV DIVFONT face=Arial size=2/FONTnbsp;/DIV DIVFONT face=Arial size=2Ive made some changes to JBossXidFactory based on our discussion./FONT/DIV DIVFONT face=Arial size=2/FONTnbsp;/DIV DIVFONT
Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
No, jboss.net is not compiling, but that is what Dr. Jung was complaining about. The axis libs were updated and a clean build was not done to see what broke. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Chris Kimpton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 11:57 AM Subject: Re: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed Does HEAD compile for anyone else ? Chris = --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
org.jboss.net.axis.mail.MailTransportService -- MailTransportServiceMBean qualified
to MailTransportServiceMBean
org.jboss.net.axis.server.AxisServiceMBean -- EngineConfigurationMBean qualified to
EngineConfigurationMBean
[mkdir] Created dir: /home/jboss/jbossci/jboss-head/jboss.net/output/classes/main
[javac] Compiling 69 source files to
/home/jboss/jbossci/jboss-head/jboss.net/output/classes/main
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/ServiceFactory.java:15:
warning: org.apache.axis.configuration.DefaultEngineConfigurationFactory in
org.apache.axis.configuration has been deprecated
import org.apache.axis.configuration.DefaultEngineConfigurationFactory;
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/ServiceFactory.java:88:
warning: org.apache.axis.configuration.DefaultEngineConfigurationFactory in
org.apache.axis.configuration has been deprecated
return new DefaultEngineConfigurationFactory().getClientEngineConfig();
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:33:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public class Adaptor extends ServiceMBeanSupport implements AdaptorMBean, Constants {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:33:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
public class Adaptor extends ServiceMBeanSupport implements AdaptorMBean, Constants {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:33:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public class Adaptor extends ServiceMBeanSupport implements AdaptorMBean, Constants {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:119:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(str,objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:123:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
return getServer().deserialize(str,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:143:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:36:
org.jboss.net.jmx.adaptor.AttributeSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.AttributeSerializer
public class AttributeSerializer implements Serializer {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:112:
createAttributeElement(java.lang.String,java.lang.Class,javax.xml.namespace.QName,boolean,org.w3c.dom.Document)
in org.apache.axis.wsdl.fromJava.Types cannot be applied to
(java.lang.String,java.lang.String,boolean,org.w3c.dom.Document)
types.createAttributeElement(
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/ObjectNameSerializer.java:35:
org.jboss.net.jmx.adaptor.ObjectNameSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.ObjectNameSerializer
public class ObjectNameSerializer implements Serializer {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/server/MBeanProvider.java:326:
warning: setMode(int) in org.apache.axis.wsdl.fromJava.Emitter has been deprecated
emitter.setMode(Emitter.MODE_RPC);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/server/MBeanProvider.java:328:
warning: setMode(int) in
[JBoss-dev] JBoss 3.0.5
Can we please apply Patch #621702 to the 3_0 branch in time for the 3.0.5 release? https://sourceforge.net/tracker/?func=detailaid=621702group_id=22866atid=376687 Thanks, Corby _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: [JBoss-dev] Updating to use Axis 1.1 beta
I was the one the broke the build. I have updated the following files within jboss.net package: org.jboss.net.jmx.adaptor.AttributeSerializer org.jboss.net.jmx.adaptor.ObjectSerializer to fix the build. You can find the changes made by searching for 'implemented to comply with Axis 1.1beta'. I certainly should have done a clean build before the update and apologize. I also am sorry that I misunderstood I would also give my ok for putting the 1.1 binaries into head as meaning that it would be ok for me to update the binaries into head. -Tom. Jung , Dr. Christoph wrote: You should have tried to build/build most before submitting then you would have noticed that the axis-beta patch has not yet been applied to jboss.net and broke the build. Grrmpf. This leaves it to me to repair it. How I love that. CGJ -Ursprüngliche Nachricht- Von: Tom Elrod [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 7. Januar 2003 08:58 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-dev] Updating to use Axis 1.1 beta I have updated the following in thirdparty to support Axis 1.1 beta (which I needed for JMX SOAP Connector). The update was done to HEAD in CVS. thirdparty/apache-axis/README thirdparty/apache-axis/release-notes.html thirdparty/apache-axis/lib/axis.jar thirdparty/apache-axis/lib/jaxrpc.jar thirdparty/apache-axis/lib/saaj.jar thirdparty/apache-commons/lib/commons-discovery.jar I was unable to verify any affect this might have had on the other jboss projects (other than the e-mail sent out previously), so if you are using any of these, please verify it does not break any of your code. Thanks. -Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jung , Dr. Christoph Sent: Thursday, January 02, 2003 3:42 AM To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-dev] Updating to use Axis 1.1 beta Tom, There is already a patch for jboss.net submitted which addresses some additional exceptions raised in the Axis1.1 beta. I think that I will be able to apply it such that jboss.net will cope with both 1.0 and 1.1 ... I would also give my ok for putting the 1.1 binaries into head, but I would hesitate going for beta in the 3.2 branch. CGJ -Ursprüngliche Nachricht- Von: Tom Elrod [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 31. Dezember 2002 06:28 An: [EMAIL PROTECTED] Betreff: [JBoss-dev] Updating to use Axis 1.1 beta I have written a SOAP connector to be used within the JBoss-MX project which uses Axis 1.1 beta. I know that Axis 1.0 is being used in the root thirdparty for jboss.net and was wondering if someone could tell me if there would be a problem upgrading it to 1.1 beta so both sub-projects (jboss-mx and jboss.net) could use the same libraries? Thanks. -Tom --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-664081 ] JCA rars packaging causes IllegalAccessError
Bugs item #664081, was opened at 2003-01-07 15:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=664081group_id=22866 Category: JBossCX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: David Jencks (d_jencks) Summary: JCA rars packaging causes IllegalAccessError Initial Comment: An java.lang.IllegalAccessError: tried to access method org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnectionFactory.getConnectionProperties (Ljavax/security/auth/Subject;Ljavax/resource/spi/Conne ctionRequestInfo;)Ljava/util/Properties; from class org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection has been reported and this is an issue with the jca classes being deployed redundantly: lib 634jar -tf ra-xa-libs.jar | grep BaseWrapper org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnection.class org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnectionFactory.class lib 635jar -tf local-ra-jdbc-libs.jar | grep BaseWrapper org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnection.class org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnectionFactory.class Under a usage pattern that happens to load the BaseWrapperManagedConnectionFactory class from the local-ra-jdbc-libs.jar, while the BaseWrapperManagedConnection class is later loaded from the ra-xa-libs.jar, because two different class loaders are involved, the package protected access fails. These classes cannot be deployed redundantly in the same scope in different jars as there is no way for the ULR to ensure that the same class loader handles the classes with package protected access. The jboss-xa.rar and jboss-local-jdbc.rar need to be refactored to fix this. Here's the exception: 16:17:58,415 ERROR [LogInterceptor] Unexpected Error: java.lang.IllegalAccessError: tried to access method org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnectionFactory.getConnectionProperties (Ljavax/security/auth/Subject;Ljavax/resource/spi/Conne ctionRequestInfo;)Ljava/util/Properties; from class org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection at org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection.checkIdentity (BaseWrapperManagedConnection.java:295) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection.getConnection (BaseWrapperManagedConnection.java:188) at org.jboss.resource.connectionmanager.BaseConnection Manager2.allocateConnection (BaseConnectionManager2.java:596) at org.jboss.resource.connectionmanager.BaseConnection Manager2$ConnectionManagerProxy.allocateConnection (BaseConnectionManager2.java:885) at org.jboss.resource.adapter.jdbc.WrapperDataSource.get Connection(WrapperDataSource.java:102) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=664081group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] patch for axis1.1beta upgrade
Hi,
Below is a patch to upgrade the jboss sources to use axis1.1beta.
The files modified are:
jboss.net/src/main/org/jboss/net/axis/server/AxisService.java
jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java
jboss.net/src/main/org/jboss/net/jmx/adaptor/ObjectNameSerializer.java
I've been using this modified source to run sessionbean-based
web-services, and it seems to be working fine for me.
hope this is useful,
fawce
---
../../../../jboss-head/jboss.net/src/main/org/jboss/net/axis/server/Axis
Service.java2003-01-07 12:30:37.0 -0500
+++
../../../../tamale_jboss4/jboss.net/src/main/org/jboss/net/axis/server/A
xisService.java 2002-12-15 10:37:09.0 -0500
@@ -5,7 +5,7 @@
* See terms of license at gnu.org.
*/
-// $Id: AxisService.java,v 1.32 2003/01/07 17:30:37 cgjung Exp $
+// $Id: AxisService.java,v 1.2 2002/12/15 15:37:09 jfawcett Exp $
package org.jboss.net.axis.server;
@@ -58,6 +58,7 @@
import javax.naming.LinkRef;
import javax.naming.Context;
import javax.naming.NamingException;
+import javax.xml.parsers.ParserConfigurationException;
import java.io.FilenameFilter;
import java.io.File;
@@ -82,7 +83,7 @@
* within JMX.
* @created 27. September 2001
* @author a href=mailto:[EMAIL PROTECTED];Christoph G.
Jung/a
- * @version $Revision: 1.32 $
+ * @version $Revision: 1.2 $
*/
public class AxisService
@@ -409,52 +410,57 @@
Document doc= (Document) sdi.metaData;
// the original command
Element root= doc.getDocumentElement();
+ // the deployment command document
+ Document deployDoc = null;
+ Document deployClientDoc = null;
try{
-
-// the deployment command document
-Document deployDoc= XMLUtils.newDocument();
-// the client deployment command document
-Document deployClientDoc= XMLUtils.newDocument();
-// create command
-Element deploy=
- deployDoc.createElementNS(root.getNamespaceURI(),
deployment);
-// create command
-Element deployClient=
- deployClientDoc.createElementNS(
- root.getNamespaceURI(),
- deployment);
-
-NamedNodeMap attributes= root.getAttributes();
-for (int count= 0; count attributes.getLength(); count++)
{
- Attr attribute= (Attr) attributes.item(count);
- deploy.setAttributeNodeNS(
- (Attr) deployDoc.importNode(attribute, true));
- deployClient.setAttributeNodeNS(
- (Attr) deployClientDoc.importNode(attribute, true));
-}
+ deployDoc= XMLUtils.newDocument();
+ // the client deployment command document
+ deployClientDoc= XMLUtils.newDocument();
+ } catch (ParserConfigurationException e){
+ e.printStackTrace();
+ }
+
+ // create command
+ Element deploy=
+deployDoc.createElementNS(root.getNamespaceURI(),
deployment);
+ // create command
+ Element deployClient=
+deployClientDoc.createElementNS(
+ root.getNamespaceURI(),
+ deployment);
-// and insert the nodes from the original document
-// and sort out the ejb-ref extensions
-NodeList children= root.getChildNodes();
-for (int count= 0; count children.getLength(); count++) {
- Node actNode= children.item(count);
- if (actNode instanceof Element) {
- Element actElement= (Element) actNode;
-
- if (actElement.getTagName().equals(ejb-ref)) {
-
- String refName=
-MetaData.getElementContent(
- MetaData.getUniqueChild(
- (Element) actNode,
- ejb-ref-name));
- String linkName=
-MetaData.getElementContent(
- MetaData.getUniqueChild((Element) actNode,
ejb-link));
+ NamedNodeMap attributes= root.getAttributes();
+ for (int count= 0; count attributes.getLength(); count++) {
+Attr attribute= (Attr) attributes.item(count);
+deploy.setAttributeNodeNS(
+ (Attr) deployDoc.importNode(attribute, true));
+deployClient.setAttributeNodeNS(
+ (Attr) deployClientDoc.importNode(attribute, true));
+ }
- log.warn(
-Web Service Deployment
+ // and insert the nodes from the original document
+ // and sort out the ejb-ref extensions
+ NodeList children= root.getChildNodes();
+ for (int count= 0; count children.getLength(); count++) {
+Node actNode= children.item(count);
+if (actNode instanceof Element) {
+
[JBoss-dev] Fw: Java+ Precompiler as an Ant Task
Could be of interest. - Original Message - From: Brad Cox [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 07, 2003 2:41 PM Subject: ANN: Java+ Precompiler as an Ant Task I hope this is the right protocol for getting Ant tools added to the external resources website. Please let me know if not. This page lists external resources for Apache Ant: tasks, IDE integration tools, loggers, you name it. If you've written something that should be included, please post all relevant information to one of the mailing lists. This is to announce Release 1.1 of the Java+ Precompiler with Ant, Make and Graphical interfaces. The Ant interface is new to this release. Here's the cover blurb from the website: http://virtualschool.edu/java+ Java+ is an open source Java preprocessorthat adds these features to any Java compiler: * Multi-line strings with executable inclusions like Perl and Ruby. It eliminates the need for JSP or ASP and their need for Java compilers on deployment servers (a security concern) while adding no overhead in either space or time. * Optionally supports localization by segregating Java+ strings into ResourceBundle files with invarient keys based on the hash code of the strings's value. This is handled automatically and transparently; no intervention is required. * Fast. Negligible impact on build times. By default, skips inputs whose outputs are up to date to avoid triggering recompilations. * Pure Java code, portable to any platform, with graphical, shell and ant interfaces. * Simple, general, recursive, digraph-driven string syntax. Digraph characters are user-selectable. * Free software, BSD open source license -- Brad Cox, PhD; [EMAIL PROTECTED] 703 361 4751 http://virtualschool.edu For industrial age goods there were checks and credit cards. For everything else there is http://virtualschool.edu/mybank Java Web Application Architecture: http://virtualschool.edu/jwaa Ruby Interactive Learning Environment: http://virtualschool.edu/ile Java+ Preprocessor: http://virtualschool.edu/java+ Support Israel and Palestine: http://virtualschool.edu/mideast -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-664081 ] JCA rars packaging causes IllegalAccessError
Bugs item #664081, was opened at 2003-01-07 23:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=664081group_id=22866 Category: JBossCX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: David Jencks (d_jencks) Summary: JCA rars packaging causes IllegalAccessError Initial Comment: An java.lang.IllegalAccessError: tried to access method org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnectionFactory.getConnectionProperties (Ljavax/security/auth/Subject;Ljavax/resource/spi/Conne ctionRequestInfo;)Ljava/util/Properties; from class org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection has been reported and this is an issue with the jca classes being deployed redundantly: lib 634jar -tf ra-xa-libs.jar | grep BaseWrapper org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnection.class org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnectionFactory.class lib 635jar -tf local-ra-jdbc-libs.jar | grep BaseWrapper org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnection.class org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnectionFactory.class Under a usage pattern that happens to load the BaseWrapperManagedConnectionFactory class from the local-ra-jdbc-libs.jar, while the BaseWrapperManagedConnection class is later loaded from the ra-xa-libs.jar, because two different class loaders are involved, the package protected access fails. These classes cannot be deployed redundantly in the same scope in different jars as there is no way for the ULR to ensure that the same class loader handles the classes with package protected access. The jboss-xa.rar and jboss-local-jdbc.rar need to be refactored to fix this. Here's the exception: 16:17:58,415 ERROR [LogInterceptor] Unexpected Error: java.lang.IllegalAccessError: tried to access method org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnectionFactory.getConnectionProperties (Ljavax/security/auth/Subject;Ljavax/resource/spi/Conne ctionRequestInfo;)Ljava/util/Properties; from class org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection at org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection.checkIdentity (BaseWrapperManagedConnection.java:295) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection.getConnection (BaseWrapperManagedConnection.java:188) at org.jboss.resource.connectionmanager.BaseConnection Manager2.allocateConnection (BaseConnectionManager2.java:596) at org.jboss.resource.connectionmanager.BaseConnection Manager2$ConnectionManagerProxy.allocateConnection (BaseConnectionManager2.java:885) at org.jboss.resource.adapter.jdbc.WrapperDataSource.get Connection(WrapperDataSource.java:102) -- Comment By: David Jencks (d_jencks) Date: 2003-01-08 03:28 Message: Logged In: YES user_id=60525 I've fixed this in 3.2. I don't think it is a problem in 3.0.x since there are no shared classes between the adapters (different xa adapter than 3.2 and 4). I haven't fixed it in 4.0 because once jca 1.5 deployment is written both adapters can be packaged together, eliminating the extra jar. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=664081group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-664081 ] JCA rars packaging causes IllegalAccessError
Bugs item #664081, was opened at 2003-01-07 15:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=664081group_id=22866 Category: JBossCX Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: David Jencks (d_jencks) Summary: JCA rars packaging causes IllegalAccessError Initial Comment: An java.lang.IllegalAccessError: tried to access method org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnectionFactory.getConnectionProperties (Ljavax/security/auth/Subject;Ljavax/resource/spi/Conne ctionRequestInfo;)Ljava/util/Properties; from class org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection has been reported and this is an issue with the jca classes being deployed redundantly: lib 634jar -tf ra-xa-libs.jar | grep BaseWrapper org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnection.class org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnectionFactory.class lib 635jar -tf local-ra-jdbc-libs.jar | grep BaseWrapper org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnection.class org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnectionFactory.class Under a usage pattern that happens to load the BaseWrapperManagedConnectionFactory class from the local-ra-jdbc-libs.jar, while the BaseWrapperManagedConnection class is later loaded from the ra-xa-libs.jar, because two different class loaders are involved, the package protected access fails. These classes cannot be deployed redundantly in the same scope in different jars as there is no way for the ULR to ensure that the same class loader handles the classes with package protected access. The jboss-xa.rar and jboss-local-jdbc.rar need to be refactored to fix this. Here's the exception: 16:17:58,415 ERROR [LogInterceptor] Unexpected Error: java.lang.IllegalAccessError: tried to access method org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnectionFactory.getConnectionProperties (Ljavax/security/auth/Subject;Ljavax/resource/spi/Conne ctionRequestInfo;)Ljava/util/Properties; from class org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection at org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection.checkIdentity (BaseWrapperManagedConnection.java:295) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection.getConnection (BaseWrapperManagedConnection.java:188) at org.jboss.resource.connectionmanager.BaseConnection Manager2.allocateConnection (BaseConnectionManager2.java:596) at org.jboss.resource.connectionmanager.BaseConnection Manager2$ConnectionManagerProxy.allocateConnection (BaseConnectionManager2.java:885) at org.jboss.resource.adapter.jdbc.WrapperDataSource.get Connection(WrapperDataSource.java:102) -- Comment By: Scott M Stark (starksm) Date: 2003-01-07 19:48 Message: Logged In: YES user_id=175228 Ok, thanks. I don't care about 4.0 at this point -- Comment By: David Jencks (d_jencks) Date: 2003-01-07 19:28 Message: Logged In: YES user_id=60525 I've fixed this in 3.2. I don't think it is a problem in 3.0.x since there are no shared classes between the adapters (different xa adapter than 3.2 and 4). I haven't fixed it in 4.0 because once jca 1.5 deployment is written both adapters can be packaged together, eliminating the extra jar. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=664081group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Sounds very interesting.. I wonder how it might help to integrate Jboss
and Emacs/JDEE, since they use the bsh to perform Lisp-Java
integration..
James
-Original Message-
From: Sacha Labourey [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 3:57 AM
To: Jboss-Dev
Cc: jBoss-User Mailing List; [EMAIL PROTECTED]
Subject: [JBoss-dev] ANNOUNCE: BeanShell JBoss sub-deployer in HEAD
Hello,
Yesterday I commited a BeanShell (BSH, www.beanshell.org)
sub-deployer in HEAD. It is in module varia and you can find
its lib in varia/output/lib/bsh-deployer.sar.
It allows you to hot-deploy *.bsh files in /deploy.
SIMPLE USAGE: client-only
=
In its simple usage, the script will act as a simple
client-script making invocations on other objects. Each
script can follow the org.jboss.system.Service interface i.e.
the create, start, stop and destroy calls. You can implement
only a subset of those. Thus, a very simply one-line script
can be: Simple.bsh:
void start() { System.out.println (I'm called!); }
that's it.
ADVANCED USAGE: server script!
==
But it is almost as easy to make your script a JBoss service
fully invocable/administrable through JMX! For this, your
script can implement any of the methods of the following interface:
public interface ScriptService
extends org.jboss.system.Service
{
public String objectName ();
public String[] dependsOn ();
public Class[] getInterfaces ();
public void setCtx (ServiceMBeanSupport wrapper);
}
You can implement the objectName method to choose your own
MBean ObjectName. You can implement the dependsOn method to
return a set of JMX MBean ObjectName (as string) on which you
depends (for service lifecyle). You can implement the
getInterfaces method to return the set of interfaces that you
*say* your script do implement. Your wrapper will analyse
these interfaces and fully generate the associated JMX
MBeanInfo (the script wrapper is a Dynamic MBean).
Example, let's say you have this interface:
public interface MyIntf
{
public void doThat();
public String getRWString ();
public void setRWString (String val);
public String getROString ();
}
You could then provide this script:
String name = bla;
String objectName () { return jboss.scripts:service=myService; }
Class[] getInterfaces () { return new Class[] {MyIntf.class}; }
void create () { System.out.println (Create called on me); }
void doThat () { System.out.println (doThat called); }
String getRWString() { return super.name; }
void setRWString(String bla) { super.name = bla; }
String getROString() { return I am read-only!; }
Then, not only can you invoke methods and get/set attributes
on your script using JMX, you can also browse your scripts
using the http://localhost:8080/jmx-console/ and see all
available methods/attributes (MBeanInfo is generated by the
DynamicMBean script wrapper)
Infos on BeanShell are available here: www.beanshell.org
Do you want this feature on 3.2?
Cheers,
Sacha
P.S.: This e-mail is cross-posted to the beanshell-users ML.
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something
2 See! http://www.vasoftware.com
___
Jboss-development mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-638488 ] Incorrect SQL with OR and IS NOT EMPTY
Bugs item #638488, was opened at 2002-11-14 08:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=638488group_id=22866 Category: JBossCMP Group: CVS HEAD Status: Closed Resolution: Fixed Priority: 5 Submitted By: Jeremy Boynes (jboynes) Assigned to: Jeremy Boynes (jboynes) Summary: Incorrect SQL with OR and IS NOT EMPTY Initial Comment: Opening this as 621270 has been closed. Incorrect SQL is generated for EJB-QL where IS NOT EMPTY is used in a OR condition such as: SELECT OBJECT(p) FROM parent p WHERE p.children IS NOT EMPTY OR p.value = ?1 generates SELECT t0_p.id FROM Parent t0_p, Child t1_p_children WHERE ((1=1) OR t0_p.value = ?) -- oops AND (t0_p.id=t1_p_children.parent) -- Comment By: Jeremy Boynes (jboynes) Date: 2003-01-07 20:50 Message: Logged In: YES user_id=378919 Fixed in Branch_3_2 and HEAD Now provided the database supports subqueries they will always be used. If the database does not (e.g. MySQL), then a query like: SELECT DISTINCT Parent.ID FROM Parent LEFT JOIN Child ON (Parent.ID = Child.Parent) WHERE Child.ID IS NOT NULL OR Parent.value = ? will be generated. This takes a performance hit but generates correct results except if the query is meant to return duplicate values - SQL requires subqueries to handle that. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=638488group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-642609 ] Deployment error with empty relation-nam
Bugs item #642609, was opened at 2002-11-22 16:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=642609group_id=22866 Category: JBossCMP Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Jeremy Boynes (jboynes) Assigned to: Jeremy Boynes (jboynes) Summary: Deployment error with empty relation-nam Initial Comment: Sun's PetStore 1.3.1 application contains empty ejb-relation-name entries such as: ejb-relation ejb-relation-name/ejb-relation-name ... /ejb-relation Presumably this deploys fine on the reference implementation. However, JBoss returns an error saying that the ejb-relation-name must be unique. According to the EJB2.0 spec: The ejb-relation-name element provides a unique name for a relationship. In EJB2.1 this is expanded to The name of the relationship, if specified, is unique within the ejb-jar file. Note the if specified IMHO the spec isn't very precise here but, for compatibility with the RI and PetStore, JBoss should treat empty ejb-relation-name elements as if they were not specified. -- Comment By: Jeremy Boynes (jboynes) Date: 2003-01-07 22:43 Message: Logged In: YES user_id=378919 Fixed in Branch_3_2 and HEAD -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=642609group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Enterprise Media Beans
Hi, I've been working on an implementation of the Enterprise Media Beans API since July of last year, but I haven't found enough time to finish it. The Enterprise Media Beans specification is described in the Java Specification Request 086 (JSR-86): http://jcp.org/en/jsr/detail?id=086 http://jcp.org/aboutJava/communityprocess/review/jsr086/index.html The Enterprise Media Beans architecture allows the integration of rich media (image, audio and video) into the J2EE programming model. This means your media could take advantage of all the capabilities of the Java2 Enterprise Edition: transactionality, security, scalability, availability, just to name a few. The specification divides the architecture in two parts: Media Foundation Beans and Media Entity Beans. Media Foundation Beans let you represent your media independently of its kind. It represents media in a uniform way, letting you program against interfaces representing the media and its metadata (width, height, color dept, frame rate, etc.) instead of programming against a particular media format (GIF or MPEG video for example). You could use Media Foundation Beans to transcode from one format to another, for example to convert your GIF files to PNG (due to patent problems) when serving them from a Servlet. You could resize your media to certain needed dimensions, or add digital watermarks to the stock photographs you sell online. All these media transformations are represented with interfaces, this allows to implement transformation chains of any kind, from any media to any media. Media formats and media converters are designed in a pluggable fashion. In my implementation I'm using Java2 1.4's new Image I/O API (javax.imageio.*) to represent image media (PNG, GIF and JPG) and it's metadata, but since the architecture is pluggable, anybody could implement a new TIFF media format using Image I/O and it could be used to represent that type of image with Media Foundation Beans (TIFF format is not available in Sun's Java2 Standard Edition SDK 1.4). I could have implemented every media format available using third party libraries found on the Internet, to read media headers (mostly magic numbers) and extract metadata information by hand, but the Java2 1.4 SDK has a whole API to represent graphics (javax.imageio.*), so I decided to use it. The only problem is that I'm only representing graphics, not audio or video yet. But since the API is designed to be pluggable, new media could be more or less easily supported, depending on the availability of utility libraries to decode media formats and their metadata. One thing that is remarkable is that the javax.imageio.* formats are represented internally as an XML document. According to the spec, Media Entity Beans (MEB) integrate the services provided by Media Foundation Beans into the Enterprise JavaBeans architecture, adding additional services that require media persistence. That means MEBs could participate in relationships with Entity Beans in J2EE! Imagine your Emmy Awards Enterprise JavaBean System (EAWEJB) representing media clips and domain objects (Artist -- Video Clip) in a transparent CMP style way. No more BLOB nonsense! I'm planning to incorporate my work into JBoss in the next months (JBossMedia is a cool name, isn't it?). I have most of the *only image-format support* Media Foundation Beans API implemented. The most important part, Media Entity Beans, is still missing. If you'd like to help, please drop me a line. Ricardo Argüello [EMAIL PROTECTED] --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: AW: [JBoss-dev] Updating to use Axis 1.1 beta
Never mind. Once we are through this, we have a common denominator to work on ;-) CGJ -Ursprüngliche Nachricht- Von: Tom Elrod [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 7. Januar 2003 23:48 An: [EMAIL PROTECTED] Betreff: Re: AW: [JBoss-dev] Updating to use Axis 1.1 beta I was the one the broke the build. I have updated the following files within jboss.net package: org.jboss.net.jmx.adaptor.AttributeSerializer org.jboss.net.jmx.adaptor.ObjectSerializer to fix the build. You can find the changes made by searching for 'implemented to comply with Axis 1.1beta'. I certainly should have done a clean build before the update and apologize. I also am sorry that I misunderstood I would also give my ok for putting the 1.1 binaries into head as meaning that it would be ok for me to update the binaries into head. -Tom. Jung , Dr. Christoph wrote: You should have tried to build/build most before submitting then you would have noticed that the axis-beta patch has not yet been applied to jboss.net and broke the build. Grrmpf. This leaves it to me to repair it. How I love that. CGJ -Ursprüngliche Nachricht- Von: Tom Elrod [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 7. Januar 2003 08:58 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-dev] Updating to use Axis 1.1 beta I have updated the following in thirdparty to support Axis 1.1 beta (which I needed for JMX SOAP Connector). The update was done to HEAD in CVS. thirdparty/apache-axis/README thirdparty/apache-axis/release-notes.html thirdparty/apache-axis/lib/axis.jar thirdparty/apache-axis/lib/jaxrpc.jar thirdparty/apache-axis/lib/saaj.jar thirdparty/apache-commons/lib/commons-discovery.jar I was unable to verify any affect this might have had on the other jboss projects (other than the e-mail sent out previously), so if you are using any of these, please verify it does not break any of your code. Thanks. -Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jung , Dr. Christoph Sent: Thursday, January 02, 2003 3:42 AM To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-dev] Updating to use Axis 1.1 beta Tom, There is already a patch for jboss.net submitted which addresses some additional exceptions raised in the Axis1.1 beta. I think that I will be able to apply it such that jboss.net will cope with both 1.0 and 1.1 ... I would also give my ok for putting the 1.1 binaries into head, but I would hesitate going for beta in the 3.2 branch. CGJ -Ursprüngliche Nachricht- Von: Tom Elrod [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 31. Dezember 2002 06:28 An: [EMAIL PROTECTED] Betreff: [JBoss-dev] Updating to use Axis 1.1 beta I have written a SOAP connector to be used within the JBoss-MX project which uses Axis 1.1 beta. I know that Axis 1.0 is being used in the root thirdparty for jboss.net and was wondering if someone could tell me if there would be a problem upgrading it to 1.1 beta so both sub-projects (jboss-mx and jboss.net) could use the same libraries? Thanks. -Tom --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored
[JBoss-dev] [ jboss-Bugs-663934 ] IllegalStateException in AbstractInstanceCache
Bugs item #663934, was opened at 2003-01-07 11:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=663934group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Nobody/Anonymous (nobody) Summary: IllegalStateException in AbstractInstanceCache Initial Comment: When I run ECperf with a txrate of 20 on Jboss 3.0.RC2, the following exception pops up every once in a while: 18:55:19,504 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: INSERTING AN ALREADY EXISTING BEAN, ID = 1041562119833 at org.jboss.ejb.plugins.AbstractInstanceCache.insert(AbstractInstanceCache.java:222) at org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.createSession(StatefulSessionFilePersistenceManager.java:199) at org.jboss.ejb.StatefulSessionContainer.createHome(StatefulSessionContainer.java:441) at sun.reflect.GeneratedMethodAccessor208.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.StatefulSessionContainer$ContainerInterceptor.invokeHome(StatefulSessionContainer.java:763) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:105) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:215) at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invokeHome(StatefulSessionInstanceInterceptor.java:128) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:111) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:228) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:62) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:129) at org.jboss.ejb.StatefulSessionContainer.invokeHome(StatefulSessionContainer.java:368) at org.jboss.ejb.Container.invoke(Container.java:730) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:382) at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:554) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=663934group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=
JAVA VERSION DETAILS
java version 1.4.1_01
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
org.jboss.net.axis.mail.MailTransportService -- MailTransportServiceMBean qualified
to MailTransportServiceMBean
org.jboss.net.axis.server.AxisServiceMBean -- EngineConfigurationMBean qualified to
EngineConfigurationMBean
[mkdir] Created dir: /home/jboss/jbossci/jboss-head/jboss.net/output/classes/main
[javac] Compiling 69 source files to
/home/jboss/jbossci/jboss-head/jboss.net/output/classes/main
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/ServiceFactory.java:15:
warning: org.apache.axis.configuration.DefaultEngineConfigurationFactory in
org.apache.axis.configuration has been deprecated
import org.apache.axis.configuration.DefaultEngineConfigurationFactory;
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/axis/ServiceFactory.java:88:
warning: org.apache.axis.configuration.DefaultEngineConfigurationFactory in
org.apache.axis.configuration has been deprecated
return new DefaultEngineConfigurationFactory().getClientEngineConfig();
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:118:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public java.io.ObjectInputStream deserialize(java.lang.String str,
javax.management.ObjectName objectName, byte[] values) throws
javax.management.InstanceNotFoundException, javax.management.OperationsException,
javax.management.ReflectionException {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:122:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
public java.io.ObjectInputStream deserialize(java.lang.String str, byte[] values)
throws javax.management.OperationsException, javax.management.ReflectionException {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:142:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
public java.io.ObjectInputStream deserialize(javax.management.ObjectName
objectName, byte[] values) throws javax.management.InstanceNotFoundException,
javax.management.OperationsException {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:119:
warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(str,objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:123:
warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has
been deprecated
return getServer().deserialize(str,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/server/Adaptor.java:143:
warning: deserialize(javax.management.ObjectName,byte[]) in
javax.management.MBeanServer has been deprecated
return getServer().deserialize(objectName,values);
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:36:
org.jboss.net.jmx.adaptor.AttributeSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.AttributeSerializer
public class AttributeSerializer implements Serializer {
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/AttributeSerializer.java:112:
createAttributeElement(java.lang.String,java.lang.Class,javax.xml.namespace.QName,boolean,org.w3c.dom.Document)
in org.apache.axis.wsdl.fromJava.Types cannot be applied to
(java.lang.String,java.lang.String,boolean,org.w3c.dom.Document)
types.createAttributeElement(
^
/home/jboss/jbossci/jboss-head/jboss.net/src/main/org/jboss/net/jmx/adaptor/ObjectNameSerializer.java:35:
org.jboss.net.jmx.adaptor.ObjectNameSerializer should be declared abstract; it does
not define writeSchema(java.lang.Class,org.apache.axis.wsdl.fromJava.Types) in
org.jboss.net.jmx.adaptor.ObjectNameSerializer
public class
