Re: SableVM & Jikes: java.lang.UnsupportedClassVersionError

2003-01-18 Thread Grzegorz B. Prokopski 
W liście z sob, 18-01-2003, godz. 08:57, Ahmed pisze: 
> Hi,
> 
> $ cat Hello.java
> class Hello {
> public static void main(String[] args) {
> System.out.println("Hello.");
> }
> }
> $ jikes-sable Hello.java
> $ sablevm --no-copyright Hello
> java.lang.UnsupportedClassVersionError
> at java.lang.VMClassLoader.nativeDefineClass(VMClassLoader.java)
> at java.lang.VMClassLoader.defineClass(VMClassLoader.java:78)
> at java.lang.VMClassLoader.defineClass(VMClassLoader.java:121)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:587)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:555)
> at 
> gnu.java.lang.SystemClassLoader.findClass(SystemClassLoader.java:108)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:259)
> at java.lang.VirtualMachine.main(VirtualMachine.java:79)
> $
> 
> My versions:
> sablevm 1.0.5-1
> jikes-sable 1:1.18-1
> jikes 1:1.18-1
> 
> The only thing I found on the net is at:
> http://sourceforge.net/mailarchive/forum.php?thread_id=1437356&forum_id=4151.
> 
> Does Jikes 1.18 bytecode work with SableVM 1.0.5?
As far as I know - No, it doesn't.

Please use jikes from testing distro (1.15). You shouldn't have any
other problems because of that. Bytecode outputed by newer
jikes makes use of some functions that SableVM doesn't have yet.

It's good question to the upstream when it will get that functions.
But I am am sure it's the no. 1 on the TODO list as soon as the author
gets back from his vacations.

BTW: I tested above example w/ jikes 1.15 (and jikes-sable wrapper
from current jikes package version) and it worked.

Grzegorz B. Prokopski
-- 
Grzegorz B. Prokopski <[EMAIL PROTECTED]>
Debian http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: SableVM & Jikes: java.lang.UnsupportedClassVersionError

2003-01-18 Thread Ahmed 
Grzegorz B. Prokopski wrote:


Please use jikes from testing distro (1.15). You shouldn't have any
other problems because of that. Bytecode outputed by newer
jikes makes use of some functions that SableVM doesn't have yet.
 

Jikes seems to have changed a lot since 1.15 
(http://www-124.ibm.com/developerworks/downloads/detail.php?group_id=10&what=rele&id=444).

Still with my 1.18:
$ jikes-sable --source 1.2 Hello.java
$ sablevm --no-copyright Hello
works, 1.3 does not.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

request feedback on JBOSS debs

2003-01-18 Thread Joe Phillips 
On Fri, 2003-01-17 at 22:28, Andrew Savory wrote:

> On Tue, 14 Jan 2003, Joe Phillips wrote:
> 
> > I spent yesterday rebuilding and testing my debs.  The versions
> > currently on my company site[1] have been tested to properly start/stop
> > the server without exceptions.
> 
> Just been trying the debs out (apt-get install jboss jboss-doc), and came
> across the following problems:

I'm glad to see interest.  I'm also glad to get feedback.

I'm assuming the above are the only packages you installed (jboss and
jboss-doc) - you're definitely missing some files then.  It would
explain bad permissions and missing files as you found...

> log4j:ERROR setFile(null,false) call failed.
> java.io.FileNotFoundException: /usr/share/jboss/server/default/log/boot.log 
>(Permission denied)
> 
> (Fixed by chown -R jboss /usr/share/jboss)

Actually, not fixed by that command.  /usr/share/jboss/server/default is
not found in jboss or jboss-doc packages.

> org.jboss.deployment.DeploymentException: url
> file:/usr/share/jboss/server/default/conf/jboss-service.xml could not be opened, 
>does it exist?
> 
> (Fixed by apt-get install jboss-server-all, then editing
> /etc/default/jboss and setting which server to start to "all")

See above comment.

> After all that, there's still no sign of life from JBoss on 8080 or
> 8082... :-(

I expect that you would see jboss on 8080 after installing
jboss-server-all and editing /etc/default/jboss.  You didn't mention but
I hope you set your JAVA_HOME properly within /etc/default/jboss?

This is likely to be a long email so bear with me...

I just now installed my packages on my laptop, a machine on which I have
never installed these packages.  Here's what I did (kindof following
your general steps) to get jboss up on 8080.

1- apt-get install jboss-server-all
this brings in jboss, libjboss3-java, libjboss3-client-java,
jboss-tomcat

2- edit /etc/default/jboss
- set JAVA_HOME to my j2sdk 1.4.1 installation
- set server to 'all'
- enabled (uncommented) console output to /var/log/jboss/console.log

3- start jboss with /etc/init.d/jboss start
waited until I saw the following in /var/log/jboss/console.log...
23:42:25,611 INFO  [Server] JBoss (MX MicroKernel) [3.0.2
Date:200209111840] Started in 0m:51s:521ms

4- hit http://localhost:8080/jmx-console with my browser

My system is Debian stable with Ximian GNOME packages, custom 2.4.18
kernel package, and custom Sun j2sdk-1.4.1 packages.



I'm going to cover details on how the packages are put together and what
motivated my decisions, I'm happy to take comments and feedback.  I'm
also assuming the reader has some experience installing and running
JBOSS from a binary distribution.


The thing to note here is that the 'jboss' package isn't the full JBOSS
and neither is 'jboss-server-all'.  In order to get the *whole* JBOSS as
distributed on sourceforge, with minor changes, you need to install all
the jboss-server-X packages (where X is all, default and minimal).  Each
is installed under a /usr/share/jboss/server/X directory.  

This is how a JBOSS zip/tarball installs by default.  Unfortunately, I
can see where 'jboss-server-all' would be confusing.

Generally, you would only want one of those packages.  By default, the
packages come configured to attempt to run the 'default' server.  You
saw this in your error messages.  This is also why installing
jboss-server-all (and not changing /etc/default/jboss) doesn't fix the
errors you saw.

Each of the jboss-server-X packages' postinstall scripts takes care of
properly setting ownership and permissions on /usr/share/jboss/server/X
files.  Also, some of the directories or files under
/usr/share/jboss/server/X are symlinks to more Debianized locations (eg
/var/log/jboss/X or /etc/jboss/X) to be more in line with Debian policy.

It comes down to, in general, you want jboss-server-minimal,
jboss-server-default or jboss-server-all installed.  /etc/default/jboss
needs to have the server set appropriately to match which server you
wish to run.

My jboss package recommends one of the above three packages but apt-get
won't force you to install a recommended package.  I chose not to depend
on the server packages because you *can* use jboss without them, if you
build your own jboss-server equivalent package.  In fact, this is what
my company is doing in production.  We have a jboss-server-isg package
which is essentially a tweaked jboss-server-default.  Our custom server
package installs under /usr/share/jboss/server/isg/ and requires us to
set JBOSS_SERVER=isg in /etc/default/jboss.

Originally, I considered creating a single server directory, say
/usr/share/jboss/server/default/ removing the all and minimal
directories.  I figured all jboss-server-X packages could install there,
with minimal being a subset of default being a subset of all.  I'm not
so sure they're strictly subsets though.  I also figured that developers
familiar with the three servers in jboss alread

Re: JBoss debs?

2003-01-18 Thread Adam Heath 
On Sat, 11 Jan 2003, Greg Wilkins wrote:

>   + lobby the JBoss project to make any changes that may
> assist you with your packaging (not sure of how successful
> that will be).

Good fucking luck.  JBoss upstream has been resistant to any suggestions on
how they package their dependants.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: JBoss debs?

2003-01-18 Thread Adam Heath 
On 10 Jan 2003, Joe Phillips wrote:

> how's very soon?
>
> you can find my packages for 3.0.2 + tomcat at
> http://debian.innovationsw.com/
>
> I have plans for 3.2 next.

I have jboss debs of 2.4(upto 2.4.7).  All properly split.  Depends on other
java debs in debian(where I can).  All non-free and non-packaged stuff is in
jboss-contrib.  Has a dh_jboss, for those building jboss-using debs.  Splits
the config files into fragments, that get automatically rebuilt into full
files whenever a jboss using deb is installed.

I had this all working last december.

Unfortunately, 3.0 was a radical change, config wise, so I haven't been able
to make 3.0 debs yet.

--
adam@gradall:~/brainfood/jboss/debian$ grep ^Package jboss-2.4.7/debian/control
Package: jboss
Package: jboss-server
Package: jboss-transaction
Package: jboss-catalina-service
Package: jboss-client
Package: jboss-admin
Package: jboss-common
Package: jnp-server
Package: jnp-client
Package: jbossmq
Package: jbossmq-client
Package: jbosssx
Package: jbosssx-client
Package: jboss-contrib-hsqldb
Package: jboss-contrib-oswego
Package: jboss-contrib-tyrex
Package: jboss-contrib-castor
Package: jboss-contrib
Package: jboss-dev
Package: jboss-docs
Package: jboss-jdbc-postgresql
Package: jboss-jdbc-mysql
Package: jboss-mail


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: JBoss debs?

2003-01-18 Thread Joe Phillips 
On Sun, 2003-01-19 at 01:42, Adam Heath wrote:
> On 10 Jan 2003, Joe Phillips wrote:
> 
> > how's very soon?
> >
> > you can find my packages for 3.0.2 + tomcat at
> > http://debian.innovationsw.com/
> >
> > I have plans for 3.2 next.
> 
> I have jboss debs of 2.4(upto 2.4.7).  All properly split.  Depends on other
> java debs in debian(where I can).  All non-free and non-packaged stuff is in
> jboss-contrib.  Has a dh_jboss, for those building jboss-using debs.  Splits
> the config files into fragments, that get automatically rebuilt into full
> files whenever a jboss using deb is installed.

Yeah...I downloaded your sources at one point.  Still need to read
through your work.  My packages are completely my own mess.

> Unfortunately, 3.0 was a radical change, config wise, so I haven't been able
> to make 3.0 debs yet.

Well I'd be happy to take comments and or work with you in improving my
3.x series of packages.

By now you should have seen my long email discussing some of the
problems I'm seeing.  I'd like to hear your suggestions.

Right now, I don't expect to see a whole lot of help from upstream in
'fixing' their distro.  We'll see what happens with time.

-joe
-- 
 Innovation Software Group, LLC - http://www.innovationsw.com/
Business Automation Specialists
 UNIX, Linux and Java Training


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: JBoss debs?

2003-01-18 Thread Adam Heath 
On 19 Jan 2003, Joe Phillips wrote:

> Yeah...I downloaded your sources at one point.  Still need to read
> through your work.  My packages are completely my own mess.
>
> > Unfortunately, 3.0 was a radical change, config wise, so I haven't been able
> > to make 3.0 debs yet.
>
> Well I'd be happy to take comments and or work with you in improving my
> 3.x series of packages.

I might be able to convince my boss to doing more work on them.

> By now you should have seen my long email discussing some of the
> problems I'm seeing.  I'd like to hear your suggestions.

I had, but hadn't read it.  I'll get a reply back to you tomorrow, most
likely.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

SableVM & Jikes: java.lang.UnsupportedClassVersionError

2003-01-18 Thread Ahmed 
Hi,
$ cat Hello.java
class Hello {
   public static void main(String[] args) {
   System.out.println("Hello.");
   }
}
$ jikes-sable Hello.java
$ sablevm --no-copyright Hello
java.lang.UnsupportedClassVersionError
   at java.lang.VMClassLoader.nativeDefineClass(VMClassLoader.java)
   at java.lang.VMClassLoader.defineClass(VMClassLoader.java:78)
   at java.lang.VMClassLoader.defineClass(VMClassLoader.java:121)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:587)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:555)
   at 
gnu.java.lang.SystemClassLoader.findClass(SystemClassLoader.java:108)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:308)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:259)
   at java.lang.VirtualMachine.main(VirtualMachine.java:79)
$

My versions:
sablevm 1.0.5-1
jikes-sable 1:1.18-1
jikes 1:1.18-1
The only thing I found on the net is at:
http://sourceforge.net/mailarchive/forum.php?thread_id=1437356&forum_id=4151.
Does Jikes 1.18 bytecode work with SableVM 1.0.5?

Re: SableVM & Jikes: java.lang.UnsupportedClassVersionError

2003-01-18 Thread Grzegorz B. Prokopski 
W liście z sob, 18-01-2003, godz. 08:57, Ahmed pisze: 
> Hi,
> 
> $ cat Hello.java
> class Hello {
> public static void main(String[] args) {
> System.out.println("Hello.");
> }
> }
> $ jikes-sable Hello.java
> $ sablevm --no-copyright Hello
> java.lang.UnsupportedClassVersionError
> at java.lang.VMClassLoader.nativeDefineClass(VMClassLoader.java)
> at java.lang.VMClassLoader.defineClass(VMClassLoader.java:78)
> at java.lang.VMClassLoader.defineClass(VMClassLoader.java:121)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:587)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:555)
> at 
> gnu.java.lang.SystemClassLoader.findClass(SystemClassLoader.java:108)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:259)
> at java.lang.VirtualMachine.main(VirtualMachine.java:79)
> $
> 
> My versions:
> sablevm 1.0.5-1
> jikes-sable 1:1.18-1
> jikes 1:1.18-1
> 
> The only thing I found on the net is at:
> http://sourceforge.net/mailarchive/forum.php?thread_id=1437356&forum_id=4151.
> 
> Does Jikes 1.18 bytecode work with SableVM 1.0.5?
As far as I know - No, it doesn't.

Please use jikes from testing distro (1.15). You shouldn't have any
other problems because of that. Bytecode outputed by newer
jikes makes use of some functions that SableVM doesn't have yet.

It's good question to the upstream when it will get that functions.
But I am am sure it's the no. 1 on the TODO list as soon as the author
gets back from his vacations.

BTW: I tested above example w/ jikes 1.15 (and jikes-sable wrapper
from current jikes package version) and it worked.

Grzegorz B. Prokopski
-- 
Grzegorz B. Prokopski <[EMAIL PROTECTED]>
Debian http://www.debian.org/

Re: SableVM & Jikes: java.lang.UnsupportedClassVersionError

2003-01-18 Thread Ahmed 
Grzegorz B. Prokopski wrote:
Please use jikes from testing distro (1.15). You shouldn't have any
other problems because of that. Bytecode outputed by newer
jikes makes use of some functions that SableVM doesn't have yet.
 

Jikes seems to have changed a lot since 1.15 
(http://www-124.ibm.com/developerworks/downloads/detail.php?group_id=10&what=rele&id=444).

Still with my 1.18:
$ jikes-sable --source 1.2 Hello.java
$ sablevm --no-copyright Hello
works, 1.3 does not.