<< 28-August-2008 : bevinbot on #glassfish at freenode [download] [back] >>
 
 
time nick message

01:12

<slyphon>

hey, i have a bit of a j2ee newb question, i'm trying to follow http://weblogs.java.net/blog/rampsarathy/archive/2007/03/glassfish_v2_an.html to get GF to to talk with activemq

01:12

<slyphon>

i'm a little confused about jndi though

01:13

<slyphon>

he links to this http://weblogs.java.net/blog/rampsarathy/archive/Main.java, but I can't figure out how that class gets invoked by Glassfish

01:59

<[pwgr]>

slyphon: i dont see why that class would get invoked by glassfish

02:00

<slyphon>

hmm, ok, i'm totally out of my element here

02:00

<slyphon>

is that used to bind a resource in jndi?

02:00

<[pwgr]>

and that toally looks like an assinine way to use glassfish and activemq

02:00

<slyphon>

slyphon laughs

02:00

<[pwgr]>

isnt there a jca way of doing it ?

02:00

<slyphon>

java connector api?

02:00

<[pwgr]>

yes

02:00

<slyphon>

slyphon looks for the link

02:01

<slyphon>

http://activemq.apache.org/sjsas-with-genericjmsra.html

02:01

<[pwgr]>

yes, there ya go

02:01

<slyphon>

i'm afraid i'm about as lost with this, though

02:01

<slyphon>

although i got the first step done

02:03

<slyphon>

generally, what i'm trying to accomplish is that my apps would be able to get a connection to activemq via JNDI

02:03

<slyphon>

am i even on the right track?

02:03

<slyphon>

and that configuration would pretty much live on glassfish

02:03

<[pwgr]>

well, how do your apps normaly get a connection to activemq ?

02:03

<slyphon>

(we're a ruby shop and moving to jruby, so it'd be nice to be able to tell the developers, "To get a connection that will work in any environment, just get a connection using 'jms/TehQueuz'"

02:03

<slyphon>

well

02:04

<[pwgr]>

well, why are you using activemq specifically?

02:04

<slyphon>

create an ActiveMQConnectionFactory, do createConnection, etc

02:04

<slyphon>

it seemed to be the best choice, as a standalone thing

02:05

<slyphon>

it was popular, recommended by someone whose opinion i trust, etc. etc.

02:05

<[pwgr]>

is that the same with glassfish ?

02:05

<[pwgr]>

same reason for using glassfish ?

02:05

<slyphon>

yeah, pretty much, plus we're a solaris shop, and everyone in the jruby community seems to have very good opinions of it

02:06

<slyphon>

i'm really a j2ee neophyte

02:06

<slyphon>

it *looks* like this would make an ideal deployment environment for our app

02:06

<[pwgr]>

if there's no coupling of the ruby stuff to activemq... i'd recommend dumping activemq and just using openmq

02:06

<slyphon>

well

02:07

<slyphon>

there's no coupling, but why move to openmq?

02:07

<[pwgr]>

less fiddling and more reliability

02:07

<slyphon>

orly?

02:07

<[pwgr]>

yhrly

02:07

<slyphon>

:D

02:07

<[pwgr]>

plus it's bundled in glassfish so... even less fiddling

02:07

<slyphon>

ah, that's good

02:07

<[pwgr]>

just sets up your destinations and go

02:08

<slyphon>

how hard is it to set up failover/clustering/HA/replication/etc

02:08

<slyphon>

you know, the Things That Let You Avoid SPOFs

02:08

<[pwgr]>

slyphon: not too hard... but the difficulty in setting is pretty linear the complexity of your requirements

02:08

<[pwgr]>

er, difficulty in setting it up

02:09

<slyphon>

we have a pretty simple use-case, i think

02:09

<slyphon>

i mean

02:09

<[pwgr]>

if you just need HA JMS then it's pretty simple

02:09

<slyphon>

yeah, that's us

02:09

<[pwgr]>

it's all built into glassfish

02:09

<slyphon>

oh nice

02:10

<slyphon>

i have activemq set up now with two master/slave pairs replicating between both

02:10

<slyphon>

but yeah, less configuration == less configuration

02:11

<[pwgr]>

and interestingly enough im hearing more and more references of people dumping activemq for openmq for reliability and stability

02:11

<slyphon>

oh, well

02:12

<[pwgr]>

i havent touched activemq for like 3 years through myself

02:12

<slyphon>

you had me at "reliablity...built in"

02:12

<slyphon>

it seems that they've made quite a lot of progress, then again, it's from The People Who Brought You Apache Web Server

02:13

<[pwgr]>

heh ive read through this blog like 6 times now and i still dont understand the steps required

02:14

<slyphon>

oh thank god

02:14

<slyphon>

i'm not a total moron

02:15

<[pwgr]>

this ramesh guy is an openmq guy though... wonder why he's blogging about activemq and websphere mq

02:15

<[pwgr]>

probably since he works on the generic jca adapter stuff

02:15

<slyphon>

yeah, a bit odd

02:16

<[pwgr]>

heh but if you look on glassfish/openmq forums... he helps everyone :)

02:16

<[pwgr]>

unless im thinking of a different ramesh

02:17

<[pwgr]>

slyphon: so this "replication" stuff you setup with activemq... that is to support HA?

02:17

<[pwgr]>

slyphon: in an active/passive way ?

02:17

<slyphon>

yeah

02:17

<[pwgr]>

failover HA strategy

02:17

<[pwgr]>

hehe, ActivePassiveMQ

02:17

<slyphon>

you can define it in your connection string

02:17

<slyphon>

:D

02:18

<slyphon>

and it'll replicate that between whatever-nodes-in-each-cluster-is-up-right-then

02:18

<slyphon>

s/is/are/

02:19

<[pwgr]>

it duplicates the messages to all the nodes specified in your connection string ?

02:19

<[pwgr]>

shouldnt it just send to one and if that fails, send to the next one ?

02:19

<[pwgr]>

the activemq nodes know about each other and replicate the data to each other? or use a shared message store?

02:20

<slyphon>

sorry, brb

02:32

<slyphon>

[pwgr]: well, you set up your servers in failover pairs (they use flock(2) afaict) and a shared message store (on NFS or a SAN), so if one process dies the other process will acquire the lock and already have all the messages ready to serve out

02:33

<slyphon>

[pwgr]: the way i configured it was having two pairs like that A-A' and B-B'

02:33

<slyphon>

tehn you set up a transport connection between the two of them (in the config file)

02:33

<slyphon>

so B-B' <-> A-A'

02:33

<[pwgr]>

over NFS? that's horrible

02:33

<slyphon>

ehhh, it's not as bad as you might think, if you have a reliable server

02:34

<[pwgr]>

well, i know exactly how bad it is. hehe

02:34

<slyphon>

plus, we have NFS pretty much everywhere, so it was a pretty easy thing to roll out

02:34

<slyphon>

heh :)

02:34

<slyphon>

yeah

02:34

<slyphon>

NFS F**king Sucks

02:34

<[pwgr]>

[pwgr] has too much experience with storage internals

02:34

<slyphon>

:)

02:35

<[pwgr]>

but SAN isnt that bad if you have it

02:35

<slyphon>

yeah, unfortunately we don't

02:35

<[pwgr]>

it uses a raw device or something ?

02:35

<slyphon>

not really sure

02:35

<slyphon>

i think they meant "shared filesystem"

02:35

<slyphon>

with locking

02:35

<[pwgr]>

or do they assume SAN == "expensive clustered filesystem on a SAN"

02:35

<slyphon>

it wasn't an option for us, so we couldn't use that

02:35

<slyphon>

yeah

02:35

<slyphon>

i think that's probably more accurate

02:36

<slyphon>

i *seriously* doubt they're doing anything at the block level

02:36

<[pwgr]>

really? that seems the best way to go

02:36

<slyphon>

well

02:36

<slyphon>

i mean

02:36

<slyphon>

"best" in one way, sure

02:36

<slyphon>

but, you know, "windows"

02:37

<[pwgr]>

w/ NFS you have the full IP stack to deal with, and then local platform locking semantics and whatever bugs and interoperability snafus lies with in that

02:37

<slyphon>

absolutely

02:37

<slyphon>

how does openmq deal with it?

02:37

<[pwgr]>

well actually if you're running on solaris its not the end of the world

02:37

<slyphon>

:)

02:37

<slyphon>

yeah, solaris has been very good to us

02:38

<[pwgr]>

but would be much better to be able to setup an iscsi device and go raw block dev access

02:38

<slyphon>

except for a 10u4/u5 NFSv4 lib conflict

02:38

<slyphon>

*that* was *hella* fun to try and figure out

02:38

<slyphon>

"WTF is 'ESTALE'?!"

02:39

<[pwgr]>

openmq uses a clustered JDBC datasource for clustering

02:39

<slyphon>

hmmm

02:39

<slyphon>

can you use derby?

02:40

<[pwgr]>

hehe nah derby's not clusterable

02:40

<slyphon>

*damn*

02:40

<[pwgr]>

you'd use something like oracle rac

02:40

<slyphon>

slyphon was hoping they'd added that

02:40

<slyphon>

fuck

02:40

<[pwgr]>

but actually it's probably preferred to just use HADB

02:40

<slyphon>

dude, if we had a budget...

02:40

<[pwgr]>

HADB is no cost

02:40

<slyphon>

HADB?

02:40

<slyphon>

unfortunately we don't have an RDBMS solution at my place

02:40

<slyphon>

we have MySQL

02:41

<slyphon>

which is good...you know...if you don't try to do anything with it that you couldn't do with sed/grep/awk

02:41

<[pwgr]>

yeah HADB is sun's HA database

02:41

<[pwgr]>

it's not opensource but it's free

02:41

<slyphon>

ahhhh

02:41

<slyphon>

is it part of cluster?

02:41

<slyphon>

slyphon phears sun cluster

02:43

<slyphon>

ohhhh

02:43

<slyphon>

riiiiight

02:43

<slyphon>

so *this* is what the "HA Session Store" is

02:43

<[pwgr]>

nah it's not part of sun cluster

02:43

<[pwgr]>

though sun cluster might have agents for it

02:43

<slyphon>

slyphon nods

02:43

<slyphon>

i tried to read through sun cluster's documentation once

02:44

<slyphon>

after i got a nosebleed and passed out, i decided that was enough

02:46

<slyphon>

so is HADB distributed with GF as well? oh, and what's the difference between GF and the Sun Application Server that's bundled with their directory server?

02:48

<[pwgr]>

HADB isnt bundled with GF or SJSAS, it's a separate download, but usually linked with the SJSAS downloads

02:48

<slyphon>

slyphon nods

02:48

<[pwgr]>

actually they may have started bundling it together but i havent looked in awhile

02:49

<slyphon>

slyphon nods

02:49

<slyphon>

what's the diff between GF and SJSAS?

02:49

<[pwgr]>

SJSAS is just a commercial distribution of GF

02:49

<slyphon>

"pizzaz"?

02:49

<slyphon>

ah

02:49

<[pwgr]>

they are very much the same thing

02:49

<slyphon>

oh

02:49

<slyphon>

is it at all like solaris v. opensolaris?

02:50

<slyphon>

or not even?

02:50

<[pwgr]>

it's not even that big of a different

02:50

<slyphon>

oh, cool

02:50

<slyphon>

well, that'll be easy to sell to the CTO :)

02:50

<[pwgr]>

but, sorta the same idea business model wise

02:50

<slyphon>

slyphon nods

02:51

<slyphon>

to be honest, it'd be easier to deploy something that had native packages anyway

02:51

<[pwgr]>

i wouldnt run anything critical on opensolaris :)

02:51

<slyphon>

no, we don't

02:51

<slyphon>

10u5, baby

02:51

<slyphon>

zfs + zones ftw

02:52

<[pwgr]>

well, i just like having patches available

02:52

<slyphon>

this is true

02:52

<slyphon>

oh, they renamed it

02:52

<[pwgr]>

i care more about real patches and timely fixes for stuff more than bleeding edge features like zfs roots and stuff

02:52

<slyphon>

it's now the Sun GlassFish Enterprise Server

02:53

<slyphon>

yeah, totally

02:53

<slyphon>

although, having the virtualized network stuff they've been talking about for zones would be sweet

02:53

<[pwgr]>

yes it would... very much looking forward to that

02:53

<[pwgr]>

have been waiting for that to come to solaris for years actually

02:54

<slyphon>

yeah, we had a hell of an adventure with multi-homed hosts and zones

02:54

<[pwgr]>

resource managment and stuff has been wonderful at the cpu and memory level in solaris... but still very much lacking in the networking realm

02:54

<slyphon>

unfortunately, my team has very talented sysadmins and systems developers, but networking ninjas we ain't

02:54

<slyphon>

slyphon nods

02:55

<slyphon>

i was really suprised at how solaris didn't even really have a decent firewall (aside from ipfilter or what-have-you)

02:56

<[pwgr]>

yeah... they got the ipf stuff down... the bsd style firewall stuff... but ipqos is still lacking

02:56

<slyphon>

slyphon nods

02:57

<[pwgr]>

but for me ive always had better luck with solaris and the primitive ipf than linux's equivalents

02:57

<slyphon>

oh yeah

02:57

<slyphon>

i mean

02:57

<[pwgr]>

i had so many pobs with the likes of ipmasq and ipfwadm or whatever that was

02:57

<slyphon>

i was really amazed at how much more solid solaris is

02:57

<[pwgr]>

and i still have some problems with iptables

02:57

<slyphon>

slyphon nods

02:58

<[pwgr]>

and it's like all the fixes are "get this newer kernel version and/or apply these kernel patches"

02:58

<slyphon>

i think pf is the only firewall config i've ever understood, and i'll be *damned* if i'm gonna run openbsd

02:58

<[pwgr]>

that's not really an option for me

02:58

<slyphon>

slyphon nods

02:58

<[pwgr]>

which is why i'm not running opensolaris and friends :)

02:58

<slyphon>

it's fun if you like bleeding a lot, and getting paged constantly

02:59

<[pwgr]>

yeah IMO once things go beyond ipf... time to get a dedicated firewall

02:59

<slyphon>

:)

02:59

<slyphon>

although

02:59

<slyphon>

we have two ASAs and they're a *bitch* to configure

02:59

<slyphon>

getting NAT working on them was *not* fun

02:59

<[pwgr]>

and my networks are never big enough to have dedicated network admins

02:59

<slyphon>

slyphon nods

03:00

<[pwgr]>

anytime i have anyone dedicated to networks... they dont have enough real work to do so they are artificially bloating requirements to make projects for themselves or increase complexity to keep themselves stimulated

03:00

<slyphon>

yup

03:01

<[pwgr]>

so, sysadmins that have social networks to draw from where we can have real network guys when we need them and have them out of the way when network is fine...

03:01

<slyphon>

heh

03:01

<[pwgr]>

those social bonds get guys who want to do a good job for the sake of their relationships with their friends... it just produces good results :)

03:01

<slyphon>

and that's why "consulting" was invented

03:01

<slyphon>

yeah, totally

03:02

<[pwgr]>

whereass getting a consultant from a local VAR usually, in my experience, ends up in consultant doing halfassed job that requirements more maintenance than is necessary

03:02

<slyphon>

well, yeah

03:02

<slyphon>

i mean

03:03

<[pwgr]>

i like the guys who come in, do the job, xfer the knowledge necessary to the admin staff, hand me an invoice and get the heck out

03:03

<slyphon>

how else are they gonna guarantee you're gonna call them back?

03:03

<[pwgr]>

exactly

03:03

<slyphon>

that's just bad business, in the end

03:06

<[pwgr]>

yeah looks like they are pushing the Glassfish Enterprise Server name now

03:07

<slyphon>

i guess it's popular enough as a brand

03:07

<[pwgr]>

yeah i was gonna say they surprisingly got the glassfish brand rolling in the past two years or so

03:07

<[pwgr]>

so why not take advantage of it

03:07

<slyphon>

indeed

03:08

<slyphon>

it's recognizable, that's for sure

03:08

<[pwgr]>

sjsas_ee-9_1_01-solaris-i586.bin Sun Java System Application Server 9.1 Update 1 with HADB 220.99 MB

03:08

<[pwgr]>

i guess they are bundling it altogether now

03:08

<[pwgr]>

how convenient

03:09

<slyphon>

slyphon is downloading it right now

03:09

<slyphon>

HADB isn't hard to set up?

03:09

<[pwgr]>

nah, not if you know how to read the documentation

03:09

<slyphon>

:)

03:10

<slyphon>

yeah, that's another thing that i was really pleased with when we moved to solaris

03:10

<slyphon>

they actually *have* documentation

03:10

<[pwgr]>

but there's more to it than simply running an ant script

03:10

<slyphon>

heh

03:10

<[pwgr]>

you have to do stuff like setup networking, clock syncing, some IPC stuff

03:11

<slyphon>

woah

03:11

<slyphon>

that's heavy-duty

03:12

<slyphon>

hmm, do you think you could use a LAG instead of IPMP?

03:13

<[pwgr]>

does LAG do failover ?

03:13

<[pwgr]>

or survive partial link failure?

03:13

<slyphon>

well, yeah, it's 2 interfaces 1 ip

03:13

<slyphon>

either goes, you're still up

03:14

<[pwgr]>

but it survives if one interface goes tits up and is left with less than initially setup with ?

03:14

<slyphon>

yeah

03:14

<slyphon>

the only disadvantage is that you have to have both wires plugged into the same switch

03:15

<[pwgr]>

i'd bet it'd work

03:15

<[pwgr]>

you just have to choose how much redundancy you actually want

03:15

<[pwgr]>

how many points of failure you want to account for

03:15

<slyphon>

i mean, the point is "This Physical Link Will Not Go Down"

03:15

<slyphon>

slyphon nods

03:15

<slyphon>

well, initially, i ain't gonna bother with that ;)

03:16

<slyphon>

ugh

03:16

<slyphon>

i wonder if i can get away with not editing /etc/system and rebooting :/

03:17

<[pwgr]>

oh, editing /etc/system fo the semaphore stuff... yes, you can

03:17

<[pwgr]>

use project stuff

03:17

<slyphon>

ah

03:17

<slyphon>

how about zone config?

03:18

<slyphon>

i think they let you set some of the shmem stuff in your config

03:23

<[pwgr]>

hrm, i dunno about that

03:23

<slyphon>

eh, i'm probably not gonna set this up tonight anyway :)

03:23

<slyphon>

i'll need to digest it a bit

03:24

<[pwgr]>

i know you can set memory caps and cpu scheduling stuff, but i dunno about IPC stuff

03:24

<slyphon>

slyphon nods

03:24

<slyphon>

i've never had to think about IPC so i'm not sure myself

03:24

<[pwgr]>

hmm, im thinking you can set zone attributes in resource configs

03:25

<slyphon>

The zone.max-msg-ids, zone.max-sem-ids, zone.max-shm-ids, and zone.max-shm-memory

03:25

<slyphon>

resource controls are used to limit System V resources used by all processes within a zone.

03:26

<[pwgr]>

hehe yep that's them right there

03:26

<slyphon>

yay!

03:29

<[pwgr]>

ok, there's an HA admin guide in the SJSAS docset

03:29

<[pwgr]>

it covers JMS

03:29

<slyphon>

*sweet*

03:29

<slyphon>

i was reading this: http://docs.sun.com/app/docs/doc/819-3679/abdca?a=view

03:29

<[pwgr]>

yep that's the HA admin guide

03:29

<slyphon>

kewl, man, they must have an *army* of people writing this stuff

03:30

<slyphon>

slyphon blinks

03:30

<slyphon>

[root@overkill ~]# xclock

03:30

<[pwgr]>

hehe it's probably like 3 dedicated people :)

03:30

<slyphon>

Segmentation Fault (core dumped)

03:30

<slyphon>

hahaha

03:30

<slyphon>

now that ^^ is something you don't expect to see

03:31

<[pwgr]>

[admin@solaris1 ~]$ xclock

03:31

<[pwgr]>

Error: Can't open display:

03:31

<[pwgr]>

that's what i expect :)

03:31

<slyphon>

hahaha

03:31

<[pwgr]>

WHOAH

03:32

<slyphon>

?!

03:32

<[pwgr]>

i logged in with ssh -X

03:32

<[pwgr]>

and accidentally typed xlock instead of xclock

03:32

<slyphon>

!

03:32

<[pwgr]>

heh locked my local X server

03:32

<slyphon>

hahahaha

03:32

<[pwgr]>

luckily it said login name was the admin user

03:32

<[pwgr]>

i would have had no idea how to unlock it otherwise

03:32

<slyphon>

that would have *sucked*

03:33

<[pwgr]>

and im multitasking between about 14 different things here

03:33

<slyphon>

:)

03:33

<[pwgr]>

would suck ot have to kill the Xserver and try to figure out everything i had going again

03:33

<slyphon>

oh yeah

03:33

<slyphon>

gnu screen, ftw

03:34

<[pwgr]>

yeah i have vncs to a bunch of servers and remote vmware connections and stuff

03:34

<slyphon>

ahhh

03:34

<slyphon>

yeah

03:35

<slyphon>

the guy that figures out 'screen' for X is gonna be famous

03:35

<[pwgr]>

im testing pca on solaris... first time ive tried it

03:35

<slyphon>

oh, i really like it

03:35

<slyphon>

and i'm a total n00b when it comes to patching solairs

03:35

<slyphon>

which may be a vote for or against it in your book :)

03:36

<[pwgr]>

if it works for me i'll like it

03:36

<[pwgr]>

otherwise I wont :)

03:36

<slyphon>

but i was able to patch our systems to roll out sun DS without really having to know what i was doing

03:36

<slyphon>

it's the closest to apt-get i've found on solaris

03:36

<[pwgr]>

smpatch treated me well for a few years but lately its really messin up on me

03:36

<slyphon>

i liked it initially, but the problem was that i'd log in and there'd be like 100 ccctransport proceses running

03:37

<[pwgr]>

sunDS ?

03:38

<[pwgr]>

I use it but i dont use the solaris package versions... i install the standalone tarball

03:38

<[pwgr]>

and dont bother with console integration and that nonsense

03:38

<slyphon>

directory server

03:38

<[pwgr]>

yeah... i'm not familiar with what ccctransport is

03:38

<[pwgr]>

common container connection transport? :)

03:38

<slyphon>

something like that

03:38

<[pwgr]>

[pwgr] guesses wildly

03:38

<slyphon>

it's like CCCP for unix

03:39

<[pwgr]>

i just like doing the directory server stuff from the commandline

03:39

<slyphon>

oh? i'm glad they have the whole webconsole thing

03:40

<slyphon>

b/c LDAP and me? we ain't friends

03:40

<slyphon>

we're cordial, but wary

03:40

<[pwgr]>

heh yeah... i use the web admin thing inside glassfish for testing

03:40

<[pwgr]>

that little struts based thing they have that comes with the directory server

03:41

<slyphon>

yeah

03:41

<[pwgr]>

they bundle a war but dont bundle a tomcat instance or anything :/

03:41

<slyphon>

:P

03:41

<[pwgr]>

so i just plop it into a glassfish domain and use it from there

03:41

<slyphon>

hahahaha

03:41

<slyphon>

nice

03:41

<[pwgr]>

works as well as is needed

03:41

<slyphon>

it's meant to integrate with webconsole (svcadm enable webconsole)

03:42

<slyphon>

but it's a bitch to get it all working smooth

03:42

<[pwgr]>

hehe yeah... me and webconsole aint friends

03:42

<slyphon>

:)

03:42

<slyphon>

thankfully someone else from work figured it out and documented it

03:42

<[pwgr]>

that's one part of solaris i havent bothered to work through

03:42

<slyphon>

the biggest problem we've had with it is that *nowhere* is it documented how to replace the SSL cert

03:43

<[pwgr]>

the webconsole or the directory server ?

03:43

<slyphon>

webconsole

03:43

<[pwgr]>

oh

03:43

<slyphon>

the DS we have working with our internal CA

03:43

<[pwgr]>

but not the webconsole ?

03:43

<slyphon>

yup

03:44

<slyphon>

it's not a huge deal, it just means firefox bitches :)

03:44

<[pwgr]>

i wouldnt know anything about it

03:44

<[pwgr]>

yeah

03:44

<[pwgr]>

i'd really only need it if i want to hand stuff off to some nonunix people

03:45

<slyphon>

slyphon nods

03:45

<[pwgr]>

i have some customers that run some linux stuff very blindly

03:45

<[pwgr]>

hehe using webmin

03:45

<slyphon>

:)

03:45

<slyphon>

oy vey

03:45

<slyphon>

webmin got me off the ground when i was starting out

03:45

<[pwgr]>

i havent tried the webmin stuff in solaris too much... i think i set it up and was trying to do some sendmail config with it and it broke and i didnt bother after that

03:45

<[pwgr]>

but figured webconsole would be better suites

03:46

<[pwgr]>

suited

03:46

<slyphon>

slyphon nods

03:46

<slyphon>

deploying that war in GF sounds like a good workaround

03:46

<[pwgr]>

actually i kinda liked the volume management stuff that was in webconsole

03:46

<slyphon>

oh? i do all that zfs stuff by hand

03:46

<[pwgr]>

for setting up concatened volumes for UFS filesystems and stuff

03:46

<slyphon>

ohhhhh

03:46

<slyphon>

yeah, that'd be useful

03:47

<[pwgr]>

yeah i havent tried any of the zfs or containers stuff in webconsole

03:47

<[pwgr]>

i just dont like how much memory it chews up :)

03:47

<slyphon>

hahaha

03:48

<[pwgr]>

and i dont like all the security vulnerabilitites and patches i see for it

03:48

<slyphon>

well

03:48

<slyphon>

i mean

03:48

<slyphon>

don't expose that to the web, duh

03:48

<slyphon>

;)

03:49

<[pwgr]>

does the webconsole stuff work OK in firefox other than the SSL complaints?

03:49

<slyphon>

oh, definately

03:49

<slyphon>

they improved the interface in u5+patches

03:49

<[pwgr]>

hehe man i just started using firefox3 and it seriously pitches a fit w/ non 3rd party authorized stuff

03:49

<slyphon>

haha

03:49

<slyphon>

yeah, at least they let you store the cert

03:50

<slyphon>

which is an improvement

03:50

<[pwgr]>

hmm i never store certs that arent validated by a known authority

03:50

<[pwgr]>

i store self signed certs but other than that... like certs that are generated for testing purposes, i never store those

03:50

<slyphon>

oh?

03:51

<slyphon>

oh, yeah

03:51

<[pwgr]>

im too afraid of forgetting about them or something

03:51

<slyphon>

our shop is sufficiently small where we don't really have to worry too much about that

03:51

<slyphon>

we're not hosting anybody else

03:52

<[pwgr]>

finally! done patching

03:53

<[pwgr]>

pca definately takes longer than smpatch :/

03:53

<slyphon>

hm

03:53

<slyphon>

well, it *is* like a 5000 line perl script

03:54

<slyphon>

[pwgr]: oh, here's a n00b question for you, can you control what uid/gid a given app runs as in GF?

03:55

<[pwgr]>

nah everything runs as the uid/gid running the jvm

03:55

<slyphon>

soh!

03:55

<slyphon>

sadlkfjas

03:55

<slyphon>

doh!

03:56

<[pwgr]>

i just standardize on a single app server user, install glassfish as that user, and everything runs as that user

03:56

<[pwgr]>

there's no concept of setuid in jvm land without resorting to skanky trickery

03:56

<slyphon>

yeah, we've pretty much got that

03:56

<slyphon>

slyphon nods

03:56

<[pwgr]>

thank goodness solaris allows you to grant privs to nonroot users to run stuff on ports less than 1024

03:57

<slyphon>

yeah, seriously

03:57

<slyphon>

the RBAC stuff is impressive

03:57

<[pwgr]>

cant believe linux doesnt support that

03:57

<[pwgr]>

linux is the future!

03:57

<slyphon>

i think you really have to *pay* people to develop shit like that

03:57

<slyphon>

haha

03:57

<slyphon>

and it always will be

03:58

<[pwgr]>

root

03:58

<[pwgr]>

ewps

03:59

<[pwgr]>

got too much stuff going on here, grabbed the wrong mouse

03:59

<slyphon>

hah

03:59

<slyphon>

eeeeeek!

04:06

<slyphon>

[pwgr]: ok, bedtime for me, good talkin' with ya

04:06

<slyphon>

thanks for the help

04:07

<[pwgr]>

yep same, gnite

04:07

<slyphon>

lata

09:28

<pookey>

hi all - I'm trying to setup Javamail, and it's insisting on a username for STMP, however... it's a internal relay, so no auth is required

09:51

<kjkoster5489>

pookey: maybe this question is better asked in #java

09:52

<pookey>

a username of '-' makes glassfish accept it, and my mail server is relaying just fine - seems a bit silly that the glassfish UI makes it required, perhaps I should open a bug report

10:47

<sisred>

if I'm monitoring a connection pool, do I enable monitoring in the DAS 'server-config' or the cluster 'roller-cluster-config'?

19:11

<nikolaj_a>

Anyone knows how to a hold of a datasource with JNDI from within a custom realm implementation?

21:29

<redrebel>

why would a values retrieved through a session bean and Entity classes doesn't match the data in the database table?

21:31

<redrebel>

this only happens when I update the records through my RDMS client

21:31

<redrebel>

my guess is that i'm seeing caching in action, if this is the case how do you stop it?

21:34

<redrebel>

yes, its a caching problem,

21:34

<nikolaj_a>

redrebel: I think there's a flush() method on the entity manager.

21:35

<redrebel>

if i wait long enough, the values do change

21:43

<[pwgr]>

if something else is changing the data without letting the app server know about it... that will happen

21:44

<redrebel>

that is what is happening

21:44

<redrebel>

em.flush() by itself is not helping

21:44

<[pwgr]>

if the session+entity setup in the app do not have exclusive access to the db... you'll have to either make everything else notify the appserver of the data changes, which is not trivial... or yu'll have to modify the querying of the session beans to refresh the data

21:44

<[pwgr]>

nah flush isnt what you need... more like refresh()

21:46

<nikolaj_a>

redrebel: refresh() was what I was referring to. Just forgot the name :)

21:46

<nikolaj_a>

flush() is the other way.

21:47

<[pwgr]>

IMO, refresh() from the entity manager isnt even that good of a way to do it

21:47

<[pwgr]>

better to tell the jpa provider to refresh during the query process

21:47

<[pwgr]>

done through query hints if you have experience with those

21:48

<[pwgr]>

if you're using glassfish w/ the bundled TLE provider you can do something like setHint("toplink.refresh", true) or something

21:49

<[pwgr]>

i guess itd be setHint("toplink.refresh","true") since it wants a string as the 2nd param

21:50

<redrebel>

i think i'm just gonna stick to managing the db through my session beans

21:53

<[pwgr]>

nikolaj_a: yeah flush is the opposite direction :)

21:53

<[pwgr]>

flush is an awesome name for an api function!

21:59

<nikolaj_a>

[pwgr]: Yeah, I have fields named 'toilet' all the time :P

21:59

<nikolaj_a>

A bit like calling your exception variables for 'up';

22:00

<nikolaj_a>

And now I'n beginning to end my sentences with ; instead of. which means it's time to go home :P

22:15

<[pwgr]>

nikolaj_a: haha yeah ive written a lot of buffering and caching code containing statements like "if (dirty) flush();

Drone v1.4 © 2002-2005 Uwyn RIFE powered